HELP - crash on start to desktop with AC Origin and Rainbow Six
  3 / 4    
Do other Uplay games work when 3D is enabled? I know TheBigDogma already tried Assassin's Creed: Unity and Agents of Mayhem profiles but I still have a hunch that the issue lies with those DX10VSCBNumber and DX10DSCBNumber flags. The same black screen and crash happens when 3D is enabled in other games (sometimes only after a game patch) if you don't have those flags properly set. So to eliminate this possibility I suggest adding the executables to Assassin's Creed: Unity in Inspector and change the following in the Unknown flags list at the bottom: 1. First disable this flag 0x70CCB5F0 by setting it from 0x00000008 to 0x00000000 (I don't know what this does and I think it's better to disable it) 2. Notice that the 0x70092D4A and 0x70F8E408 flags are set to 0x0000000E. Change them both from the drop-down list for each test like this: - Test 1 0x70092D4A - 0x00000008 0x70F8E408 - 0x00000008 Apply changes -> Start game -> crash -> Test 2 - Test 2 0x70092D4A - 0x00000009 0x70F8E408 - 0x00000009 Apply changes -> Start game -> crash -> Test 3 - Test 3 0x70092D4A - 0x0000000D 0x70F8E408 - 0x0000000D Apply changes -> Start game -> crash -> Test 4 - Test 4 0x70092D4A - 0x0000000F 0x70F8E408 - 0x0000000F Apply changes -> Start game Also I would check to make sure the patch didn't change the exe name in the game folder or if the game runs through another exe maybe, because otherwise these profile changes are useless. I'm really out of ideas so I hope something works lol.
Do other Uplay games work when 3D is enabled?

I know TheBigDogma already tried Assassin's Creed: Unity and Agents of Mayhem profiles but I still have a hunch that the issue lies with those DX10VSCBNumber and DX10DSCBNumber flags. The same black screen and crash happens when 3D is enabled in other games (sometimes only after a game patch) if you don't have those flags properly set.

So to eliminate this possibility I suggest adding the executables to Assassin's Creed: Unity in Inspector and change the following in the Unknown flags list at the bottom:

1. First disable this flag 0x70CCB5F0 by setting it from 0x00000008 to 0x00000000 (I don't know what this does and I think it's better to disable it)
2. Notice that the 0x70092D4A and 0x70F8E408 flags are set to 0x0000000E. Change them both from the drop-down list for each test like this:
- Test 1
0x70092D4A - 0x00000008
0x70F8E408 - 0x00000008
Apply changes -> Start game -> crash -> Test 2
- Test 2
0x70092D4A - 0x00000009
0x70F8E408 - 0x00000009
Apply changes -> Start game -> crash -> Test 3
- Test 3
0x70092D4A - 0x0000000D
0x70F8E408 - 0x0000000D
Apply changes -> Start game -> crash -> Test 4
- Test 4
0x70092D4A - 0x0000000F
0x70F8E408 - 0x0000000F
Apply changes -> Start game

Also I would check to make sure the patch didn't change the exe name in the game folder or if the game runs through another exe maybe, because otherwise these profile changes are useless.

I'm really out of ideas so I hope something works lol.

#31
Posted 01/22/2018 09:14 PM   
I've only had time to do a quick check on two games... AC: Unity is working as normal in CM mode with the default profile. Far Cry Primal is performing normally with the S3D fix.
I've only had time to do a quick check on two games... AC: Unity is working as normal in CM mode with the default profile. Far Cry Primal is performing normally with the S3D fix.

#32
Posted 01/23/2018 05:11 AM   
OK... I tried disabling 3DV before launching AC: O and the game will now launch. I was having a similar problem with Okami and decided to try disabling 3DV before launching and this also solved the problem and was able to get into the game. What was interesting was that, with Okami (which defaults to launching in Windowed mode prior to the user altering anything), once I set the game to Fullscreen mode, the next time I launched the game, with 3DV enabled, it worked and 3D kicked in. Unfortunately, I have not had the same success with AC: O. I am going to try a few other things after re-installing the game.
OK... I tried disabling 3DV before launching AC: O and the game will now launch.

