[1.10.1+] Contract Configurator [v1.30.5] [2020-10-05]

[nightingale]

I run tests and figured out it was caused by something related to part unlocking. Certain modded tech tree nodes cause CC to stop working properly upon being unlocked, but only if they contain certain part as far as I can figure out.

This is a method for replicating the bug:

-A fresh install of KSP 0.9

-Install mods

-Contract Configurator 0.7.0 -Initial Contracts 1.0 (some contracts to do)

-ADIOS techtree 1.5 (a modded tech tree)

-Start a new carrer game with default parameters

-TechManager will pop up asking which tech tree to use

-For debugging purposes use the No Cost tree to unlock node freely

-In mission control take some contract (reach 18km is the easiest one)

-Unlock tech tree nodes. not all nodes trigger the bug, but in the ADIOS tech tree, the "miniaturized thrusters" node causes it, maybe other nodes as well.

-Launch a rocket and make it climb to 18km

Before unlocking tech nodes the contract will be completed instantly upon reaching the indicated height, however when unlocking certain nodes, like the one I indicated above the contract objective will not be completed. In the reach 18 km contract it will show as uncompleted even if you are flying over 18 km of height.

Here is a log from the game when the bug happened, take a look at the bottom, I think thats where the error is

http://pastebin.com/djZmDhKx

Thanks.

Funny thing is, based on that log you should be able to reproduce without Contract Configurator at all:

[EXC 14:28:25.966] InvalidOperationException: Operation is not valid due to the current state of the object
        System.Linq.Enumerable.First[RDTech] (IEnumerable`1 source, System.Func`2 predicate, Fallback fallback)
        System.Linq.Enumerable.First[RDTech] (IEnumerable`1 source, System.Func`2 predicate)
        Contracts.Templates.PartTest.Generate ()
        Contracts.Contract.Generate (System.Type contractType, ContractPrestige difficulty, Int32 seed, State state)
        Contracts.ContractSystem.GenerateContract (Int32 seed, ContractPrestige difficulty, System.Type contractType)
        Contracts.ContractSystem.GenerateContract (System.Int32& seed, ContractPrestige difficulty)
        Contracts.ContractSystem.GenerateContracts (System.Int32& seed, ContractPrestige difficulty, Int32 count)
        Contracts.ContractSystem.RefreshContracts ()
        Contracts.ContractSystem+.MoveNext ()

What's happening is that the stock Part Test contract is failing, and bringing the whole contract system down with it. From what little I know of the tech tree stuff, what appears to happen is:

1. The contract chooses a random part to test that has the ModuleTestSubject part module and is either researched in the next set of nodes that can be researched.
   
2. It looks for it in the tech tree (pretty sure that's what it's doing when it fails).
   

That's all I can gather - your best bet is to head over to TechManager to continue the discussion there. You may have some luck identifying the specific part causing the trouble by looking at the parts in the node(s) that are opened after you research the node that causes problems - best guess is that it's something about the tech assignment of one of those parts that is causing the problem.

Good luck.

[klefenz]

What's happening is that the stock Part Test contract is failing, and bringing the whole contract system down with it. From what little I know of the tech tree stuff, what appears to happen is:

1. The contract chooses a random part to test that has the ModuleTestSubject part module and is either researched in the next set of nodes that can be researched.
   
2. It looks for it in the tech tree (pretty sure that's what it's doing when it fails).
   

That's all I can gather - your best bet is to head over to TechManager to continue the discussion there. You may have some luck identifying the specific part causing the trouble by looking at the parts in the node(s) that are opened after you research the node that causes problems - best guess is that it's something about the tech assignment of one of those parts that is causing the problem.

Good luck.

Oh, OK, I didnt try any vanilla contracts with these new tech trees, so its not your mod then.

Thank you very much.

[Robotengineer]

Would anyone be interested in having an in-game GUI for making contracts? Or has this already been tried?

Edited March 20, 2015 by Robotengineer
Terrible typos.

[nightingale]

Would anyone want interested in having an in-game GUI for making contracts? Or has this already been tried?

I get requests for it every now and then, so there's probably some interest out there. It's a pretty big task, and there's not enough value in it for me personally. As such, I have no intention of building it, but if someone else does want to, I will support their efforts (ie. explaining how/why stuff works a certain way in Contract Configurator, adding code hooks in where appropriate).

[DirtyFace83]

If the effort were to be made, I would rather it be an out-of-game editor. Dunno. Just makes morre sense to me that way.

EDIT: Unless you mean to make contracts on the fly?

[nightingale]

If the effort were to be made, I would rather it be an out-of-game editor. Dunno. Just makes morre sense to me that way.

EDIT: Unless you mean to make contracts on the fly?

That would be one of the main differences. It would also be might be more difficult for someone to link in the actual Contract Configurator dlls (for the purpose of mining the list of valid parameters, etc. directly from the source).

[linuxgurugamer]

Nightingale,

I'm running 0.70, the following parameter isn't working while all others are fulfilled:

PARAMETER

{

name = VesselDestroyed5701

type = VesselDestroyed

mustImpactTerrain = true

completeInSequence = true

}

There is actually only one other parameter, which is that crew=0

I've watched it impact, both in normal time and accelerated time.

It never says in the contract window that the vessel is destroyed, although KSP itself knows.

Edit: I tried commenting out the completeInSequence, but it still didn't work

Edited March 20, 2015 by linuxgurugamer

[nightingale]

