Disabling damage on Kerbal Foundries wheels causes Bon Voyage to read tracks as "not online"

Reproduction steps:

Use a clean 1.10.1 install

Using CKAN, install Kerbal Foundries 2, KSPWheel (dependency,) and the last version of BV compatible with 1.10.1 (although I've reproduced this with the 1.11 version on 1.10.1)

Start a new game. Set KSPWheel settings for "Wear and damage" to "NONE." It doesn't appear to matter whether this is done in the initial game setup, or later on.

Use cheats to give max tech/max VAB (though I don't think the latter is necessary now that I think of it...)

Build a simple rover in the SPH - 2x2 structural panel, tracks on the side, BV controller, probe core of some flavor to provide unmanned control.

Launch.

Open up BV controller window. Observe that "wheels aren't online!" and max speed is 0m/s

Phase 1:

• main window
• settings window
• controller window
• module
• base controller
• rover controller
• localization
• Wiki
• update forum thread

Phase 2a:

• KSPWheel support when updated for 1.5.x
• Kerbalism support when updated for 1.5.x - partial, only solar panels are registered
• Kopernicus support when updated for 1.5.x
• KSP Interstellar support when updated for 1.5.x
• NF Electrical and Solar support when updated for 1.5.x
• WBI support when updated for 1.5.x
• USI support when updated for 1.5.x
• finding a main star in a binary systems

Phase 2b:

• catchup process
• batteries
• fuel cells
• the rotation fix is still on the table
• move a rover up/down if it's wrongly placed
• Unmanned vessels must have a working connection

Phase 3:

• someone said ship controller? 😄

Currently, Bon Voyage does not acknowledge RTGs from Realism Overhaul, and doesn't even run on rover batteries. There seems to be no workaround except for setting infinite electricity in KSP cheats menu, which is a hassle to do every time.

A proper patch would be preferred, but if at least BV would allow to disable electricity check in it's settings, it would work too.

When KSP app toolbar icon is not selected in the settings and the main window is closing, then exception is generated.

Submited to the old repo by @Snakedog49

Whenever I load in my rover from doing a drive. If it is halfway through the ground. It explodes. If it is fully clipped through the ground then it falls to sea level and explodes. But if the whole rover is above ground it just falls down. And while I know explosions are cool and all its killing my crew members and a lot of money is being invested in rescue missions that end up exploding because of this. It makes me afraid to open my rovers after sending them to a destination. This has been happening in the most recent version of the game. Please fix!

Using fuel cells with infinity fuel cheat and without any fuel (missing tanks) causes the BV to report "Not enough fuel" when activating the autopilot (RoverController.Activate)

@kovakthemost Hi, can you check if this translation is ok?

#LOC_BV_HeightOffset = Height offset
#LOC_BV_HeightOffset = Смещение по высоте

Mod is using KSPWheel, but there is probably issue with wheel stress, because BV reports, that wheels are in the air.

Kerbal Foundry treads prevent the controller from working, regardless of wheels or anything, it simply will not respond when attempted to use.

Test Kerbalism support PR in test branch

The current link of the version file lead to 404 error. The "Versioning" directory is missing.
It should be replaced by https://raw.githubusercontent.com/jarosm/KSP-BonVoyage/master/GameData/BonVoyage/Versioning/BonVoyage.version

While it'd be ideal to have a button that figures out the right rotational vector from the current position, I get that the math there is tricky. But an arrow showing which way the vehicle will be rotated when next loaded would save a ton of aggravation. An arrow pointing "up" from the root part would suffice, maybe just showing whenever the BV control panel is open?

If drawing that is tricky, a button that calculates how far the vehicle would have to be rotated from its current position to match the current configuration could also work; orient the vehicle correctly, press the button, and if you've picked the right rotational vector it should report close to (0, 0, 0).

NFA has Advanced Propeller Engines. They consume EC and IntakeAtm (basically, generalized IntakeAir that doesn't depend on an oxygenated atmosphere).

This mod thinks IntakeAtm is a regular fuel and therefore doesn't account that IntakeAtm is basically infinite when you're in a planet that has atmosphere.
This is a problem since when your rover/ship is mainly powered by these propeller engines, you can't really use Bon Voyage without it just stopping after 2 seconds.

Fixing this should be easy:

• Adjust speed based on atmospheric pressure at the vessel's current altitude if it uses engines that consume IntakeAtm.
• If celestial body has no atmosphere, then show a message that basically says "Rover/Ship stopped: no atmosphere"

Pretty often when returning to the rover, the game spawns it 200m above ground. Even if the area is pretty flat. It seems to happen more often the more polar your position is. This is very frustrating, since the mod should check the position at loading the scene and eventually correct it.

When "set rotation" is selected, and I switch to an active rover, the rover will fall apart. Since the vehicle has to be controlled (e.g. not from tracking station), there's no way to move the rover to another position for another attempt.

As a workaround, I disabled the rotation set, but the vehicle is in freefall when I switch to the scene and hits the ground hard.

Would there be any way to implement a landing set system like KRASH or HyperEdit?
https://github.com/linuxgurugamer/KRASH
https://github.com/Ezriilc/HyperEdit

Steps to reproduce:

1. Create a new rover and launch from the SPH
2. Set a rover destination (been using ~5km north for testing)
3. Make sure "Disable rotation" is disabled (e.g. rotation enabled)
4. Switch away from scene, warp ahead ~10m
5. Re-focus vehicle.

Currently using KSP 1.12.3.3173 and Bon Voyage 1.4.1

As I wrote on the forum thread, I think it would be neat to be able to send rovers somewhere without switching to them. This would be especially useful seeing how you have to switch away from a rover for it to move, and it's a little weird to constantly have to move between ships to do a multi-step journey. It would also work well with mods that allow useful things to happen in the background, such as Kerbalism science experiments.

Done by @Raven-233486

https://drive.google.com/file/d/11T_AvN3InqOFEkXR9c3zs4XbiuziXgYp/view?usp=sharing

Curved solar arrays are not detected.

I've had a devil of a time using Bon Voyage on my mun rover. Either my rover spawns too low, causing its wheels to explode and launching it up, or it spawns really high up. I think I now know why.

I've been using SCANSAT to make waypoints to use as destinations for Bon Voyage, to ensure I end up at a location with little slope (it wouldn't be the first time I came out right over the edge of a cliff). But the waypoints get created at a couple of kilometers altitude, and my rover drives up to that altitude when I use the waypoint method of selecting a destination. That means it can end up inside the terrain if it's high up, or far above it if it's low.

I consider this a bug in BV. When using waypoints, it should adjust the destination altitude to match the local terrain altitude, not use the waypoint altitude verbatim.

(Wrong first assumption of bug origin - Internal LFO of Malemute rover is not detected when using fuel cells.)

When fuel cell contains more then one ModuleResourceConverter module, then every module is processed. In reality, only one module can be active.

When you have installed Kerbalism, the USI reactors are no longer recognized. This is because Kerbalism replaces the ModuleResourceConverter with a ProcessController module:

MODULE
{
name = ProcessController
resource = _Nukereactor
title = Fission reactor
capacity = 1
}

The capacity is 1/10th of the generated EC.

I don't know if you handle CKAN update for this mod yourself or if someone else do this (there is no statement on the forum post about it). If someone else manage CKAN update, apologize for disturbing you whit that and just close the ticket.
If you manage it: the source code URL link to RealGecko's repository on GitHub instead of this one.

KSP.log

Hello, I am using a rover design that uses the white rover body rotated, and on top of that I placed a kerbal seat. After landing, I tell that from now on the kerbal seat is controlling the rover, so the navball gets correct. Without this the navball would tell me I am seeing the sky.

When bonvoyage returns to my rover, it restores it seeing the sky. Coincidence? I am supspecting that you are using the direction of some kind of default control part, but the adequate startegy would be to look up the one that had the control when the mission was unloaded to maintain proper direction. Or to read the direction some other way that is universal.

Bon voyage has flipped/destroyed 2 of my rovers and I am playing in "ironman mode". This makes me sad. 😄

Keep up your good work! 👍 Thank you!

Is it possible, to extend BV functionality to Kerbals?

Add option to configure additional height offset in meters above terrain. Default is 0, that means no offset.

via Crixomix: While I'm here, can I request a feature/setting. That when you go to "select on map" it doesn't show the biome? I'd prefer to "need" to use scansat to figure out where biomes are and make my own waypoints.

via tomf: I think that with interstellar bon voyage is seeing the same problems as mentioned with kerbalism a few pages back. Interstellar has replaced the modules on all the solar pannels to ones that bon voyage doesn't recognise. Would it be possible to add this support as well?

To fully support the latest versions of NFE, you'll need to also support ModuleSystemHeatFissionReactor.
I think this line here is the one you'll need to update.

Originally posted by @johnabsher in #37 (comment)

The Bon Voyage Module needs bulkheadProfiles = srf added to the file: GameData\BonVoyage\Parts\part.cfg

https://forum.kerbalspaceprogram.com/index.php?/topic/181078-vab-category-fail/#comment-3517556

Docking / undocking vessels do not always seem to have the Bon Voyage autopilot follow the appropriate module.

Steps to reproduce:

1. Have a Bon Voyage module in the Kerbal stock inventory system of a lander.
2. Have a Kerbal Engineer attach the Bon Voyage module to a separate rover with a docking port.
3. Dock the rover to the lander.
4. Undock the rover from the lander.
5. The Bon Voyage control panel was no longer available on the rover with the Bon Voyage module.
   Additionally, the Bon Voyage control panel is available on the lander, which does not have the Bon Voyage module.

Closing the game and restarting it caused the control panel to reset, making the Bon Voyage control panel available on the rover.

Sup.

I've noticed that in the most recent KSP version, if you start your game, and switch to any vessel in space, your Scatterer / EVE shaders will not load,

And an actual worse problem, is the IVA itself being unrendered and a seethrough when you try going IVA to a vessel you switched from.

All this is simply manageable by switching to those vessels, and going to the Tracking Center prior doing any switch from the Bon Voyage control panel,
That causes the Kerbin to be rendered with all its fanciness as normal, and the vessel you switch to, render its IVA kerbals and interior alright.

Didn't used to be like this though.
Is it perhaps something to do with compatability with the latest KSP 1.12.3 version?

Config values aren't probably loaded correctly in KSP 1.9.1. Check needed.

Should improve usability and reduce bug reports (suggested by Jognt)

Yeah, it will spare my nerves :D - maja

Can you make the Autopilot Module EVA Construction Mode compatible?

I fixed it, so you can add it in your Inventory:
MODULE { name = ModuleCargoPart packedVolume = 100 }

In my opinion 100l ist a good volume.

@vinix38 Hi, can you check if this translation is ok?

#LOC_BV_HeightOffset = Height offset
#LOC_BV_HeightOffset = Décalage en hauteur

• Kerbal Foundries
• Kopernicus
• Umbra Space Industries
• Wild Blue Industries
• Near Future
• KSP Interstellar Extended
• RemoteTech
• Feline Utility Rovers
• Community Tech Tree
• Kerbalism
• Toolbar

From forum:
It appears to be to do with when you decouple a rover from a landing craft (specifically when the detached rover wasn't the original root part), resulting in the bon-voyage control menu not opening.

The same also seems to happen (though not always) when constructing a rover with KIS/KAS (which is also fixable by going to the space centre, and then back to the rover)

via Crixomix: Quick question. Are the "reserve battery" packs from AmpYear supported? Those would be a cool way to enable night rides on rovers.