• Content count

  • Joined

  • Last visited

Community Reputation

2787 Excellent

About nightingale

  • Rank
    Configurer of Contracts

Profile Information

  • Location Canada

Recent Profile Visitors

8325 profile views
  1. You should now be able to just grab the new Contract Configurator, cancel the existing contract and then be good to go.
  2. Going from memory, but the problem in the linked thread had to do with displaying with the "P0" display format (ie. percentages). It sounds like you just need more decimal places - try with displayFormat="F3".
  3. New release, download here. Contract Configurator 1.23.2 Clarified wording of ActiveVesselRangeRequirement for RemoteTech (thanks Alshain). Added check for old usage of partModuleType=Power (thanks muppet9876). Prevent Rendezvous parameter from completing when doing an EVA (thanks pap1723). Don't allow main menu to continue while still loading (prevents issues on slower systems). Made RemoteTech distance function (for coverage system) more generous (thanks NathanKell). Fixed issue with Kerbals spawned at KSC starting an extra ~60 meters in the air (thanks Keniamin). Fixed error when cancelling a contract with spawned Kerbals. Fixed exception with FlyBy and ReturnFromFlyBy requirements. Properly fixed Facility requirement in the tracking station (thanks Kerbas_ad_astra). Fixed NRE from struts breaking (thanks Alshain). Fixed multiple exceptions when using Sigma Binary (thanks Rodger).
  4. Something changed in stock KSP - I've been trying to work through some issues and am going to get a new build out to see if that resolves some of this stuff. @SchrottBot - I haven't been able to reproduce that particular issue. I'm going to do a release to sort of re-baseline things. @chrisl - I'll see if I can take a look on GitHub. @TheRagingIrishman - Yup, no reason you can't change another mod's contracts using Module Manager.
  5. @Filigan - Please raise that on GitHub, and I'll see if I can get that fixed when I'm doing the next Strategia bugfix pass. @Raphaello - They would need a serious redesign to make them work, given that most of those strategies work by increasing rewards for one body and decreasing for others. Having one unmanned + one manned could be feasible, but otherwise it's probably not a change that I'd be looking at doing soon. @canisin - I assume you mean the stock on screen messages? I can probably do that, please raise that in GitHub as well.
  6. @Gordon Dry - That one should be fixed in the upcoming Contract Configurator release. I'm aiming to get it out this week, but non-KSP constraints are currently making things difficult. @WakabaGyaru - Agree - raise an issue in GitHub for that one and I'll take a closer look.
  7. Sorry about the late reply. Thanks for putting all that together. Based on that log (and the fact that it works on the dev build), I'm fairly confident I made the right fixes. Let me know if this crops up again. --- @kgbeast - If I had to take a guess, that's an incorrectly installed ResearchBodies (the class that it's complaining about and the contract generating the error both come from ResearchBodies). Make sure that RB is correctly installed and try again.
  8. This: ContractConfigurator.ContractType: CONTRACT_TYPE 'SpaceStation': Error parsing targetBody1 (Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42) NullReferenceException: Object reference not set to an instance of an object at ContractConfigurator.ExpressionParser.CelestialBodyParser.CheckTree (KSPAchievements.CelestialBodySubtree tree, ProgressItem pi) [0x00000] in <filename unknown>:0 at ContractConfigurator.ExpressionParser.CelestialBodyParser+<>c__DisplayClass9_0.<BodiesForItem>b__0 (KSPAchievements.CelestialBodySubtree node) [0x00000] in <filename unknown>:0 at System.Linq.Enumerable+<CreateWhereIterator>c__Iterator1D`1[KSPAchievements.CelestialBodySubtree].MoveNext () [0x00000] in <filename unknown>:0 at System.Linq.Enumerable+<CreateSelectIterator>c__Iterator10`2[KSPAchievements.CelestialBodySubtree,CelestialBody].MoveNext () [0x00000] in <filename unknown>:0 at System.Linq.Enumerable+<CreateWhereIterator>c__Iterator1D`1[CelestialBody].MoveNext () [0x00000] in <filename unknown>:0 at System.Collections.Generic.List`1[CelestialBody].AddEnumerable (IEnumerable`1 enumerable) [0x00000] in <filename unknown>:0 at System.Collections.Generic.List`1[CelestialBody]..ctor (IEnumerable`1 collection) [0x00000] in <filename unknown>:0 at System.Linq.Enumerable.ToList[CelestialBody] (IEnumerable`1 source) [0x00000] in <filename unknown>:0 at ContractConfigurator.ExpressionParser.CelestialBodyParser+<>c.<RegisterMethods>b__6_43 () [0x00000] in <filename unknown>:0 at ContractConfigurator.ExpressionParser.Function`1[System.Collections.Generic.List`1[CelestialBody]].Invoke () [0x00000] in <filename unknown>:0 at ContractConfigurator.ExpressionParser.Function`1[System.Collections.Generic.List`1[CelestialBody]].Invoke (System.Object[] parameters) [0x00000] in <filename unknown>:0 at ContractConfigurator.ExpressionParser.ExpressionParser`1[CelestialBody].ParseMethod[CelestialBody] (ContractConfigurator.ExpressionParser.Token token, .CelestialBody obj, Boolean isFunction) [0x00000] in <filename unknown>:0 Rethrow as Exception: Error parsing statement. Error occurred near '*': ReturnedFromBodies().Where(body => @/stations.Where(v => v.CelestialBody() == body).Count() == 0).SelectUnique() ....................* <-- HERE Is a very different statement than the one you posted today. Since then, I've replied that it's fixed in the next release, and you've confirmed that the issue was resolved in the dev build. So again, I have to ask: what problem are you trying to solve?
  9. No - as that's not a string, it's a CelestialBody. Also, I haven't seen an error related to that statement posted, so I don't know what it is you're trying to solve.
  10. @Gordon Dry - That issue looks like something that needs to be fixed in the Career Evolution Contract Pack. @pap1723 - For that error, the string parser in Contract Configurator is a little bit flaky when the value starts with an identifier. To get around that, you should be able to put the value in double-quotes: title = "@/foodSpace Food"
  11. @Tivec - No problem, I'll put a fix in for that symptom, and hopefully between that and the other fix that covers everything.
  12. @Rodger - That looks like a different one, fixed for next release. @Tivec - Sorry, I should've been more clear. I want the full KSP.log, as the error you're getting is a symptom of something else (and I need to see the full log to understand what that is). @Gordon Dry - That looks to be the same one as Rodger. Should be fixed for the next release. EDIT: @Tivec - Actually I did see something that was still causing the contracts to potentially get loaded late, which could be the cause. Please use this new dev build. and let me know how it goes.
  13. Whoops, made a mistake. Should be good with this version. Hmmm... that's odd, I'll take a closer look.
  14. Should've. Post the new KSP.log and I'll take a look.
  15. @Tivec - Can you do me a favour and grab the dev dll file from here and replace the one in your GameData/ContractConfigurator folder with it. Once that's done, can you let me know if you're still able to reproduce the issue, and if so please provide the KSP.log file from startup to the point where the error occurs. I suspect that one of my other changes has already fixed your issue, but I can't say for certain.