I was having a similar problem with Okami and decided to try disabling 3DV before launching and this also solved the problem and was able to get into the game.

What was interesting was that, with Okami (which defaults to launching in Windowed mode prior to the user altering anything), once I set the game to Fullscreen mode, the next time I launched the game, with 3DV enabled, it worked and 3D kicked in.

Unfortunately, I have not had the same success with AC: O. I am going to try a few other things after re-installing the game.

#33
Posted 01/23/2018 06:43 PM   
@TheBigDogma I had the same black screen issue with Okami HD. Last time I tried it I had to create a game profile for it, switch to fullscreen mode, because like you said the game defaults to windowed mode at first launch, and then set values for those two flags I mentioned. Tested this now with fresh nVidia drivers and the game launched directly in fullscreen due to my prior settings and with a black screen again. I tried the flags and apparently they were not working like the last time in fullscreen. I removed them and switched to windowed mode but still the black screen was there. However this time when I set the flags once more it worked. So the solution at least on my system was setting those two flags + switching to windowed or fullscreen at least once and then sticking with the two flags enabled. Whenever I remove them I get a black screen no matter if the game starts in fullscreen or windowed mode. I don't remember the best flag pair for 3D in Okami. Some of them have glitches but I think I stayed with 0x0000000E or 0x0000000F in the end. In other games sometimes only a certain pair works correctly.
@TheBigDogma

I had the same black screen issue with Okami HD. Last time I tried it I had to create a game profile for it, switch to fullscreen mode, because like you said the game defaults to windowed mode at first launch, and then set values for those two flags I mentioned.

Tested this now with fresh nVidia drivers and the game launched directly in fullscreen due to my prior settings and with a black screen again. I tried the flags and apparently they were not working like the last time in fullscreen. I removed them and switched to windowed mode but still the black screen was there. However this time when I set the flags once more it worked.

So the solution at least on my system was setting those two flags + switching to windowed or fullscreen at least once and then sticking with the two flags enabled. Whenever I remove them I get a black screen no matter if the game starts in fullscreen or windowed mode.

I don't remember the best flag pair for 3D in Okami. Some of them have glitches but I think I stayed with 0x0000000E or 0x0000000F in the end. In other games sometimes only a certain pair works correctly.

#34
Posted 01/23/2018 07:58 PM   
@Kaimasta i tryed to set those flags in the AC Unity profile at the unknow flags at the bottom but dont know why i dont have the same numbers than you posted there? im on win7 with 388.13 drivers installed.
@Kaimasta

i tryed to set those flags in the AC Unity profile at
the unknow flags at the bottom but dont know why i
dont have the same numbers than you posted there?
im on win7 with 388.13 drivers installed.

#35
Posted 01/23/2018 08:45 PM   
Strange... this is what you should be seeing: [img]https://forums.geforce.com/cmd/default/download-comment-attachment/74437/[/img] Also you should switch from fullscreen to windowed mode at least once before trying the flags.
Strange... this is what you should be seeing:

Image

Also you should switch from fullscreen to windowed mode at least once before trying the flags.
Attachments

Inspector.JPG

#36
Posted 01/23/2018 09:12 PM   
my profile miss all those 0x70...numbers i think you have newer nvidia drivers than me but i dont want to install the newest because the superdepth didnt work on them.
my profile miss all those 0x70...numbers i think you have
newer nvidia drivers than me but i dont want to install the newest
because the superdepth didnt work on them.

#37
Posted 01/23/2018 09:40 PM   
Your drivers are ok. You probably need to get the latest Inspector version 2.1.3.10 https://ci.appveyor.com/project/Orbmu2k/nvidiaprofileinspector/build/artifacts
Your drivers are ok. You probably need to get the latest Inspector version 2.1.3.10 https://ci.appveyor.com/project/Orbmu2k/nvidiaprofileinspector/build/artifacts

#38
Posted 01/23/2018 09:53 PM   
Ah thanks will install this version and try the flag changes.
Ah thanks will install this version and try the flag changes.

#39
Posted 01/23/2018 10:06 PM   
Has someone found a working fix for this problem yet?
Has someone found a working fix for this problem yet?

