Map & Tracking Station Non spherical bodies have incorrect impact locations (Bop and Gilly)

[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

 

Impact  location on Bop is incorrect, it appears above the terrain in map view - see image.

 

Included Attachments:

Edited December 28, 2023 by Spicat

[Vortygont]

I think it's because all celestial bodies in map view have spherical collsison model probably. I saw this on the Mun, Minmus and other bodies with complex relief, but of course on Bop it's most notably. I believe we need more accurate non-spherical models in map view, maybe without soapy textures when you zoom in on the planet

[Jeq]

Reported Version: v0.2.0 (latest) | Mods: none | Can replicate without mods? Yes 
OS: win 11 | CPU: I7 | GPU: rtx 3080 | RAM: 32

At video flying low at gilly, map might show crashpoint when there is no surface near it.

After flying to that point, orbit seems to show normal.

Included Attachments:

[Spicat]

@Jeq, merged your bug report.

@Vl3d, changed the title to fit Gilly as well.

[jclovis3]

Related issue maybe is that you can't set a low orbit on Bop to do low orbit science. The divide between low and high orbit is so low that the impact icon shows up and you can't set an orbit that you can simply leave in place.

I read in another article that the low orbit was raised to 30 km, but it needs to be raised much higher as the warp speed automatically reduces you to 4x while still in high orbit above this level.

See: 

Edit: I just landed in the giant crater and the low orbit triggered below 25 km, which is already within the lip of the crater. Warp is reduced to 4x well above that so I think low orbit needs to be raised to at least 55 km if they're going to keep warp speed limits where they are.

 

Edited January 1, 2024 by jclovis3
Added new text.

[Navoan]

Reported Version: v0.2.1 (latest) | Mods: none | Can replicate without mods? Yes 
OS: Windows 11 | CPU: i7-14700KF | GPU: 2070 SUPER | RAM: 32GB

When in orbit around a body that isn't strictly spherical the low orbit trajectory lines show the vessel as crashing.  I expect that the trajectory in fact checks if my craft will interersect terrain in an exact manner, and show this exact impact site.  As it is, there was an impact, but not where it was shown on the trajectory (even though there was a ~1600m close flyby) at that point.

After going to KSC, time warping, and coming back to the craft after that 'impact' point, the trajectory updated, like to how I would have originally expected, like this:


Whilst close the lowest altitude here was 1160m.  Which is far from an impact.

 

Included Attachments:

Save2024-03-23BopCrash.json

[Spicat]

@Navoan, merged your bug report.