Dead Rising (1)
Capcom has released a reportedly solid port of the original Dead Rising on PC. Just curious if anyone has had an opportunity to try it out in 3D Vision?
Capcom has released a reportedly solid port of the original Dead Rising on PC. Just curious if anyone has had an opportunity to try it out in 3D Vision?

#1
Posted 09/23/2016 01:12 AM   
Works perfect on my 1080p passive display. Unfortunately, this is one of those titles where visual quality takes a huge hit due to interlacing, so I've been playing in 2D. Dead Rising 1 is a fantastic game and the only good Dead Rising game.
Works perfect on my 1080p passive display. Unfortunately, this is one of those titles where visual quality takes a huge hit due to interlacing, so I've been playing in 2D.

Dead Rising 1 is a fantastic game and the only good Dead Rising game.

4K 55" LG 55EF9500 3D OLED TV for sale! Pickup ONLY in Philadelphia, PA. PM for details.

#2
Posted 09/23/2016 03:28 AM   
Picked up a 55" LG Passive OLED 4K, the game looks much better now. The only issue I've noticed is that lights aren't aligned with their sources.
Picked up a 55" LG Passive OLED 4K, the game looks much better now. The only issue I've noticed is that lights aren't aligned with their sources.

4K 55" LG 55EF9500 3D OLED TV for sale! Pickup ONLY in Philadelphia, PA. PM for details.

