maja

I don't see any issues with the parachutes and launch clamps in the stock KSP 1.8.1 (Restock 1.0.0). You will probably need to figure out, which mod(s) are messing with them.

I tried to find that yesterday. If it is there, then I didn't saw that either.

What's interesting, it's only two habs from three.

I found, that this patch still isn't working and module USI_ModuleFieldRepair isn't added to parts. I brought this to the MM thread and the reason for the nonfunctionality is, that you can't have OR syntax in HAS block. I submitted PR# 142 to fix it. In the MKS repository is related issue for this: Issue# 1449

That may be it. The second one will not be working on the part I tried, because it doesn't have MaterialKits as I recall. I must test it more. Thanks EDIT: When I splitted it, it worked. I can continue in my game

Hi, I found in USI Tools two patches, that aren't for some reason applied. I tried to find a solution but to no avail, so I'm here The two patches are following: @PART[*]:HAS[!MODULE[USI_ModuleFieldRepair],@RESOURCE[Machinery|EnrichedUranium|DepletedFuel|Recyclables]]:FOR[USITools] { MODULE { name = USI_ModuleFieldRepair } } @PART[*]:HAS[!MODULE[USI_ModuleRecycleBin],@RESOURCE[MaterialKits]]:FOR[USITools] { MODULE { name = USI_ModuleRecycleBin } } If I omit the @RESOURCE part in the HAS block, then the patches are applied as intended. What's wrong there?

@aluc24 Kerbalism will be the culprit. It removes modules of mods and use it's own in a lot of cases. I had issues with it before KSP 1.5, so I ended with accepting zero power of a rover when Kerbalism was present, but I withdrawed this "support" when I did overhaul of BV for KSP 1.5.1. I don't know, if I want to try it again and start fully supporting Kerbalism. How many of you, Kerbalism users who are using BV, are here anyway?

The same. KSP 1.7.3, BV 0.5.3, NF Electrical 1.0.3. The support for NF is there a long time. But I see, that you have differnt PAW on the reactor than I (see bellow). Don't you have other mod, which can change the reactor's behavior?

https://en.wikipedia.org/wiki/My_Name_Is_Nobody

I checked it (KSP 1.8.1, BV 1.0.1, NF Electrical 1.1.0) and it worked as intended.

(sorry ) There was change in the tech tree node for the part, because there are now part updates later in the tree, which affects unmanned penalties. Check your difficulty settings, because buying parts depends on them.

I see. For some reason, Total commander plays games with me...fixing it @HebaruSan Fixed, thanks.

New update! 1.0.1 Changes Minimum height of a rover over the terrain was changed to avoid some clipping issues KSP 1.8.1 compatibility

I noticed it yesterday on some parts from other mods (Near future mods), so it can be stock issue.

It's the default which works for the most rovers with some sort of a cabin. It also depends, where the real top of the root part (RoveBody in your case) is.

No problem. I understand, that you must translate it to/from english, but I can't translate your text, if I'm looking at it on my phone. Like small bugs

Follow the section 3, there it is. I started with this tutorial a few weeks ago, then leaved it for a while and must start once again, so I can't help you more right now

https://github.com/jarosm/KSP-BonVoyage/wiki/Settings Look for Rotation vector advance tweakable section English please.

Which tutorial? DialogGUI? If yes, then one of the parameters of a button constructor is OnClick function. Just pass it without parenthesis (e.g. OnClick) to the constructor.

English isn't my first language, neither yours as I understand, but I try to explain it to you as best as I can When a rover moves behind the scene, the Bon Voyage sets its latitude, longitude and altitude based on computations and data about terrain on that spot. The problem is, that the terrain information isn't exact, so the rover is sometimes underground or too high. Bon Voyage handles these situations by moving the rover up or down when you switch to it during a ride or after it arrives to the destination. How high or low BV moves the rover is computed from the position of colliders of rover's parts. If the colliders are wrongly defined, then the computations are wrong and the rover can be moved too high or too low, so it clips to the terrain and after resuming the physics it explodes. I tested your rover with modified Bon Voyage, which skipped the move down step, so the tested rover wasn't moved and stayed above terrain. That means, that it wasn't clipping through the terrain and therefore no explosion happened. Now I must find what is the reason, that the rover is moved too low by BV. Is it wrong collider? Is it the rover construction? Or is it something else?

@jaunco325 I think, that there are two possible reasons for a failure. The collider for little rover wheels is badly defined and BV gets wrong informations about the lowest point of the rover or the rover is too wide and therefore clips on one side to the terrain. I disabled the move down feature (it can be done only by editing the code) during my tests and the rover was high enough to not clip to the terrain. I must do more tests with different rovers and wheels to decide, which reason it is.

You have unfinished sentence there:

I don't see any exceptions regarding BonVoyage, but you are using bunch of mods, that are not compatible with KSP 1.8.*. This could lead to various problems. If you have a save file from before switching to that problematic rover, send it to me.

On Windows: <KSP folder>\KSP.log c:\Users\<username>\AppData\LocalLow\Squad\Kerbal Space Program\Player.log

The function is switched off, if World Stabilizer or BD Armory is present, because they are doing the same thing - Moving vessel up or down, to get a clearance over a terrain and avoid clipping of parts. But there are a few cases, where it could go wrong (the terrain is too bumpy or steep, the vessel is too long and clips somewhere, part dimensions are wrongly defined) and I can't do a thing with it, because BV is trying to find the lowest point of the vessel and then move it up over the terrain.