Project

General

Profile

Bug #6768

Station One vehicles cannot be launched

Added by Zwolf over 8 years ago. Updated almost 8 years ago.

Status:
Needs Clarification
Severity:
Low
Assignee:
-
Category:
Gameplay
Target version:
-
Start date:
01/23/2016
% Done:

0%

Version:
Platform:
Windows
Expansion:
Language:
English (US)
Mod Related:
No
Votes:
Arrow u r green
Arrow d r red

Description

It seems that the parts in use may have changed significantly since the 'Station One' scenario was created, and as such I am unable to fly any of the pre-built craft in this scenario.

After hitting the launch button, all of the buttons in upper right become grayed out and even the escape key no longer works. At this point I've just had to close KSP using Windows.

The vehicles already in orbit appear to be working correctly but when launching from the Space Center I get the same console message saying
"Could not find a part of the path C: (...) Kerbal Space Program\thumbs\scenarios\Space Station 1_VAB-Auto-Saved Ship.png"
This message appear on all the pre-built vehicles I tested, not just the auto-saved one

The vehicles already docked at Station One can be docked/undocked/piloted normally, this issue appears to related only to loading vehicles in prep for launch.

2016-01-23_00005.jpg (480 KB) 2016-01-23_00005.jpg [email protected] Zwolf, 01/23/2016 08:50 AM
2016-01-23_00006.jpg (461 KB) 2016-01-23_00006.jpg [email protected] Zwolf, 01/23/2016 09:13 AM
KSP.log (198 KB) KSP.log [email protected] Zwolf, 01/23/2016 09:21 AM
output_log.txt (476 KB) output_log.txt [email protected] Zwolf, 01/23/2016 09:25 AM
10647
10648

History

#1 Updated by Kasuha over 8 years ago

I tested it and I can confirm it freezes with similar exception when I try to deploy a ship from VAB even though I have the game installed at different path where it can't have problems with access rights.

The scenario is old, for instance Kerbal XX ship near Duna still has oxidizer in its tank although its only engine is LV-N. Also the orbital station has some parts that don't quite match parts attached to them since they were resized in 1.0. It's unclear what the scenario goal is and access to VAB/SPH itself might be a bug in scenario settings.

I guess it awaits major revision.

#2 Updated by TriggerAu almost 8 years ago

  • Status changed from New to Needs Clarification

Also available in: Atom PDF