A-10C / Nvidia Vision 3D

[topdog]

Seems to be a typo here, hopefully you can clear it up for peop's as to which it should really be :)

 

The red values should either be both 0 or both 1.

 

StereoMemoEnabled REG_DWORD 0x00000001 (0)

StereoTextureEnable REG_DWORD 0x00000001 (1)

[Rodney1111]

Seems to be a typo here, hopefully you can clear it up for peop's as to which it should really be :)

 

The red values should either be both 0 or both 1.

 

StereoMemoEnabled REG_DWORD 0x00000001 (0)

StereoTextureEnable REG_DWORD 0x00000001 (1)

 

Should both be zero

 

StereoMemoEnabled REG_DWORD 0x00000000 (0)

[vanislepilot]

Forgive gents, but I can't seem to locate the specified Stereo3D path in regedit. I'm running Win 7 64-bit, and the NVidia in-games stereoscopic profile shows up as the DCS: BS.

 

The options I get in the global path are:

 

DrsPath

Hybrid

NvCplApi

NvSvc

NVTweak

Startup

 

Any help would be appreciated!

[Rodney1111]

I had the same problem. After updating to Win 7 64 bit and also updating to NVidia graphics driver 266.58 I found the aforementioned folder no longer exists. (I think it was my update to 266.58 today that did it, I'm pretty sure I had DCS A10 working before with Win 7 64 Bit).

(The great thing about 266.58 is that I got back 100Hz on my ancient 22" CRT. Amazing the difference going from 85 to 100Hz makes with eliminating flicker. I'd stopped playing A10 because I could only get 85 Hz on the monitor and wouldn't dream of flying in 2D but now I'm backk to 100Hz I can play again).

 

Anyway after updating to 266.58 I found the new location of the required folder to be

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NVIDIA Corporation\Global\Stereo3D\GameConfigs\dcs

I then found that there was no dcs folder. When I went to create the dcs folder it wouldn't let me because it said the folder already existed. I concluded the folder was hidden (with no immediately apparent option to unhide it).

Apparently programmers hide their registry folders when they don't want people fiddling with their registry settings.

A quick search of the net shows how to unhide reg folders.

Go to

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Advanced\Folder\Hidden\SHOWALL\

And make sure that you have

CheckedValue RED_DWORD 0x00000001 (1)

With the dcs folder unhidden you can then go to the dcs folder and modify exactly as I describe in previous 2 posts.

3D vision then works very well again.

[Rodney1111]

Should both be zero

 

StereoMemoEnabled REG_DWORD 0x00000000 (0)

 

I was reading my old notes and got mixed up with the 0x00000000 (1) bit and went with 0x00000001 (1) instead of 0x00000000 (0) for StereoMemoEnabled and still got the stereoscopic vision working fine. So it would seem it doesn't actually matter what StereoMemoEnabled value is.

[Frazer]

Interesting reads here in this thread. I'm thinking of gettings a 3 screen setup with 3D.

 

Now, I still have one question for you guys about the FPS.

 

ED products run on low and jumpy FPS (going from 20 to 60+ is not rare). Now, what exactly happens when you run like 20 fps for a moment? Does that mean that you really halfen the fps to 10? Or does the brain still counts 10 on the left and 10 on the right eye as 20 in total?

 

Curious about your experiences :)

[topdog]

minor necro time !

 

The framerate feels smoother, presumably because you're brain is merging time-delayed frames together. E.g this:

 

 

L-----L-----L-----L-----L-----L-----L-----
R-----R-----R-----R-----R-----R-----R-----

 

Feels less smoothed than:

 

L-----L-----L-----L-----L-----L-----L-----
--R-----R-----R-----R-----R-----R-----R---

 

Each right-eye image has to fuse with a left-eye image to be whole, but which one? I suggest it is merging with a little bit of both probably, and thus the intervals feel more like:

 

L--l--L--l--L--l--L--l--L--l--L--l--L--l--
r--R--r--R--r--R--r--R--r--R--r--R--r--R--

 

Where this comes crashing down and immersion breaks, is if you're doing something like looking at an area of screen where lots of change is occurring during the low framerate (let's say with trackir on you pan your head from 9 oclock to 3 oclock), the jumps in pixels for each frame are simply too large to happily merge the images together and you now feel like you've just experienced that kind of strobing effect you get when you wave your hand in front of the TV.

 

Also incidentally, the hit for 3d vision (in auto mode, meaning developers haven't implemented their own stereo3d and rely on the nvidia driver to do it) isn't 50%, a 20 fps rate normally would go down to around 15 fps in 3d vision typically. Only part of the rendering pipeline is hacked by the driver, it doesn't do double the work for the stuff that isn't relevant to it.

 

In other words, it only puts the pieces on the chessboard one time, it then creates two different perspectives of the view. Even smarter custom implementations of some stereo3d implementations can minimise the hit even further, but as we all know to get that, something else in the development has to give way.

 

A word of warning about triple monitors though.. imagine having triple monitors, but only viewing them via a periscope. The glasses create that kind of a tunnel for you because the 3d is only going to work where:

 

a) the focal area of your two eyes overlap in the middle