Nightingale,

I'm running 0.70, the following parameter isn't working while all others are fulfilled:

PARAMETER

{

name = VesselDestroyed5701

type = VesselDestroyed

mustImpactTerrain = true

completeInSequence = true

}

There is actually only one other parameter, which is that crew=0

I've watched it impact, both in normal time and accelerated time.

It never says in the contract window that the vessel is destroyed, although KSP itself knows.

Edit: I tried commenting out the completeInSequence, but it still didn't work

Just for kicks, let's see what happens if you turn off mustImpactTerrain. Either way, can you turn on VERBOSE logging for type=VesselDestroyed and provide the KSP.log?

[linuxgurugamer]

Just for kicks, let's see what happens if you turn off mustImpactTerrain. Either way, can you turn on VERBOSE logging for type=VesselDestroyed and provide the KSP.log?

did that, no change

Log file located here:

https://drive.google.com/file/d/0Bzid7e3pW1k7OVFtRzAtMmswZGM/view?usp=sharing

Thanks

[nightingale]

Your log shows a ton of stuff being destroyed, and supposedly meeting the parameter. Can you send me the contract so I can test myself? If it's as simple as you say it is, I can't see why it's not working. Maybe a screenshot of the crash before destruction. Maybe the root part isn't being destroyed and that's what matters?

