"Alice: Madness Returns" crashes under 331.82 with 3D Vision Enabled
1 / 2
Hi, every time I try to get past the player selection screen the game crashes whenever I have 3D Vision enabled, even though the game claims to support 3D Vision and the settings are there. Any ideas to solve it?
Besides, this is another title that claims to use PhysX but the visual indicator reads CPU instead of GPU, even though PhysX is configured as Auto in the NVIDIA Control Panel...
Miguel
Hi, every time I try to get past the player selection screen the game crashes whenever I have 3D Vision enabled, even though the game claims to support 3D Vision and the settings are there. Any ideas to solve it?
Besides, this is another title that claims to use PhysX but the visual indicator reads CPU instead of GPU, even though PhysX is configured as Auto in the NVIDIA Control Panel...
Miguel
ASUS P8Z77-V with Intel Core i5 3570K 3.5~4.2 Ghz, 32 GB DDR3 2400, Windows 10 Pro x64 - Version 1511 Build 10586.545.
ASUS STRIX GTX970 DC2OC 4GD5, 4 GB GDDR5, NVIDIA 3D Vision P854 Glasses.
BenQ XL2420T. WD Caviar Black 2 TB, 7200 rpm.
ASUS ROG GL552VW-DH71 with Intel Core i7 6700HQ 2.6 Ghz, 16 GB DDR4 2133, Windows 10 Pro x64 - Version 10.0 Build 10240.
Built-in NVIDIA GeForce GTX 960M, 2GB GDDR5.
https://forums.geforce.com/default/topic/535717/
[quote="mbloof"]This game CAN be played with the latest 314.21 drivers, however one of three things will happen:
1. The game looks perfect (mostly) with the 3D image of Alice and proper placement of shadows on her.
2. Alice is displayed, however the shadows are fubar.
3. When you select the player name the game locks up.
For me the game worked fine after a default instal however after tweaking the in game Video settings (everything turned on) the game simply locked up upon selecting the player name. Finding and editing the 'AliceEngine.ini' file and setting "AllowNvidiaStereo3d=False" fixed the lockup but left the shadows on Alice (and in game) looking fubar. Exiting the game and changing "AllowNvidiaStereo3d=True" and "UseMinimalNVIDIADriverShaderOptimization=True" fixed the lockup AND the shadows.
If you have #1 above feel free to find 'AliceEngine.ini' and change it to 'read-only' in case you accidentally wander into the configuration screen and change a setting (or futz with the Nvidia profile).
[/quote]
mbloof said:This game CAN be played with the latest 314.21 drivers, however one of three things will happen:
1. The game looks perfect (mostly) with the 3D image of Alice and proper placement of shadows on her.
2. Alice is displayed, however the shadows are fubar.
3. When you select the player name the game locks up.
For me the game worked fine after a default instal however after tweaking the in game Video settings (everything turned on) the game simply locked up upon selecting the player name. Finding and editing the 'AliceEngine.ini' file and setting "AllowNvidiaStereo3d=False" fixed the lockup but left the shadows on Alice (and in game) looking fubar. Exiting the game and changing "AllowNvidiaStereo3d=True" and "UseMinimalNVIDIADriverShaderOptimization=True" fixed the lockup AND the shadows.
If you have #1 above feel free to find 'AliceEngine.ini' and change it to 'read-only' in case you accidentally wander into the configuration screen and change a setting (or futz with the Nvidia profile).
You know, it's funny... I remember this problem popping up on the forum months ago, but I have never had any issues with this game even with more recent driver releases. Granted, I haven't tried the game since the last two driver updates, but I have with the ones before that, and like I said, never any issues. Weird. Makes me think there's something unique going on besides a driver issue.
.... Just posted this in the other "Alice" thread as well.
You know, it's funny... I remember this problem popping up on the forum months ago, but I have never had any issues with this game even with more recent driver releases. Granted, I haven't tried the game since the last two driver updates, but I have with the ones before that, and like I said, never any issues. Weird. Makes me think there's something unique going on besides a driver issue.
.... Just posted this in the other "Alice" thread as well.
|CPU: i7-2700k @ 4.5Ghz
|Cooler: Zalman 9900 Max
|MB: MSI Military Class II Z68 GD-80
|RAM: Corsair Vengence 16GB DDR3
|SSDs: Seagate 600 240GB; Crucial M4 128GB
|HDDs: Seagate Barracuda 1TB; Seagate Barracuda 500GB
|PS: OCZ ZX Series 1250watt
|Case: Antec 1200 V3
|Monitors: Asus 3D VG278HE; Asus 3D VG236H; Samsung 3D 51" Plasma;
|GPU:MSI 1080GTX "Duke"
|OS: Windows 10 Pro X64
The AliceEngine.ini file does exist, and the settings you mention are present in it and also in the DefaultEngine.ini file. This is the EA/Origin version of the game.
I have noticed another behaviour: With the Stereoscopic 3D enabled in NVIDIA Control Panel the PhysX indicator shows it is running on the CPU, until I get to choose which player to use, then the game crashes. However with Stereoscopic 3D disabled in NVIDIA Control Panel, the PhysX indicator shows it is running as correctly set up, in the GPU, and the game runs fine (without 3D Vision, of course, independent of the in-game setting of Stereoscopic 3D). Some kind of race condition between 3D Vision and PhysX for the GPU at init time, then messes the CPU and crashes the game process when it's going to start using both 3D Vision and PhysX at the same time (after the player selection screen)???
Miguel
The AliceEngine.ini file does exist, and the settings you mention are present in it and also in the DefaultEngine.ini file. This is the EA/Origin version of the game.
I have noticed another behaviour: With the Stereoscopic 3D enabled in NVIDIA Control Panel the PhysX indicator shows it is running on the CPU, until I get to choose which player to use, then the game crashes. However with Stereoscopic 3D disabled in NVIDIA Control Panel, the PhysX indicator shows it is running as correctly set up, in the GPU, and the game runs fine (without 3D Vision, of course, independent of the in-game setting of Stereoscopic 3D). Some kind of race condition between 3D Vision and PhysX for the GPU at init time, then messes the CPU and crashes the game process when it's going to start using both 3D Vision and PhysX at the same time (after the player selection screen)???
Miguel
ASUS P8Z77-V with Intel Core i5 3570K 3.5~4.2 Ghz, 32 GB DDR3 2400, Windows 10 Pro x64 - Version 1511 Build 10586.545.
ASUS STRIX GTX970 DC2OC 4GD5, 4 GB GDDR5, NVIDIA 3D Vision P854 Glasses.
BenQ XL2420T. WD Caviar Black 2 TB, 7200 rpm.
ASUS ROG GL552VW-DH71 with Intel Core i7 6700HQ 2.6 Ghz, 16 GB DDR4 2133, Windows 10 Pro x64 - Version 10.0 Build 10240.
Built-in NVIDIA GeForce GTX 960M, 2GB GDDR5.
I tried it out, I was able to get it past the title screen by changing the line AllowNvidiaStereo3d=False then set the resolution, etc ... quit the game and then change it back to AllowNvidiaStereo3d=True just like mbloof was saying, UseMinimalNVIDIADriverShaderOptimization was already set to True, and it fixed the shadows ... but I'm still running 320.49 drivers ...
%USERPROFILE%\Documents\My Games\Alice Madness Returns\AliceGame\Config\AliceEngine.ini
I tried it out, I was able to get it past the title screen by changing the line AllowNvidiaStereo3d=False then set the resolution, etc ... quit the game and then change it back to AllowNvidiaStereo3d=True just like mbloof was saying, UseMinimalNVIDIADriverShaderOptimization was already set to True, and it fixed the shadows ... but I'm still running 320.49 drivers ...
[quote="TsaebehT"]I tried it out, I was able to get it past the title screen by changing the line AllowNvidiaStereo3d=False then set the resolution, etc ... quit the game and then change it back to AllowNvidiaStereo3d=True just like mbloof was saying, UseMinimalNVIDIADriverShaderOptimization was already set to True, and it fixed the shadows ... but I'm still running 320.49 drivers ...
%USERPROFILE%\Documents\My Games\Alice Madness Returns\AliceGame\Config\AliceEngine.ini[/quote]
Humm..so you got it to work with the same technique that I had used before? I'll have to try it again and see if it works. Odd, how it survived and worked through a number of driver releases and then suddenly 1yr or more ago it stopped working.
TsaebehT said:I tried it out, I was able to get it past the title screen by changing the line AllowNvidiaStereo3d=False then set the resolution, etc ... quit the game and then change it back to AllowNvidiaStereo3d=True just like mbloof was saying, UseMinimalNVIDIADriverShaderOptimization was already set to True, and it fixed the shadows ... but I'm still running 320.49 drivers ...
Humm..so you got it to work with the same technique that I had used before? I'll have to try it again and see if it works. Odd, how it survived and worked through a number of driver releases and then suddenly 1yr or more ago it stopped working.
I'm not even sure how/why it works, in essence all you're doing is turning it off and then back on again. I did it a few times to make sure, I deleted the whole AMR folder in Documents and every time on first run it creates the ini and locks up on the title screen and changing AllowNvidiaStereo3d to False and back to True again fixed it.
I'm not even sure how/why it works, in essence all you're doing is turning it off and then back on again. I did it a few times to make sure, I deleted the whole AMR folder in Documents and every time on first run it creates the ini and locks up on the title screen and changing AllowNvidiaStereo3d to False and back to True again fixed it.
The crashing is related to the nvidia Awesome Driver.. 331.40 is the latest one that actually works for me (for any game) without any crashes or craps from the driver or driver kernel...
The crashing is related to the nvidia Awesome Driver.. 331.40 is the latest one that actually works for me (for any game) without any crashes or craps from the driver or driver kernel...
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
VERY GOOD WORK!!!
With drivers 332.21 the crashing goes away, and having "Enable Stereoscopic 3D" checked in NVIDIA Control Panel will allow the game to start with 3D enabled. It starts with PhysX on the CPU however, and at the player selection screen 3D Vision gets disabled. Then you can press the button on the IR emmitter and 3D Vision will be enabled again without crashing. When you select your player and hit "Continue Game" on the screen with Alice looking at you and the main menu for the selected player, PhysX gets to run on the GPU , but and at every point where the game loads new levels 3D Vision will be disabled and you have to press the IR emmitter button again to turn it back on.
STILL VERY ANNOYING but MUCH BETTER than the game crashing.
Miguel
With drivers 332.21 the crashing goes away, and having "Enable Stereoscopic 3D" checked in NVIDIA Control Panel will allow the game to start with 3D enabled. It starts with PhysX on the CPU however, and at the player selection screen 3D Vision gets disabled. Then you can press the button on the IR emmitter and 3D Vision will be enabled again without crashing. When you select your player and hit "Continue Game" on the screen with Alice looking at you and the main menu for the selected player, PhysX gets to run on the GPU , but and at every point where the game loads new levels 3D Vision will be disabled and you have to press the IR emmitter button again to turn it back on.
STILL VERY ANNOYING but MUCH BETTER than the game crashing.
Miguel
ASUS P8Z77-V with Intel Core i5 3570K 3.5~4.2 Ghz, 32 GB DDR3 2400, Windows 10 Pro x64 - Version 1511 Build 10586.545.
ASUS STRIX GTX970 DC2OC 4GD5, 4 GB GDDR5, NVIDIA 3D Vision P854 Glasses.
BenQ XL2420T. WD Caviar Black 2 TB, 7200 rpm.
ASUS ROG GL552VW-DH71 with Intel Core i7 6700HQ 2.6 Ghz, 16 GB DDR4 2133, Windows 10 Pro x64 - Version 10.0 Build 10240.
Built-in NVIDIA GeForce GTX 960M, 2GB GDDR5.
I tried rolling back my drivers to 332.21 & 331.40. But the game still crashes at the menu. I tried deleting "alicegame" folder in My Documents, but still no help. I can get past the menu if I set "AllowNvidiaStereo3d=False", but the lighting & shadows are messed up (as others have mentioned).
I tried rolling back my drivers to 332.21 & 331.40. But the game still crashes at the menu. I tried deleting "alicegame" folder in My Documents, but still no help. I can get past the menu if I set "AllowNvidiaStereo3d=False", but the lighting & shadows are messed up (as others have mentioned).
Did you follow mbloof's post above to the letter? ... set to false ... run the game, set settings, quit ... set back to true and then it should run perfectly ...
Last time I ran it after I fixed it that way (on the 1st '2D Vision' beta drivers iirc) it ran perfectly fine.
edit:double-checked before I left for work and it was still running fine on the beta drivers mentioned above.
Did you follow mbloof's post above to the letter? ... set to false ... run the game, set settings, quit ... set back to true and then it should run perfectly ...
Last time I ran it after I fixed it that way (on the 1st '2D Vision' beta drivers iirc) it ran perfectly fine.
edit:double-checked before I left for work and it was still running fine on the beta drivers mentioned above.
Nice thread. I've tried playing this games a couple different times in the past, and it's always crashed on me. And after a couple minutes of frustration, had my attention drawn elsewhere and just forgot about the game again.
Nice thread. I've tried playing this games a couple different times in the past, and it's always crashed on me. And after a couple minutes of frustration, had my attention drawn elsewhere and just forgot about the game again.
I have "different kind" of crashes with this game with my GTX 780, whether running 3d or not. At random intervals (every few mins to half hour) the game crashes for around 1 min then resumes... I tried looking up my issue but nothing worked. I finally gave up on this game. I game a lot and this is the only game that crashes on my current pc, I think it's optimized for older hardware/drivers.
I have "different kind" of crashes with this game with my GTX 780, whether running 3d or not. At random intervals (every few mins to half hour) the game crashes for around 1 min then resumes... I tried looking up my issue but nothing worked. I finally gave up on this game. I game a lot and this is the only game that crashes on my current pc, I think it's optimized for older hardware/drivers.
Ok I think I got it. It seems that if I disable motion blur, it causes the game to crash at the menu screen. If I try to disable motion blur during the game, the game will crash later on. So I just left it enabled. I'm only 20 minutes into the game, but it's stable so far. I'm on the latest driver (334.89).
Ok I think I got it. It seems that if I disable motion blur, it causes the game to crash at the menu screen. If I try to disable motion blur during the game, the game will crash later on. So I just left it enabled. I'm only 20 minutes into the game, but it's stable so far. I'm on the latest driver (334.89).
I have a GTX780, I tried to play this game using driver 331.40 and 334.89. The game crashes at the menu. (motion blur is enabled!) If I set "AllowNvidiaStereo3d=False" I can play, but dynamic shadows are messed up.
I have read another thread about this topic, probably the game needs driver version 306.97 to activate correctly 3d vision. I have not test yet but I will! I will try to rollback to driver version 306.97 ...
I have a GTX780, I tried to play this game using driver 331.40 and 334.89. The game crashes at the menu. (motion blur is enabled!) If I set "AllowNvidiaStereo3d=False" I can play, but dynamic shadows are messed up.
I have read another thread about this topic, probably the game needs driver version 306.97 to activate correctly 3d vision. I have not test yet but I will! I will try to rollback to driver version 306.97 ...
Besides, this is another title that claims to use PhysX but the visual indicator reads CPU instead of GPU, even though PhysX is configured as Auto in the NVIDIA Control Panel...
Miguel
ASUS P8Z77-V with Intel Core i5 3570K 3.5~4.2 Ghz, 32 GB DDR3 2400, Windows 10 Pro x64 - Version 1511 Build 10586.545.
ASUS STRIX GTX970 DC2OC 4GD5, 4 GB GDDR5, NVIDIA 3D Vision P854 Glasses.
BenQ XL2420T. WD Caviar Black 2 TB, 7200 rpm.
ASUS ROG GL552VW-DH71 with Intel Core i7 6700HQ 2.6 Ghz, 16 GB DDR4 2133, Windows 10 Pro x64 - Version 10.0 Build 10240.
Built-in NVIDIA GeForce GTX 960M, 2GB GDDR5.
[MonitorSizeOverride][Global/Base Profile Tweaks][Depth=IPD]
.... Just posted this in the other "Alice" thread as well.
|CPU: i7-2700k @ 4.5Ghz
|Cooler: Zalman 9900 Max
|MB: MSI Military Class II Z68 GD-80
|RAM: Corsair Vengence 16GB DDR3
|SSDs: Seagate 600 240GB; Crucial M4 128GB
|HDDs: Seagate Barracuda 1TB; Seagate Barracuda 500GB
|PS: OCZ ZX Series 1250watt
|Case: Antec 1200 V3
|Monitors: Asus 3D VG278HE; Asus 3D VG236H; Samsung 3D 51" Plasma;
|GPU:MSI 1080GTX "Duke"
|OS: Windows 10 Pro X64
I have noticed another behaviour: With the Stereoscopic 3D enabled in NVIDIA Control Panel the PhysX indicator shows it is running on the CPU, until I get to choose which player to use, then the game crashes. However with Stereoscopic 3D disabled in NVIDIA Control Panel, the PhysX indicator shows it is running as correctly set up, in the GPU, and the game runs fine (without 3D Vision, of course, independent of the in-game setting of Stereoscopic 3D). Some kind of race condition between 3D Vision and PhysX for the GPU at init time, then messes the CPU and crashes the game process when it's going to start using both 3D Vision and PhysX at the same time (after the player selection screen)???
Miguel
ASUS P8Z77-V with Intel Core i5 3570K 3.5~4.2 Ghz, 32 GB DDR3 2400, Windows 10 Pro x64 - Version 1511 Build 10586.545.
ASUS STRIX GTX970 DC2OC 4GD5, 4 GB GDDR5, NVIDIA 3D Vision P854 Glasses.
BenQ XL2420T. WD Caviar Black 2 TB, 7200 rpm.
ASUS ROG GL552VW-DH71 with Intel Core i7 6700HQ 2.6 Ghz, 16 GB DDR4 2133, Windows 10 Pro x64 - Version 10.0 Build 10240.
Built-in NVIDIA GeForce GTX 960M, 2GB GDDR5.
%USERPROFILE%\Documents\My Games\Alice Madness Returns\AliceGame\Config\AliceEngine.ini
[MonitorSizeOverride][Global/Base Profile Tweaks][Depth=IPD]
Humm..so you got it to work with the same technique that I had used before? I'll have to try it again and see if it works. Odd, how it survived and worked through a number of driver releases and then suddenly 1yr or more ago it stopped working.
i7-2600K-4.5Ghz/Corsair H100i/8GB/GTX780SC-SLI/Win7-64/1200W-PSU/Samsung 840-500GB SSD/Coolermaster-Tower/Benq 1080ST @ 100"
[MonitorSizeOverride][Global/Base Profile Tweaks][Depth=IPD]
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)
With drivers 332.21 the crashing goes away, and having "Enable Stereoscopic 3D" checked in NVIDIA Control Panel will allow the game to start with 3D enabled. It starts with PhysX on the CPU however, and at the player selection screen 3D Vision gets disabled. Then you can press the button on the IR emmitter and 3D Vision will be enabled again without crashing. When you select your player and hit "Continue Game" on the screen with Alice looking at you and the main menu for the selected player, PhysX gets to run on the GPU , but and at every point where the game loads new levels 3D Vision will be disabled and you have to press the IR emmitter button again to turn it back on.
STILL VERY ANNOYING but MUCH BETTER than the game crashing.
Miguel
ASUS P8Z77-V with Intel Core i5 3570K 3.5~4.2 Ghz, 32 GB DDR3 2400, Windows 10 Pro x64 - Version 1511 Build 10586.545.
ASUS STRIX GTX970 DC2OC 4GD5, 4 GB GDDR5, NVIDIA 3D Vision P854 Glasses.
BenQ XL2420T. WD Caviar Black 2 TB, 7200 rpm.
ASUS ROG GL552VW-DH71 with Intel Core i7 6700HQ 2.6 Ghz, 16 GB DDR4 2133, Windows 10 Pro x64 - Version 10.0 Build 10240.
Built-in NVIDIA GeForce GTX 960M, 2GB GDDR5.
Dual boot Win 7 x64 & Win 10 (1809) | Geforce Drivers 417.35
Last time I ran it after I fixed it that way (on the 1st '2D Vision' beta drivers iirc) it ran perfectly fine.
edit:double-checked before I left for work and it was still running fine on the beta drivers mentioned above.
[MonitorSizeOverride][Global/Base Profile Tweaks][Depth=IPD]
Dual boot Win 7 x64 & Win 10 (1809) | Geforce Drivers 417.35
I have read another thread about this topic, probably the game needs driver version 306.97 to activate correctly 3d vision. I have not test yet but I will! I will try to rollback to driver version 306.97 ...