Author |
Message |
Anonymous
Rating: N/A Votes: 0 (Vote!) | Posted on Saturday, February 09, 2002 - 12:31 pm: | |
Ok, off the bat, I sort of have things working thanks to some information in these forumns, but I want to see if there is any suggestions on this forum, so here is my story... As the title says I have a Asus V6600 Deluxe (Includes the VR100 shutter glasses) running in Windows 98. I decided to use the reference drivers after messing around with the Asus drivers I found the stereo vision lacking in controls (I like sinking into the screen more then popping out, popping out looks bad to me especially with clipping), so I uninstalled the Asus drivers and downloaded and installed the NVidia reference drivers 23.11, and the stereo drivers, and everything went fine in the installation. But where things went wrong was that I could not go higher in frequency, I could only get 60hz to run the test even at 640x480 (with the asus drivers I could get 120hz). When I try to run the test at a higher frequencing a dialog ("RenderEngine version 1.0") appears stating "Generic application error. Enable debug output for detailed information. Switching to the reference rasterizer, a software device that implements the entire Direct3D feature set, but runs very slowly." So I press okay and a software rendered version appears in a window, slow like it says and not in stereo. So that is when I started looking for information about this problem, I came across information that said that Asus VR100 users should set the stereoViewerType to 2, and even provided a registery entry for it. But that only made things worse, as the graphics were glitchy and I still could not reach higher frequencies. But leaving it that way, I did even more reading and came across that people Running Windows XP and the reference drivers also had refresh rate problems, and in reading one of the posts here they recommended the utility PowerStrip. This made the tests run fine, I still could not run it at higher frequencies with in the nVIDIA stereo setup dialog, but PowerStrip forced the test even though it said 60hz, it forced it to the 120hz (the frequencing I set up in PowerStrip). But this solution is clunky. While the stereo test worked fine, I tried playing Quake3, and the first time I ran this it was flickering like it was running at 60hz, so then I changed the video mode to 800x600, and it was flickery there as well, then I changed it back to 640x480 and BAMB, it worked, it was running at 120hz, BUT I have to wear the glasses up side down, because I cant get them to reverese, Ctrl-W doesnt reverse the stereo under quake3 :p. I tried other games as well (return to Wolfenstien demo, and Medal of Honor Allied assault demo) and same results, I have to change the resolution before the game runs at 120hz and I have to wear the glasses up side down. A tutorial for PowerStrip said that if not all applications work, to select something in the Advanced Timing dialog, but I could not find what he was talking about, the tutorial even had images and he referenced one of the images as showing this thing to select, but I still could not find what he was talking about... weird. Also a final note, the graphics were glitchy when stereoViewerType was set to 2, I went into registery and switched it back to 1, and that cleared up the graphical glitchs. Which is weird because I read in several places that if you use the VR100 glasses you have to switch the type to 2, but type 1 works for me, and works better. Anway, that is about where I am in this story, any recommendations to make my stereo viewing easier? |
Christoph Bungert (Admin)
Rating: N/A Votes: 0 (Vote!) | Posted on Thursday, February 14, 2002 - 8:53 pm: | |
Yes the ASUS-mode in the nVidia drivers seems to be buggy for anyone. Let's see if this will be fixed in the future. When using the ASUS controller/glasses with nVidia in viewer type 1 there is no control of the stereo orientation. So about 50% of the time you'll be in reversed stereo, which is very bad. I suggest you return to the ASUS-drivers. Your argument about the ASUS drivers regarding out-of-screen effects isn't correct. The ASUS drivers provide an on-screen-display and hotkeys which allow individual settings. You can set out-of-screen effect to zero easily. This is done with the 'Embossment' control. Start with the foreground set to 0 and the background set to 1. Most likely the 3D-objects, which are represented by green bars won't be distributed evenly over the range. Now change the foreground and background settings to distribute them evenly, this will greatly enhance the 3D-effect. When this is done you can use Embossment to set the point in space where the layer of your screen is (where the parallax is zero). If you move the Embossment to the left out-of-screen effects will vanish. I usually set the Embossment in a way that the HUD in a game has no parallax. O.K. this all sounds complicated, but you have to play around with the settings. Christoph |
Anonymous
Rating: N/A Votes: 0 (Vote!) | Posted on Saturday, February 16, 2002 - 2:16 am: | |
I understand how the Asus driver works, but I dont think you understood my problem with it. Like I said I prefer stereoscopic where objects sink into the screen, rather then objects popping out. When objects pop out, they have more clipping problems, the clipping problem I refer to is when they get to close, one eye will see an object clipped at the edge of the screen, while the other eye will not (thus slightly destroying the stereoscopic illusion). This is not the Asus drivers fault, this is just the results of the technique that Asus drivers have choosen in order to control stereo as well as the amount of limiations they applied to it. I have a 20 inch monitor (17 inch diagonal viewing area) I need a seperation of around 2.5 inches for far away objects (my eyes are aproximately 2.5 inches apart), that is when I look at things in the distance my eyes are more parellel and less crossed, I simply can not do that with the Asus drivers (I dont get enough seperation from them, popping out is easier to do then sinking in) and so the NVidia drivers look better for me. |
Christoph Bungert (Admin)
Rating: N/A Votes: 0 (Vote!) | Posted on Saturday, February 16, 2002 - 9:35 pm: | |
Sounds to me as if you talk about OpenGL with the ASUS drivers. In OpenGL it's hard to get much in-screen effect. In D3D it should be possible to find good settings. Christoph |
Christoph Bungert (Admin)
Rating: N/A Votes: 0 (Vote!) | Posted on Sunday, February 17, 2002 - 11:17 am: | |
I tried the latest ASUS drivers 21.83beta3. It seems they changed at least the bias of the Embossment. Now you only get zero out-of-screen effects when Embossment AND Foreground were 0. It's worse now. Christoph |
Anonymous
Rating: N/A Votes: 0 (Vote!) | Posted on Sunday, February 17, 2002 - 2:46 pm: | |
Yeah that explains it, I was primarily speaking about OpenGL, because my primarily 2 favorite games is Quake3 and Unreal Tournament, and several mods and games (like MOHAA and Wolfenstien) based upon those 2 engines. Problem is that Unreal Tournament never worked for me in stereo in Direct3D (OpenGL is buggier and slower in UT), I suspected it was the way it uses Direct3D that limits it. On the Other hand, as of right now Quake3 is awesome for stereoscopic 3d especially with the NVidia drivers, as well as that the graphics quality from the game is also adds an extra punch (not that I think UT does not have good graphics, but UT out side of mods IMO has better game play and for a while there network gaming performance was better in UT). |
Anonymous
Rating: N/A Votes: 0 (Vote!) | Posted on Sunday, February 17, 2002 - 2:49 pm: | |
Oh yeah, I did try that beta driver recently, thats probably where I got the idea that you only get out-of-screen (adapting your good terminology here ). |
|