[LOG 18:02:22.821] [noseCone]: Deactivated
[LOG 18:02:22.824] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: OnVesselAboutToBeDestroyed: EventReport
[LOG 18:02:22.824] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: SetState to Complete for vessel 30ec69c4-2113-4b1e-b3f6-e2f0184bebdf
[LOG 18:02:22.824] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: -> CheckVessel(30ec69c4-2113-4b1e-b3f6-e2f0184bebdf)
[LOG 18:02:22.825] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: <- CheckVessel
[LOG 18:02:22.825] [00:00:54]: Aerodynamic Nose Cone collided into RT-10 Solid Fuel Booster.
[LOG 18:02:22.825] solidBooster collided into solidBooster - relative velocity: 13.08964 - impact momentum: 26.3
[LOG 18:02:22.825] [Explosion] Combined.
[LOG 18:02:22.825] solidBooster Exploded!! - blast awesomeness: 0.5
[LOG 18:02:22.827] [solidBooster]: Deactivated
[LOG 18:02:22.829] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: OnVesselAboutToBeDestroyed: EventReport
[LOG 18:02:22.829] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: SetState to Complete for vessel 8ec29c96-33f9-4cb4-b938-7c4f336d57fa
[LOG 18:02:22.829] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: -> CheckVessel(8ec29c96-33f9-4cb4-b938-7c4f336d57fa)
[LOG 18:02:22.829] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: <- CheckVessel
[LOG 18:02:22.829] [00:00:54]: RT-10 Solid Fuel Booster collided into RT-10 Solid Fuel Booster.
[LOG 18:02:22.829] noseCone collided into solidBooster - relative velocity: 14.41263 - impact momentum: 29.0
[LOG 18:02:22.829] [Explosion] Combined.
[LOG 18:02:22.829] noseCone Exploded!! - blast awesomeness: 0.5
[LOG 18:02:22.829] [noseCone]: Deactivated
[LOG 18:02:22.830] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: OnVesselAboutToBeDestroyed: EventReport
[LOG 18:02:22.830] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: SetState to Complete for vessel 5ede63a5-e4e3-433d-98d7-0de6ac17d274
[LOG 18:02:22.830] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: -> CheckVessel(5ede63a5-e4e3-433d-98d7-0de6ac17d274)
[LOG 18:02:22.830] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: <- CheckVessel
[LOG 18:02:22.830] [00:00:54]: Aerodynamic Nose Cone collided into RT-10 Solid Fuel Booster.
[LOG 18:02:22.830] radialDecoupler collided into solidBooster - relative velocity: 13.46204 - impact momentum: 27.1
[LOG 18:02:22.830] [Explosion] Combined.
[LOG 18:02:22.830] radialDecoupler Exploded!! - blast awesomeness: 0.5
[LOG 18:02:22.832] [radialDecoupler]: Deactivated
[LOG 18:02:22.837] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: OnVesselAboutToBeDestroyed: EventReport
[LOG 18:02:22.837] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: SetState to Complete for vessel 137d8f90-7098-4a5e-8487-eff2265edafb
[LOG 18:02:22.837] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: -> CheckVessel(137d8f90-7098-4a5e-8487-eff2265edafb)
[LOG 18:02:22.837] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: <- CheckVessel
[LOG 18:02:22.837] [00:00:54]: TT-38K Radial Decoupler collided into RT-10 Solid Fuel Booster.
[LOG 18:02:22.844] 1 explosions created.
[LOG 18:02:22.858] radialDecoupler collided into solidBooster - relative velocity: 13.683 - impact momentum: 27.5
[LOG 18:02:22.858] radialDecoupler Exploded!! - blast awesomeness: 0.5
[LOG 18:02:22.861] [radialDecoupler]: Deactivated
[LOG 18:02:22.862] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: OnVesselAboutToBeDestroyed: EventReport
[LOG 18:02:22.862] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: SetState to Complete for vessel 0e5532d6-319b-42e1-b92c-d348383255e0
[LOG 18:02:22.862] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: -> CheckVessel(0e5532d6-319b-42e1-b92c-d348383255e0)
[LOG 18:02:22.862] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: <- CheckVessel
[LOG 18:02:22.862] [00:00:55]: TT-38K Radial Decoupler collided into RT-10 Solid Fuel Booster.
[LOG 18:02:22.862] solidBooster collided into solidBooster - relative velocity: 13.94195 - impact momentum: 28.0
[LOG 18:02:22.862] [Explosion] Combined.
[LOG 18:02:22.862] solidBooster Exploded!! - blast awesomeness: 0.5
[LOG 18:02:22.863] [solidBooster]: Deactivated
[LOG 18:02:22.863] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: OnVesselAboutToBeDestroyed: EventReport
[LOG 18:02:22.863] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: SetState to Complete for vessel 30ec69c4-2113-4b1e-b3f6-e2f0184bebdf
[LOG 18:02:22.863] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: -> CheckVessel(30ec69c4-2113-4b1e-b3f6-e2f0184bebdf)
[LOG 18:02:22.863] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: <- CheckVessel
[LOG 18:02:22.863] [00:00:55]: RT-10 Solid Fuel Booster collided into RT-10 Solid Fuel Booster.
[LOG 18:02:22.866] radialDecoupler collided into solidBooster - relative velocity: 10.09878 - impact momentum: 20.3
[LOG 18:02:22.866] [Explosion] Combined.
[LOG 18:02:22.866] radialDecoupler Exploded!! - blast awesomeness: 0.5
[LOG 18:02:22.866] [radialDecoupler]: Deactivated
[LOG 18:02:22.866] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: OnVesselAboutToBeDestroyed: EventReport
[LOG 18:02:22.866] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: SetState to Complete for vessel 8ec29c96-33f9-4cb4-b938-7c4f336d57fa
[LOG 18:02:22.866] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: -> CheckVessel(8ec29c96-33f9-4cb4-b938-7c4f336d57fa)
[LOG 18:02:22.866] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: <- CheckVessel
[LOG 18:02:22.866] [00:00:55]: TT-38K Radial Decoupler collided into RT-10 Solid Fuel Booster.
[LOG 18:02:22.868] 1 explosions created.
[LOG 18:02:32.004] Untitled Space Craft Debris Unloaded
[LOG 18:02:32.005] Packing Untitled Space Craft Debris for orbit
[WRN 18:02:32.023] BackgroundProcessing: Ran out of modules before finding module ModuleAeroReentry
[WRN 18:02:32.023] BackgroundProcessing: Ran out of modules before finding module FARBasicDragModel
[WRN 18:02:32.023] BackgroundProcessing: Ran out of modules before finding module FARBasicDragModel
[WRN 18:02:32.023] BackgroundProcessing: Ran out of modules before finding module ModuleAeroReentry
[WRN 18:02:32.023] BackgroundProcessing: Ran out of modules before finding module FARBasicDragModel
[WRN 18:02:33.540] Vessel Untitled Space Craft Debris crashed through terrain on the Mun
[LOG 18:02:36.293] Untitled Space Craft Debris Unloaded
[LOG 18:02:36.294] Packing Untitled Space Craft Debris for orbit
[WRN 18:02:36.305] BackgroundProcessing: Ran out of modules before finding module ModuleAeroReentry
[WRN 18:02:36.305] BackgroundProcessing: Ran out of modules before finding module FARBasicDragModel
[WRN 18:02:36.305] BackgroundProcessing: Ran out of modules before finding module FARBasicDragModel
[WRN 18:02:36.848] Vessel Untitled Space Craft Debris crashed through terrain on the Mun
[LOG 18:02:42.581] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: OnVesselAboutToBeDestroyed: EventReport
[LOG 18:02:42.581] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: SetState to Complete for vessel 30ec69c4-2113-4b1e-b3f6-e2f0184bebdf
[LOG 18:02:42.581] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: -> CheckVessel(30ec69c4-2113-4b1e-b3f6-e2f0184bebdf)
[LOG 18:02:42.581] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: <- CheckVessel
[LOG 18:02:42.581] [00:01:14]: TT-38K Radial Decoupler collided into the surface.
[LOG 18:02:42.581] radialDecoupler Exploded!! - blast awesomeness: 0.5
[LOG 18:02:42.582] [radialDecoupler]: Deactivated
[LOG 18:02:42.587] 1 explosions created.
[LOG 18:02:42.677] activating stage 0 - current stage: 1
[LOG 18:02:42.678] [probeCoreSphere]: Activated
[LOG 18:02:42.678] [fuelTank.long]: Activated
[LOG 18:02:42.678] [batteryPack]: Activated
[LOG 18:02:42.678] [batteryPack]: Activated
[LOG 18:02:42.678] [NP.sas.125m]: Activated
[LOG 18:02:42.678] [fuelTank.long]: Activated
[LOG 18:02:42.678] [KW1mengineWildCatV]: Activated
[LOG 18:02:42.678] [solarPanels2]: Activated
[LOG 18:02:42.678] [solarPanels2]: Activated
[LOG 18:02:42.678] [solarPanels2]: Activated
[LOG 18:02:42.678] [solarPanels2]: Activated
[WRN 18:02:47.788] Vessel Untitled Space Craft Debris crashed through terrain on the Mun
[LOG 18:02:56.222] probeCoreSphere collided into Xn213113 - relative velocity: 145.6395 - no impact momentum (no RB)
[LOG 18:02:56.222] probeCoreSphere Exploded!! - blast awesomeness: 0
[LOG 18:02:56.227] [probeCoreSphere]: Deactivated
[LOG 18:02:56.237] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: OnVesselAboutToBeDestroyed: EventReport
[LOG 18:02:56.237] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: SetState to Complete for vessel 0deecb8c-b35a-494b-a151-3073093f1376
[LOG 18:02:56.237] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: -> CheckVessel(0deecb8c-b35a-494b-a151-3073093f1376)
[LOG 18:02:56.237] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: SetState to Complete for vessel 0deecb8c-b35a-494b-a151-3073093f1376
[LOG 18:02:56.237] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: <- CheckVessel
[LOG 18:02:56.238] [00:01:27]: Stayputnik Mk. 1 crashed into terrain.
[LOG 18:02:56.238] [00:01:27]: Structural failure on linkage between SP-L 1x6 Photovoltaic Panels and FL-T800 Fuel Tank.
[LOG 18:02:56.247] 1 explosions created.
[LOG 18:02:56.255] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: OnVesselAboutToBeDestroyed: EventReport
[LOG 18:02:56.255] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: SetState to Complete for vessel d8058418-15b5-4246-a8d9-1d013ae2b553
[LOG 18:02:56.255] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: -> CheckVessel(d8058418-15b5-4246-a8d9-1d013ae2b553)
[LOG 18:02:56.255] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: <- CheckVessel
[LOG 18:02:56.255] [00:01:27]: SP-L 1x6 Photovoltaic Panels collided into the surface.
[LOG 18:02:56.255] solarPanels2 Exploded!! - blast awesomeness: 0.5
[LOG 18:02:56.255] [solarPanels2]: Deactivated
[LOG 18:02:56.256] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: OnVesselAboutToBeDestroyed: EventReport
[LOG 18:02:56.256] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: SetState to Complete for vessel 4cbea31d-3a75-41fa-9c68-978b696b69d4
[LOG 18:02:56.256] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: -> CheckVessel(4cbea31d-3a75-41fa-9c68-978b696b69d4)
[LOG 18:02:56.256] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: <- CheckVessel
[LOG 18:02:56.256] [Explosion] Combined.
[LOG 18:02:56.256] solarPanels2 Exploded!! - blast awesomeness: 0.5
[LOG 18:02:56.256] [solarPanels2]: Deactivated
[LOG 18:02:56.256] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: OnVesselAboutToBeDestroyed: EventReport
[LOG 18:02:56.256] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: SetState to Complete for vessel 1cb5287c-c897-4da1-acf9-b3127c4ea59a
[LOG 18:02:56.256] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: -> CheckVessel(1cb5287c-c897-4da1-acf9-b3127c4ea59a)
[LOG 18:02:56.256] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: <- CheckVessel
[LOG 18:02:56.256] [Explosion] Combined.
[LOG 18:02:56.256] solarPanels2 Exploded!! - blast awesomeness: 0.5
[LOG 18:02:56.256] [solarPanels2]: Deactivated
[LOG 18:02:56.257] fuelTank.long collided into Xn213113 - relative velocity: 129.9674 - no impact momentum (no RB)
[LOG 18:02:56.257] [Explosion] Combined.
[LOG 18:02:56.257] fuelTank.long Exploded!! - blast awesomeness: 0.5
[LOG 18:02:56.257] [batteryPack]: Deactivated
[LOG 18:02:56.417] [batteryPack]: Deactivated
[LOG 18:02:56.430] [fuelTank.long]: Deactivated
[LOG 18:02:56.432] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: OnVesselAboutToBeDestroyed: EventReport
[LOG 18:02:56.432] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: SetState to Complete for vessel f9873201-444f-4dd9-a6ea-6950f6f30979
[LOG 18:02:56.432] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: -> CheckVessel(f9873201-444f-4dd9-a6ea-6950f6f30979)
[LOG 18:02:56.432] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: <- CheckVessel
[LOG 18:02:56.432] [00:01:27]: FL-T800 Fuel Tank crashed into terrain.
[LOG 18:02:56.433] [00:01:27]: Structural failure on linkage between FL-T800 Fuel Tank and MPM-125 Reaction Wheel Module.
[LOG 18:02:56.455] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: OnVesselAboutToBeDestroyed: EventReport
[LOG 18:02:56.455] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: SetState to Complete for vessel d258308a-ebc8-4ca2-9c6a-ea176b206686
[LOG 18:02:56.456] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: -> CheckVessel(d258308a-ebc8-4ca2-9c6a-ea176b206686)
[LOG 18:02:56.456] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: <- CheckVessel
[LOG 18:02:56.456] [00:01:27]: SP-L 1x6 Photovoltaic Panels collided into the surface.
[LOG 18:02:56.456] [Explosion] Combined.
[LOG 18:02:56.456] solarPanels2 Exploded!! - blast awesomeness: 0.5
[LOG 18:02:56.456] [solarPanels2]: Deactivated
[LOG 18:02:56.458] fuelTank.long collided into Xn213113 - relative velocity: 115.1033 - no impact momentum (no RB)
[LOG 18:02:56.458] [Explosion] Combined.
[LOG 18:02:56.458] fuelTank.long Exploded!! - blast awesomeness: 0.5
[LOG 18:02:56.468] [fuelTank.long]: Deactivated
[LOG 18:02:56.469] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: OnVesselAboutToBeDestroyed: EventReport
[LOG 18:02:56.469] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: SetState to Complete for vessel efa05c45-55a6-47cb-930a-2750527b2999
[LOG 18:02:56.469] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: -> CheckVessel(efa05c45-55a6-47cb-930a-2750527b2999)
[LOG 18:02:56.470] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: <- CheckVessel
[LOG 18:02:56.470] [00:01:27]: FL-T800 Fuel Tank crashed into terrain.
[LOG 18:02:56.482] 1 explosions created.
[LOG 18:02:56.555] KW1mengineWildCatV collided into Xn213113 - relative velocity: 43.60037 - no impact momentum (no RB)
[LOG 18:02:56.555] KW1mengineWildCatV Exploded!! - blast awesomeness: 0.5
[LOG 18:02:56.555] [KW1mengineWildCatV]: Deactivated
[LOG 18:02:56.558] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: OnVesselAboutToBeDestroyed: EventReport
[LOG 18:02:56.558] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: SetState to Complete for vessel 589515a1-8e42-4406-b191-0be5829643f3
[LOG 18:02:56.558] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: -> CheckVessel(589515a1-8e42-4406-b191-0be5829643f3)
[LOG 18:02:56.558] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: <- CheckVessel
[LOG 18:02:56.559] [00:01:27]: KW Rocketry WildCat-V crashed into terrain.
[LOG 18:02:56.567] 1 explosions created.
[WRN 18:02:58.991] [FlightPersistence]: Vessel Untitled Space Craft not saved because it was dead.

