Inconsistencies when using stereoscopic modes

Bugs that have been investigated and resolved somehow.

Moderator: GZDoom Developers

Forum rules
Please don't bump threads here if you have a problem - it will often be forgotten about if you do. Instead, make a new thread here.
Post Reply
User avatar
GFD
Posts: 347
Joined: Mon May 31, 2010 7:42 pm
Preferred Pronouns: He/Him
Location: Canada
Contact:

Inconsistencies when using stereoscopic modes

Post by GFD »

When vr_mode is nonzero, gl_menu_blur no longer has any effect.

When vr_mode is 12 (row interleaved), 13 (column interleaved), or 14 (checkerboard), vid_saturation no longer has any effect.
User avatar
Rachael
Posts: 13530
Joined: Tue Jan 13, 2004 1:31 pm
Preferred Pronouns: She/Her
Contact:

Re: Inconsistencies when using stereoscopic modes

Post by Rachael »

Nothing can be done about vr_mode=={12|13|14} with vid_saturation, as the screen switches to hardware gamma in those modes and vid_saturation is not currently supported on that system. If it is, someone will have to let me know how to code that. The gamma ramps are set in "src/gl/system/gl_framebuffer.cpp" for the hardware gamma so if you do know, that's where it needs to go. (Although - maybe it's safe to enable the shader gamma in those modes? I don't know why it was disabled to begin with...)

Also - menu blur in VR modes is not something I want to explicitly support. If someone else wants to work on that and get it working, be my guest, but it's something I have absolutely zero interest in.
User avatar
Graf Zahl
Lead GZDoom+Raze Developer
Lead GZDoom+Raze Developer
Posts: 49056
Joined: Sat Jul 19, 2003 10:19 am
Location: Germany

Re: Inconsistencies when using stereoscopic modes

Post by Graf Zahl »

Rachael wrote: but it's something I have absolutely zero interest in.
Same here. I do not have any VR equipment and no plans ever to buy some.
Post Reply

Return to “Closed Bugs [GZDoom]”