The-Grim-Sleeper

Errmmm. I'd like that 'feature' removed, or at least better reflected in the descriptions (altough yes, on reflection, the level up button did say 'lvl 0 -> lvl 1, and not lvl 1 -> lvl 2). I was about to file a bug report. But beyond that, Field Training Labs works fine with KSP v1.12.2!

I am having some difficulties here. Below the last checkpoint there is some empty space and then the 'Checkpoint mode | add new checkpoint' buttons. I am using Firefox 95.0.2 if that could be relevant.

Just found this tool going to try it later today. Questions: Does using the 'Route Type: effecient' effecivly calculate a gravity assist via the intermediaries, or is it more like a full stop and awaiting a favorable transfer to the next leg? Is there a way to tally up the total Delta-v for a mission. If not, (where) can I request the feature to display the sum of the Delta-v for all the legs of the trip in vacuum and/or in non-zero admospheric pressure?

Bug report/feature request: When I manually rename a maneuver node alarm, don't rename it back to the craft name, and give to option to unlink the alarm from the node, so if the node is deleted, the alarm can stay. I like to use Maneuver node to get an estimate on the time to switch back to do something that isn't an actual maneuver. Yes, I can turn off the auto-rename, but I actually like that on most of the time, just not when I need a little bit more info on the name tag.

I donno. I do wonder how much KAC you'd need to have installed to trick other mods into cooperation. I can't really speak for others preference. An alternative would be for somebody to pick up KAC again and give it the same 'replace stock button' as 'Alternate Resource Panel'. I do have another feature request: contract details on the alarm clock.

Moar feature requests: Closest Approach timer A pass-though so that mods trying to add a timer to 'Kerbal Alarm Clock' will be added to the stock alarm instead. Yes, it would be better if those mods are just updated properly, but imma ask anyway.

I am Patient zero of this issue and I just ran a quick test with NavInstuments-0.8.0.5. I still have more or less the same results. That said, I can confirm that reducing system load in minor ways seems to alleviate the issue, and having a lot of GUI elements open (but not NavInstuments Compass specifically) causes a lesser version of this problem with framerate and my system in general. NavInstuments is a big contributor, but that is probably due to the Compass being a bit more graphical than text-boxes used by most mods. It is indeed more a Linux-Unity problem, and is out-of-scope for any mods to fix. I will pursue other solutions to this problem.

That would be great. I'd have to defer to Ser (or Kujuman) for a full adoption, but having a 1.12 version would at least allow me to continue troubleshooting during my normal play-time.

Thank you. I am trying to compile a version with debug logging enabled (GlobalVariables.cs, ln 84 bool enableDebugging = false), but even a simple recompile is an uphill battle. Looks like my references list is to blame, but a full import of KSP_Data/managed just causes conflicts and versioning errors. I've run out of time to work on this. Welp, I'll just have to make do without this one for a while.

I am having a malfunction with This specific scenario. For reference, I've turned off engineers for parachutes requirements (I'd like to leave that on if possible, but this is for troubleshooting) I have a craft with 3 seats (Mk1 command pod, Mk1 Crew Cabin). Assigned crew: Valentina (pilot), Clauke (tourist) and Melnard (tourist). And saved this status Going to launch with these settings works fine. But any change to the craft (adding or removing any part), loading the same craft, or reverting to VAB causes the crew assignment to be scrambled: Valentina (pilot), Corrim (tourist) and Dunbus (tourist). These 2 are simply the first 2 tourists in the available crew list; the names of the tourists are not properly saved with the craft. Log file: KSP(BetterCrewAssignmentScramble).log

I'm using this mod with Contract pack: Tourism Plus in KSP 1.12.2, but I am experiencing some crew-ing issues: assigned tourists keep getting bumped in favor of Lvl1 engineers and random tourists. (Yeah my 1-use $8k and seven bottlecaps craft lands with parachutes) I take it that this is something that can be resolved with the module manager file, line 107, importance of engineers for parachute modules. But I am a not sure how this field works. Does a higher value for importance mean that it gets a higher priority? Are negative values allowed? Is there a way to set the 'profession = tourist' importance to make sure planned tourism flights get their assigned passenger load-out, even at the cost of 'vital personnel'?

Just did that complete refresh, with JUST NavUtilities and nothing else. Complete starting directory wipe, fresh install from steam, all local dependencies up-to-date. The stutter starts whenever the NavUtilities-radar is open and I hold right mouse to move the view. IVA is fine, rotating the camera without the NavUtilities-radar open is fine. No if/and/or/but about it: NavUtilities does not function properly. The scenario for this issue is consistent. This issue is systemic. It might be because of something on my system, but this issue is not part of KSP vanilla or related to any other mods. If anybody has a log file that could be used to make a comparison, knows some way to turn on debug mode for NavUtilities or knows where @Ser keeps the source code, I could look at that. Until that happens, I can not do anything. MOAR logs: https://drive.google.com/file/d/1zsFmOCvbLPk4V8fTq67KsyQGCPIMAHIs/view?usp=sharing

I don't and I think that is why our experience is different. IVA the nav utils work fine, but 3rd person vehicle view causes me problems. Could you share an assessment of your frame-rate when using that view-mode?

I just tried this and weirdly enough, there is a positive effect, but no real solution. In Kerbal-perspective mode, a tap of Right Mouse Button to enable free-look, the stutter quickly fades and stays away, even when I switch back the external view. But if the free-look is turn off, and Right Mouse Button is held down enable free-look in the external view, the stutter comes back with gusto. Rukhafi, do you use RPM? Or otherwise fly a lot in Kerbal-perspective mode? Does anybody know if there is there some way to turn on a sort of debug mode for NavUtils?

Change the camera as in change the angle or the view mode?