[LOG 18:02:22.819] noseCone collided into solidBooster - relative velocity: 14.1073 - impact momentum: 28.4[LOG 18:02:22.820] noseCone Exploded!! - blast awesomeness: 0.5

[linuxgurugamer]

Here is the contract:

CONTRACT_TYPE

{

name = FirstMunImpact

group = SpaceTuxGroup

title = Crash a probe on Mun!

description = We want to get larger, clearer closeup pictures. To do this, we need to send a probe to crash on Mun.

This will be a monumental achievement.

notes = Complete the following:

synopsis = Launch an unmanned probe and have it crash onto the Mun

completedMessage = Future generations will remember this day.

agent = Space Penguins, Inc

// agent = Research & Development Department

minExpiry = 50.0

maxExpiry = 100.0

// Contract deadline in days. Default is no deadline.

deadline = 100

cancellable = true

declinable = true

prestige = Significant

targetBody = Mun

maxCompletions = 1

maxSimultaneous = 1

rewardScience = 25.0

rewardReputation = 10.0

rewardFunds = Random(18000.0, 22000.0)

advanceFunds = Random(9000.0, 11000.0)

weight = 910.0

REQUIREMENT

{

name = ReachSpace5702

type = ReachSpace

}

// If we've landed, then no need to crash a probe into it

REQUIREMENT

{

name = Nolanding5702

type = Landing

targetBody = Mun

invertRequirement = true

}

PARAMETER

{

name = VPG5702

type = VesselParameterGroup

PARAMETER

{

name = HasCrew5702

type = HasCrew

maxCrew = 0

minCrew = 0

}

PARAMETER

{

name = VesselDestroyed5701

type = VesselDestroyed

// mustImpactTerrain = true

// completeInSequence = true

}

}

}

