Destiny 2 coming to PC
  2 / 3    
3D causes it to crash on launch for me.
3D causes it to crash on launch for me.

#16
Posted 10/27/2017 03:26 PM   
@Pirateguybrush Me TOO, it just sucks to disable 3D to play a game... note 6 Bungie, sit down. [b][i][u]Crash_info:[/u][/i][/b] stack: session_id: Sat_11182017_170557_011180@x64@unknown_pc_user@93_7A_55_E6_C8_5D_084F version: d2_live tiger_final release pc_x64 60823.17.11.10.1426.d2_live 17.11.10 1426 thread information: thread_name: unknown, thread_id: 00002bb0 halt: ### RUNTIME ERROR: EXCEPTION_ACCESS_VIOLATION at 0000000000000000 halt information: (<unknown>) crash: tried to write address 0000000000000000 fatal error detected, current status was:
@Pirateguybrush

Me TOO, it just sucks to disable 3D to play a game... note 6 Bungie, sit down.

Crash_info:


stack:
session_id:
Sat_11182017_170557_011180@x64@unknown_pc_user@93_7A_55_E6_C8_5D_084F
version:
d2_live tiger_final release pc_x64 60823.17.11.10.1426.d2_live 17.11.10 1426
thread information:
thread_name: unknown, thread_id: 00002bb0
halt:
### RUNTIME ERROR: EXCEPTION_ACCESS_VIOLATION at 0000000000000000
halt information:
(<unknown>)
crash: tried to write address 0000000000000000
fatal error detected, current status was:

#17
Posted 11/18/2017 09:27 PM   
Guild wars two recently pushed an update that was crashing the game with a very similar error, developers came to the rescue and fixed it pretty fast good luck with blizzard, activision though =/
Guild wars two recently pushed an update that was crashing the game with a very similar error, developers came to the rescue and fixed it pretty fast good luck with blizzard, activision though =/

i7-4790K CPU 4.8Ghz stable overclock.
16 GB RAM Corsair
EVGA 1080TI SLI
Samsung SSD 840Pro
ASUS Z97-WS
3D Surround ASUS Rog Swift PG278Q(R), 2x PG278Q (yes it works)
Obutto R3volution.
Windows 10 pro 64x (Windows 7 Dual boot)

#18
Posted 11/18/2017 10:56 PM   
Deleting the destiny 2 profile then using the ac unity profile solved this problem for me.
Deleting the destiny 2 profile then using the ac unity profile solved this problem for me.

#19
Posted 11/20/2017 05:47 AM   
[quote="Wil84"]Deleting the destiny 2 profile then using the ac unity profile solved this problem for me. [/quote] Hi Wil84 , thanks so much for this. It looks really good in 1440p compatibility mode . Cheers!
Wil84 said:Deleting the destiny 2 profile then using the ac unity profile solved this problem for me.


Hi Wil84 , thanks so much for this. It looks really good in 1440p compatibility mode . Cheers!

