Bingo. Looks like you have no issues then...!
I had modified your version, but I believe I didn't change these states. I started with every shader as normal. Turned of ambient lighting with F4 and F3 for internal ship lights (my settings). F2 was for toggling old black space. F1 for HUD and the states. My HUD looked 100% normal when I logged in. When I pressed F1 one time, part of the HUD in the spaceship went away. When I pressed F1 again I think the entire HUD went away. Third time back to before. I will provide screenshot and explain in more detail shortly when I'm on the PC.Help me out (anybody) - when are you seeing this, when you first start the game or after pressing F1? What would really be helpful is to have a screenshot of the three F1 states (full HUD, partial HUD, and no HUD).
Also, make sure you are all using version
1.3.16
of 3DMigoto!
That's on purpose but easy to fix if you don't like it (I have this as "eyes adjust to the darkness to see nebula better" mode).Except for the brown Milky Way in the middle shot
[CommandListToggleHud]
$hideHUD = $hideHUD + 1
if $hideHUD == 2
y = 0
else if $hideHUD > 2
$hideHUD = 0
y = 1
endif
[CommandListToggleHud]
$hideHUD = 1 - $hideHUD
I will try in a phantom and see, have one waiting here. I have tried sidewinder and it does the same.This would be a lot easier to fix if everybody was having this issue. It could be that ED uses a different shader for HUD on certain ships (it does weird stuff like that). Try an Eagle or Type 9 or Phantom - all of these ships work for me. I'm out in the middle of nowhere, otherwise I'd try one of your ships.
ps - I didn't know so many players wanted a shortcut for HUD-off! The reason I added it is because it's near impossible for me to hit CTRL-ALT-G in VR.
The three settings which I get is a) Everything there with muted galaxyy b) Holographics background and window gone with muted galaxy c) Ship, radar, and target animation gone with full galaxy. Another F1 press go back to A.
Not of 3DMigoto as I've not changed anything with it and got the 1.3.16 version already. I can check that tomorrow (sleep for me in a minute).Is it a clean install: that would help rule some things out
MP
; Next level of HUD deactivation is turning off the HUD inside the ship. This also turns off lights
[ShaderOverrideInternalHUD]
Hash=f6f4895ec35cc873
;if $hideHUD > 1
Handling=skip
;endif
[ShaderOverrideRadarSegment1]
Hash=9813bfc19f632619
;if $hideHUD > 1
Handling=skip
;endif
[ShaderOverrideRadarSegment2]
Hash=a79b5e1b8183c2b0
;if $hideHUD > 1
Handling=skip
;endif
[ShaderOverrideRadarSegment3]
Hash=abcb5cfb5b1d8b7d
;if $hideHUD > 1
Handling=skip
;endif
[ShaderOverrideRadarSegment4]
Hash=af442f80671a4878
;if $hideHUD > 1
Handling=skip
;endif
[ShaderOverrideRadarSegment5]
Hash=ba58bc885c2dac25
;if $hideHUD > 1
Handling=skip
;endif
[ShaderOverrideRadarSegment6]
Hash=122f37290d55ce94
;if $hideHUD > 1
Handling=skip
;endif
[ShaderOverrideRadarSegment7]
Hash=f27049cc4a93e1f2
;if $hideHUD > 1
Handling=skip
;endif
The only advice I can give is to install the default d3dx.ini that comes with 3DMigoto and turn Hunting on, and find the hash for that section of HUD on your computer. For whatever reason, it must be different for some people than others. There's really not anything I can do for you from here, as it's apparently not an error in my own file (otherwise everyone would have this problem)Not of 3DMigoto as I've not changed anything with it and got the 1.3.16 version already.
Y'all seem to be confusing me with a full-time paid developer from Frontier, LOL. What you ask for is not simple, it might not even be possible.@Old Duck, not really related but I think it is a nice idea for FA-off and such: Perhaps you could provide a simple directional vector gauge based on the space dust shader info. That would be really useful.
Ha, I wonder if CMDR A D is glad he gave up on itLook folks, I do this as a side-hobby to improve my own gameplay, and I'm happy to share what I've successfully done for myself with others, but that's it. Please manage your expectations.