-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
USI Sounding Rocket parts not recognized for Destroyed Vessel #513
Comments
I can take a look into this, but I'll need some more detail, as the vessel destroyed stuff checks for lots of different conditions. The (typically) sure-fire way to get it to fire is to make sure the probe core is destroyed. I'm assuming with the sounding rocket there isn't one? Can you describe how the vessel is getting destroyed (impacting terrain vs water, how hard its hitting) and provide a KSP.log covering the desctruction of the vessel? |
USI only has one probe core. The test is total destruction falling from 2100m. I'll get a log shortly. |
Ok so I tested using this Sounding Rocket made from USI Sounding Rockets mod: http://www.mediafire.com/download/jbff03tc86cf227/Sounding_Rocket.craft using this contract: https://github.com/inigmatus/ContractPack-SoundingRockets/blob/master/Core/KSP-SR-2000m.cfg Issue: Launched it, did not deploy parachute intentionally, and let it crash to the ground, resulting in total destruction of vehicle, all parts. The VesselNotDestroyed parameter is not triggering a contract failure.
|
Okay, VesselNotDestroyed has had a fair bit of improvements, but it didn't work in all tests for your contract. The problem is that your VesselParameterGroup can un-assign the vessel right before it's destroyed (for example, if the avionics is knocked loose and then destroyed). I'd suggest moving the "reach 2000m" bit into the same VPG and setting it to disableOnStateChange = true (once they hit 2000m with a valid vessel they must either pass or fail the contract). |
Thanks. Setting VPG definition to disableOnStateChange = true resolved it in the latest dev build. unrelated: latest dev build apparently duplicates CC contract offerings now. |
Could you raise a new issue with more specifics and I'll take a look
|
Unable to get a qualifying Sounding Rocket to trigger Vessel Destruction contract failure:
https://github.com/inigmatus/ContractPack-SoundingRockets/blob/master/Core/KSP-SR-2500m.cfg
The text was updated successfully, but these errors were encountered: