Kerbal Joint Reinforcement - Next

[Rudolf Meier]

2 hours ago, StreS said:

Hi. Have some problem.

I launched a spaceplane into orbit, separated the probe, switched to the probe, performed the maneuver, and switched back to the spaceplane.

And after that the game showed it.

  Reveal hidden contents

It says here: Error loading machine The device is not loaded due to lack of details: KJRAutoStrutHelper.

Thank you.

UPD: I switched straight from the flight through the map. If you first switch to Space Center, and then to the spaceplane, nothing happens. Everything works well.

interesting... now that's a good description of the problem... I will investigate this

[mrclucks]

 

 

 

On 5/14/2019 at 5:37 PM, Rudolf Meier said:

hm? ... sorry... did I miss something?

no man, I was just being ridiculous and pushing KSP past what it's supposed to be capable of.  

i'll post the craft soonish

[fronbow]

10 hours ago, Rudolf Meier said:

interesting... now that's a good description of the problem... I will investigate this

I'm getting this too, when I switch to vehicles that have decoupled, the game kills the vehicle because "KJRAutoStrutHelper" is missing. I've lost 2 space stations so far, just going to head off into the gamesave to see if I can try to salvage them

[Rudolf Meier]

2 minutes ago, fronbow said:

I'm getting this too, when I switch to vehicles that have decoupled, the game kills the vehicle because "KJRAutoStrutHelper" is missing. I've lost 2 space stations so far, just going to head off into the gamesave to see if I can try to salvage them

if you have a gamesave, you can delete those parts...

sorry for those problems

[fronbow]

There weren't any parts with that name in my save, just loads of Missing astronauts!!

Hope you can what and where this bug is hiding!

[Rudolf Meier]

42 minutes ago, fronbow said:

There weren't any parts with that name in my save, just loads of Missing astronauts!!

Hope you can what and where this bug is hiding!

currently I cannot reproduce this... I've removed the releases as a precaution...

but... I can decouple, switch vessels... everything... and have no problem

do you have other mods installed? ... e.g. easy vessel switch??

[fronbow]

Yes I have other mods installed, and just checked and yes EVS is installed. Is this a known conflict or EVS problem?

[Rudolf Meier]

6 minutes ago, fronbow said:

Yes I have other mods installed, and just checked and yes EVS is installed. Is this a known conflict or EVS problem?

no idea... currently I'm just guessing

[kurtu5]

A couple of questions.  I think I am having a problem with 4.0.3 and would like to know what kind of debug info you need. 

1. I see on github there is a debug flag in the config, but what should I be looking for in the logs after setting it? 

2. Also, you say there is a debug version and that I should see a AppLauncher Icon in flight, what version is this enabled on?

3.  What forum should we all be using?  The one with wip in the url or the one without?

 

To give a preview of the problem I faced, I had been using 4.0.0(KSP 1.6.1) and then upgraded to 4.0.3 and some craft that have "Autostrut Locked: Heaviest part" were flipping out on launch.  I haven't set and autostruts manually yet.  In this case the rover flips over on launch and the command pod is cantered off axis on the attachment point.  Reverting back to 4.0.0 removes the issue.

https://imgur.com/FOTaCSN

[Rudolf Meier]

1 hour ago, kurtu5 said:

A couple of questions.  I think I am having a problem with 4.0.3 and would like to know what kind of debug info you need. 

hi, thanks for the info... I don't need anything, I already understand this problem...

it is a combination of a KSP bug, a missing event in KSP and some other problems including incompatibilities with other mods... that's why I give up this idea now and I'm implementing something new now... if it works, we will have a new version in about 12 hours

see the development thread for further information on this

[Rudolf Meier]

I have rewritten a lot of the system and released version 4.0.5 now

it should solve the problems we saw with the unlucky versions 4.0.1 to 4.0.3 and the version 4.0.4 with a small bug ... and it should be compatible with the new DLC (which is the main reason why the version 4.0.0 had to be updated massively)

 