b) won't be obscured by the frame and rims of the glasses

 

You'd have to be bat**** crazy hardcore I think to shell out at the moment for 3d vision surround (3 monitors all in 3d vision 120Hz mode). Whereas the benefit of either single monitor 3d vision or triple monitor plain 3d would offer the greater reward for the outlay.

 

One thing I'm curious about is ED's standpoint on stereo3d.. would I be right in thinking it's a nice freebie, it won't get intentionally broken in the future, but it's not being explicitly supported and catered for?

 

I'd like to collate the problems and workarounds of using 3d vision, as each patch can have an unintended but serious impact on this, and it would be useful to know if ED would care to officially recognise stereo 3d issues as real bugs or unsupported. Anyone know?

[topdog]

Bleh, one last thing to mention - if you were thinking of overcoming the periscope mode by having the 3 monitors in portrait mode, whether it's a problem with all of them or not I don't know but due to the way the polarization of the glasses work, turning them 90 degrees results in massively less light passing through than before, so rather than being ~50% dimmed it's down to only letting about 25% light through. Not good, for that scenario.

[reemit0772]

I had the same problem. After updating to Win 7 64 bit and also updating to NVidia graphics driver 266.58 I found the aforementioned folder no longer exists.

 

Thanks Rodney, :thumbup: I used your fix for 1.1.0.8 and 275.33. Somewhere in all the updates my registry key went west and was causing my 3Dvision to not work. I wouldn't have known how to fix it myself.

With the new shadows in cockpit 3d is even more immersive.

[jireland607]

Could someone post a screenshot so we can see what it look like :idiot::laugh:

[Dimebag1]

Could someone post a screenshot so we can see what it look like :idiot::laugh:

 

Yes they can, but you will have to go cross-eyed to view it without 3d glasses.

[reemit0772]

Could someone post a screenshot so we can see what it look like :idiot::laugh:

 

 

:wacko: Like Db1 said, I think you would need the kit to see the screenie anyway.

 

Its hard to describe: but when we fly sims in conventional 2D we have to subconsciously think that we sitting are in a cockpit, not just sitting behind a monitor. In 3D you dont have to transfer this belief as much, because the cockpit is presented "in" the monitor with actual depth, every switch, instrument, control and panel is somehow given this extra dimension which gives you the feeling that each part is actually physically there. Also DCS A10 (and to a lesser degree BS) is the first 3D pc "g#m*" I have seen that doesn't feel like you are looking at a "model" when viewed in 3D.

As I said before the shadows really increase the 3D immersion factor too. As far as I can see only the cockpit is presented in real 3D, not the external views.

 

I hope this helps, Im sure others can describe it better.

Edited June 7, 2011 by reemit0772

[topdog]

It's all 3D but the 'fall off' effect (as it is in real life) drops away really quick and you can't really distinguish relative distances anymore. Things are just 'near' or 'far'.

 

You do still get an impressively enhanced sense of elevation, which certainly helps judge landings and altitude-impacting manouvres a lot more (or landing ka-50's on the back of boats I find it helpful too).

 

It would be possible to capture some footage and post it somewhere like youtube (I have some captured in fraps already), for those who have 3D tv's that can see such but aren't able to play games due to lack of 3d vision kit/monitor - if interested.

 

Otherwise the free-viewing (cross-eye or parallel) will help show off the cockpit stuff (which can also be seen in video format, not just screenshot), but the sense of elevation would be too muted and lost under such resolution reductions.

[mmed]

There is no 3D with the latest Nvidia driver (280.26). Same problem with the latest beta (280.19).

[CEPEGA]

Bleh, one last thing to mention - if you were thinking of overcoming the periscope mode by having the 3 monitors in portrait mode, whether it's a problem with all of them or not I don't know but due to the way the polarization of the glasses work, turning them 90 degrees results in massively less light passing through than before, so rather than being ~50% dimmed it's down to only letting about 25% light through. Not good, for that scenario.

 

It's because you need 120Hz vertical sync. When you turn the screens 90°, then you have 120hz horizontal sync but no 120 vertical sync anymore. Horizontal sync on monitors is no more Hz, its kHz.

 

That's because 3D isn't working in portrait mode. It's the same effect when you roll your head by 90°, then your normal-standing 3D monitor turns black :)

Edited August 12, 2011 by CEPEGA

[jason_peters]

Hi

 

Thanks so much to Rodney 1111

 

Stereo 3D does work in DCS A10 and very - all the cockpit is full 3d as well as the world - only issue is labels are 2d (the HUD is fine) - but who plays with labels!!!!

 

You need to look and action posts 54 and 49 (in that order)

 

Thanks again

[PoleCat]

i tried 3d glasses few years back and it was gimmick garbage.

 

maybe todays sets are improved , but i noticed you got to buy a 3d display as well for them,

 

pass on that.

 

Yes well todays version of the Nvidia 3D technology using a 3D enabled display is pretty damned good. Nothing like the older shutter glasses. Pass that on. ;)

 

