1.0 - 1.2 BUG Radar often doesn't want to display - Fix in a future build.

[AkrionXxarr]

I've never been able to get the radar to show up "normally". The only time I've been able to make the radar appear is by...

1. "Radar Display" is initially set to "Off"
2. Go into Game Settings, change "Radar Display" to "Separate Panel"
3. Exit the menu. No radar is visible.
4. Go back into Game Settings, change "Radar Display" back to "Off"
5. Exit the menu. Radar now shows up between the Message and Information panels.

The radar will persist until I load the game, leave the ship, etc. and I'll have to repeat the above steps to get it back. If I get the radar working and change the "Radar Display" setting back to "Separate Panel" it shuts off again.

Edit: Behavior is unchanged as of 1.2. I haven't gotten a chance to check against 1.21 but given the change notes I'd guess the issue is still present.

[CBJ]

Could you provide some of the information requested at the top of the forum, particularly your DXDiag and vulkaninfo files?

[AkrionXxarr]

Alright, I've added them to my signature for you guys.

[CBJ]

I have a feeling this relates to your very wide screen aspect ratio. Have you tried reducing the UI scaling to see if it reappears?

[AkrionXxarr]

Made no difference. However when I get the radar to show it works just fine. Here's a picture: https://i.imgur.com/llMdTmL.jpg
It behaves like my "Radar Display" setting is in a funky state. Like the setting is out of sync with something.

I can say that before I started my game I changed it from "Separate Panel" to "Integrated" and, after never seeing it, tried switching back to "Separate Panel" which didn't work.
This behavior of switching to the desired setting, exiting the menu, then switching the setting back to off works for both "Separate Panel" and "Integrated" btw.

[Slamdance_Kozmopolis]

I am having a similar issue but my radar display, when working, is stuck floating on the right side of the cockpit.

The problem started when I changed game settings--> radar display from "integrated" to "separate panel"...

I'm assuming "separate panel" means floating on the right side of the cockpit. BUT, it won't change positions now and works intermittently.

[AkrionXxarr]

I actually think that "Separate Panel" is what you see in the picture of my previous post, with the radar sitting between the message and info panels, and I think "Integrated" is supposed to combine it with the info panel.

[Unclejack]

I can confirm this issue is still present in 1.21 323477.

I actually think it has gotten worse as I cannot seem to reliably get the radar to show in the middle bottom part of the interface (between the left and right panels).

[sycholic]

Im having the same issue either it dont wanna show up, or its not following what the actual setting is. and I def cant get it attached into the console of my ship anymore its always on the side detached now....

also think I found the problem

<separateRadar>0</separateRadar> (all other fields dont use 0 for boolean false)

I saved my config ini i was having radar problems in game with then deleted it made the game generate a fresh one. soon as I did that all my radar problems poof'd and the field uses 'false' so I believe ingame the setup menu is saving it as a numeric.
At least this is my theory based on what I am experiencing, that and all other boolean values are textual not numeric values in the same config file there isnt any '0' to indicate boolean logic.

[sycholic]

dont like bumping but its clear there is a problem and the source of said problem has likely been found but not a word from the devs after a whole week that and judging by the replies its been assumed its a display linked issue. its not its flat out a in-game value writing the wrong data type when it tries to apply it to the ini file. (I have tested and repetitively broken and fixed it several times now)

[stefanEgo]

Thanks for the report and sorry it took a while to tackle the problem. We identified an issue with the setting not correctly being applied and think this should also solve the problem you reported in this thread.

The fix is expected to be shipped in the next beta version (please note that I can't give an ETA on when this will be available atm).

Also FTR: The issue is not related to the setting using 0 rather than false as you suspected. 0 and false are evaluated equally for this config value and using one or the other doesn't change the behavior.