Construction DeltaV Tool not working when switching between different launch assemblies in the same workspace [only the first assembly placed in the VAB will have DV calculated]

[Vl3d]

Reported Version: v0.2.0 (latest) | Mods: none | Can replicate without mods? Yes 
OS: Windows 11 | CPU: AMD Ryzen 5 7600X | GPU: Nvidia RTX 4070 | RAM: 32 GB DDR5

 

Delta-V Tool not working when switching between different launch assemblies in the same workspace - see video.
This prevents me from building and testing multiple variants of first stages in the same workspace. I really want to be able to build first stage rocket families with variable tonnage to LKO.
Also, please add a utility weight to the game. Please!

 

Included Attachments:

 

Edited December 23, 2023 by Spicat

[The Aziz]

Not only the tool but the whole dv readout for the assembly.

[Faer]

Reported Version: v0.2.0 (latest) | Mods: none | Can replicate without mods? Yes 
OS: Windows 10 | CPU: AMD Ryzen 5 3600 6-Core Processor | GPU: NVDIA GeForce RTX2060 | RAM: 16Go

In the VAB, If you add a second vehicule to the workshop, its delta V readouts, TWR and burn time will always be 0.

- If you delete the first ship, the delta V is correctly calculated for the second vehicule, now alone in the VAB.
- Clicking on the vehicule selection icon above the vehicule doesn't update dV if it's not the first ship created in the workshop.
- Changing vehicule by using the launch assembly feature doesn't update dV.
- Updating staging of the second ship doesn't update dV.
- Adding new stages to the second ship doesn't update dV.
- Fuel mass is correctly shown either way.

From what I understand, It must be something related to the first ship being the "primary focus" of the deltaV readout, and the game is trying to read the values of the first ship while looking at the second one. Since no parts of the first ship exists in the second one, the dV reading will always be 0.

Issues that might be related :

 

Included Attachments:

[WingC3]

Reported Version: v0.2.0 (latest) | Mods: none | Can replicate without mods? Yes 
OS: Win 11 23H2 | CPU: AMD Ryzen 9 3900XT | GPU: nVidia GeForce 3900 | RAM: 32GB

 

For reasons I have been unable to determine, craft in the VAB will sometimes begin showing 0dV for all of their stages. Reloading does not resolve the issue, and separating and re-attaching parts doesn't solve it either.  I have observed a few things, though, that may help:

1. The issue does not persist to the launch pad. Loading the craft there will display dV values correctly. So, it is unique to the VAB.

2. If you select the vehicle and copy it to a new workspace, dV calculations are done correctly.

2. It does not affect all assemblies within the same craft file, it can affect only one of them. (See attached screenshots and craft file: one vehicle is affected while the other is not.) So this appears to be an issue with workspaces containing more than one assembly.

3. It MAY have some relation to attaching one assembly to another and then separating them again, but even then, not all assemblies are affected.

4. In the deltaV info for the stage, it does not show a planetary body AND does not allow you to select one. So I peaked into the JSON, and saw that this was reflected there too:

 "StageID": 0,
                "IsActive": false,
                "DeltaVSituation": {
                  "CelestialBody": null,
                  "IsAtmosphere": false,
                  "Altitude": 0.0
                }

HOWEVER, changing this value back to "Kerbin"  does NOT resolve the issue.  The root cause lies elsewhere.

 

Included Attachments:

DunaMissions.json

Edited December 23, 2023 by WingC3
Additional Info

[Vortygont]

I got rid of this bug by saving my craft file again. Maybe after saving game updates all states of current VAB craft

Edited December 20, 2023 by Vortygont
Typo

[tpidgin]

resaving the craft file and quicksave/quickload worked once for me to fix this, but now that no longer works either.

[The Space Peacock]

@Faer merged your report

[Faer]

Nice thank you !

[SuperBrutal666]

Also experiencing this. Thanks for reporting!

Edited December 22, 2023 by SuperBrutal666

[The Space Peacock]

@WingC3 merged your report with this one

[Papow]

I tried building a Duna mission that required multiple launches in a single workspace. Ran into this same issue. The second vehicle in workspace has Delta V calculation that always shows 0 m/s. I could not find a way to get it to show. Saving and reloadin g save file, saving and reloading workspace, quitting game, none of these changed behavior. 

When switching between vehicles in a workspace, I would expect that the Delta-V calculation for all vehicles can be seen.

[Ghosty141]

The only workaround I found yet is either launching the craft or deleting the other one. This should be high priority since it makes building bigger ships **really** annoying since you always gotta delete stuff to check dV.

[yijian huang]

Reported Version: v0.2.0 (latest) | Mods: none | Can replicate without mods? Yes 
OS: Windows 10 | CPU: Intel i5-11400F | GPU: GeForce RTX 3060 | RAM: 16GB

As shown in the attached screenshot, the dv of my rocket, the current launch assembly, is displayed to be zero, abnomral.

It obviously has a non-zero dv.

Please try to reproduce with my uploaded craft file.

Included Attachments:

CZ2B.json

[The Space Peacock]

@yijian huang merged your report

[Anonymous Bug Reporter]

Reported Version: v0.2.0 (latest) | Mods: none | Can replicate without mods? Yes 
OS: windows 11 | CPU: 3950x | GPU: 2080 super | RAM: 128

the VAB thinks my craft has a delta V of zero when it should be in the thousands.

Included Attachments: