linuxgurugamer

@nightingale I'm looking into some issues with my rover contracts. This is the first time I'm looking at it since the 1.1 release. In 1.0.5, they worked fine, but in 1.1.2, I see the following error: ContractConfigurator.Behaviour.WaypointGeneratorFactory: CONTRACT_TYPE 'RoverExplore', BEHAVIOUR '@/a1' of type 'WaypointGenerator: A validation error occured while loading the key 'maxDistance' with value '3000'. (Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 64) ArgumentException: Must be greater than 3500 at ContractConfigurator.Validation.GT[Double] (Double val, Double referenceValue) [0x00000] in <filename unknown>:0 at ContractConfigurator.Behaviour.WaypointGenerator+<>c__DisplayClass8_0.<Create>b__25 (Double x) [0x00000] in <filename unknown>:0 at ContractConfigurator.ConfigNodeUtil.ParseValue[Double] (.ConfigNode configNode, System.String key, System.Action`1 setter, IContractConfiguratorFactory obj, Double defaultValue, System.Func`2 validation) [0x00000] in <filename unknown>:0 UnityEngine.Debug:Internal_LogException(Exception, Object) UnityEngine.Debug:LogException(Exception) ContractConfigurator.LoggingUtil:LogException(Exception) ContractConfigurator.ConfigNodeUtil:ParseValue(ConfigNode, String, Action`1, IContractConfiguratorFactory, Double, Func`2) ContractConfigurator.ConfigNodeUtil:ParseValue(ConfigNode, String, Action`1, IContractConfiguratorFactory, Func`2) ContractConfigurator.DeferredLoadUtil:ExecuteLoad(DeferredLoadObject`1) System.Reflection.MonoMethod:InternalInvoke(Object, Object[], Exception&) System.Reflection.MonoMethod:Invoke(Object, BindingFlags, Binder, Object[], CultureInfo) System.Reflection.MethodBase:Invoke(Object, Object[]) ContractConfigurator.<UpdateNonDeterministicValuesIterator>d__26:MoveNext() System.Linq.<CreateConcatIterator>c__Iterator1`1:MoveNext() ContractConfigurator.<ContractGenerator>d__26:MoveNext() ContractConfigurator.<ContractGenerator>d__25:MoveNext() ContractConfigurator.ContractPreLoader:Update() When I look at the CC screen, it says it successfully loaded 2 out of 2 contracts This happened after a first mission, didn't see it again.

I submitted a pull which adds a hotkey (ctl-F2) to show/hide the window, hope it gets accepted

Woo hoo! Looking forward to it. While I know it's hard to be specific, do you think there is a chance it will be available for testing by the weekend?

The update I did last night was only for 1.1.2 compatibility, I haven't yet had a chance to test these contracts yet.

This is fixed, just finished uploading new version: 0.5.9

I found the problem, will fix it this evening. It has to do with the new code I added to lock the altimeterslider Thanks for the report

Career or sandbox mod? I just turned off vsync and saw the problem.

for something like this, mostly a matter of updating the veriosn file and testing

If it's red, it didn't load. I'll be looking at this later this evening, watch for an update

something I haven't gotten around to doing, I hope to do it this evening

I did, but I was referring to the way that the Redux has two different configs which it loads in at install time via CKAN

I'll get to this in the evening

Updated

Yes, and I haven't had time to fix it yet :-(

Take a look at what I did for KW Rocketry Redux to see how to solve t his

From the changelog: - Added missing FX info to some fairings - Renamed FX from deploy to decouple in some fairings The following lines were either missing or had an old name: fx_gasBurst_white = 0.0, 0.3, 0.0, 0.0, 1.0, 0.0, decouple sound_vent_large = decouple KW had the old status of "deploy" instead of "decouple" You can read more about the FX definitions at this page: http://wiki.kerbalspaceprogram.com/wiki/CFG_File_Documentation#FX_definitions Keep in mind that this documentation is old, and is not totally accurate.

Great, thanks for letting me know

Send me the save file, please, I'll take a look tomorrow

Interesting. I did confirm it as a bug. This is from the original mod which I incorporated. I've done a lot of work recently on EEx, need to get some work done on other mods. Since you seem to be the first to report it, I'm not going to make it a priority. Could you raise a github issue so i can keep track of it, I'll look into this later. Thanks

I just released 3.0.7 which fixes these messages. Now, when I load a game with KW, there aren't any of those messages in the log.

The message "Cannot find fx group of that name for decoupler" is likely from code that used to work one way in 0.21 or something, and no longer works that way, but the line is still there for that part and therefore you get a warning. It can probably be ignored in THIS case. It looks like the some of the fairing don't even have the fx group. I'll work on adding it, for now, just ignore those messages

Suggestion for improvement: Add ability to watch the log for a specific string (or set of strings). I often watch the log looking for certain events (logged), this would be very helpful

This is SO cool! Thank you very much, I learned a lot, and would not have figured this out myself.

So, would it be something like this (not exactly sure about the names, not at my dev system now): GizmoOffset ego; ego.AddComponent("localscriptname"); or this: EditorGizmos.GizmoOffset.Attach(.....)

it's already fixed in 3.2.10