Run test button a no-op when two contracts for that part are active

[quyxkh]

KSP Version: Kerbal Space Program - 1.0.5.1028 (WindowsPlayer) Steam
What Happens: The "Run Test" button on the heat shield is a no-op
Mods / Add-Ons: none

Steps to Replicate: load the included save. Run test on the heatshield. Quickload. Run test on the heatshield.

Result: The persistent state works. The quicksaved state doesn't.

Fixes/Workarounds: Edit out the other contract for heat shield testing.

Other Notes/Pictures/Log Files: [URL="https://drive.google.com/file/d/0B3BGQdoSFUWMaUR2YW5PSW1jX0U/view?usp=sharing"]KSP.log, saves/heatshield*/*[/URL]

Paste of output_log.txt:

[CODE]Initialize engine version: 4.6.4f1 (99f88340878d)
GfxDevice: creating device client; threaded=1
Direct3D:
Version: Direct3D 9.0c [aticfx32.dll 8.17.10.1404]
Renderer: AMD Radeon HD 6900 Series
Vendor: ATI
VRAM: 2032 MB (via DXGI)
Caps: Shader=30 DepthRT=1 NativeDepth=1 NativeShadow=1 DF16=1 INTZ=1 RAWZ=0 NULL=1 RESZ=1 SlowINTZ=1
Begin MonoManager ReloadAssembly
Platform assembly: E:\Steam\steamapps\common\Kerbal Space Program\Launcher_Data\Managed\UnityEngine.dll (this message is harmless)
Loading E:\Steam\steamapps\common\Kerbal Space Program\Launcher_Data\Managed\UnityEngine.dll into Unity Child Domain
Platform assembly: E:\Steam\steamapps\common\Kerbal Space Program\Launcher_Data\Managed\Assembly-CSharp-firstpass.dll (this message is harmless)
Loading E:\Steam\steamapps\common\Kerbal Space Program\Launcher_Data\Managed\Assembly-CSharp-firstpass.dll into Unity Child Domain
Platform assembly: E:\Steam\steamapps\common\Kerbal Space Program\Launcher_Data\Managed\Assembly-CSharp.dll (this message is harmless)
Loading E:\Steam\steamapps\common\Kerbal Space Program\Launcher_Data\Managed\Assembly-CSharp.dll into Unity Child Domain
Platform assembly: E:\Steam\steamapps\common\Kerbal Space Program\Launcher_Data\Managed\UnityEngine.UI.dll (this message is harmless)
Loading E:\Steam\steamapps\common\Kerbal Space Program\Launcher_Data\Managed\UnityEngine.UI.dll into Unity Child Domain
Platform assembly: E:\Steam\steamapps\common\Kerbal Space Program\Launcher_Data\Managed\ICSharpCode.SharpZipLib.dll (this message is harmless)
Loading E:\Steam\steamapps\common\Kerbal Space Program\Launcher_Data\Managed\ICSharpCode.SharpZipLib.dll into Unity Child Domain
- Completed reload, in 0.208 seconds
<RI> Initializing input.

<RI> Input initialized.

desktop: 1920x1080 60Hz; virtual: 1920x1080 at 0,0
Platform assembly: E:\Steam\steamapps\common\Kerbal Space Program\Launcher_Data\Managed\System.Core.dll (this message is harmless)
Platform assembly: E:\Steam\steamapps\common\Kerbal Space Program\Launcher_Data\Managed\System.dll (this message is harmless)
Platform assembly: E:\Steam\steamapps\common\Kerbal Space Program\Launcher_Data\Managed\System.Xml.dll (this message is harmless)
Platform assembly: E:\Steam\steamapps\common\Kerbal Space Program\Launcher_Data\Managed\Mono.Security.dll (this message is harmless)
Local BuildID: 1028

(Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56)

Backup file overwritten

(Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56)

Allowed Start game

(Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56)

Windows 8.1 (6.3.10586) 64bit

(Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56)

ExecPath = E:/Steam/steamapps/common/Kerbal Space Program/Launcher_Data\../KSP.exe

(Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56)

Loading Settings...

(Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56)

Arguments:

(Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56)

Stats sent. Value: DISABLED

(Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56)[/CODE] Edited November 26, 2015 by quyxkh
Added output_log.txt paste

[sal_vager]

Sorry quyxkh but I cannot reproduce this with the save and steps you provided, the "run test" button is available again after I quickload.

Also, there is only one contract to test the heat shield in the save files.

Maybe some one else can reproduce this and figure out what you are seeing.

[quyxkh]

Just to be sure: did you try clicking that button? I start the game, hit fly, hold F9, click the run test button, it stays there and does nothing.

I just downloaded the archive, extracted it into a completely new install, tried it, it happens.

I see the two contracts are for different heat shields, but after quickload and recover, they're both in mission control. Edited November 27, 2015 by quyxkh
re two contracts

[sal_vager]

Sorry for the delay in answering this, forum move and all that.

 

Yes I clicked the button after saving then again after reloading the quicksave, but I'm not seeing the issue you mention.

 

What I do see is one heatshield contract in the persistent.sfs (the file I first looked at) and two heatshield contracts in the quicksave, one to test a 1.25m heatshield at 43km to 53km and between 1,940m/s and 2,360m/s, the other contract is to test a 2.5m heatshield while landed, this is two different contracts for two different parts.

 

But you only have a single 1.25m heatshield on your craft.

 

So running the test on the launchpad will result in no activity because it's the wrong heatshield.

 

Also, your craft is incapable of achieving the required speed and altitude for the 1.25m heatshield contract, so in neither case would I expect the "run test" button to actually have an effect.

 

What is interesting here is the lack of a prototype 2.5m heatshield which is usually provided for any test contract when the player doesn't already have that part, and you have a prototype 1.25m heatshield despite having already researched it, but without knowing more about the history of this save and what occurred when the contracts were accepted there's not really anything to point to a cause or solution.

 

Researching the "Landing" node to get the 2.5m heatshield allows me to complete that contract, as for the other all I can suggest is moar boosters!

 

 

[quyxkh]

Okay, thanks loads for the detailed response.  While trying to understand how I'd missed something _that_ fundamental I discovered that when I launch KSP via Steam, the save doesn't show up on the resume list. That jogged my memory.

That's what happened the first time, and me thinking it was because it was failing some check, I'd noticed I'd deleted the heatshield1 contract and left a heatshield2 contract. . Thinking that was a serial number sequence it didn't like, I changed them to ones and relaunched KSP . . . from my desktop KSP.exe icon (I set it to grab ctrl-alt-K) .  Now the save showed up, reinforcing my serial-number belief, and I saw the 1.25 contract working in persistent and not working in quicksaved without noticing the conditions had switched.

Why Steam won't show the save I don't know.  I tried renaming the directory to have no spaces, and changing the internal title to match, that didn't do it.  This steam/.exe difference I don't care about, I only mention it because of the part it played here.  Thanks again for the really excellent response.