[KSP >= 1.8.0] Bon Voyage - Under Lisias' Management - 1.5.0.0 - 2024-1007

[Lisias]

  As from 2024-1010 and under @maja agreement, I'm the New Management for Bon Voyage.

In a Hurry:

• Current Release:  1.5.0.0 for KSP >= 1.3 (2024-0921)
  • It works from KSP 1.8.0 to KSP 1.12.5! Seriously!
    • How to check Compatibility on CurseForge.
  • IMPORTANT
    • read this post before updating!
  • Downloads
    • on CurseForge. Soon™
    • on SpaceDock (for CKAN users). Soon™
    • on GitHub (for manual and/or KSP-AVC users). 
• Relevant Notes
  • Bon Voyage only kicks when the craft is on rails.
    • You need to switch scenes, or focus a vessel beyound the current physics range!

 

Spoiler

• Old thread: on Forum.
• Project:
  • Source: on GitHub
    • Licensed under GPLv3
  • Change Log.
  • Known Issues Mandatory Reading
  • Issue Tracking (You can check what I'm doing here!)

Description:

What's the best way of getting science from celestial body? The answer is DRIVE!

What's the best way of delivering ore or supplies from distant location to your base? The answer is make your wheels rolling and ships rowing!

But did you try to drive for 110 km for two hours, avoiding obstacles and keeping your speed in sane limits? It's not fun anymore.

Don't worry!  Automagic Industries brings you a new autopilot, which reduces driving accidents by 100%. Bon Voyage is here and it will drive your rovers and ships in background!

Credits:

Contributions From:

• RealGecko. [original release thread]
• Maja [previous release thread]

And future new features/bugs/mishaps from yours truly.

Support:

I need help in order to proper help you.  Open the spoiler for instructions about how to get support:

Spoiler

Please provide:

• A concise, textual description of the problem
  • Mentioning the KSP version and the TweakScale version involved
• A screenshot of the problem
• When applicable, the .craft file with a vessel that have the problem
• When asked, the KSP.log and output_txt log from Unity.
  • See this article for instructions.
  • The Player.log changed location:
    • On MacOS
      • For KSP < 1.8, they are on ~/Library/Logs/Unity
      • On KSP >=1.8, you will find the Player.log on ~/Library/Logs/Squad/KSP/
    • On Windows
      • On KSP >=1.8, you will find the Player.log on C:\Users\<USERNAME>\AppData\LocalLow\Squad\KSP\
    • On Linux
      • On KSP >=1.8, you will find the Player.log on ~/.config/unity3d/Squad/KSP/
  • Publish the files on DropBox, Google Drive or similar, and post the link so we can inspect it.
    • DO NOT paste the log on Forum, this causes a lot of problems and it's useless, as Forum also truncate the file
      • It's ok to paste small excerpts to pinpoint something, but we still need the full KSP.log and Player.log in order to help you/
    • Do not use pastebin, gist or similars. They have a pretty small cap on the file size, and will truncate the log rendering yet more useless
  • Imgur is a good choice for publishing screenshots when needed.

Be sure to quit KSP before copyong the KSP.log, otherwise we risk losing information due the internal file buffers (technical thingy, it's a way to make writing files faster by consolidating lots of small writes into a big one).

Using the Issue Tracker is highly encouraged, as GitHub provides services that make everything above easier. You can open an issue there, and call me here pinpointing there to be sure to get my attention.

Thank you.

Navigate Safe!

[Fizzlebop Smith]

One of my favorite unsupported mods, thank you for absorbing this into you management umbrella. 

 

This made my morning. Truly excited, thank you.

[bright Universe]

After installing the Near Future Electrical - Decaying RTGs mod, RTG generation does not count towards the generated power, resulting in the inability to use BonVoyage

Edited November 3, 2024 by bright Universe

[Lisias]

On 11/3/2024 at 6:01 AM, bright Universe said:

After installing the Near Future Electrical - Decaying RTGs mod, RTG generation does not count towards the generated power, resulting in the inability to use BonVoyage

Known issue. Essentially BonVoyage knows only about Stock modules (with a few exceptions). I need to implement support for 3rd party modules too,

Edited November 5, 2024 by Lisias
Hit "Save" too soon

[omegalex]

On 11/5/2024 at 6:25 AM, Lisias said:

Known issue. Essentially BonVoyage knows only about Stock modules (with a few exceptions). I need to implement support for 3rd party modules too,

Looking forward to this, since the new rtg's that come with NF Electrical are much more convenient to use

[Lisias]

22 minutes ago, omegalex said:

Looking forward to this, since the new rtg's that come with NF Electrical are much more convenient to use

I don't think I will be able to deliver this for Xmas, but I'm somewhat confident that it will be released early January.

Right now I'm working on fixing my bag of tricks, fixing some long standing stupidities and creating some others that I know it's going to be used, including on BV.

Spoiler

On a side note, I think I may had found Yet Another Unity Idiosyncrasy™ - if I confirm that behaviour on other KSP releases (right now, I just confirmed it on 1.4.3), I will write Yet Another Rant Post© about.

 

[omegalex]

On 12/9/2024 at 9:28 PM, Lisias said:

I don't think I will be able to deliver this for Xmas, but I'm somewhat confident that it will be released early January.

Right now I'm working on fixing my bag of tricks, fixing some long standing stupidities and creating some others that I know it's going to be used, including on BV.

  Reveal hidden contents

On a side note, I think I may had found Yet Another Unity Idiosyncrasy™ - if I confirm that behaviour on other KSP releases (right now, I just confirmed it on 1.4.3), I will write Yet Another Rant Post© about.

 

No worries, take your time! I'm also having my own issues with ksp constantly crashing in the VAB and especially in the SPH (freezes or screen turns into a color), sometimes followed by an unity crash message. It's now happening to totally accurate battle simulator too.

Even if I tried to play ksp, I can't even build one tiny satellite before the game crashing in 3-5 minutes...

I'll still be looking forward to this mod, no matter how long it takes.

Happy holidays! (soon to arrive)

[Lisias]

9 minutes ago, omegalex said:

No worries, take your time! I'm also having my own issues with ksp constantly crashing in the VAB and especially in the SPH (freezes or screen turns into a color), sometimes followed by an unity crash message. It's now happening to totally accurate battle simulator too.

Yes, I had detected something similar this weekend. I'm pretty puzzled why this started to happen only nowadays - on a 1.4.3 that I used to do some testings 3 months ago and the problem didn't manifested before.

Interesting information you provided, TABS is made on Unity, exactly as KSP.

Too much coincidences - but, still, coincidences: Correlation does not imply Causation.

[omegalex]

The same issue happened on Assassins' Creed Black Flags today (only once), before I installed a new nvidia driver. The issue seems to be gone, but I haven't tried KSP yet. Must be a coincidence, since Subnautica also runs on unity, but it never crashed like that (not even last week).

 

Edited December 18, 2024 by omegalex

[Lisias]

On 12/18/2024 at 10:10 AM, omegalex said:

The same issue happened on Assassins' Creed Black Flags today (only once), before I installed a new nvidia driver. The issue seems to be gone, but I haven't tried KSP yet. Must be a coincidence, since Subnautica also runs on unity, but it never crashed like that (not even last week).

I just remembered you today.

I still like to use an old MacOS Mojave for gaming, as most of my favorite games are 32 bits (yeah, I know - but I'm used to this old crap, and for everything else, I have a Steam Deck so...), and the best KSP to run on this old MacCrap is... KSP 1.4.3. From KSP 1.4.4, they introduced a thing called PQS cache to optimize the PQS by using the GPU, and this eats VRAM, something that this rig doesn't have in abundance and the net result is that the PQS cache benefits doesn't outweigh the cost on this rig. So KSP 1.4.3 it is.

And I'm used to run this thing on this rig for years. I literally know when something weird is going to happen (not rarely, knowing exactly what will happen) just by the pattern of the stuttering what, in the end, helps a bit while trying to figure out what gone wrong. And the net result of this is that I have a KSP 1.4.3 installment that is the same for 2 or 3 years already - no updates, the same add'ons, the same savegame, running on the same MacMini under the same MacOS - and without any "security updates" since I don't even remember when.

Well... These days, something different started to happen. Mojave have a very nasty misfeature: if you ran out of VRAM, things start to get weird while switching spaces on Mission Control, pieces of the screen are not drawn or drawn wrongly, you name it - and then we get a Kernel Panic. This happens when I really abuse the number of Browser tabs opened at the same time.

I had also detected that playing videos with sound increases the chances of a Kernal Panic to happen even before the video glitches, and my current working theory is that as the programs start to eat swapfile, Mission Controls start to get sluggish as you switch Spaces because it tries to update all the miniatures on the Windows on different spaces, and with something injecting sound into the Event Queue 44.1K times per second, the Event Queue grows faster than is consumed due Mission Control monopolizing the CPU for itself.

Great, it makes sense - but what the hell does that have to do with the subject under our noses currently?

Well... I had detected a new misbehaviour on KSP 1.4.3 that wasn't happening before! On the very same freaking installment, if I left KSP running unattended for hours, once I come back to it the rig starts to behave like I described above but with both symptoms at the same time, leading to a Kernel Panic inside Darwin! Even KSP itself starts to fail to draw some widgets, clearly suggesting a VRAM exhaustion problem on a machine that was left unattended for hours.

I'm considering that perhaps Unity is leaking VRAM on MacOS? But if I'm right, why this wasn't happening some months before when I had played with this KSP installment the last time? I usually left the game in pause for hours when working on my professional rig, instead of closing KSP and opening it again every time. So I'm pretty sure I'm not doing something different these days.

But, yet, I have this Kernel Panic happening these days on use cases where it didn't happened months ago.

It's the same KSP, the same machine, the same MacOS (without any new patches, for sure). Even the installed Add'Ons are the same.

I'm trying to figure out some more deterministic test case to reproduce the issue reliably - right now, there're still to many loose ends to be sure about the real trigger of the problem.

Anyway, I though you may be interested on it.

[Fizzlebop Smith]

On 12/10/2024 at 1:45 PM, Lisias said:

Yes, I had detected something similar this weekend. I'm pretty puzzled why this started to happen only nowadays - on a 1.4.3 that I used to do some testings 3 months ago and the problem didn't manifested before.

Interesting information you provided, TABS is made on Unity, exactly as KSP.

Too much coincidences - but, still, coincidences: Correlation does not imply Causation.

I have had unity crashes recently and not really sure what is going on. It only happens rarely and so far the games seem to have managed a dump save prior to crash bc KSP persistent was up to date.

I forget the other game but my KSP is largely unmodified for months. Aside from a few updates I loaded.

I think it has something to do with a recent Windows update / amd driver but that only because I had so many issue with last few AMD / Windows updates.

But again.. my process analysis / root cause skills lie in manufacturing production chains.. not black magic.

[AmanitaVerna]

22 hours ago, Lisias said:

I had also detected that playing videos with sound increases the chances of a Kernal Panic to happen even before the video glitches, and my current working theory is that as the programs start to eat swapfile, Mission Controls start to get sluggish as you switch Spaces because it tries to update all the miniatures on the Windows on different spaces, and with something injecting sound into the Event Queue 44.1K times per second, the Event Queue grows faster than is consumed due Mission Control monopolizing the CPU for itself.

Great, it makes sense - but what the hell does that have to do with the subject under our noses currently?

Well... I had detected a new misbehaviour on KSP 1.4.3 that wasn't happening before! On the very same freaking installment, if I left KSP running unattended for hours, once I come back to it the rig starts to behave like I described above but with both symptoms at the same time, leading to a Kernel Panic inside Darwin! Even KSP itself starts to fail to draw some widgets, clearly suggesting a VRAM exhaustion problem on a machine that was left unattended for hours.

Do you happen to have this mod installed? Because I'm pretty sure it either has a memory leak or eats way more RAM than it reasonably should, which might also cause problems with your OS.

 

[Lisias]

19 hours ago, AmanitaVerna said:

Do you happen to have this mod installed? Because I'm pretty sure it either has a memory leak or eats way more RAM than it reasonably should, which might also cause problems with your OS.

Nope. The affected rig does not have it installed.

I will investigate your report - chances are that this may be a unholy interaction with some other add'on, because I didn't notice an memory leak while testing it. Granted, I didn't really played with it this year so it may be something that felt through the cracks. Anyway: https://github.com/net-lisias-ksp/BonVoyage/issues/2

=== POST EDIT ===

@AmanitaVerna, I did a quick run on the problem today (while cleaning up the Xmas Mess ). I found absolutely no evidence of misbehaviours related to memory on BV.

Full report here:https://github.com/net-lisias-ksp/BonVoyage/issues/2#issuecomment-2561842873

As explained here, this doesn't means that you didn't found something. It only means that BV is a side effect of the problem, not it's cause - correlation is not causality.

My best shot about your problem can be explained on this thread:

https://forum.kerbalspaceprogram.com/topic/203645-how-to-play-ksp-with-unity-2019-on-old-potatoes/

Edited December 25, 2024 by Lisias
post eedit