Out

[The_Nephilim]

OK I just Bought A10c and am experiencing NO 3D in game.. I was using the 301 drivers NO GOOD.. I then tried the 296.10 drivers same thing..

 

I do NOT have the DCS Entry to change in the Registry and My Hidden file entry was already on?

 

What gives I am out of ideas??

 

One thing did change when I tried turning on 3D the terrain got darker but NO 3D effect.. I tried turning up the 3D and Convergance Nothing??

 

Any help with this?? Not going to post too many specs I have 2 480GTX SlI'd and capable of 3D with this system with any game I have tried so far besides A10C.. :( :(

 

It is late and I figured post now and goto bed hopefully when I wake up there will be a responce here worth trying as I have tried the suggestions in post 49 and 54??

 

 

EDIT: I reread post #49 and I needed to SAVE the 3D config with CTRL F7 ingame then input the Launcher.exe in the registry.. IT works NOW..

 

 

1) Run Regedit (if you don't know what this is don't touch it, just wait for Nvidia to release an updated driver).

 

2) Go to the address HKEY_LOCAL_MACHINE\SOFTWARE\NVIDIA Corporation\Global\Stereo3D\GameConfigs\dcs

 

Make the data at above address look like this:

 

(Default) REG_SZ (value not set)

Link1 REG_SZ Launcher.exe

 

 

Hey ED Why do we need to do this and shouldnt this just work in 3D without having to jump through these hoops?? I know you guys did a Bang up job on the A10c and your other sims but these bugs we find need fixing..

 

I am really stumped as to why the 3D would need fixing?? BS was really good in 3D just wierd as too why A10C did Not work in 3D without modifying the Registry??

Edited May 25, 2012 by The_Nephilim

[Rodney1111]

Make sure that when you are running the A-10 beta you have checked "window mode off", the default is to start with it on at least on mine.

 

I am currently running the latest (at time of post) Nvidia driver 310.90 (Win 7 64 bit) and after downloading the latest free version of DCS world I found that I could not get stero vision working until I unchecked the "Full Screen" option. This is the opposite advice to what I gave above (which was true when I gave it for the A10 beta).

 

So where as once you had to run in full screen mode rather than window mode to get stereo vision to work it seems it is now the other way around and you now have to run with "Full screen" off.

[coilwinder]

Rodney1111:

 

Thanks for that! I tried a few combinations in regedit with a folder (or "key") named "dcs", "Dcs" or "DCS" with the expandable string or just regular string named "Link1", ctrl-F7 to save 3D settings, etc, getting nowhere.

 

Unticking the "Full screen" setting worked! It was still full screen though (thankfully), so I'm not sure why it is named that.

 

Using the latest nVidia at this time too (nVidia driver 310.90), Windows Vista Ultimate 64-bit.

[lefuneste01]

hello,

As i am not very pleased with my "Helix mod fix" I am still looking for a way of having good 3Dvision HUD in DCS BS/A10C.

And I think I found something interesting. I changed the depth of the HMS (which is flashing in stock game) in DCS/BS by modifying the file :

DCS World\Mods\aircrafts\Ka-50\Cockpit\Scripts\HELMET\HELMET_page.lua

 

I changed these three lines:

frame.init_pos = {0,-frame_y,0}

ring.init_pos = {0,math.tan(v_angle_shift),0}

cross.init_pos = {0,math.tan(v_angle_shift),0}

to

frame.init_pos = {0,-frame_y,

1.0

}

ring.init_pos = {0,math.tan(v_angle_shift),

1.0

}

cross.init_pos = {0,math.tan(v_angle_shift),

1.0

}

and the HMS is pushed back and no more flashing. The scale is wrong (and maybe the position), but I think that it could be fixed. This could be the start of a trail to have an efficient 3Dvision fix. I am not sure I will have soon some time to look further, but anybody can. I someone find more information, please post them in this thread.

 

It seems to me that there are some things to try in DCS World\Mods\aircrafts\Ka-50\Cockpit\Scripts\HUD\HUD_base_page.lua for BS2 and in DCS World\Mods\aircrafts\A-10C\Cockpit\Scripts\HUD\Indicator\HUD_base_page.lua for A10C...

Edited February 25, 2013 by lefuneste01