#20
Posted 11/27/2017 06:33 AM   
I recently came up with a decent profile after many hours of trial & error. Even though it works only with 8-10% depth I think it's better than CM and definitely worth mentioning. So first of all set these in the game and quit: Shadow Quality - Lowest | Motion Blur - Off. Open nVidia Profile Inspector and change the following: - StereoCutoff - 0x00000002 Use StereoCutoffDepthNear (This will prevent the player's weapon from splitting at the expense of a 2D halo that appears around you) - StereoCutoffDepthNear - 0x3FC8FC00 (This StereoCutoff value will unsplit some long-ass weapons and also fix some broken compute shadows when using high convergence/depth but it will slightly extend the 2D halo) - StereoFlagsDX10: * 0x00005000 (This will fix some one-eye Compute Shaders and flickering shadows in outdoor areas but it will sometimes make a double stereo correction on world shadows getting them stuck wrong in one eye which can be fixed with an alt+enter to reset the graphics) * 0x0000C000 (This will fix flickering shadows in outdoor areas but Compute Shaders will be rendered in mono; however I recommend using this for now since I found the double stereo correction way too bad and the mono Compute Shaders are still rendered in both eyes) - At the bottom of the list disable this flag "0x00110992" with this value 0x00000000 (this is only required if you get crashes with the latest drivers; after updating W10 FCU and the nVidia drivers to 388.43 this is no longer occurring at startup for me but randomly while playing) If you find the 2D halo around you too annoying, you can either decrease the in-game FOV value (which apparently hides some of the broken world shadows that appear near the camera when you're playing at high conv) or use the default StereoCutoffDepthNear value if you're not playing with snipers or other long weapons but keep in mind that broken compute shadows will be more noticeable at high depth/conv values. Other issues: - Some lights and decals are broken, couldn't find any good profile setting to fix this. - World and dynamic shadows have to be aligned with proper depth/convergence levels. This is the biggest issue unfortunately, which is why I'm playing with a low 8-10% depth most of the time. - Some cutscenes will suffer from the 2D halo so I suggest turning 3D off or lowering convergence. Anywho I think the graphics are amazing in 3D even with such a low depth level. Too bad using 3DMigoto will probably get you banned, if the game even starts that is. I will continue working on this profile and see if I can find more useful things.
I recently came up with a decent profile after many hours of trial & error. Even though it works only with 8-10% depth I think it's better than CM and definitely worth mentioning. So first of all set these in the game and quit: Shadow Quality - Lowest | Motion Blur - Off.

Open nVidia Profile Inspector and change the following:

- StereoCutoff - 0x00000002 Use StereoCutoffDepthNear (This will prevent the player's weapon from splitting at the expense of a 2D halo that appears around you)

- StereoCutoffDepthNear - 0x3FC8FC00 (This StereoCutoff value will unsplit some long-ass weapons and also fix some broken compute shadows when using high convergence/depth but it will slightly extend the 2D halo)

- StereoFlagsDX10:
* 0x00005000 (This will fix some one-eye Compute Shaders and flickering shadows in outdoor areas but it will sometimes make a double stereo correction on world shadows getting them stuck wrong in one eye which can be fixed with an alt+enter to reset the graphics)
* 0x0000C000 (This will fix flickering shadows in outdoor areas but Compute Shaders will be rendered in mono; however I recommend using this for now since I found the double stereo correction way too bad and the mono Compute Shaders are still rendered in both eyes)

- At the bottom of the list disable this flag "0x00110992" with this value 0x00000000 (this is only required if you get crashes with the latest drivers; after updating W10 FCU and the nVidia drivers to 388.43 this is no longer occurring at startup for me but randomly while playing)

If you find the 2D halo around you too annoying, you can either decrease the in-game FOV value (which apparently hides some of the broken world shadows that appear near the camera when you're playing at high conv) or use the default StereoCutoffDepthNear value if you're not playing with snipers or other long weapons but keep in mind that broken compute shadows will be more noticeable at high depth/conv values.

Other issues:
- Some lights and decals are broken, couldn't find any good profile setting to fix this.
- World and dynamic shadows have to be aligned with proper depth/convergence levels. This is the biggest issue unfortunately, which is why I'm playing with a low 8-10% depth most of the time.
- Some cutscenes will suffer from the 2D halo so I suggest turning 3D off or lowering convergence.

Anywho I think the graphics are amazing in 3D even with such a low depth level. Too bad using 3DMigoto will probably get you banned, if the game even starts that is.

I will continue working on this profile and see if I can find more useful things.

#21
Posted 11/28/2017 05:48 AM   
[quote="Kaimasta"]I recently came up with a decent profile after many hours of trial & error. Even though it works only with 8-10% depth I think it's better than CM and definitely worth mentioning. So first of all set these in the game and quit: Shadow Quality - Lowest | Motion Blur - Off. Open nVidia Profile Inspector and change the following: - StereoCutoff - 0x00000002 Use StereoCutoffDepthNear (This will prevent the player's weapon from splitting at the expense of a 2D halo that appears around you) - StereoCutoffDepthNear - 0x3FC8FC00 (This StereoCutoff value will unsplit some long-ass weapons and also fix some broken compute shadows when using high convergence/depth but it will slightly extend the 2D halo) - StereoFlagsDX10: * 0x00005000 (This will fix some one-eye Compute Shaders and flickering shadows in outdoor areas but it will sometimes make a double stereo correction on world shadows getting them stuck wrong in one eye which can be fixed with an alt+enter to reset the graphics) * 0x0000C000 (This will fix flickering shadows in outdoor areas but Compute Shaders will be rendered in mono; however I recommend using this for now since I found the double stereo correction way too bad and the mono Compute Shaders are still rendered in both eyes) - At the bottom of the list disable this flag "0x00110992" with this value 0x00000000 (this is only required if you get crashes with the latest drivers; after updating W10 FCU and the nVidia drivers to 388.43 this is no longer occurring at startup for me but randomly while playing) If you find the 2D halo around you too annoying, you can either decrease the in-game FOV value (which apparently hides some of the broken world shadows that appear near the camera when you're playing at high conv) or use the default StereoCutoffDepthNear value if you're not playing with snipers or other long weapons but keep in mind that broken compute shadows will be more noticeable at high depth/conv values. Other issues: - Some lights and decals are broken, couldn't find any good profile setting to fix this. - World and dynamic shadows have to be aligned with proper depth/convergence levels. This is the biggest issue unfortunately, which is why I'm playing with a low 8-10% depth most of the time. - Some cutscenes will suffer from the 2D halo so I suggest turning 3D off or lowering convergence. Anywho I think the graphics are amazing in 3D even with such a low depth level. Too bad using 3DMigoto will probably get you banned, if the game even starts that is. I will continue working on this profile and see if I can find more useful things. [/quote] Hey man! You are awesome! Did you have more Information for better profiles jet? Your settings helped alot, the broken shadows are gone and the "reflect" on some objects is also very good now. Problem atm are mostly the "lights spot´s" - the are too deep. the left and right one is too extreme, it looks not nice and is very exhausting for eyes. Love to hear a update!
Kaimasta said:I recently came up with a decent profile after many hours of trial & error. Even though it works only with 8-10% depth I think it's better than CM and definitely worth mentioning. So first of all set these in the game and quit: Shadow Quality - Lowest | Motion Blur - Off.

Open nVidia Profile Inspector and change the following:

- StereoCutoff - 0x00000002 Use StereoCutoffDepthNear (This will prevent the player's weapon from splitting at the expense of a 2D halo that appears around you)

- StereoCutoffDepthNear - 0x3FC8FC00 (This StereoCutoff value will unsplit some long-ass weapons and also fix some broken compute shadows when using high convergence/depth but it will slightly extend the 2D halo)

- StereoFlagsDX10:
* 0x00005000 (This will fix some one-eye Compute Shaders and flickering shadows in outdoor areas but it will sometimes make a double stereo correction on world shadows getting them stuck wrong in one eye which can be fixed with an alt+enter to reset the graphics)
* 0x0000C000 (This will fix flickering shadows in outdoor areas but Compute Shaders will be rendered in mono; however I recommend using this for now since I found the double stereo correction way too bad and the mono Compute Shaders are still rendered in both eyes)

- At the bottom of the list disable this flag "0x00110992" with this value 0x00000000 (this is only required if you get crashes with the latest drivers; after updating W10 FCU and the nVidia drivers to 388.43 this is no longer occurring at startup for me but randomly while playing)

If you find the 2D halo around you too annoying, you can either decrease the in-game FOV value (which apparently hides some of the broken world shadows that appear near the camera when you're playing at high conv) or use the default StereoCutoffDepthNear value if you're not playing with snipers or other long weapons but keep in mind that broken compute shadows will be more noticeable at high depth/conv values.

Other issues:
- Some lights and decals are broken, couldn't find any good profile setting to fix this.
- World and dynamic shadows have to be aligned with proper depth/convergence levels. This is the biggest issue unfortunately, which is why I'm playing with a low 8-10% depth most of the time.
- Some cutscenes will suffer from the 2D halo so I suggest turning 3D off or lowering convergence.

Anywho I think the graphics are amazing in 3D even with such a low depth level. Too bad using 3DMigoto will probably get you banned, if the game even starts that is.

I will continue working on this profile and see if I can find more useful things.


Hey man! You are awesome! Did you have more Information for better profiles jet?

Your settings helped alot, the broken shadows are gone and the "reflect" on some objects is also very good now.

Problem atm are mostly the "lights spot´s" - the are too deep. the left and right one is too extreme, it looks not nice and is very exhausting for eyes.

Love to hear a update!

#22
Posted 12/05/2017 12:58 PM   
Glad you like the profile but there's only so much you can do with profile editing and sadly there's no setting that could possibly fix the light spots so if they bother you much you'll have to use a lower depth and align them with the convergence hotkeys to get a bare minimum 3D experience. A game like this can't be properly fixed without 3Dmigoto and from what I've read a lot of stuff is banned in this game including some overlays and injectors like reshade or sweetfx... not even taking a 3D screenshot works :(
Glad you like the profile but there's only so much you can do with profile editing and sadly there's no setting that could possibly fix the light spots so if they bother you much you'll have to use a lower depth and align them with the convergence hotkeys to get a bare minimum 3D experience. A game like this can't be properly fixed without 3Dmigoto and from what I've read a lot of stuff is banned in this game including some overlays and injectors like reshade or sweetfx... not even taking a 3D screenshot works :(

#23
Posted 12/06/2017 02:33 PM   
Oh man :( What a bad news mate ;( But thanks alot for your work - with your settings the game is for me 90% Playable in 3D. Its so disgusting from the developer that they don´t take some effects for 3D to standard works. I dont understand why the developer always need to get a single 3D Game, why its not a standard like some good homework? Ill payed so much money nVidia to have a great setup, to play in 2k full settings with 3D and 100FPS+ and then nvidia/bungie is not to have for some free work.
Oh man :( What a bad news mate ;( But thanks alot for your work - with your settings the game is for me 90% Playable in 3D.

Its so disgusting from the developer that they don´t take some effects for 3D to standard works. I dont understand why the developer always need to get a single 3D Game, why its not a standard like some good homework?

Ill payed so much money nVidia to have a great setup, to play in 2k full settings with 3D and 100FPS+ and then nvidia/bungie is not to have for some free work.

#24
Posted 12/06/2017 05:27 PM   
Duplicate because of server issue...
Duplicate because of server issue...

3D Vision must live! NVIDIA, don't let us down!

#25
Posted 01/05/2018 03:03 AM   
Duplicate because of server issue...
Duplicate because of server issue...

3D Vision must live! NVIDIA, don't let us down!

#26
Posted 01/05/2018 03:04 AM   
Well, saw there was a demo so I just downloaded 36GB to test it as I still have the promo code but wasn't sure to keep or sell. Game won't start normally on my new rig with fresh Windows 10 installed. I tried a few things and was able to start it using Vista SP2 compatibility. Strange! Then I see 3D does not kick in, because it's the demo maybe? Nothing in 3D Fix Manager. Is the only option yet to use nVidia Profile Inspector?
Well, saw there was a demo so I just downloaded 36GB to test it as I still have the promo code but wasn't sure to keep or sell.

Game won't start normally on my new rig with fresh Windows 10 installed. I tried a few things and was able to start it using Vista SP2 compatibility. Strange!

Then I see 3D does not kick in, because it's the demo maybe? Nothing in 3D Fix Manager. Is the only option yet to use nVidia Profile Inspector?

3D Vision must live! NVIDIA, don't let us down!

#27
Posted 01/05/2018 03:06 AM   
You probably need one of the latest nvidia drivers as the older ones pre-388.00 don't even have a Destiny 2 profile. So 3D doesn't work either because the game has no profile in your drivers or because you set Vista SP2 compatibility. In any case, 3D is pretty broken unless you use a CM profile from another game or modify its own profile with the settings I mentioned.
You probably need one of the latest nvidia drivers as the older ones pre-388.00 don't even have a Destiny 2 profile. So 3D doesn't work either because the game has no profile in your drivers or because you set Vista SP2 compatibility.

In any case, 3D is pretty broken unless you use a CM profile from another game or modify its own profile with the settings I mentioned.

#28
Posted 01/05/2018 05:51 AM   
I'm overwriting my initial post... didn't make much sense. Initially I wasn't able to start game without having destiny2.exe set with Windows 7 compatibility but now it works without it, strange. I wasn't able to have 3D to kick in and now it works, will now try to modify Destiny 2 profile with settings above.
I'm overwriting my initial post... didn't make much sense. Initially I wasn't able to start game without having destiny2.exe set with Windows 7 compatibility but now it works without it, strange.

I wasn't able to have 3D to kick in and now it works, will now try to modify Destiny 2 profile with settings above.

3D Vision must live! NVIDIA, don't let us down!

#29
Posted 01/06/2018 04:54 PM   
...
...

3D Vision must live! NVIDIA, don't let us down!

#30
Posted 01/06/2018 04:59 PM   
  2 / 3    
Scroll To Top