One of the main challenges of the version supporting moveable parts like those of Infernal Robotics Next and the new DLC is, that sometimes the joints needs to be rebuilt (while the game is running) ... and you may have seen this already, often this leads to gaps and strange deformations of the ships until you reload the scene or go to time warp (but, sometimes this doesn't help). The latest version tries to fix this. And it tries to reduce the amount of joints it's building as well as the internal bookkeeping data for a better performance and less lag in the gaming.

Edited May 17, 2019 by Rudolf Meier

[yafeshan]

I need to report that KJR next creates a serious error when i used in Realism Overhaul. It creates a part KJRsensor1 with partID 0. Causes game to crash. Happens in all compatible ksp versions.

[Rudolf Meier]

23 hours ago, yafeshan said:

I need to report that KJR next creates a serious error when i used in Realism Overhaul. It creates a part KJRsensor1 with partID 0. Causes game to crash. Happens in all compatible ksp versions.

ok... I'm just guessing... tell me more

Edited May 20, 2019 by Rudolf Meier

[yafeshan]

On 5/20/2019 at 1:01 AM, Rudolf Meier said:

ok... I'm just guessing... tell me more

It was all fine until I installed principia. Obviously I went ahead to ask their support. They requested info about my crash, I sent loads of logs and next day, their dev told there is a part ID given as 0 (KJRsensor1)coming from KJR next. They said it is the reason of crash and they were correct. I removed KJR next and installed KJR continued and then everything works perfectly now. 

RO and principia have no alternatives for me really but I also would like to use Infernal Robotics Next and their suggested mod KJR next. However I had to make a compromise and start another game career instead of waiting. Principia can not be added to a continuing career but any fix for KJR next can be applied later.

[Rudolf Meier]

6 minutes ago, yafeshan said:

It was all fine until I installed principia. Obviously I went ahead to ask their support. They requested info about my crash, I sent loads of logs and next day, their dev told there is a part ID given as 0 (KJRsensor1)coming from KJR next. They said it is the reason of crash and they were correct. I removed KJR next and installed KJR continued and then everything works perfectly now. 

I've no idea why an id should be zero here... can you send me those logs too?

... and, "part id" ... I don't know what they're talking about, sorry... I don't know a variable named like that

Edited May 21, 2019 by Rudolf Meier

[yafeshan]

I will send what i can now. 

This is what principia dev showed me from your github pointing faulty part is from kjr next

https://github.com/meirumeiru/Kerbal-Joint-Reinforcement/blob/master/KerbalJointReinforcement/KerbalJointReinforcement/KJRAutoStrutModule.cs#L59

And this is my gist includes my save and info related to principia logs

https://gist.github.com/yafeshan/68ae0c4263bc42ca3e31fc1b94968291

I do not have anything else because I deleted and reinstall everything half a dozen times after that

Edited May 21, 2019 by yafeshan

[pleroy]

10 hours ago, Rudolf Meier said:

... and, "part id" ... I don't know what they're talking about, sorry... I don't know a variable named like that

From the KSP documentation:

uint Part.flightID

a unique id to identify this part in flight. This one is guaranteed to be unique for all parts in the simulation. Not assigned in the editor.

[Rudolf Meier]

4 minutes ago, pleroy said:

From the KSP documentation:

uint Part.flightID

a unique id to identify this part in flight. This one is guaranteed to be unique for all parts in the simulation. Not assigned in the editor.

 aaahhh... "flightID" ... yes, this one I know... and I also know the "persistentId", the craftID, the missionID and the launchID  ... but no "part id"... that was my problem. Now it's clear. ...

[AccidentalDisassembly]

On 5/19/2019 at 3:16 PM, yafeshan said:

I need to report that KJR next creates a serious error when i used in Realism Overhaul. It creates a part KJRsensor1 with partID 0. Causes game to crash. Happens in all compatible ksp versions.

I'm afraid I don't know enough to know the exact effects in my game, since mine does not crash, but I also get log spam related to KJRsensor1 and KJRsensor2, and I don't have RO installed (although many other mods are).

Looks like this in my KSP log and seems to relate to the KSTS mod, I guess:

Spoiler

[LOG 21:39:12.994] [FlightTracker]: OnVesselRollout fired
[LOG 21:39:12.995] [FlightTracker]: Jebediah Kerman launched at 379.279999999945
[LOG 21:39:12.995] [FlightTracker]: Bob Kerman launched at 379.279999999945
[LOG 21:39:13.040] Flight State Captured
[LOG 21:39:13.041] Saving Achievements Tree...
[LOG 21:39:13.042] [FlightTracker]: Saved 2 kerbals flight data
[LOG 21:39:13.042] [EarnYourStripes]: Saved 0 kerbals flight data
[LOG 21:39:13.042] [KRnD] saved 0 upgrades in 0.000s
[LOG 21:39:13.048] [MessageSystem] Save Messages
[LOG 21:39:13.074] Game State Saved as persistent
[LOG 21:39:13.140] [OD] --> ScaledSpaceDemand.LoadTextures loading NewMunSurfaceMap00 and NewMunSurfaceMap01
[LOG 21:39:15.454] [Untitled Space Craft]: ground contact! - error. Moving Vessel  down -0.225m
[LOG 21:39:15.454] Unpacking Untitled Space Craft
[LOG 21:39:15.503] KJR easing Untitled Space Craft
[LOG 21:39:15.567] [UIMasterController]: ShowUI
[ERR 21:39:15.924] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor1' not found in dictionary

[ERR 21:39:15.958] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor2' not found in dictionary

[ERR 21:39:16.981] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor1' not found in dictionary

[ERR 21:39:17.014] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor2' not found in dictionary

[ERR 21:39:18.025] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor1' not found in dictionary

[ERR 21:39:18.058] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor2' not found in dictionary

[ERR 21:39:19.068] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor1' not found in dictionary

[ERR 21:39:19.100] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor2' not found in dictionary

[ERR 21:39:20.108] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor1' not found in dictionary

[ERR 21:39:20.143] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor2' not found in dictionary

[ERR 21:39:21.149] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor1' not found in dictionary

[ERR 21:39:21.184] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor2' not found in dictionary

[ERR 21:39:22.217] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor1' not found in dictionary

[ERR 21:39:22.252] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor2' not found in dictionary

[ERR 21:39:23.252] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor1' not found in dictionary

[ERR 21:39:23.290] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor2' not found in dictionary

[ERR 21:39:24.312] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor1' not found in dictionary

[ERR 21:39:24.344] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor2' not found in dictionary

[ERR 21:39:25.351] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor1' not found in dictionary

[ERR 21:39:25.385] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor2' not found in dictionary

[ERR 21:39:26.403] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor1' not found in dictionary

[ERR 21:39:26.436] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor2' not found in dictionary

[ERR 21:39:27.436] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor1' not found in dictionary

[ERR 21:39:27.470] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor2' not found in dictionary

[LOG 21:39:28.424] [5/20/2019 9:39:28 PM [x] Science!]: <Trace> (StatusWindow) - Finding Module for Science Report: mobileMaterialsLab
[LOG 21:39:28.425] [5/20/2019 9:39:28 PM [x] Science!]: <Trace> (StatusWindow) - Running Experiment mobileMaterialsLab on part science.module
[LOG 21:39:28.426] [Experiments]: Setting FX Modules to 1...
[ERR 21:39:28.489] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor1' not found in dictionary

[ERR 21:39:28.522] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor2' not found in dictionary

[ERR 21:39:29.539] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor1' not found in dictionary

[ERR 21:39:29.573] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor2' not found in dictionary

[ERR 21:39:30.574] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor1' not found in dictionary

[ERR 21:39:30.609] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor2' not found in dictionary

[ERR 21:39:31.623] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor1' not found in dictionary

[ERR 21:39:31.656] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor2' not found in dictionary

[LOG 21:39:32.239] [Experiments]: FX Modules set: 1
[LOG 21:39:32.257] [Science_Relay] Connected vessels detected for science transmission: 0
[ERR 21:39:32.673] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor1' not found in dictionary

[ERR 21:39:32.706] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor2' not found in dictionary

[ERR 21:39:33.714] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor1' not found in dictionary

[ERR 21:39:33.746] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor2' not found in dictionary

[LOG 21:39:34.185] [Experiments]: Setting FX Modules to 0...
[ERR 21:39:34.777] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor1' not found in dictionary

[ERR 21:39:34.810] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor2' not found in dictionary

[LOG 21:39:35.255] [Experiments]: Setting FX Modules to 0...
[LOG 21:39:35.513] [BetterBurnTime] Current celestial body set to Kerbin
[LOG 21:39:35.513] [BetterBurnTime] Geosync altitude: 2863.334 km
[ERR 21:39:35.810] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor1' not found in dictionary

[ERR 21:39:35.843] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor2' not found in dictionary

[LOG 21:39:36.308] [Experiments]: Setting FX Modules to 0...
[LOG 21:39:36.972] [MechJebModuleAscentAutopilot] LaunchStarted = 0
[LOG 21:39:36.972] [MechJebModuleAscentAutopilot] LaunchStarted = 400.399999999926
[LOG 21:39:36.973] [MechJebModuleAscentAutopilot] LaunchStarted = 0
[LOG 21:39:36.973] [MechJebModuleAscentAutopilot] LaunchStarted = 0
[LOG 21:39:37.016] [Experiments]: FX Modules set: 0
[LOG 21:39:37.016] [Experiments]: FX Modules set: 0
[LOG 21:39:37.016] [Experiments]: FX Modules set: 0
[LOG 21:39:37.045] [Progress Node Reached]: RecordsAltitude
[LOG 21:39:37.048] [Progress Node Reached]: RecordsSpeed
[LOG 21:39:37.049] [Progress Node Reached]: RecordsDistance
[LOG 21:39:37.481] [5/20/2019 9:39:37 PM [x] Science!]: <Trace> (StatusWindow) - ScienceThisBiome: 7 / 0

 

Edited May 21, 2019 by AccidentalDisassembly

[Rudolf Meier]

10 minutes ago, AccidentalDisassembly said:

I'm afraid I don't know enough to know the exact effects in my game, since mine does not crash, but I also get log spam related to KJRsensor1 and KJRsensor2, and I don't have RO installed (although many other mods are).

Looks like this in my KSP log and seems to relate to the KSTS mod, I guess:

  Reveal hidden contents

[LOG 21:39:12.994] [FlightTracker]: OnVesselRollout fired
[LOG 21:39:12.995] [FlightTracker]: Jebediah Kerman launched at 379.279999999945
[LOG 21:39:12.995] [FlightTracker]: Bob Kerman launched at 379.279999999945
[LOG 21:39:13.040] Flight State Captured
[LOG 21:39:13.041] Saving Achievements Tree...
[LOG 21:39:13.042] [FlightTracker]: Saved 2 kerbals flight data
[LOG 21:39:13.042] [EarnYourStripes]: Saved 0 kerbals flight data
[LOG 21:39:13.042] [KRnD] saved 0 upgrades in 0.000s
[LOG 21:39:13.048] [MessageSystem] Save Messages
[LOG 21:39:13.074] Game State Saved as persistent
[LOG 21:39:13.140] [OD] --> ScaledSpaceDemand.LoadTextures loading NewMunSurfaceMap00 and NewMunSurfaceMap01
[LOG 21:39:15.454] [Untitled Space Craft]: ground contact! - error. Moving Vessel  down -0.225m
[LOG 21:39:15.454] Unpacking Untitled Space Craft
[LOG 21:39:15.503] KJR easing Untitled Space Craft
[LOG 21:39:15.567] [UIMasterController]: ShowUI
[ERR 21:39:15.924] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor1' not found in dictionary

[ERR 21:39:15.958] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor2' not found in dictionary

[ERR 21:39:16.981] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor1' not found in dictionary

[ERR 21:39:17.014] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor2' not found in dictionary

[ERR 21:39:18.025] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor1' not found in dictionary

[ERR 21:39:18.058] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor2' not found in dictionary

[ERR 21:39:19.068] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor1' not found in dictionary

[ERR 21:39:19.100] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor2' not found in dictionary

[ERR 21:39:20.108] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor1' not found in dictionary

[ERR 21:39:20.143] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor2' not found in dictionary

[ERR 21:39:21.149] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor1' not found in dictionary

[ERR 21:39:21.184] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor2' not found in dictionary

[ERR 21:39:22.217] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor1' not found in dictionary

[ERR 21:39:22.252] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor2' not found in dictionary

[ERR 21:39:23.252] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor1' not found in dictionary

[ERR 21:39:23.290] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor2' not found in dictionary

[ERR 21:39:24.312] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor1' not found in dictionary

[ERR 21:39:24.344] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor2' not found in dictionary

[ERR 21:39:25.351] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor1' not found in dictionary

[ERR 21:39:25.385] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor2' not found in dictionary

[ERR 21:39:26.403] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor1' not found in dictionary

[ERR 21:39:26.436] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor2' not found in dictionary

[ERR 21:39:27.436] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor1' not found in dictionary

[ERR 21:39:27.470] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor2' not found in dictionary

[LOG 21:39:28.424] [5/20/2019 9:39:28 PM [x] Science!]: <Trace> (StatusWindow) - Finding Module for Science Report: mobileMaterialsLab
[LOG 21:39:28.425] [5/20/2019 9:39:28 PM [x] Science!]: <Trace> (StatusWindow) - Running Experiment mobileMaterialsLab on part science.module
[LOG 21:39:28.426] [Experiments]: Setting FX Modules to 1...
[ERR 21:39:28.489] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor1' not found in dictionary

[ERR 21:39:28.522] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor2' not found in dictionary

[ERR 21:39:29.539] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor1' not found in dictionary

[ERR 21:39:29.573] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor2' not found in dictionary

[ERR 21:39:30.574] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor1' not found in dictionary

[ERR 21:39:30.609] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor2' not found in dictionary

[ERR 21:39:31.623] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor1' not found in dictionary

[ERR 21:39:31.656] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor2' not found in dictionary

[LOG 21:39:32.239] [Experiments]: FX Modules set: 1
[LOG 21:39:32.257] [Science_Relay] Connected vessels detected for science transmission: 0
[ERR 21:39:32.673] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor1' not found in dictionary

[ERR 21:39:32.706] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor2' not found in dictionary

[ERR 21:39:33.714] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor1' not found in dictionary

[ERR 21:39:33.746] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor2' not found in dictionary

[LOG 21:39:34.185] [Experiments]: Setting FX Modules to 0...
[ERR 21:39:34.777] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor1' not found in dictionary

[ERR 21:39:34.810] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor2' not found in dictionary

[LOG 21:39:35.255] [Experiments]: Setting FX Modules to 0...
[LOG 21:39:35.513] [BetterBurnTime] Current celestial body set to Kerbin
[LOG 21:39:35.513] [BetterBurnTime] Geosync altitude: 2863.334 km
[ERR 21:39:35.810] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor1' not found in dictionary

[ERR 21:39:35.843] [KSTS] RecordingVesselStats.GetStats(): part 'KJRsensor2' not found in dictionary

[LOG 21:39:36.308] [Experiments]: Setting FX Modules to 0...
[LOG 21:39:36.972] [MechJebModuleAscentAutopilot] LaunchStarted = 0
[LOG 21:39:36.972] [MechJebModuleAscentAutopilot] LaunchStarted = 400.399999999926
[LOG 21:39:36.973] [MechJebModuleAscentAutopilot] LaunchStarted = 0
[LOG 21:39:36.973] [MechJebModuleAscentAutopilot] LaunchStarted = 0
[LOG 21:39:37.016] [Experiments]: FX Modules set: 0
[LOG 21:39:37.016] [Experiments]: FX Modules set: 0
[LOG 21:39:37.016] [Experiments]: FX Modules set: 0
[LOG 21:39:37.045] [Progress Node Reached]: RecordsAltitude
[LOG 21:39:37.048] [Progress Node Reached]: RecordsSpeed
[LOG 21:39:37.049] [Progress Node Reached]: RecordsDistance
[LOG 21:39:37.481] [5/20/2019 9:39:37 PM [x] Science!]: <Trace> (StatusWindow) - ScienceThisBiome: 7 / 0

 

*hmm* ... interesting... I have modified something already. Maybe it's solved then, otherwise I will investigate it.

... thanks for the input

[MikeO89]

Just tried 4.0.9 and craft started wobbling pretty bad on way to orbit. Using 1.7. Hadn't seen this happen for quite some time now.

Edited May 23, 2019 by MikeO89

[kcs123]

17 hours ago, MikeO89 said:

Just tried 4.0.9 and craft started wobbling pretty bad on way to orbit. Using 1.7. Hadn't seen this happen for quite some time now.

Can you try same with 4.0.0. version ? I have one craft that worked well with 4.0.0. but after some coding overhaul that fix discovered issues with 4.0.0. later versions have introduced some new bugs that was not happend to everyone. It would be of great help if you can send craft file that work properly with KJRn 4.0.0. but have issues with 4.0.9. If possible, only with stock parts.

And be patient, next version is being worked on, hopefully it will solve issue you have, but describing problem with better details, creating videos, screenshots etc. might help to get fix sooner rather than later.

[Rudolf Meier]

thanks to the help of @kcs123 I could develop a new version -> 4.0.10

this one is not using the AutoStrut sensors anymore (they seem to bring too many problems)... it still works with DLC and it still uses the new way of building additional joints... in case you don't want this or think it is unstable, you can turn this off and let KJR build the joints the old way. To do this you have to add a "bool" value with the name "useOldJointCreation" in the "config.xml" file and set this to "true".

[kcs123]

1 hour ago, Rudolf Meier said:

thanks to the help of @kcs123 I could develop a new version -> 4.0.10

You are welcome, but I'm not sure how CKAN will handle such version number. IIRC it sorts version number as string, so 4.0.9 is greater version number than 4.0.10 due to string sort. I might be wrong with this, have to check with CKAN staff to confirm, but might be better to set version number as 4.1.0 instead. It was released 18 hours ago, CKAN bot should be able to catch it by now.

Afterall, latest release have received some serious overhaul in code.

 

[DasSkelett]

4 hours ago, kcs123 said:

You are welcome, but I'm not sure how CKAN will handle such version number. IIRC it sorts version number as string, so 4.0.9 is greater version number than 4.0.10 due to string sort. I might be wrong with this, have to check with CKAN staff to confirm, but might be better to set version number as 4.1.0 instead. It was released 18 hours ago, CKAN bot should be able to catch it by now.

Afterall, latest release have received some serious overhaul in code.

 

No, that works fine. A lot of mods use a semantic-versioning-like style, and that specifically dictates an independent increase of each element.
CKAN supports going from .9 to .10, in fact, that's CKAN-wise the correct way.

There's something written in our spec: https://github.com/KSP-CKAN/CKAN/blob/master/Spec.md#version-ordering, extract:

Quote

Then the initial part of the remainder of each string which consists entirely of digit characters is determined. The numerical values of these two parts are compared, and any difference found is returned as the result of the comparison.

The version string is split, comparing non-digit parts lexically and comparing digit parts numerically.
For this mod, this means we have ABCDEF (or AB.D.F) (= v4.0.10  and v4.0.9 for example).

First part,       A: it's the v. the v is compared lexically. It stays the same, so returns an "equals".
Second part, B: it's the 4 in each case, compared numerically, returns "equals".
Third part,     C: it's the first ., not a digit, compared lexically (not really, has some special handling), returns "equals".
Fourth part,  D: it's the 0, returns "equals".
Fifth part,      E: Another dot.
Sixth part,     F: in the first case the 10, in the second case the 9. Compared numerically, 10 > 9: returns "greater than".

Edited May 28, 2019 by DasSkelett