I have an app that used to work, that displays stereoscopic video through Direct3D 9 by combining two independent 2D images for each view. I create an offscreen surface with resolution 3840x1081, put the structure _Nv_Stereo_Image_Header in the last line, left view in the left half of the surface, right view in the right half, and call StretchRect from the offscreen surface to the back buffer.
This used to work fine (but only in fullscreen mode) in drivers up to 266.xx.
In the driver 270.61, it does not work any more. It's like the stereo header is completely ignored. I read through the "NVIDIA 3D Vision Automatic Best Practices guide" front to back five times and my conclusion is that it's not helpful. "Active Stereoization" is apparently unavailable in DX9, and the guide does not explain how I would go about constructing a stereo surface out of two separate views in the "Passive Stereoization" mode.
- Was this capability of StretchRect removed in driver version 270, or were there some changes to the way it's supposed to be used?
- How come some applications are able to display stereo in the windowed mode? What am I supposed to do in my code to add that functionality?
I have an app that used to work, that displays stereoscopic video through Direct3D 9 by combining two independent 2D images for each view. I create an offscreen surface with resolution 3840x1081, put the structure _Nv_Stereo_Image_Header in the last line, left view in the left half of the surface, right view in the right half, and call StretchRect from the offscreen surface to the back buffer.
This used to work fine (but only in fullscreen mode) in drivers up to 266.xx.
In the driver 270.61, it does not work any more. It's like the stereo header is completely ignored. I read through the "NVIDIA 3D Vision Automatic Best Practices guide" front to back five times and my conclusion is that it's not helpful. "Active Stereoization" is apparently unavailable in DX9, and the guide does not explain how I would go about constructing a stereo surface out of two separate views in the "Passive Stereoization" mode.
- Was this capability of StretchRect removed in driver version 270, or were there some changes to the way it's supposed to be used?
- How come some applications are able to display stereo in the windowed mode? What am I supposed to do in my code to add that functionality?
I have an app that used to work, that displays stereoscopic video through Direct3D 9 by combining two independent 2D images for each view. I create an offscreen surface with resolution 3840x1081, put the structure _Nv_Stereo_Image_Header in the last line, left view in the left half of the surface, right view in the right half, and call StretchRect from the offscreen surface to the back buffer.
This used to work fine (but only in fullscreen mode) in drivers up to 266.xx.
In the driver 270.61, it does not work any more. It's like the stereo header is completely ignored. I read through the "NVIDIA 3D Vision Automatic Best Practices guide" front to back five times and my conclusion is that it's not helpful. "Active Stereoization" is apparently unavailable in DX9, and the guide does not explain how I would go about constructing a stereo surface out of two separate views in the "Passive Stereoization" mode.
- Was this capability of StretchRect removed in driver version 270, or were there some changes to the way it's supposed to be used?
- How come some applications are able to display stereo in the windowed mode? What am I supposed to do in my code to add that functionality?
[/quote]
[quote name='hamster143' date='29 April 2011 - 09:39 PM' timestamp='1304131155' post='1231856']
andrewf:
I have an app that used to work, that displays stereoscopic video through Direct3D 9 by combining two independent 2D images for each view. I create an offscreen surface with resolution 3840x1081, put the structure _Nv_Stereo_Image_Header in the last line, left view in the left half of the surface, right view in the right half, and call StretchRect from the offscreen surface to the back buffer.
This used to work fine (but only in fullscreen mode) in drivers up to 266.xx.
In the driver 270.61, it does not work any more. It's like the stereo header is completely ignored. I read through the "NVIDIA 3D Vision Automatic Best Practices guide" front to back five times and my conclusion is that it's not helpful. "Active Stereoization" is apparently unavailable in DX9, and the guide does not explain how I would go about constructing a stereo surface out of two separate views in the "Passive Stereoization" mode.
- Was this capability of StretchRect removed in driver version 270, or were there some changes to the way it's supposed to be used?
- How come some applications are able to display stereo in the windowed mode? What am I supposed to do in my code to add that functionality?
We encountered the same problem with Passive Stereoization (manual left and right surface/pairs submit to the driver) and presenting them using [b]NvStereoImageHeader[/b] and [b]StretchRect()[/b] tweak.
Our code worked fine on Windows 7 32/64 bits with Quadro FX3700 or GeForrce 580 cards using drivers [b]v266.45[/b].
Now with drivers [b]v270.71[/b] code is broken, no more passive stereo pair, the new driver does automatic stereo so only one image is presented.
- Is it a bug, or feature was removed/disabled?
- Also sample code for passive/manual stereo in windowed mode will be very appreciate.
We encountered the same problem with Passive Stereoization (manual left and right surface/pairs submit to the driver) and presenting them using NvStereoImageHeader and StretchRect() tweak.
Our code worked fine on Windows 7 32/64 bits with Quadro FX3700 or GeForrce 580 cards using drivers v266.45.
Now with drivers v270.71 code is broken, no more passive stereo pair, the new driver does automatic stereo so only one image is presented.
- Is it a bug, or feature was removed/disabled?
- Also sample code for passive/manual stereo in windowed mode will be very appreciate.
I'd also like to know what this solution is, as the data my project is trying to visualise it not part of a 3D geometry, and therefore needs to be treated like a stereo image pair.
I've only recently started working on this, and this is the only post I've found anywhere that seems to indicate that this stereo blitting method is still possible. The machine I'm using was bought specifically to use the 3D Vision tools, but it came loaded with the most recent drivers, so my code has never shown 3D images using this method correctly.
I'd also like to know what this solution is, as the data my project is trying to visualise it not part of a 3D geometry, and therefore needs to be treated like a stereo image pair.
I've only recently started working on this, and this is the only post I've found anywhere that seems to indicate that this stereo blitting method is still possible. The machine I'm using was bought specifically to use the 3D Vision tools, but it came loaded with the most recent drivers, so my code has never shown 3D images using this method correctly.
Evidently there is little chance of seeing any freely available information on the topic...
I see all over these forums people complaining about lack of support from NVidia; cries that appear to fall on deaf ears... The only obvious solution seems to be writing something capable of doing page-flipping... will this cause the 3D Vision system to enter 3D mode? Or do I need to use the NVAPI for that?
With all the talk of these new drivers being 'Automatic' and 'Intelligent' I didn't really anticipate having to do so much work to get them to do anything...
Evidently there is little chance of seeing any freely available information on the topic...
I see all over these forums people complaining about lack of support from NVidia; cries that appear to fall on deaf ears... The only obvious solution seems to be writing something capable of doing page-flipping... will this cause the 3D Vision system to enter 3D mode? Or do I need to use the NVAPI for that?
With all the talk of these new drivers being 'Automatic' and 'Intelligent' I didn't really anticipate having to do so much work to get them to do anything...
The stretchrect problem doesn't actually seem to just be a 3D Vision issue, I was using it in a project to change a multisampled backbuffer into something usable for a bloom post processor, but it recently stopped working, after debugging for a while, I realised that it still worked on one of my ATI machines. I've not gone and tested other drivers, but it does seem to be stretchrect that is the problem, and if it's not working for post processing, I wouldn't be surprised if it's broken for other uses aswell, like 3D Vision.
The stretchrect problem doesn't actually seem to just be a 3D Vision issue, I was using it in a project to change a multisampled backbuffer into something usable for a bloom post processor, but it recently stopped working, after debugging for a while, I realised that it still worked on one of my ATI machines. I've not gone and tested other drivers, but it does seem to be stretchrect that is the problem, and if it's not working for post processing, I wouldn't be surprised if it's broken for other uses aswell, like 3D Vision.
[quote]Evidently there is little chance of seeing any freely available information on the topic...[/quote]
Not on this board, no. Try the developer forums. Andrew posted a link the developer resources above. Or you can just poke around on the NVIDIA website and find it pretty fast.
Evidently there is little chance of seeing any freely available information on the topic...
Not on this board, no. Try the developer forums. Andrew posted a link the developer resources above. Or you can just poke around on the NVIDIA website and find it pretty fast.
So there is some larger underlying issue connecting the StretchRect method and NVidia cards then? For the meantime I've somewhat solved my problem by mimicking a 3D geometry so the drivers will do their automatic 3D conversion, but it's far from ideal...
@Zloth; I already tried the developer forums and got no response, but it's a good suggestion :D As someone over there has pointed out the 'Developer Resources' are more of a brochure on what Stereo 3D [i]is[/i] than documentation on how to write applications that work with NVidia's hardware (it's missing things like working code samples ;P).
Although, it doesn't seem that the lack of communication is solely related to 3D Vision; I know several people that work at large tech companies associated with NVidia and even they get cryptic non-responses to a lot of tech related queries... oh well =/
So there is some larger underlying issue connecting the StretchRect method and NVidia cards then? For the meantime I've somewhat solved my problem by mimicking a 3D geometry so the drivers will do their automatic 3D conversion, but it's far from ideal...
@Zloth; I already tried the developer forums and got no response, but it's a good suggestion :D As someone over there has pointed out the 'Developer Resources' are more of a brochure on what Stereo 3D is than documentation on how to write applications that work with NVidia's hardware (it's missing things like working code samples ;P).
Although, it doesn't seem that the lack of communication is solely related to 3D Vision; I know several people that work at large tech companies associated with NVidia and even they get cryptic non-responses to a lot of tech related queries... oh well =/
I have an app that used to work, that displays stereoscopic video through Direct3D 9 by combining two independent 2D images for each view. I create an offscreen surface with resolution 3840x1081, put the structure _Nv_Stereo_Image_Header in the last line, left view in the left half of the surface, right view in the right half, and call StretchRect from the offscreen surface to the back buffer.
This used to work fine (but only in fullscreen mode) in drivers up to 266.xx.
In the driver 270.61, it does not work any more. It's like the stereo header is completely ignored. I read through the "NVIDIA 3D Vision Automatic Best Practices guide" front to back five times and my conclusion is that it's not helpful. "Active Stereoization" is apparently unavailable in DX9, and the guide does not explain how I would go about constructing a stereo surface out of two separate views in the "Passive Stereoization" mode.
- Was this capability of StretchRect removed in driver version 270, or were there some changes to the way it's supposed to be used?
- How come some applications are able to display stereo in the windowed mode? What am I supposed to do in my code to add that functionality?
I have an app that used to work, that displays stereoscopic video through Direct3D 9 by combining two independent 2D images for each view. I create an offscreen surface with resolution 3840x1081, put the structure _Nv_Stereo_Image_Header in the last line, left view in the left half of the surface, right view in the right half, and call StretchRect from the offscreen surface to the back buffer.
This used to work fine (but only in fullscreen mode) in drivers up to 266.xx.
In the driver 270.61, it does not work any more. It's like the stereo header is completely ignored. I read through the "NVIDIA 3D Vision Automatic Best Practices guide" front to back five times and my conclusion is that it's not helpful. "Active Stereoization" is apparently unavailable in DX9, and the guide does not explain how I would go about constructing a stereo surface out of two separate views in the "Passive Stereoization" mode.
- Was this capability of StretchRect removed in driver version 270, or were there some changes to the way it's supposed to be used?
- How come some applications are able to display stereo in the windowed mode? What am I supposed to do in my code to add that functionality?
andrewf:
I have an app that used to work, that displays stereoscopic video through Direct3D 9 by combining two independent 2D images for each view. I create an offscreen surface with resolution 3840x1081, put the structure _Nv_Stereo_Image_Header in the last line, left view in the left half of the surface, right view in the right half, and call StretchRect from the offscreen surface to the back buffer.
This used to work fine (but only in fullscreen mode) in drivers up to 266.xx.
In the driver 270.61, it does not work any more. It's like the stereo header is completely ignored. I read through the "NVIDIA 3D Vision Automatic Best Practices guide" front to back five times and my conclusion is that it's not helpful. "Active Stereoization" is apparently unavailable in DX9, and the guide does not explain how I would go about constructing a stereo surface out of two separate views in the "Passive Stereoization" mode.
- Was this capability of StretchRect removed in driver version 270, or were there some changes to the way it's supposed to be used?
- How come some applications are able to display stereo in the windowed mode? What am I supposed to do in my code to add that functionality?
[/quote]
Please PM me your email address.
andrewf:
I have an app that used to work, that displays stereoscopic video through Direct3D 9 by combining two independent 2D images for each view. I create an offscreen surface with resolution 3840x1081, put the structure _Nv_Stereo_Image_Header in the last line, left view in the left half of the surface, right view in the right half, and call StretchRect from the offscreen surface to the back buffer.
This used to work fine (but only in fullscreen mode) in drivers up to 266.xx.
In the driver 270.61, it does not work any more. It's like the stereo header is completely ignored. I read through the "NVIDIA 3D Vision Automatic Best Practices guide" front to back five times and my conclusion is that it's not helpful. "Active Stereoization" is apparently unavailable in DX9, and the guide does not explain how I would go about constructing a stereo surface out of two separate views in the "Passive Stereoization" mode.
- Was this capability of StretchRect removed in driver version 270, or were there some changes to the way it's supposed to be used?
- How come some applications are able to display stereo in the windowed mode? What am I supposed to do in my code to add that functionality?
Please PM me your email address.
Our code worked fine on Windows 7 32/64 bits with Quadro FX3700 or GeForrce 580 cards using drivers [b]v266.45[/b].
Now with drivers [b]v270.71[/b] code is broken, no more passive stereo pair, the new driver does automatic stereo so only one image is presented.
- Is it a bug, or feature was removed/disabled?
- Also sample code for passive/manual stereo in windowed mode will be very appreciate.
Our code worked fine on Windows 7 32/64 bits with Quadro FX3700 or GeForrce 580 cards using drivers v266.45.
Now with drivers v270.71 code is broken, no more passive stereo pair, the new driver does automatic stereo so only one image is presented.
- Is it a bug, or feature was removed/disabled?
- Also sample code for passive/manual stereo in windowed mode will be very appreciate.
I'd also like to know what this solution is, as the data my project is trying to visualise it not part of a 3D geometry, and therefore needs to be treated like a stereo image pair.
I've only recently started working on this, and this is the only post I've found anywhere that seems to indicate that this stereo blitting method is still possible. The machine I'm using was bought specifically to use the 3D Vision tools, but it came loaded with the most recent drivers, so my code has never shown 3D images using this method correctly.
Thanks in advance!
I'd also like to know what this solution is, as the data my project is trying to visualise it not part of a 3D geometry, and therefore needs to be treated like a stereo image pair.
I've only recently started working on this, and this is the only post I've found anywhere that seems to indicate that this stereo blitting method is still possible. The machine I'm using was bought specifically to use the 3D Vision tools, but it came loaded with the most recent drivers, so my code has never shown 3D images using this method correctly.
Thanks in advance!
I see all over these forums people complaining about lack of support from NVidia; cries that appear to fall on deaf ears... The only obvious solution seems to be writing something capable of doing page-flipping... will this cause the 3D Vision system to enter 3D mode? Or do I need to use the NVAPI for that?
With all the talk of these new drivers being 'Automatic' and 'Intelligent' I didn't really anticipate having to do so much work to get them to do anything...
I see all over these forums people complaining about lack of support from NVidia; cries that appear to fall on deaf ears... The only obvious solution seems to be writing something capable of doing page-flipping... will this cause the 3D Vision system to enter 3D mode? Or do I need to use the NVAPI for that?
With all the talk of these new drivers being 'Automatic' and 'Intelligent' I didn't really anticipate having to do so much work to get them to do anything...
Edit: I'll have to try with the 280.19 drivers.
Edit: I'll have to try with the 280.19 drivers.
Not on this board, no. Try the developer forums. Andrew posted a link the developer resources above. Or you can just poke around on the NVIDIA website and find it pretty fast.
Not on this board, no. Try the developer forums. Andrew posted a link the developer resources above. Or you can just poke around on the NVIDIA website and find it pretty fast.
So there is some larger underlying issue connecting the StretchRect method and NVidia cards then? For the meantime I've somewhat solved my problem by mimicking a 3D geometry so the drivers will do their automatic 3D conversion, but it's far from ideal...
@Zloth; I already tried the developer forums and got no response, but it's a good suggestion :D As someone over there has pointed out the 'Developer Resources' are more of a brochure on what Stereo 3D [i]is[/i] than documentation on how to write applications that work with NVidia's hardware (it's missing things like working code samples ;P).
Although, it doesn't seem that the lack of communication is solely related to 3D Vision; I know several people that work at large tech companies associated with NVidia and even they get cryptic non-responses to a lot of tech related queries... oh well =/
So there is some larger underlying issue connecting the StretchRect method and NVidia cards then? For the meantime I've somewhat solved my problem by mimicking a 3D geometry so the drivers will do their automatic 3D conversion, but it's far from ideal...
@Zloth; I already tried the developer forums and got no response, but it's a good suggestion :D As someone over there has pointed out the 'Developer Resources' are more of a brochure on what Stereo 3D is than documentation on how to write applications that work with NVidia's hardware (it's missing things like working code samples ;P).
Although, it doesn't seem that the lack of communication is solely related to 3D Vision; I know several people that work at large tech companies associated with NVidia and even they get cryptic non-responses to a lot of tech related queries... oh well =/