I'm using Counter-Strike: Source as an example.
In the main menu with stereoscopic unchecked the fps is 300.
if 3d is checked and enabled the fps is 60
if 3d is checked but disabled using ctrl+T the fps is 120.
[quote="TsaebehT"][s]Sounds about right ... can't exactly be getting more FPS than you can sync to. :)[/s][/quote][img]http://allpoetry.com/s/images/smile/dunce.gif[/img] Nevermind, it was one of those quick responses on my way out the door that I regretted after I actually though about it. Lol :) ... I just tried Tomb Raider on LOW with VSYNC off with 3D enabled and got:
MIN FPS: 85.6
MAX FPS: 138.0
AVERAGE FPS: 114.6
TsaebehT said:Sounds about right ... can't exactly be getting more FPS than you can sync to. :)
Nevermind, it was one of those quick responses on my way out the door that I regretted after I actually though about it. Lol :) ... I just tried Tomb Raider on LOW with VSYNC off with 3D enabled and got:
[quote="TsaebehT"][quote="TsaebehT"][s]Sounds about right ... can't exactly be getting more FPS than you can sync to. :)[/s][/quote][img]http://allpoetry.com/s/images/smile/dunce.gif[/img] Nevermind, it was one of those quick responses on my way out the door that I regretted after I actually though about it. Lol :) ... I just tried Tomb Raider on LOW with VSYNC off with 3D enabled and got:
MIN FPS: 85.6
MAX FPS: 138.0
AVERAGE FPS: 114.6
[/quote]
Yes but doesn't TR uses his own stereo 3D rendering engine? Which means nVidia Automatic doesn't hook up in there which means, that you could get those results...
If you try it in an another game (were nVidia Automatic does kick in ->game without enable stereo 3d in the options) you will see that if you are using Fraps (or any other software) that your FPS will be capped at 120hz /60hz even if VSYNC is disabled in the game.
Bottom line is:
- using nvidia stereo automatic you will always get 120fps/60 fps
- using a game with its own rendering you will also SEE 120fps/60 fps but that doesn't mean the engine will not render more than 120...
What is interesting is if in your benchmark you also used fraps to monitor the actual things that are rendered.... I bet it will not go higher than 120/60fps;)) even if the results says so;))
TsaebehT said:Sounds about right ... can't exactly be getting more FPS than you can sync to. :)
Nevermind, it was one of those quick responses on my way out the door that I regretted after I actually though about it. Lol :) ... I just tried Tomb Raider on LOW with VSYNC off with 3D enabled and got:
MIN FPS: 85.6
MAX FPS: 138.0
AVERAGE FPS: 114.6
Yes but doesn't TR uses his own stereo 3D rendering engine? Which means nVidia Automatic doesn't hook up in there which means, that you could get those results...
If you try it in an another game (were nVidia Automatic does kick in ->game without enable stereo 3d in the options) you will see that if you are using Fraps (or any other software) that your FPS will be capped at 120hz /60hz even if VSYNC is disabled in the game.
Bottom line is:
- using nvidia stereo automatic you will always get 120fps/60 fps
- using a game with its own rendering you will also SEE 120fps/60 fps but that doesn't mean the engine will not render more than 120...
What is interesting is if in your benchmark you also used fraps to monitor the actual things that are rendered.... I bet it will not go higher than 120/60fps;)) even if the results says so;))
1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc
I normally run my computer with 3d checked in Control panel.
I believed that by just disabling 3d (ctrl-T i would get the same behaviour as without 3D.
I don't want to run Everything with vsync but Before discovering this I was and now I have to remember to turn off 3D when I don't use it.
I thought other people would find it useful as I didn't consider it common knowledge and I clearly didn't know it myself already.
Starting a game in 3D and then disabling is apparently a way to get lightboost in 2D along with vsync resulting in reduced blur.
http://www.blurbusters.com/zero-motion-blur/lightboost/
[quote="Flugan"]I normally run my computer with 3d checked in Control panel.
I believed that by just disabling 3d (ctrl-T i would get the same behaviour as without 3D.
I don't want to run Everything with vsync but Before discovering this I was and now I have to remember to turn off 3D when I don't use it.
I thought other people would find it useful as I didn't consider it common knowledge and I clearly didn't know it myself already.
Starting a game in 3D and then disabling is apparently a way to get lightboost in 2D along with vsync resulting in reduced blur.
http://www.blurbusters.com/zero-motion-blur/lightboost/[/quote]
I remember some years ago discovering this myself at some point;))
The reason is simple:
CASE 1. IF 3D is enabled in nvPanel but Stereo Mode is disabled (ctrl+T) the stereo 3D CONTEXT is STILL created!!! but the hardware is disabled. This means that Stereo Automatic still hooks your app and does it magic in the shaders etc.
CASE 2. IF 3D is disabled in nvPanel the stereo 3D context is NOT CREATED! meaning you render in PURE 2D so to speak;))
Hence the different behavior;))
Another Important thing to mention is if you are in case 1 (3D enabled but viewing in 2D) and run a benchmark then you move to Case 2 (3D Disabled ) and run the same benchmark you will get better results in case 2. The reason is simple and mentioned above: the nvapi doesn't hook your App and no stereo 3D context is created;))
[url=http://3dvision-blog.com/forum/viewtopic.php?f=29&t=1024&start=10]http://3dvision-blog.com/forum/viewtopic.php?f=29&t=1024&start=10[/url]
On second page near the bottom we discussed about this;))
I remember some years ago discovering this myself at some point;))
The reason is simple:
CASE 1. IF 3D is enabled in nvPanel but Stereo Mode is disabled (ctrl+T) the stereo 3D CONTEXT is STILL created!!! but the hardware is disabled. This means that Stereo Automatic still hooks your app and does it magic in the shaders etc.
CASE 2. IF 3D is disabled in nvPanel the stereo 3D context is NOT CREATED! meaning you render in PURE 2D so to speak;))
Hence the different behavior;))
Another Important thing to mention is if you are in case 1 (3D enabled but viewing in 2D) and run a benchmark then you move to Case 2 (3D Disabled ) and run the same benchmark you will get better results in case 2. The reason is simple and mentioned above: the nvapi doesn't hook your App and no stereo 3D context is created;))
1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc
As you kind of neglected to discuss the topic of vsync above I just want to add that you are compleetely correct but as you are aware any app in CASE 1 have vsync on.
Unless you know an exception where you can run an app at above screen hz using CASE 1.
As you kind of neglected to discuss the topic of vsync above I just want to add that you are compleetely correct but as you are aware any app in CASE 1 have vsync on.
Unless you know an exception where you can run an app at above screen hz using CASE 1.
Thanks to everybody using my assembler it warms my heart.
To have a critical piece of code that everyone can enjoy!
What more can you ask for?
[quote="Flugan"]As you kind of neglected to discuss the topic of vsync above I just want to add that you are compleetely correct but as you are aware any app in CASE 1 have vsync on.
Unless you know an exception where you can run an app at above screen hz using CASE 1.[/quote]
That is also correct;)) But in benchmarks last I checked the benchmark will return (print the value on screen) of the calculated rendered frames NOT the actual render frames! Like in the Tomb Raider Case described above..:)
But as far as I am aware, you cannot disable Vsync in Case 1
EDIT: What I said above is not entirely true. Is Valid ONLY for DirectX apps where nvapi can hook the stereo automatic.
In OpenGL case Vsync Is DISABLED and I can render up to 1000fps (based on the app ofc).
Flugan said:As you kind of neglected to discuss the topic of vsync above I just want to add that you are compleetely correct but as you are aware any app in CASE 1 have vsync on.
Unless you know an exception where you can run an app at above screen hz using CASE 1.
That is also correct;)) But in benchmarks last I checked the benchmark will return (print the value on screen) of the calculated rendered frames NOT the actual render frames! Like in the Tomb Raider Case described above..:)
But as far as I am aware, you cannot disable Vsync in Case 1
EDIT: What I said above is not entirely true. Is Valid ONLY for DirectX apps where nvapi can hook the stereo automatic.
In OpenGL case Vsync Is DISABLED and I can render up to 1000fps (based on the app ofc).
1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc
In the main menu with stereoscopic unchecked the fps is 300.
if 3d is checked and enabled the fps is 60
if 3d is checked but disabled using ctrl+T the fps is 120.
Thanks to everybody using my assembler it warms my heart.
To have a critical piece of code that everyone can enjoy!
What more can you ask for?
donations: ulfjalmbrant@hotmail.com
[MonitorSizeOverride][Global/Base Profile Tweaks][Depth=IPD]
MIN FPS: 85.6
MAX FPS: 138.0
AVERAGE FPS: 114.6
[MonitorSizeOverride][Global/Base Profile Tweaks][Depth=IPD]
Yes but doesn't TR uses his own stereo 3D rendering engine? Which means nVidia Automatic doesn't hook up in there which means, that you could get those results...
If you try it in an another game (were nVidia Automatic does kick in ->game without enable stereo 3d in the options) you will see that if you are using Fraps (or any other software) that your FPS will be capped at 120hz /60hz even if VSYNC is disabled in the game.
Bottom line is:
- using nvidia stereo automatic you will always get 120fps/60 fps
- using a game with its own rendering you will also SEE 120fps/60 fps but that doesn't mean the engine will not render more than 120...
What is interesting is if in your benchmark you also used fraps to monitor the actual things that are rendered.... I bet it will not go higher than 120/60fps;)) even if the results says so;))
1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc
My website with my fixes and OpenGL to 3D Vision wrapper:
http://3dsurroundgaming.com
(If you like some of the stuff that I've done and want to donate something, you can do it with PayPal at tavyhome@gmail.com)
I believed that by just disabling 3d (ctrl-T i would get the same behaviour as without 3D.
I don't want to run Everything with vsync but Before discovering this I was and now I have to remember to turn off 3D when I don't use it.
I thought other people would find it useful as I didn't consider it common knowledge and I clearly didn't know it myself already.
Starting a game in 3D and then disabling is apparently a way to get lightboost in 2D along with vsync resulting in reduced blur.
http://www.blurbusters.com/zero-motion-blur/lightboost/
Thanks to everybody using my assembler it warms my heart.
To have a critical piece of code that everyone can enjoy!
What more can you ask for?
donations: ulfjalmbrant@hotmail.com
I remember some years ago discovering this myself at some point;))
The reason is simple:
CASE 1. IF 3D is enabled in nvPanel but Stereo Mode is disabled (ctrl+T) the stereo 3D CONTEXT is STILL created!!! but the hardware is disabled. This means that Stereo Automatic still hooks your app and does it magic in the shaders etc.
CASE 2. IF 3D is disabled in nvPanel the stereo 3D context is NOT CREATED! meaning you render in PURE 2D so to speak;))
Hence the different behavior;))
Another Important thing to mention is if you are in case 1 (3D enabled but viewing in 2D) and run a benchmark then you move to Case 2 (3D Disabled ) and run the same benchmark you will get better results in case 2. The reason is simple and mentioned above: the nvapi doesn't hook your App and no stereo 3D context is created;))
http://3dvision-blog.com/forum/viewtopic.php?f=29&t=1024&start=10
On second page near the bottom we discussed about this;))
1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc
My website with my fixes and OpenGL to 3D Vision wrapper:
http://3dsurroundgaming.com
(If you like some of the stuff that I've done and want to donate something, you can do it with PayPal at tavyhome@gmail.com)
Unless you know an exception where you can run an app at above screen hz using CASE 1.
Thanks to everybody using my assembler it warms my heart.
To have a critical piece of code that everyone can enjoy!
What more can you ask for?
donations: ulfjalmbrant@hotmail.com
That is also correct;)) But in benchmarks last I checked the benchmark will return (print the value on screen) of the calculated rendered frames NOT the actual render frames! Like in the Tomb Raider Case described above..:)
But as far as I am aware, you cannot disable Vsync in Case 1
EDIT: What I said above is not entirely true. Is Valid ONLY for DirectX apps where nvapi can hook the stereo automatic.
In OpenGL case Vsync Is DISABLED and I can render up to 1000fps (based on the app ofc).
1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc
My website with my fixes and OpenGL to 3D Vision wrapper:
http://3dsurroundgaming.com
(If you like some of the stuff that I've done and want to donate something, you can do it with PayPal at tavyhome@gmail.com)
Thanks to everybody using my assembler it warms my heart.
To have a critical piece of code that everyone can enjoy!
What more can you ask for?
donations: ulfjalmbrant@hotmail.com