geo-11 TAB and SBS outputs produce some garbage pixels in certain resolutions

[Zerofool]

Hi, I was testing geo-11 on my 3DTV in its native 1080p res, as well as 2880x1620 (2.25x DSR). I was using TAB output and I noticed a weird line at the top of the image, only for one of the eyes. I was chatting with my buddy artox, who had the same issue and he found that it's gone when playing at 2160p (4x DSR).

So I went pixel peeping (Mirror's Edge: Catalyst and Snowrunner) and I think I found a possible root cause for the issue.

This was what I found when I took a look at a 1080p TAB screenshot (from the top row to the bottom-most):
540 lines of image for the one eye
4 lines of pixels which are almost identical copies (there's slight color shift) of the last row from the first image
536 lines of image for the other eye

Then I did the same for a 1620p TAB screenshot:
810 lines of image for the one eye
6 lines of pixels which are almost identical copies of the last row from the first image
804 lines of image for the other eye

I also checked a 2160p TAB screenshot - there are, as expected, 1080 lines for the first image followed by 1080 lines for the second one - no problematic rows.


Looking at these numbers, I came up with a theory that you guys are using a buffer/texture to store each view which has mod8 dimensions (540+4; 810+6). If my assumption was correct, this would mean that other resolutions which are mod8 would not exhibit this issue, so I tried 2560x1440 (720 lines per eye, which is mod8) and it worked without exhibiting the garbage lines.

I decided to check sbs with resolutions where the width of the image will not be mod8 but the stock DSR multipliers either result in odd-numbered resolutions or ones that are mod8. I tried DSR 1.20x - 2103x1183 (1501,5 x 1183 per eye?) which produced even weirder results at the border between both views.

I hope this will be easy to fix without reducing performance or other such potential drawbacks.

I'm attaching some raw screenshots and zoomed-in details for reference (taken from ME Catalyst), especially interesting for the messy sbs image.

_

[3DNovice]

....

[Zerofool]

Just curious if you tried it and if it works with 3D

Yes, the TAB tests I did at 2560x1440 (1.78x) and 2880x1620 (2.25x) were using the DL-DSR algo. Nvidia has trained networks just for these two factors. The rest of the tests I did were using the traditional DSR algo.

As I explained, 2880x1620 and 1920x1080 (no downscaling at all in this case) exhibited the issue with duplicated lines, while 2560x1440 and 3840x2160 didn't, so the DSR type is not causing this.

And most importantly - the problem is visible even before the DSR algorithm kicks in to scale the image down to the native resolution (1080p), as seen in the shots taken by MSI Afterburner. So the cause must lie somewhere in the geo-11 driver which composits both views into a single TAB/SBS image before it's sent to the DSR/scanout logic in the nv driver. It would be nice to hear bo3b's opinion on the matter.

Is nobody else experiencing this aside from artox (in the witcher 3 thread), Poligraphovich (in the "New geo-11 driver" thread) and myself?

On your question about DSR in 3D, aside from geo-11, I can only speak about 3DTV Play in HDMI Checkerboard mode - OG DSR doesn't work, and neither does DL-DSR in DX9 games, no way to test DX11 games as the feature was introduced only in recent drivers as you pointed out. I never tried DSR back in the day with the SBS/TAB output provided by 3dmigoto.

[daspwan]

daspwanJuly 9, 2022 at 9:10 PM
My 1080ti can use direct at 452.06_ mode = nvidia_ Dx11 runs geo-11. After installing 511.79, and 3D vision is installed through fix manager_ Driver, but cannot hack, causing 3DTV to be locked in the nvdia control panel, whether it is NVIDIA_ Dx11 or DX9 are both black screens, and only tab mode can be used.
The geo-11 tab mode is different from the tab mode of 3dmigoto. The top picture of the screen will have the bottom picture with about 10 pixels vertical, which is equivalent to cutting the bottom 10 rows of pixels to the top of the screen, which is particularly obvious.Do you guys have the same problem?



I posted this question on geo-11 blog before, but no one responded,They should be busy with something else

[BazzaLB]

daspwanJuly 9, 2022 at 9:10 PM
My 1080ti can use direct at 452.06_ mode = nvidia_ Dx11 runs geo-11. After installing 511.79, and 3D vision is installed through fix manager_ Driver, but cannot hack, causing 3DTV to be locked in the nvdia control panel, whether it is NVIDIA_ Dx11 or DX9 are both black screens, and only tab mode can be used.
The geo-11 tab mode is different from the tab mode of 3dmigoto. The top picture of the screen will have the bottom picture with about 10 pixels vertical, which is equivalent to cutting the bottom 10 rows of pixels to the top of the screen, which is particularly obvious.Do you guys have the same problem?

I posted this question on geo-11 blog before, but no one responded,They should be busy with something else

All I can say is I run driver 516+ on a 3080. I pretty much run all my 3d Games in geo-11 using TAB. I dont have this cut-off issue. I was also able to run Wreckfest using geo-11 nvidia_dx9 output into 3DTV Play (Injected via 3DFM) on same machine and got proper frame packed display with no issues.

[daspwan]

global hack can only toggle Before version 452.06? The new version of driver 511 Injected via 3DFM prompts failure。Is your nvdia 3d panel locked, too?

[BazzaLB]

Nope. I can select 3D using nvpanel but I did the cp panel trick outlined by bo3b (viewtopic.php?t=26356) to stop the cp panel stalls. The global hack is only required for dx11 output path (nvidia_dx11) as far as I know. nvidia_dx9 output works fine without any hack which is all I can use anyway with my driver. So, frame packed output into 3DTVPlay using nvidia_dx9 output path works fine for me on my 516 driver on my RTX3080.

[artox]

I also have this garbage pixel line in TAB.
Have a 1070ti card and using 452. drivers.
With the standard driver in tab mode (using 3dfix mgr) it was ok (no garbage pixels), but with GEO 11 only setting resolutions below
1080p or a custom DSR (thanks to Zerofool) works (vertical resolution again under 1080p

Not sure what the issue is, but essentially I can't play games in native 1080p with the driver.

[3DNovice]

...