- - - Updated - - -

I don't have time to get screenshots right now.

I'll be back tomorrow, if you still need it, just post and I'll do it then.

[nightingale]

Okay, ran some tests, the parameter seems to only get triggered if I smash the root part. If I go up off the launch pad a bit and come down and blow most of everything up, it's not quite good enough. If I got up and flip the rocket a bit and smash the root part, then it registers. Not sure if there's much I can do... what was your test scenario? Were you really smashing it, or just doing an up and down test?

[linuxgurugamer]

Okay, ran some tests, the parameter seems to only get triggered if I smash the root part. If I go up off the launch pad a bit and come down and blow most of everything up, it's not quite good enough. If I got up and flip the rocket a bit and smash the root part, then it registers. Not sure if there's much I can do... what was your test scenario? Were you really smashing it, or just doing an up and down test?

Interesting. Are there any parts not destroyed in the log I sent you?

I tried several things. I first noticed it when testing the waypoints, then I tried using hyperedit and just flying it into the ground (hyperd to 7300, then killed orbital speed and accelerated to the ground).

It's a fairly simple ship, a stayputnick, ft-800 tanks, 4 srb, batteries & solar.

There doesn't seem to be any parts undestroyed after I crash it.

Here is a link to the craft file:

https://drive.google.com/file/d/0Bzid7e3pW1k7ckpCTThwZUg0ZVk/view?usp=sharing

Hope it helps.

Thanks

[nightingale]

Contract Configurator 0.7.1 is out! Download it now!

New contract pack coming within the next hour.

Contract Configurator 0.7.1

• Better support for spawning landed Kerbals in SpawnKerbal.
  
• SpawnKerbal now supports PQS offsets.
  
• HasCrew improvements: moved to delegate system, add support for requiring a specific Kerbal.
  
• Added support for Duration datatype in expressions.
  
• Expression support for SpawnKerbal and WaypointGenerator behaviours.
  
• Improvements to location debug window.
  
• Support for notes in most contract parameters.
  
• Weight in contract types now only applies within a contract group, and all contract groups are given equal preference. This means that one contract group (or contract pack) can't cause contract starvation in another group.
  
• Fix NullReferenceException when using TextGen without an agent specified (thanks AppoloFunghi).
  