#3
Posted 10/04/2016 03:11 AM   
Is someone playing this on Windows 7 and not getting crashes? I get random crashes sometimes and it may be related to the mandatory "evil update" that the game needs. That't why I haven't released the fix sooner (which may be done if there aren't new effects after the start of Case 2). It's really frustrating.
Is someone playing this on Windows 7 and not getting crashes? I get random crashes sometimes and it may be related to the mandatory "evil update" that the game needs. That't why I haven't released the fix sooner (which may be done if there aren't new effects after the start of Case 2). It's really frustrating.

CPU: Intel Core i7 7700K @ 4.9GHz
Motherboard: Gigabyte Aorus GA-Z270X-Gaming 5
RAM: GSKILL Ripjaws Z 16GB 3866MHz CL18
GPU: Gainward Phoenix 1080 GLH
Monitor: Asus PG278QR
Speakers: Logitech Z506
Donations account: masterotakusuko@gmail.com

#4
Posted 12/19/2016 11:11 PM   
[quote="masterotaku"]Is someone playing this on Windows 7 and not getting crashes? I get random crashes sometimes and it may be related to the mandatory "evil update" that the game needs. That't why I haven't released the fix sooner (which may be done if there aren't new effects after the start of Case 2). It's really frustrating.[/quote] Hmmm.. I'm quite certain that I don't have the Evil update installed. I didn't experience any crashes, but I must admit that I'm still early in the game, sooo many great games and sooo litle time.....sigh..
masterotaku said:Is someone playing this on Windows 7 and not getting crashes? I get random crashes sometimes and it may be related to the mandatory "evil update" that the game needs. That't why I haven't released the fix sooner (which may be done if there aren't new effects after the start of Case 2). It's really frustrating.


Hmmm.. I'm quite certain that I don't have the Evil update installed.

I didn't experience any crashes, but I must admit that I'm still early in the game, sooo many great games and sooo litle time.....sigh..

Win7 64bit Pro
CPU: 4790K 4.8 GHZ
GPU: Aurus 1080 TI 2.08 GHZ - 100% Watercooled !
Monitor: Asus PG278QR
And lots of ram and HD's ;)

#5
Posted 12/20/2016 04:22 PM   
The fix is on the blog. I had lost all my work on the game a month ago, but I could repeat all of it in one or two hours (and with the crosshair depth extra on top of that). Sorry for taking so long. I'm near the start of the game, so I don't know how many random crashes can happen on Windows 10. If you find any 3D issues, please report them here.
The fix is on the blog. I had lost all my work on the game a month ago, but I could repeat all of it in one or two hours (and with the crosshair depth extra on top of that). Sorry for taking so long.

I'm near the start of the game, so I don't know how many random crashes can happen on Windows 10. If you find any 3D issues, please report them here.

CPU: Intel Core i7 7700K @ 4.9GHz
Motherboard: Gigabyte Aorus GA-Z270X-Gaming 5
RAM: GSKILL Ripjaws Z 16GB 3866MHz CL18
GPU: Gainward Phoenix 1080 GLH
Monitor: Asus PG278QR
Speakers: Logitech Z506
Donations account: masterotakusuko@gmail.com

#6
Posted 04/23/2017 01:04 PM   
[quote="masterotaku"]The fix is on the blog. I had lost all my work on the game a month ago, but I could repeat all of it in one or two hours (and with the crosshair depth extra on top of that). Sorry for taking so long. I'm near the start of the game, so I don't know how many random crashes can happen on Windows 10. If you find any 3D issues, please report them here.[/quote] thank you for you fix.
masterotaku said:The fix is on the blog. I had lost all my work on the game a month ago, but I could repeat all of it in one or two hours (and with the crosshair depth extra on top of that). Sorry for taking so long.

I'm near the start of the game, so I don't know how many random crashes can happen on Windows 10. If you find any 3D issues, please report them here.


thank you for you fix.

#7
Posted 04/25/2017 04:43 AM   
hello ! thank you for the fix masterotaku ! i just bought the game , it's only 8 $ thanks to Steam's capcom promotions this week end. the game works fine with 3DVision but if i install your fix, the game crashes at boot Nom de l’application défaillante DeadRising.exe, version : 1.0.0.1, horodatage : 0x57f6c176 Nom du module défaillant : d3d11.dll, version : 1.2.63.0, horodatage : 0x596429c5 Code d’exception : 0xc0000005 Décalage d’erreur : 0x000000000008d3e2 ID du processus défaillant : 0x374c Heure de début de l’application défaillante : 0x01d3189b7a55cee8 Chemin d’accès de l’application défaillante : X:\#STEAM\steamapps\common\Dead Rising\DeadRising.exe Chemin d’accès du module défaillant: X:\#STEAM\steamapps\common\Dead Rising\d3d11.dll
hello ! thank you for the fix masterotaku !

i just bought the game , it's only 8 $ thanks to Steam's capcom promotions this week end.

the game works fine with 3DVision but if i install your fix, the game crashes at boot

Nom de l’application défaillante DeadRising.exe, version : 1.0.0.1, horodatage : 0x57f6c176
Nom du module défaillant : d3d11.dll, version : 1.2.63.0, horodatage : 0x596429c5
Code d’exception : 0xc0000005
Décalage d’erreur : 0x000000000008d3e2
ID du processus défaillant : 0x374c
Heure de début de l’application défaillante : 0x01d3189b7a55cee8
Chemin d’accès de l’application défaillante : X:\#STEAM\steamapps\common\Dead Rising\DeadRising.exe
Chemin d’accès du module défaillant: X:\#STEAM\steamapps\common\Dead Rising\d3d11.dll

Corei7 4790K 32GB / 2xSLI: Titan X Pascal 3DSurr 7680x1440 +FSIM cockpit :D

My Hardcore gamer rig : http://forum.hardware.fr/configuration.php?config=hardwarefr.inc&pseudo=greatxerox
YOUTUBE Video updated : https://www.youtube.com/channel/UC7CDItQG3ycOxD7alNomG3A?view_as=subscriber
Pictures : http://www.casimages.com/u/greatxerox/369138
Best site Emulation on the net : http://www.emu-france.com/

#8
Posted 08/19/2017 03:40 AM   
Strange. Try changing these settings and their surroundings: [code] allow_create_device=2 allow_platform_update=1 [/code]
Strange.

Try changing these settings and their surroundings:

allow_create_device=2
allow_platform_update=1

CPU: Intel Core i7 7700K @ 4.9GHz
Motherboard: Gigabyte Aorus GA-Z270X-Gaming 5
RAM: GSKILL Ripjaws Z 16GB 3866MHz CL18
GPU: Gainward Phoenix 1080 GLH
Monitor: Asus PG278QR
Speakers: Logitech Z506
Donations account: masterotakusuko@gmail.com

#9
Posted 08/19/2017 04:54 PM   
Does the game crash at boot with the fix for all Windows 10 users? I'm using the Creators Update of Windows 10 (1703 version) and the game crashes no matter what configuration or 3Dmigoto version I use. The game worked months ago, and I don't know if the problem is because of drivers or Windows updates. I want to know more tests before opening a github issue. The unbuffered "d3d11_log.txt" doesn't end with any error, and analyzing the crash with SpecialK shows this: [code] 01/05/2018 23:31:14.880: ----------------------------------------------------------- 01/05/2018 23:31:14.881: [! Except !] 01/05/2018 23:31:14.881: ----------------------------------------------------------- 01/05/2018 23:31:14.881: [ FaultMod ] # File.....: 'C:\WINDOWS\System32\KERNELBASE.dll' 01/05/2018 23:31:14.881: [ FaultMod ] * RIP Addr.: KERNELBASE.dll+0000000000069D98h 01/05/2018 23:31:14.881: [StackFrame] <-> Rip=7ffaa4a39d98h, Rsp=006dccefdb10h, Rbp=006dccefdc50h 01/05/2018 23:31:14.881: [StackFrame] >-< Rsi=01a8914f04dbh, Rdi=006dccefdd08h 01/05/2018 23:31:14.881: [ GP Reg ] rax: 0x00000000000f 01/05/2018 23:31:14.881: [ GP Reg ] rbx: 0x7ffa75361bb0 01/05/2018 23:31:14.881: [ GP Reg ] rcx: 0x000003000003 01/05/2018 23:31:14.881: [ GP Reg ] rdx: 0x01a8242f030c 01/05/2018 23:31:14.881: [ GP Reg ] r8: 0x7ffa7529c221 r9: 0x000003000003 01/05/2018 23:31:14.881: [ GP Reg ] r10: 0x000002000002 r11: 0x01a89113e030 01/05/2018 23:31:14.881: [ GP Reg ] r12: 0x01a8914f04c0 r13: 0x7ffa7530bec0 01/05/2018 23:31:14.881: [ GP Reg ] r14: 0x006dccefde10 r15: 0x006dccefde50 01/05/2018 23:31:14.881: [ GP Flags ] EFlags: 0x00000206 01/05/2018 23:31:14.881: ----------------------------------------------------------- 01/05/2018 23:31:14.882: [--(Name)--] [!] { KERNELBASE.dll} RaiseException 01/05/2018 23:31:14.883: [--(Name)--] [!] { KERNELBASE.dll} RaiseException 01/05/2018 23:31:14.888: [--(Name)--] [!] { d3d11.dll} D3DKMTWaitForVerticalBlankEvent 01/05/2018 23:31:14.889: ----------------------------------------------------------- 01/05/2018 23:31:14.890: ----------------------------------------------------------- 01/05/2018 23:31:14.890: [! Except !] << EXCEPTION_NONCONTINUABLE_EXCEPTION >> 01/05/2018 23:31:14.890: ----------------------------------------------------------- 01/05/2018 23:31:14.890: [ FaultMod ] # File.....: 'C:\WINDOWS\SYSTEM32\ntdll.dll' 01/05/2018 23:31:14.890: [ FaultMod ] * RIP Addr.: ntdll.dll+0000000000004B90h 01/05/2018 23:31:14.890: [StackFrame] <-> Rip=7ffaa7d44b90h, Rsp=006dccefc600h, Rbp=006dccefc700h 01/05/2018 23:31:14.890: [StackFrame] >-< Rsi=000000000001h, Rdi=000000000000h 01/05/2018 23:31:14.890: [ GP Reg ] rax: 0x000000000000 01/05/2018 23:31:14.890: [ GP Reg ] rbx: 0x0000c0000025 01/05/2018 23:31:14.890: [ GP Reg ] rcx: 0x01a82ddc68f8 01/05/2018 23:31:14.890: [ GP Reg ] rdx: 0x01a82ddc6840 01/05/2018 23:31:14.890: [ GP Reg ] r8: 0x000000000001 r9: 0x000000000351 01/05/2018 23:31:14.890: [ GP Reg ] r10: 0x7ffa7529c8df r11: 0x000000000006 01/05/2018 23:31:14.890: [ GP Reg ] r12: 0x7ffaa7d40000 r13: 0x7ffaa7db0d51 01/05/2018 23:31:14.890: [ GP Reg ] r14: 0x000000000000 r15: 0x006dccefdb30 01/05/2018 23:31:14.890: [ GP Flags ] EFlags: 0x00000206 01/05/2018 23:31:14.890: ----------------------------------------------------------- 01/05/2018 23:31:14.891: [--(Name)--] [!] { ntdll.dll} RtlRaiseStatus 01/05/2018 23:31:14.892: [--(Name)--] [!] { ntdll.dll} RtlRaiseStatus 01/05/2018 23:31:14.915: ----------------------------------------------------------- [/code]
Does the game crash at boot with the fix for all Windows 10 users? I'm using the Creators Update of Windows 10 (1703 version) and the game crashes no matter what configuration or 3Dmigoto version I use. The game worked months ago, and I don't know if the problem is because of drivers or Windows updates.

I want to know more tests before opening a github issue. The unbuffered "d3d11_log.txt" doesn't end with any error, and analyzing the crash with SpecialK shows this:

01/05/2018 23:31:14.880: -----------------------------------------------------------
01/05/2018 23:31:14.881: [! Except !]
01/05/2018 23:31:14.881: -----------------------------------------------------------
01/05/2018 23:31:14.881: [ FaultMod ] # File.....: 'C:\WINDOWS\System32\KERNELBASE.dll'
01/05/2018 23:31:14.881: [ FaultMod ] * RIP Addr.: KERNELBASE.dll+0000000000069D98h
01/05/2018 23:31:14.881: [StackFrame] <-> Rip=7ffaa4a39d98h, Rsp=006dccefdb10h, Rbp=006dccefdc50h
01/05/2018 23:31:14.881: [StackFrame] >-< Rsi=01a8914f04dbh, Rdi=006dccefdd08h
01/05/2018 23:31:14.881: [ GP Reg ] rax: 0x00000000000f
01/05/2018 23:31:14.881: [ GP Reg ] rbx: 0x7ffa75361bb0
01/05/2018 23:31:14.881: [ GP Reg ] rcx: 0x000003000003
01/05/2018 23:31:14.881: [ GP Reg ] rdx: 0x01a8242f030c
01/05/2018 23:31:14.881: [ GP Reg ] r8: 0x7ffa7529c221 r9: 0x000003000003
01/05/2018 23:31:14.881: [ GP Reg ] r10: 0x000002000002 r11: 0x01a89113e030
01/05/2018 23:31:14.881: [ GP Reg ] r12: 0x01a8914f04c0 r13: 0x7ffa7530bec0
01/05/2018 23:31:14.881: [ GP Reg ] r14: 0x006dccefde10 r15: 0x006dccefde50
01/05/2018 23:31:14.881: [ GP Flags ] EFlags: 0x00000206
01/05/2018 23:31:14.881: -----------------------------------------------------------
01/05/2018 23:31:14.882: [--(Name)--] [!] { KERNELBASE.dll} RaiseException
01/05/2018 23:31:14.883: [--(Name)--] [!] { KERNELBASE.dll} RaiseException
01/05/2018 23:31:14.888: [--(Name)--] [!] { d3d11.dll} D3DKMTWaitForVerticalBlankEvent
01/05/2018 23:31:14.889: -----------------------------------------------------------
01/05/2018 23:31:14.890: -----------------------------------------------------------
01/05/2018 23:31:14.890: [! Except !] << EXCEPTION_NONCONTINUABLE_EXCEPTION >>
01/05/2018 23:31:14.890: -----------------------------------------------------------
01/05/2018 23:31:14.890: [ FaultMod ] # File.....: 'C:\WINDOWS\SYSTEM32\ntdll.dll'
01/05/2018 23:31:14.890: [ FaultMod ] * RIP Addr.: ntdll.dll+0000000000004B90h
01/05/2018 23:31:14.890: [StackFrame] <-> Rip=7ffaa7d44b90h, Rsp=006dccefc600h, Rbp=006dccefc700h
01/05/2018 23:31:14.890: [StackFrame] >-< Rsi=000000000001h, Rdi=000000000000h
01/05/2018 23:31:14.890: [ GP Reg ] rax: 0x000000000000
01/05/2018 23:31:14.890: [ GP Reg ] rbx: 0x0000c0000025
01/05/2018 23:31:14.890: [ GP Reg ] rcx: 0x01a82ddc68f8
01/05/2018 23:31:14.890: [ GP Reg ] rdx: 0x01a82ddc6840
01/05/2018 23:31:14.890: [ GP Reg ] r8: 0x000000000001 r9: 0x000000000351
01/05/2018 23:31:14.890: [ GP Reg ] r10: 0x7ffa7529c8df r11: 0x000000000006
01/05/2018 23:31:14.890: [ GP Reg ] r12: 0x7ffaa7d40000 r13: 0x7ffaa7db0d51
01/05/2018 23:31:14.890: [ GP Reg ] r14: 0x000000000000 r15: 0x006dccefdb30
01/05/2018 23:31:14.890: [ GP Flags ] EFlags: 0x00000206
01/05/2018 23:31:14.890: -----------------------------------------------------------
01/05/2018 23:31:14.891: [--(Name)--] [!] { ntdll.dll} RtlRaiseStatus
01/05/2018 23:31:14.892: [--(Name)--] [!] { ntdll.dll} RtlRaiseStatus
01/05/2018 23:31:14.915: -----------------------------------------------------------

CPU: Intel Core i7 7700K @ 4.9GHz
Motherboard: Gigabyte Aorus GA-Z270X-Gaming 5
RAM: GSKILL Ripjaws Z 16GB 3866MHz CL18
GPU: Gainward Phoenix 1080 GLH
Monitor: Asus PG278QR
Speakers: Logitech Z506
Donations account: masterotakusuko@gmail.com

#10
Posted 01/06/2018 09:26 AM   
Kinda false alarm. The alt+tab trick I say in the blog post (which I had forgotten) works with the fix in the blog post. But it doesn't with 3Dmigoto 1.2.68.
Kinda false alarm. The alt+tab trick I say in the blog post (which I had forgotten) works with the fix in the blog post. But it doesn't with 3Dmigoto 1.2.68.

CPU: Intel Core i7 7700K @ 4.9GHz
Motherboard: Gigabyte Aorus GA-Z270X-Gaming 5
RAM: GSKILL Ripjaws Z 16GB 3866MHz CL18
GPU: Gainward Phoenix 1080 GLH
Monitor: Asus PG278QR
Speakers: Logitech Z506
Donations account: masterotakusuko@gmail.com

#11
Posted 01/06/2018 10:05 AM   
Fix updated. See the "known issues" and other stuff in the blog post.
Fix updated. See the "known issues" and other stuff in the blog post.

CPU: Intel Core i7 7700K @ 4.9GHz
Motherboard: Gigabyte Aorus GA-Z270X-Gaming 5
RAM: GSKILL Ripjaws Z 16GB 3866MHz CL18
GPU: Gainward Phoenix 1080 GLH
Monitor: Asus PG278QR
Speakers: Logitech Z506
Donations account: masterotakusuko@gmail.com

#12
Posted 01/06/2018 02:39 PM   
Scroll To Top