I get this shadow problem from time to time. although probably unrelated, but if I go out of game, disable 3dvision, turn it back on and make sure Vsync is off, the problem disappears.
I actually also get this issue in GTAIV
I get this shadow problem from time to time. although probably unrelated, but if I go out of game, disable 3dvision, turn it back on and make sure Vsync is off, the problem disappears.
I actually also get this issue in GTAIV
i7-4790K CPU 4.8Ghz stable overclock.
16 GB RAM Corsair
ASUS Turbo 2080TI
Samsung SSD 840Pro
ASUS Z97-WS3D
Surround ASUS Rog Swift PG278Q(R), 2x PG278Q (yes it works)
Obutto R3volution.
Windows 10 pro 64x (Windows 7 Dual boot)
I uninstalled Windows 10 and got back to Windows 7. My game no longer crashes at start with the Migoto Wrapper so Win 10 definitely was the problem. I will reinstall Windows 10 after i finish this game.
I had a few aura shadows in cinematics but Post process effects = medium fixed it.
So far, the 3D is perfect. Tks guys.
I uninstalled Windows 10 and got back to Windows 7. My game no longer crashes at start with the Migoto Wrapper so Win 10 definitely was the problem. I will reinstall Windows 10 after i finish this game.
I had a few aura shadows in cinematics but Post process effects = medium fixed it.
Finally got some time to give this some attention again... GOOD NEWS, all I had to do was reinstall my geforce drivers (latest version)!
So now I have DA:I running on Windows 10 using the Flugan wrapper with all my settings maxed (except for those 2 or 3 explicitly mentioned on the helixmod page).
It was TOTALLY worth the effort, awesome game and brilliant in 3D. If I had struggled every day for a week it would still have been worth it, so don't give up guys!
The only negative for me is that I have to change my convergence pretty often to make the cutscenes look better, but those are usually pretty long anyway so no biggie.
Finally got some time to give this some attention again... GOOD NEWS, all I had to do was reinstall my geforce drivers (latest version)!
So now I have DA:I running on Windows 10 using the Flugan wrapper with all my settings maxed (except for those 2 or 3 explicitly mentioned on the helixmod page).
It was TOTALLY worth the effort, awesome game and brilliant in 3D. If I had struggled every day for a week it would still have been worth it, so don't give up guys!
The only negative for me is that I have to change my convergence pretty often to make the cutscenes look better, but those are usually pretty long anyway so no biggie.
I havn't figured out good convergence setting for cutscenes but when that is done you will be able to do a hold button to be used for cutscenes and a higher convergence otherwise.
It is hard to find a convergence that works under all circumstances.
Here is a hold button to adjust convergence for cinematics.
Actual value can be tweaked to your liking.
[KeyCinematics]
Key = c
convergence = 0.63422567
type = hold
transition = 200
transition_type = cosine
release_transition = 200
release_transition_type = cosine
I havn't figured out good convergence setting for cutscenes but when that is done you will be able to do a hold button to be used for cutscenes and a higher convergence otherwise.
It is hard to find a convergence that works under all circumstances.
Here is a hold button to adjust convergence for cinematics.
Actual value can be tweaked to your liking.
[KeyCinematics]
Key = c
convergence = 0.63422567
type = hold
transition = 200
transition_type = cosine
release_transition = 200
release_transition_type = cosine
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?
I may have spoke too soon. The 3d is perfect but some cutscenes are rendered in 2d. Like the one where they send the ravens to find the black woman. Right before the cutscene with the female dwarf in the second map. That cutscene for some reason always displays in 2d for me.
(both lenses display the left image but the right lense from time to time keeps trying to display the other image without success)
Any ideas why this is happening?
I may have spoke too soon. The 3d is perfect but some cutscenes are rendered in 2d. Like the one where they send the ravens to find the black woman. Right before the cutscene with the female dwarf in the second map. That cutscene for some reason always displays in 2d for me.
(both lenses display the left image but the right lense from time to time keeps trying to display the other image without success)
[quote="Payne-TK"]I may have spoke too soon. The 3d is perfect but some cutscenes are rendered in 2d. Like the one where they send the ravens to find the black woman. Right before the cutscene with the female dwarf in the second map. That cutscene for some reason always displays in 2d for me.
(both lenses display the left image but the right lense from time to time keeps trying to display the other image without success)
Any ideas why this is happening?[/quote]
I had what sounds like the same problem, except it happened with every single cutscene. Setting the Post-Process Quality setting to Medium fixed it for me.
Payne-TK said:I may have spoke too soon. The 3d is perfect but some cutscenes are rendered in 2d. Like the one where they send the ravens to find the black woman. Right before the cutscene with the female dwarf in the second map. That cutscene for some reason always displays in 2d for me.
(both lenses display the left image but the right lense from time to time keeps trying to display the other image without success)
Any ideas why this is happening?
I had what sounds like the same problem, except it happened with every single cutscene. Setting the Post-Process Quality setting to Medium fixed it for me.
[quote="Flugan"]I havn't figured out good convergence setting for cutscenes but when that is done you will be able to do a hold button to be used for cutscenes and a higher convergence otherwise.
It is hard to find a convergence that works under all circumstances.
Here is a hold button to adjust convergence for cinematics.
Actual value can be tweaked to your liking.
[KeyCinematics]
Key = c
convergence = 0.63422567
type = hold
transition = 200
transition_type = cosine
release_transition = 200
release_transition_type = cosine[/quote]
Legend! Thank you so much!
Flugan said:I havn't figured out good convergence setting for cutscenes but when that is done you will be able to do a hold button to be used for cutscenes and a higher convergence otherwise.
It is hard to find a convergence that works under all circumstances.
Here is a hold button to adjust convergence for cinematics.
Actual value can be tweaked to your liking.
[KeyCinematics]
Key = c
convergence = 0.63422567
type = hold
transition = 200
transition_type = cosine
release_transition = 200
release_transition_type = cosine
The mountains in the background are also rendered in 2d for me, also burning fires and a shadow here and there is out of place.
I already have
Post-Process Quality: Medium
Shader Cache: OFF
Post-Process AA: OFF
MSAA: OFF
Using Flawless Widescreen
Entering game with Administrative Rights
I don't know what else to do.
Nevermind, i updated the drivers though GeForce Experience, disabled shader cache and vsync again, and somehow that fixed the broken mountains, burning fires and shadows.
Now, other than the cutscene i mentioned, everything is cristal clear and the 3d is impeccable. Hope i wont run into another cutscene where the right image is broken. I just love the cutscenes from this game. :)
Nevermind, i updated the drivers though GeForce Experience, disabled shader cache and vsync again, and somehow that fixed the broken mountains, burning fires and shadows.
Now, other than the cutscene i mentioned, everything is cristal clear and the 3d is impeccable. Hope i wont run into another cutscene where the right image is broken. I just love the cutscenes from this game. :)
Items rendered in 2d is Vsync related. Play around with the different options should resolve it, and you wont need to disable the shader cache.
i7-4790K CPU 4.8Ghz stable overclock.
16 GB RAM Corsair
ASUS Turbo 2080TI
Samsung SSD 840Pro
ASUS Z97-WS3D
Surround ASUS Rog Swift PG278Q(R), 2x PG278Q (yes it works)
Obutto R3volution.
Windows 10 pro 64x (Windows 7 Dual boot)
I have never come across any game with so much conflicting information with regards to getting it to run in 3D. The solution just seems to be so different for everybody. I can't even suggest setting everything to low and taking it from there, because in some situations one setting has to be set to Medium or High or whatever otherwise everything breaks. But for other people it works just fine.
Like Payne-TK said as well, reinstalling your GeForce drivers should make a difference but even I had to do that twice. After changing some GENERAL and seemingly unrelated settings in NVidia Control Panel it also crashed the game and I could only get it going again with a reinstall (after uninstalling with DDU). So frustrating.
It's a real shame because a lot of people probably just give up, I know I very nearly did. All I can say is DA:I is awesome and worth the effort!
I have never come across any game with so much conflicting information with regards to getting it to run in 3D. The solution just seems to be so different for everybody. I can't even suggest setting everything to low and taking it from there, because in some situations one setting has to be set to Medium or High or whatever otherwise everything breaks. But for other people it works just fine.
Like Payne-TK said as well, reinstalling your GeForce drivers should make a difference but even I had to do that twice. After changing some GENERAL and seemingly unrelated settings in NVidia Control Panel it also crashed the game and I could only get it going again with a reinstall (after uninstalling with DDU). So frustrating.
It's a real shame because a lot of people probably just give up, I know I very nearly did. All I can say is DA:I is awesome and worth the effort!
OMG, the 3D problem was so much deeper than just this game that i finally got it to work (and it's still a struggle) ...but at least now i know how to make all my games run smooth.
After days of trying the fix and reinstalling video drivers even sound drivers, i discovered a common problem in all my games. (regardless of drivers)
In a different game that i used for experimentation, with adaptive v-sync, or any v-sync, or even without v-sync, i had constant 60 fps in 3D (more without v-sync but it doesn't matter). After i Alt-Tab to desktop and back, my fps dropped to a constant 56-57 FPS but the worst problem is that i got a constant snappy camera that it's more visible if you look at the left and right images without the glasses. This is happening in all games, in DA:I too but i will come back to it later.
It's like a tremble while you move or rotate the camera. It doesn't go away unless you travel to a new map and back to trigger the loading screen so it can load new shaders or something. Every time you Alt-Tab the problem comes back, you lose a couple of FPS and the camera smoothness becomes agitated and snappy while moved. This only happens in 3D and it can make you dizzy if you ignore it.
So if you want smooth gameplay in every game, NEVER EVER Alt-Tab (unless you can easily reload map)
Now let me get back to Dragon Age Inquisition. The problem is, that you get it from the very start because it deactivates and reactivates the 3D at every loading screen, so it's like an involuntary Alt-Tab without the solution of reloading the map.
The real solution is the one posted on the blog by mike_ar69. Open regedit, change the StereoDefaultOn values, don't have any window open other than the game, at every loading screen, count 2 seconds when you see the cards and ALT+TAB to Windows, then count to 2 and ALT+TAB back, and reactivate the 3D with Ctrl-T once the game is loaded. And BOOM, smooth gameplay!! (this also keeps the 3D together for some reason as it's no longer breaking the images)
I lost so much faith in Alt-Tab-ing that i am constantly using Fraps in all games to monitor it, and Alt-Tab breaks the camera smoothness every single time. Not even V-Sync ON/Off can help you after that.
TL;DR = conclusion is: always check your camera in all games after you alt-tab to see if it's no longer smooth, and fix it with reloading the map.
(in the case of DA:I, go to the step: "VII. Game Stability issue." from the blog posted by mike_ar69)
Tks alot guys for the fix...
OMG, the 3D problem was so much deeper than just this game that i finally got it to work (and it's still a struggle) ...but at least now i know how to make all my games run smooth.
After days of trying the fix and reinstalling video drivers even sound drivers, i discovered a common problem in all my games. (regardless of drivers)
In a different game that i used for experimentation, with adaptive v-sync, or any v-sync, or even without v-sync, i had constant 60 fps in 3D (more without v-sync but it doesn't matter). After i Alt-Tab to desktop and back, my fps dropped to a constant 56-57 FPS but the worst problem is that i got a constant snappy camera that it's more visible if you look at the left and right images without the glasses. This is happening in all games, in DA:I too but i will come back to it later.
It's like a tremble while you move or rotate the camera. It doesn't go away unless you travel to a new map and back to trigger the loading screen so it can load new shaders or something. Every time you Alt-Tab the problem comes back, you lose a couple of FPS and the camera smoothness becomes agitated and snappy while moved. This only happens in 3D and it can make you dizzy if you ignore it.
So if you want smooth gameplay in every game, NEVER EVER Alt-Tab (unless you can easily reload map)
Now let me get back to Dragon Age Inquisition. The problem is, that you get it from the very start because it deactivates and reactivates the 3D at every loading screen, so it's like an involuntary Alt-Tab without the solution of reloading the map.
The real solution is the one posted on the blog by mike_ar69. Open regedit, change the StereoDefaultOn values, don't have any window open other than the game, at every loading screen, count 2 seconds when you see the cards and ALT+TAB to Windows, then count to 2 and ALT+TAB back, and reactivate the 3D with Ctrl-T once the game is loaded. And BOOM, smooth gameplay!! (this also keeps the 3D together for some reason as it's no longer breaking the images)
I lost so much faith in Alt-Tab-ing that i am constantly using Fraps in all games to monitor it, and Alt-Tab breaks the camera smoothness every single time. Not even V-Sync ON/Off can help you after that.
TL;DR = conclusion is: always check your camera in all games after you alt-tab to see if it's no longer smooth, and fix it with reloading the map.
(in the case of DA:I, go to the step: "VII. Game Stability issue." from the blog posted by mike_ar69)
Just a heads up!
The latest DLC: Trespasser is pure epic! If you are into Dragon Age Universe you will simply LOVE IT;)
A MUST for this game;) ^_^
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
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 actually also get this issue in GTAIV
i7-4790K CPU 4.8Ghz stable overclock.
16 GB RAM Corsair
ASUS Turbo 2080TI
Samsung SSD 840Pro
ASUS Z97-WS3D
Surround ASUS Rog Swift PG278Q(R), 2x PG278Q (yes it works)
Obutto R3volution.
Windows 10 pro 64x (Windows 7 Dual boot)
I had a few aura shadows in cinematics but Post process effects = medium fixed it.
So far, the 3D is perfect. Tks guys.
i7-6700K 4.0GHz, GTX 970, 8 Gb DDR4, SSD
So now I have DA:I running on Windows 10 using the Flugan wrapper with all my settings maxed (except for those 2 or 3 explicitly mentioned on the helixmod page).
It was TOTALLY worth the effort, awesome game and brilliant in 3D. If I had struggled every day for a week it would still have been worth it, so don't give up guys!
The only negative for me is that I have to change my convergence pretty often to make the cutscenes look better, but those are usually pretty long anyway so no biggie.
It is hard to find a convergence that works under all circumstances.
Here is a hold button to adjust convergence for cinematics.
Actual value can be tweaked to your liking.
[KeyCinematics]
Key = c
convergence = 0.63422567
type = hold
transition = 200
transition_type = cosine
release_transition = 200
release_transition_type = cosine
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
(both lenses display the left image but the right lense from time to time keeps trying to display the other image without success)
Any ideas why this is happening?
i7-6700K 4.0GHz, GTX 970, 8 Gb DDR4, SSD
I had what sounds like the same problem, except it happened with every single cutscene. Setting the Post-Process Quality setting to Medium fixed it for me.
Legend! Thank you so much!
I already have
Post-Process Quality: Medium
Shader Cache: OFF
Post-Process AA: OFF
MSAA: OFF
Using Flawless Widescreen
Entering game with Administrative Rights
I don't know what else to do.
i7-6700K 4.0GHz, GTX 970, 8 Gb DDR4, SSD
Now, other than the cutscene i mentioned, everything is cristal clear and the 3d is impeccable. Hope i wont run into another cutscene where the right image is broken. I just love the cutscenes from this game. :)
i7-6700K 4.0GHz, GTX 970, 8 Gb DDR4, SSD
Overclocked Intel® Core™i5-4690k Quad Core
32 Gb RAM
8GB GEFORCE GTX 1080
3D Vision 2
Windows 10 64 Bit
NVidia driver 419.17
SAMSUNG - UE55H8000 Smart 3D 55" Curved
Philips G-Sync 272G
Oculus Rift with Touch controlers
i7-4790K CPU 4.8Ghz stable overclock.
16 GB RAM Corsair
ASUS Turbo 2080TI
Samsung SSD 840Pro
ASUS Z97-WS3D
Surround ASUS Rog Swift PG278Q(R), 2x PG278Q (yes it works)
Obutto R3volution.
Windows 10 pro 64x (Windows 7 Dual boot)
Like Payne-TK said as well, reinstalling your GeForce drivers should make a difference but even I had to do that twice. After changing some GENERAL and seemingly unrelated settings in NVidia Control Panel it also crashed the game and I could only get it going again with a reinstall (after uninstalling with DDU). So frustrating.
It's a real shame because a lot of people probably just give up, I know I very nearly did. All I can say is DA:I is awesome and worth the effort!
After days of trying the fix and reinstalling video drivers even sound drivers, i discovered a common problem in all my games. (regardless of drivers)
In a different game that i used for experimentation, with adaptive v-sync, or any v-sync, or even without v-sync, i had constant 60 fps in 3D (more without v-sync but it doesn't matter). After i Alt-Tab to desktop and back, my fps dropped to a constant 56-57 FPS but the worst problem is that i got a constant snappy camera that it's more visible if you look at the left and right images without the glasses. This is happening in all games, in DA:I too but i will come back to it later.
It's like a tremble while you move or rotate the camera. It doesn't go away unless you travel to a new map and back to trigger the loading screen so it can load new shaders or something. Every time you Alt-Tab the problem comes back, you lose a couple of FPS and the camera smoothness becomes agitated and snappy while moved. This only happens in 3D and it can make you dizzy if you ignore it.
So if you want smooth gameplay in every game, NEVER EVER Alt-Tab (unless you can easily reload map)
Now let me get back to Dragon Age Inquisition. The problem is, that you get it from the very start because it deactivates and reactivates the 3D at every loading screen, so it's like an involuntary Alt-Tab without the solution of reloading the map.
The real solution is the one posted on the blog by mike_ar69. Open regedit, change the StereoDefaultOn values, don't have any window open other than the game, at every loading screen, count 2 seconds when you see the cards and ALT+TAB to Windows, then count to 2 and ALT+TAB back, and reactivate the 3D with Ctrl-T once the game is loaded. And BOOM, smooth gameplay!! (this also keeps the 3D together for some reason as it's no longer breaking the images)
I lost so much faith in Alt-Tab-ing that i am constantly using Fraps in all games to monitor it, and Alt-Tab breaks the camera smoothness every single time. Not even V-Sync ON/Off can help you after that.
TL;DR = conclusion is: always check your camera in all games after you alt-tab to see if it's no longer smooth, and fix it with reloading the map.
(in the case of DA:I, go to the step: "VII. Game Stability issue." from the blog posted by mike_ar69)
Tks alot guys for the fix...
i7-6700K 4.0GHz, GTX 970, 8 Gb DDR4, SSD
The latest DLC: Trespasser is pure epic! If you are into Dragon Age Universe you will simply LOVE IT;)
A MUST for this game;) ^_^
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)