• Fix broken completeInSequence attribute.
  
• Minor bug fixes.
  

- - - Updated - - -

linuxgurugamer - give 0.7.1 a try. Since I wasn't able to reproduce on my dev version, maybe I inadvertently fixed the problem? If not, I'll try to reproduce again tomorrow with your .craft file and specific circumstances.

- - - Updated - - -

It's here, Space Tourism contract pack is live!

[severedsolo]

Thanks for 0.7.1 - I can now finally release an early version of my pack

I present: the Kerbal Space Station - http://forum.kerbalspaceprogram.com/threads/113642-WIP-Contract-Pack-Kerbin-Space-Station?p=1798024#post1798024

[khearn]

So, KSP-AVC is telling me that Contract Configurator 0.7.2 is available. Coming this close on the heels of 0.7.1, I'm guessing it's a hotfix for a significant issue. Any info for us?

I just installed the Tourism pack and am looking forward to giving it a spin, as soon as KSP finishes loading. With all the mods I have now, it takes 5-10 minutes to load everything. *sigh*

Thanks for all the great work on the configurator and the packs you've put out.

[nightingale]

So, KSP-AVC is telling me that Contract Configurator 0.7.2 is available. Coming this close on the heels of 0.7.1, I'm guessing it's a hotfix for a significant issue. Any info for us?

I just installed the Tourism pack and am looking forward to giving it a spin, as soon as KSP finishes loading. With all the mods I have now, it takes 5-10 minutes to load everything. *sigh*

Thanks for all the great work on the configurator and the packs you've put out.

Not sure what you're talking about, it says 0.7.2...

Yeah, I had just enough time to get the release out this morning before I had to leave, so I couldn't update the Contract Configurator thread properly. So, with that, Contract Configurator 0.7.2 is out! Download it here!

Contract Configurator 0.7.2

• Fix zero orbit period bug (thanks SpaceNomad).
  

- - - Updated - - -

Thanks for 0.7.1 - I can now finally release an early version of my pack

I present: the Kerbal Space Station - http://forum.kerbalspaceprogram.com/threads/113642-WIP-Contract-Pack-Kerbin-Space-Station?p=1798024#post1798024

Congrats on the release, this'll mesh well with the Tourism pack (it should offer contracts to bring tourists to visit the station). I'll update the first post with a link to your contract pack..

- - - Updated - - -

It's been a busy week or so for Contract Configurator contract packs! We've gone from four to nine contract packs listed on the first post. In case anyone's missed one of the new ones, here's the full listing as of right now:

[TABLE=class: grid]

[TR]

[TD]Name[/TD]

[TD]Description[/TD]

[TD]Author[/TD]

[TD]License[/TD]

[TD]Download(s)[/TD]

[/TR]

[TR]

[TD]Advanced Progression Contracts[/TD]

[TD]Contains a series of missions intended to add some more direction and depth to career mode.[/TD]

[TD]tjsnh[/TD]

[TD]CC-BY-NC-SA-4.0[/TD]

[TD]CKAN, KerbalStuff[/TD]

[/TR]

[TR]

[TD]Anomaly Surveyor[/TD]

[TD]Contracts to go search out the various Easter eggs that are included in KSP.[/TD]

[TD]nightingale[/TD]

[TD]CC-BY-NC-SA-4.0[/TD]

[TD]CKAN, GitHub[/TD]

[/TR]

[TR]

[TD]Banking[/TD]

[TD]Adds a bank to the game. The bank gives you money and after 2 weeks it takes it back with some interest.[/TD]

[TD]Arachnidek[/TD]

[TD]MIT[/TD]

[TD]CKAN, KerbalStuff[/TD]

[/TR]

[TR]

[TD]Kerbin Space Station[/TD]

[TD]Build a space station in Kerbin orbit over several contracts. Once it's up, get contracts to upgrade and maintain your station.[/TD]

[TD]severedsolo[/TD]

[TD]CC BY-SA 3.0[/TD]

[TD]GitHub[/TD]

[/TR]

[TR]

[TD]Initial Contracts[/TD]

[TD]InitialContracts replaces the buggy/annoying stock starting contracts with 3 similar ones, which can be completed by manned and unmanned craft. Thus the mods contracts are especially useful for TechTrees which start unmanned and may be redistributed with them.

If you like what you see, then check out SETI-BalanceMod for the full deal![/TD]

[TD]Yemo[/TD]

[TD]Give author credit (see post for details)[/TD]

[TD]CKAN, KerbalStuff[/TD]

[/TR]

[TR]

[TD]RemoteTech Contract Pack[/TD]

[TD]Contracts for setting up RemoteTech satellite networks and providing coverage to planets/moons.[/TD]

[TD]nightingale[/TD]

[TD]CC-BY-NC-SA-4.0[/TD]

[TD]CKAN, GitHub[/TD]

[/TR]

[TR]

[TD]Tourism[/TD]

[TD]Space tourism! Take tourists to space and to visit the stations and bases that you've already created. Build new tourist attractions like the space casino mega-project.[/TD]

[TD]nightingale[/TD]

[TD]CC-BY-NC-SA-4.0[/TD]

[TD]CKAN, GitHub[/TD]

[/TR]

[TR]

[TD]SCANsat Contract Pack[/TD]

[TD]Adds in SCANSat contracts. Currently has 11 missions for Kerbin, Mun, Minmus, Duna, Ike, Eve, Gilly, Moho, Dres, Jool's Moons and Eeloo included.[/TD]

