Solved 4.36u3 artifact flicker in 3D
-
Windows 10
GPU AMD RX6600
I’ve seen the issue in AAR and Groud Ops TE
Happens on a clean install as well
Borderless
No vsync
No triple buffer -
@danaos75
I don’t have any quick look callbacks bound -
@Todd1215 head-tracking? do you have the z-axis set to fov-control? (if so, try turning that off for a while and see if problem still repros?)
-
Track IR Z-Axis mode is set to Z-Axis Control and it still occurs
also this even happens in 4.36 u2.
-
@Todd1215 said in 4.36u3 artifact flicker in 3D:
the flicker seems to be a zoomed in image of the HUD
I’m wondering if this is a flicker of “look-closer” … or a flicker of the HUD-only view (press [1] on keyboard)?
ie. Does it still happen when looking down or to the side … if so, what do you see?
I don’t have any explanation or workaround to offer, either way. Just trying to help the investigation along…
-
Try this, go to the config file, find the “look closer” line and enter the same FOV value as your in cockpit default FOV. If it is the"look closer"acting up, then it should stop. Since the FOV is now the same as your normal view.
-
-
flicker still occurs when looking to the side. Also setting set g_fNarrowFOV to same value as DefaultFOV doesn’t make a difference.
-
@Todd1215 can you describe what you see, looking to the side – is it the green HUD markings, zoomed-in still?
(maybe have to turn off HMCS to tell, I suppose)
-
@Todd1215
Have you tried without trackir or whatever headtracker you are using?
Have seen something similar to this and was caused by trackir losing the track and snapping back to center repeatedly. One more thing to eliminate either way. -
@TxMtb I’ve tried it with and without TrackIR, in either case it still presents itself.
-
Do you have any controller axis mapped to FoV? This looks like a controller spike to me.
-
@Seifer Yes I do. Let me unmap that and see if it still happens.
-
gadzooks man, you were right!! the slider pot is spiking which is what I had my FOV mapped to. I never even considered this but am glad that we found the issue. It was driving me nuts! So much for new hardware.
-
Glad you found it
-