#40
Posted 02/04/2018 07:36 PM   
No i cant play the game since the 1.2 patch if 3d vision is enabled. For no 3d users the workaround was to set FXAA to off in the NVidia control panel but that didnt help for me.I didnt recieve any answers from the ubisoft support.
No i cant play the game since the 1.2 patch if 3d vision is enabled. For no 3d users
the workaround was to set FXAA to off in the NVidia control panel but that didnt help
for me.I didnt recieve any answers from the ubisoft support.

#41
Posted 02/04/2018 11:18 PM   
Win10 FCU? That version changed a lot of 3D vision code, and I think only the very latest driver is working. If you can, skip the pain and roll back. Or dual boot Win7 for an easier life.
Win10 FCU? That version changed a lot of 3D vision code, and I think only the very latest driver is working. If you can, skip the pain and roll back. Or dual boot Win7 for an easier life.

Acer H5360 (1280x720@120Hz) - ASUS VG248QE with GSync mod - 3D Vision 1&2 - Driver 372.54
GTX 970 - i5-4670K@4.2GHz - 12GB RAM - Win7x64+evilKB2670838 - 4 Disk X25 RAID
SAGER NP9870-S - GTX 980 - i7-6700K - Win10 Pro 1607
Latest 3Dmigoto Release
Bo3b's School for ShaderHackers

#42
Posted 02/05/2018 12:35 AM   
I'm on win 7 and have the same issue, so it's not related to Win10. I was hoping that issue was caused by Uplay, so tried illegal version and still the same. Kaimasta's solution not worked for me, tried with both older and newest Inspector, but the values are different in "unknown" section. I'm playing with Tridef (AC Unity profile) and it's working good. Unfortunately Tridef is officially dead, if you want to buy a license keep in mind that probably there will be no more updates or support. There's a warning thread in its forums. Also Tridef site certificate is not renewed and it may alert some browsers and anti virus softwares, but it's still online.
I'm on win 7 and have the same issue, so it's not related to Win10. I was hoping that issue was caused by Uplay, so tried illegal version and still the same. Kaimasta's solution not worked for me, tried with both older and newest Inspector, but the values are different in "unknown" section.

I'm playing with Tridef (AC Unity profile) and it's working good. Unfortunately Tridef is officially dead, if you want to buy a license keep in mind that probably there will be no more updates or support. There's a warning thread in its forums.

Also Tridef site certificate is not renewed and it may alert some browsers and anti virus softwares, but it's still online.

Asus Deluxe Gen3, Core i7 2700k@4.5Ghz, GTX 1080Ti, 16 GB RAM, Win 7 64bit
Samsung Pro 250 GB SSD, 4 TB WD Black (games)
Benq XL2720Z

#43
Posted 02/05/2018 03:50 AM   
I solved the issue, hope it works for you too. Now game is working with 3DV using 384.76 driver for me. So it's not just a game update issue, but also drivers causing issues. After having issues with latest driver again (monitors don't wake up from sleep with this one too), I installed this old driver. It's the least problematic driver for me and it prooved itself again with this game. Edit: Don't forget to delete ACOrigins profile and add the exe to AC Unity profile (or whatever profile you like) with Nividia Inspector for compatibiliy mod.
I solved the issue, hope it works for you too. Now game is working with 3DV using 384.76 driver for me. So it's not just a game update issue, but also drivers causing issues.

After having issues with latest driver again (monitors don't wake up from sleep with this one too), I installed this old driver. It's the least problematic driver for me and it prooved itself again with this game.


Edit: Don't forget to delete ACOrigins profile and add the exe to AC Unity profile (or whatever profile you like) with Nividia Inspector for compatibiliy mod.

Asus Deluxe Gen3, Core i7 2700k@4.5Ghz, GTX 1080Ti, 16 GB RAM, Win 7 64bit
Samsung Pro 250 GB SSD, 4 TB WD Black (games)
Benq XL2720Z

#44
Posted 02/05/2018 08:35 AM   
Thanks alot lacuna that did the trick installed the 384.76 Driver and voila it works now.
Thanks alot lacuna that did the trick installed the 384.76 Driver
and voila it works now.

#45
Posted 02/05/2018 07:23 PM   
  3 / 4    
Scroll To Top