[TD]DBT85[/TD]

[TD]CC-BY-NC-SA-4.0[/TD]

[TD]CKAN, GitHub[/TD]

[/TR]

[TR]

[TD]Spacetux - Unmanned Contracts[/TD]

[TD]A series of missions intended to add some more direction and depth to career mode.

It is recommended that you also install the Advanced Progression Contracts.[/TD]

[TD]linuxgurugamer[/TD]

[TD]CC-BY-NC-SA-4.0[/TD]

[TD]CKAN, KerbalStuff[/TD]

[/TR]

[/TABLE]

[Cocox]

Guys, does contract configurator have compatibility issues with other mods?

Some contracts behave oddly (don't show) when using Tarsier Space Tech, Mission Controller 2 and DMagic Orbital Science.

[nightingale]

Guys, does contract configurator have compatibility issues with other mods?

Some contracts behave oddly (don't show) when using Tarsier Space Tech, Mission Controller 2 and DMagic Orbital Science.

No incompatibilities that I'm aware of. If you're willing to do a little debugging, you can go to the Contract Configurator debug menu (alt-F10) and hit the "Force check requirements" button. Then expand the contract isn't showing up and have a look at the colors. If it's all green that it should be generating. Try cancelling other outstanding contracts of the same prestige level or hitting the clear all contracts buttons in the stock debug menu (alt-F12). Be careful in the stock debug menu, as it's fairly easy to accidentally clear all completed contracts as well, which can mess up contract progression (just have a quicksave handy to reload, just in case).

[linuxgurugamer]

Contract Configurator 0.7.1 is out! Download it now!

New contract pack coming within the next hour.

Contract Configurator 0.7.1

• Better support for spawning landed Kerbals in SpawnKerbal.
  
• SpawnKerbal now supports PQS offsets.
  
• HasCrew improvements: moved to delegate system, add support for requiring a specific Kerbal.
  
• Added support for Duration datatype in expressions.
  
• Expression support for SpawnKerbal and WaypointGenerator behaviours.
  
• Improvements to location debug window.
  
• Support for notes in most contract parameters.
  
• Weight in contract types now only applies within a contract group, and all contract groups are given equal preference. This means that one contract group (or contract pack) can't cause contract starvation in another group.
  
• Fix NullReferenceException when using TextGen without an agent specified (thanks AppoloFunghi).
  
• Fix broken completeInSequence attribute.
  
• Minor bug fixes.
  

- - - Updated - - -

linuxgurugamer - give 0.7.1 a try. Since I wasn't able to reproduce on my dev version, maybe I inadvertently fixed the problem? If not, I'll try to reproduce again tomorrow with your .craft file and specific circumstances.

- - - Updated - - -

It's here, Space Tourism contract pack is live!

Unfortunately, it didn't work, I tried it with 0.7.2

I also tried putting a decoupler on to seperate the Stayputnik, so that it would be the only part of the ship. Didn't work either

Edit: I also tried with just the Stayputnik, and used Hyperedit to put it in orbit and then kill the orbital velocity. Still didn't work.

This is on an OSX install. I'm going to reinstall KSP and then install the mods I need and will try again

Edit 2: I created a totally new install, installed the mods and my contract. Did the Stayputnik hyperedited to Mun orbit. Still didn't work

Edited March 22, 2015 by linuxgurugamer

[linuxgurugamer]

Some more info.

I redid this, and kept the log.

Now, the ship only consisted of a probe core. So I see in the log that:

[LOG 21:33:12.477] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: -> CheckVessel(57d2b08b-7054-40d6-bfff-422fc43b02c9)

[LOG 21:33:12.477] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: SetState to Incomplete for vessel 57d2b08b-7054-40d6-bfff-422fc43b02c9

[LOG 21:33:12.478] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: <- CheckVessel

[LOG 21:33:12.481] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: SetState to that of vessel 57d2b08b-7054-40d6-bfff-422fc43b02c9

[LOG 21:33:12.484] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: SetState to that of vessel 57d2b08b-7054-40d6-bfff-422fc43b02c9

[LOG 21:33:12.488] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: SetState to that of vessel 57d2b08b-7054-40d6-bfff-422fc43b02c9

[LOG 21:33:12.489] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: SetState to that of vessel 57d2b08b-7054-40d6-bfff-422fc43b02c9

[LOG 21:33:12.489] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: SetState to that of vessel 57d2b08b-7054-40d6-bfff-422fc43b02c9

[LOG 21:33:12.489] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: SetState to that of vessel 57d2b08b-7054-40d6-bfff-422fc43b02c9

.

.

.

.

[LOG 21:34:06.377] probeCoreSphere collided into Zn20100101 - relative velocity: 106.0997 - no impact momentum (no RB)

[LOG 21:34:06.378] probeCoreSphere Exploded!! - blast awesomeness: 0

[LOG 21:34:06.381] [probeCoreSphere]: Deactivated

[LOG 21:34:06.393] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: OnVesselAboutToBeDestroyed: EventReport

[LOG 21:34:06.393] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: SetState to Complete for vessel 57d2b08b-7054-40d6-bfff-422f

c43b02c9

[LOG 21:34:06.393] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: -> CheckVessel(57d2b08b-7054-40d6-bfff-422fc43b02c9)

[LOG 21:34:06.393] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: SetState to Complete for vessel 57d2b08b-7054-40d6-bfff-422f

c43b02c9

[LOG 21:34:06.393] [VERBOSE] ContractConfigurator.Parameters.VesselDestroyed: <- CheckVessel

[LOG 21:34:06.393] [00:01:15]: Stayputnik Mk. 1 crashed into terrain.

[LOG 21:34:06.397] 1 explosions created

So it seems that it is trying to set the state, but for some reason the contract isn't getting fulfilled.

I tried removing the BackgroundProcessing mod, but that didn't seem to help

[nightingale]

Alright, this info helps. I'm going to get that VesselDestroyed issue squashed, let me try to reproduce it again...

[linuxgurugamer]

Alright, this info helps. I'm going to get that VesselDestroyed issue squashed, let me try to reproduce it again...

Ok. Let me know if I can help.

FYI, I'm testing with a totally new career, in easy mode, with lots of money and science to start. Don't know if it's relevant, but can't hurt to know.

also, just so you have it, here is the meta ckan file which is created by CKAN, you can use it to create a fresh install with the same mods:

{
    "spec_version": "v1.6",
    "identifier": "installed-default",
    "version": "2015.03.21.09.19.14",
    "license": "unknown",
    "name": "installed-default",
    "abstract": "A list of modules installed on the default KSP instance",
    "kind": "metapackage",
    "depends": [
        {
            "name": "AerodynamicModel",
            "version": "provided by FerramAerospaceResearch"
        },
        {
            "name": "FAR",
            "version": "provided by FerramAerospaceResearch"
        },
        {
            "name": "ActiveTextureManagement",
            "version": "provided by ActiveTextureManagement-x86-Aggressive"
        },
        {
            "name": "MechJebForAll",
            "version": "1.1.0"
        },
        {
            "name": "QuickSearch",
            "version": "v1.10"
        },
        {
            "name": "KerbalAlarmClock",
            "version": "v3.2.3.0"
        },
        {
            "name": "WernherChecker",
            "version": "v0.3.4"
        },
        {
            "name": "EditorExtensions",
            "version": "2.5.1"
        },
        {
            "name": "FerramAerospaceResearch",
            "version": "v0.14.6"
        },
        {
            "name": "ContractsWindowPlus",
            "version": "4.0"
        },
        {
            "name": "HyperEdit",
            "version": "1.3"
        },
        {
            "name": "KWRocketry",
            "version": "2.6d2"
        },
        {
            "name": "ModuleManager",
            "version": "2.5.10"
        },
        {
            "name": "ContractConfigurator",
            "version": "0.7.2"
        },
        {
            "name": "SAVE",
            "version": "0.9.17-387"
        },
        {
            "name": "NovaPunch",
            "version": "2.08"
        },
        {
            "name": "KSPAPIExtensions",
            "version": "v1.7.2"
        },
        {
            "name": "ActiveTextureManagement-x86-Aggressive",
            "version": "4-3"
        },
        {
            "name": "BackgroundProcessing",
            "version": "0.4.0.1"
        },
        {
            "name": "RasterPropMonitor-Core",
            "version": "v0.19"
        },
        {
            "name": "StockBugFixModules",
            "version": "v0.1.7d"
        },
        {
            "name": "MechJeb2",
            "version": "2.4.2"
        },
        {
            "name": "KerbalEngineerRedux",
            "version": "1.0.15.2"
        },
        {
            "name": "KSP-AVC",
            "version": "1.1.5.0"
        },
        {
            "name": "SmartParts",
            "version": "1.5.1"
        },
        {
            "name": "SmartStage",
            "version": "v2.5.0"
        },
        {
            "name": "CheatMenu",
            "version": "1.0.5"
        },
        {
            "name": "CIT-Util",
            "version": "1.2.1"
        },
        {
            "name": "DeadlyReentry",
            "version": "v6.4.0"
        },
        {
            "name": "ExceptionDetector",
            "version": "v.1.1"
        },
        {
            "name": "GCMonitor",
            "version": "1.2.1.0-20"
        },
        {
            "name": "KronalVesselViewer",
            "version": "0.0.4_0.90.0"
        },
        {
            "name": "LandingHeight",
            "version": "1.3"
        },
        {
            "name": "SafeChute",
            "version": "1.6"
        },
        {
            "name": "Toolbar",
            "version": "1.7.8"
        },
        {
            "name": "ToadicusTools",
            "version": "6"
        },
        {
            "name": "VOID",
            "version": "0.17"
        },
        {
            "name": "FilterExtensions",
            "version": "2.0.3"
        }
    ]
}

Edited March 22, 2015 by linuxgurugamer

[nightingale]

Found and fixed the problem! It wasn't working correctly when under a VesselParameterGroup, which was the difference between your test and mine. I've got a couple other fixes that I need to look at, so I will be releasing 0.7.3 relatively soon. In the meantime if you want to test this early, you can grab the updated dll from GitHub.

[linuxgurugamer]

Found and fixed the problem! It wasn't working correctly when under a VesselParameterGroup, which was the difference between your test and mine. I've got a couple other fixes that I need to look at, so I will be releasing 0.7.3 relatively soon. In the meantime if you want to test this early, you can grab the updated dll from GitHub.

It worked in my first test, will be doing some more. But it feels good.

Thanks for your perservance

Edit: Worked in a full test, where I actually flew a ship to Minmus and crashed onto it. This contract had several requirements, and all worked!

Good Job!

Edited March 22, 2015 by linuxgurugamer