Jump to content

Velocity of Target Not Displayed as Relative to Target [Anth12 Edit: Added Proof of 0.1.4.0 fix]

Davidian1024

By Davidian1024
in v0.1.3

 Share

Recommended Posts

Davidian1024

Davidian1024

Posted
Posted (edited)

Reported Version: v0.1.3 (latest) | Mods: none | Can replicate without mods? Yes 
OS: Linux Ubuntu 20.04.6 | CPU: AMD Ryzen 5 3400G | GPU: NVIDIA GeForce GTX 1080 Ti | RAM: 16GB

[Anth12 Edit: Adding Save Files + Video for 0.1.3.2 Repo and 0.1.4.0 Fix Confirmation]
---------------------------------------------------------------
Happens When Undocking From a Craft and then Re-targetting.
Video Evidence:
0.1.3.2 Bug Replication:
https://youtu.be/XPd0cSTucoI
0.1.4.0 Working as intended:
https://youtu.be/pUm5xS7mnO8

Steps to Replicate in 0.1.3.2:

  1. Load quicksave_6.json
  2. Undock the craft with the pod
  3. Target the craft undocked from.

---------------------------------------------------------------

Specs: (Obtained from Steam via Help > System Information)
 

Spoiler

Computer Information:
Manufacturer: ASUSTeK COMPUTER INC.
Model: PRIME B450M-A
Form Factor: Desktop
No Touch Input Detected
Processor Information:
CPU Vendor: AuthenticAMD
CPU Brand: AMD Ryzen 5 3400G with Radeon Vega Graphics
CPU Family: 0x17
CPU Model: 0x18
CPU Stepping: 0x1
CPU Type: 0x0
Speed: 3700 MHz
8 logical processors
4 physical processors
Hyper-threading: Supported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Supported
SSE41: Supported
SSE42: Supported
AES: Supported
AVX: Supported
AVX2: Supported
AVX512F: Unsupported
AVX512PF: Unsupported
AVX512ER: Unsupported
AVX512CD: Unsupported
AVX512VNNI: Unsupported
SHA: Supported
CMPXCHG16B: Supported
LAHF/SAHF: Supported
PrefetchW: Unsupported
Operating System Version:
Ubuntu 20.04.6 LTS (64 bit)
Kernel Name: Linux
Kernel Version: 5.15.0-75-generic
X Server Vendor: The X.Org Foundation
X Server Release: 12013000
X Window Manager: GNOME Shell
Steam Runtime Version: steam-runtime_0.20230509.49499
Video Card:
Driver: NVIDIA Corporation NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2
Driver Version: 4.6.0 NVIDIA 530.41.03
OpenGL Version: 4.6
Desktop Color Depth: 24 bits per pixel
Monitor Refresh Rate: 60 Hz
VendorID: 0x10de
DeviceID: 0x1b06
Revision Not Detected
Number of Monitors: 2
Number of Logical Video Cards: 1
Primary Display Resolution: 1920 x 1080
Desktop Resolution: 3840 x 1080
Primary Display Size: 20.75" x 11.65" (23.78" diag), 52.7cm x 29.6cm (60.4cm diag)
Primary Bus: PCI Express 16x
Primary VRAM: 11264 MB
Supported MSAA Modes: 2x 4x 8x 16x
Sound card:
Audio device: Nvidia GPU 82 HDMI/DP
Memory:
RAM: 15913 Mb
VR Hardware:
VR Headset: None detected
Miscellaneous:
UI Language: English
LANG: en_US.UTF-8
Total Hard Disk Space Available: 467875 MB
Largest Free Hard Disk Block: 51023 MB
Storage:
Number of SSDs: 9
SSD sizes: 2000G,2000G,1000G,500G,63G,4510M,0B,0B,0B
Number of HDDs: 0
Number of removable drives: 0

Severity: Med (This feels like it's on the high end of medium. I can see it causing docking to be difficult if not impossible, as this information can be critical to performing docking maneuvers.)

Frequency: High (This has happened every time I've performed docking maneuvers since version 0.1.3 came out. It wasn't happening prior.)

Description:  The velocity display to the left of the Navball does not appear to display the speed relative to the target when target velocity is selected. In the screenshot below I parked the lower vehicle about 3 meters away from the command pod at the top of the picture. To be sure I was right, I left them about this far apart for at least a couple of minutes. The display continued to show the command pod being 3 meters away. This tells me the velocity relative to the target should be close to zero. But as you can see in the screenshot it's showing 5484m/s. Which is close to what my orbital and surface velocities were at the time.

DbjcwYC.jpg

Edited by Anth12
Changed Font to Default Colour. Black shows badly in Dark Mode
Link to comment
Share on other sites
Anth

Anth

Posted
Posted
6 hours ago, Davidian1024 said:

Description:  The velocity display to the left of the Navball does not appear to display the speed relative to the target when target velocity is selected. In the screenshot below I parked the lower vehicle about 3 meters away from the command pod at the top of the picture. To be sure I was right, I left them about this far apart for at least a couple of minutes. The display continued to show the command pod being 3 meters away. This tells me the velocity relative to the target should be close to zero. But as you can see in the screenshot it's showing 5484m/s. Which is close to what my orbital and surface velocities were at the time.

I had the number weirdly high when I had two crafts far apart like on the other side of the planet.
However, once I got them close together things corrected themselves.

In your screenshot the 3m icon was greyed out. Which means it shouldn't be the target.

In this screenshot the other craft is targeted because the icon is blue.

KESAeyh.png

Link to comment
Share on other sites
Davidian1024

Davidian1024

Posted
  • Author
Posted
33 minutes ago, Anth12 said:

In your screenshot the 3m icon was greyed out. Which means it shouldn't be the target.

Ok, I see that my "target" has grey text instead of blue.  I've never noticed that when things are targeted.  Maybe that indicates what's going wrong?

Either way they were definitely behaving as if they were targeting each other.  All the navball markers seemed to be what I'd expect.  I had both craft set to have the docking ports set as "control from here", and they were both targeting the docking port on the other craft.  That's basically how I've always done it.

Link to comment
Share on other sites
Anth

Anth

Posted
Posted
16 minutes ago, Davidian1024 said:

Either way they were definitely behaving as if they were targeting each other.  All the navball markers seemed to be what I'd expect.  I had both craft set to have the docking ports set as "control from here", and they were both targeting the docking port on the other craft.  That's basically how I've always done it.

Thanks. I will do further testing.

Link to comment
Share on other sites
BechMeister

BechMeister

Posted
Posted (edited)

Reported Version: v0.1.3 (latest) | Mods: none | Can replicate without mods? Yes 
OS:  Windows 11 Home  | CPU: Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz   2.59 GHz | GPU: NVIDIA GeForce GTX 1660 TI | RAM: Ram: 16,0 GB

 

Hello! 

I have had a few times were my "Target" Navball velocity setting doesn't show relative speed but my orbit speed. Which means I now have to subtract my target speed and orbital speed to get the difference.

Here is a screenshot for proof:

BxQq45G.jpeg

I at one point I thought I had found a fix - namely cycling through the vehicles some times makes them show the correct relative speed. Quick save Quick load does also some times work..

 

Edited by Anth12
Link to comment
Share on other sites
Davidian1024

Davidian1024

Posted
  • Author
Posted

So, today I tried to reproduce this again, and it's working fine.  I'm getting a target velocity close to zero while parked next to my target.

FWIW, the target label is grey.  @Anth12Is it supposed to be blue?  A separate display bug perhaps?

Link to comment
Share on other sites
Anth

Anth

Posted
Posted
5 minutes ago, Davidian1024 said:

FWIW, the target label is grey.  @Anth12Is it supposed to be blue?  A separate display bug perhaps?

Target Icon:
A targeted craft's icon should always be a different colour.
As for Two Possibly Related Issues:
If both issues happen 100% at the same time, then they could be related to each other.
Then personally I would report two separate bug reports and have them mention each other in that case.
That way the developers can't miss one of the issues because it's somewhere within the one post.

Link to comment
Share on other sites
  • 2 weeks later...
wjxway

wjxway

Posted
Posted

Definitely a bug. I encountered a similar problem today and yesterday when trying to dock two satellites together.

Viewing from satellite 1, I get a expected relative speed (<3m/s) when setting satellite 2 as target, but when viewing from satellite 2 when setting satellite 1 as target, I get several hundred meters per second, which is obviously wrong. Reloading the saves cannot solve the issue, while restarting the game can. I don't have any screenshots left unfortunately.

Link to comment
Share on other sites
  • KSP2 Alumni
Dakota

Dakota

Posted
  • KSP2 Alumni
Posted

Heya, we are aware of an issue where setting a target does not change the velocity shown to the correct Target velocity, but instead keeps it in Orbital mode. However, clicking on the Orbit velocity should allow you to cycle to Target mode which has the correct velocity. Is this the behavior observed?

@Davidian1024 @BechMeister @wjxway @Anth12

Link to comment
Share on other sites
BechMeister

BechMeister

Posted
Posted

@Dakota If you look at my screenshot specifically it is in "target mode" and shows the orbital velocity and not the target velocity. In reality the target velocity is something like 0.5 - 1m/s since its a engineless "drone" moving a fuel tank around, with only RCS thrusters available. (it would be very impressive indeed to accelerate the drone to a 2k m/s relative velocity to the target with only RCS thrusters)

I have not been studying the fenomen - So I dont know the behavior for certain, but I often find that when i launch rockets from KSC to LKO to rendezvous with my station the target velocity works. Its when I undock my drones, that are already in orbit, from my station to grab the cargo from the rocket and move it to the correct position and dock, that the drone does not show the correct target velocity.

I wonder if its because the game wrongly sets the orbit velocity as 0 and then just add the relative speed on top of that.. because there is a difference between the orbit velocity and the target velocity... but its bit of a hassle to subtract the orbit velocity from the target velocity to get the correct number x)

I have found that quicksave-quickload fixes the issue and displays target velocity correct.

If you want I can try film the fenomen next time I send a rocket into orbit and It will better illustrate how and when I encounter the bug? - I can also try note the data of when this occurs better? 

Link to comment
Share on other sites
Filed.Teeth

Filed.Teeth

Posted
Posted (edited)
On 7/6/2023 at 11:29 AM, Dakota said:

Heya, we are aware of an issue where setting a target does not change the velocity shown to the correct Target velocity, but instead keeps it in Orbital mode. However, clicking on the Orbit velocity should allow you to cycle to Target mode which has the correct velocity. Is this the behavior observed?

@Davidian1024 @BechMeister @wjxway @Anth12

No, switching between the three doesn't change it. 

If the video pastes okay, if not here's what it showed, lol:

Two craft, slowly approaching (can see it change from 20m to 19m) 

Cycle from Target to Orbit to Surface and back to Target. Can see Nav ball icons change from orbit to target lock on.

Target icon is grey even though target is obviously locked. Target was locked with a right click, targeted in Parts Manager.

Isn't included in video, but other ship has blue icon, target locked via Orbital Map. Same bug with velocity on it too.

https://forum.kerbalspaceprogram.com/applications/core/interface/file/cfield.php?storage=form_Fields&path=KerbalSpaceProgram2_2023_07.01-11_18.mp4&fileKey=[!AES128GCM[UZt7vUxP6NXrOC8T1PDvfoVxodZWs2pJw2FkLTojbWSYzaXeKCwGn2wL56HZosO45naYH3hl8DZfqQzGPkCmUlj9TgLfpxTn9I9JGba9Y6DYWGmI14w86sR01n%2BJ][15bf3fb9a045ac9ac68cb4a4][2acf3e1d70b6518cfb9bef155003e1af]]

In other instances I've had one craft display correctly, the second one has the bug. In this case it was both.

 

Edited by Filed.Teeth
Link to comment
Share on other sites
Anth

Anth

Posted
Posted
4 minutes ago, Filed.Teeth said:

https://forum.kerbalspaceprogram.com/applications/core/interface/file/cfield.php?storage=form_Fields&path=KerbalSpaceProgram2_2023_07.01-11_18.mp4&fileKey=[!AES128GCM[UZt7vUxP6NXrOC8T1PDvfoVxodZWs2pJw2FkLTojbWSYzaXeKCwGn2wL56HZosO45naYH3hl8DZfqQzGPkCmUlj9TgLfpxTn9I9JGba9Y6DYWGmI14w86sR01n%2BJ][15bf3fb9a045ac9ac68cb4a4][2acf3e1d70b6518cfb9bef155003e1af]]

In other instances I've had one craft display correctly, the second one has the bug. In this case is was both.

Which bug report is that from? 
I do recognise the video.

Link to comment
Share on other sites
Anth

Anth

Posted
Posted
2 minutes ago, Filed.Teeth said:

It's not from a separate report, I just made that. When I came to post I found this one, so added to it.

It looks like a link that is from an uploaded file via the bug reporting form.

Link to comment
Share on other sites
Davidian1024

Davidian1024

Posted
  • Author
Posted
On 7/6/2023 at 5:29 PM, Dakota said:

Heya, we are aware of an issue where setting a target does not change the velocity shown to the correct Target velocity, but instead keeps it in Orbital mode. However, clicking on the Orbit velocity should allow you to cycle to Target mode which has the correct velocity. Is this the behavior observed?

@Davidian1024 @BechMeister @wjxway @Anth12

When I encountered this I wasn't sure what was being displayed.  It was giving me different numbers for all three different modes.  The number being displayed in target mode did seem close to the number orbit mode displayed, but it was significantly different.  I think it was off by 10 or more m/s.

Link to comment
Share on other sites
BechMeister

BechMeister

Posted
Posted

I took a screenshot of the Orbit speed and target speed:

uDkR40P.png

the interesting thing is my relative speed is not 4m/s - I would eye ball it to like 1m/s

I have also now tried that it said the relative speed was like 1m/s - but if i cancled out the speed out so it was 0 It would not be. its a bit weird.

Link to comment
Share on other sites
Rubenio

Rubenio

Posted
Posted

I can confirm this is an issue with the latest release - I was making a video for a suggestion on SAS and undocked and redocked two vessels in succession and the second time around, the target speed was the same as the orbit speed though i was probably approaching <1 m/s...

Link to comment
Share on other sites
  • 1 month later...
  • 3 weeks later...
 Share
Go to topic listing
×
×
  • Create New...