This has to be the NVIDIA physX driver DLL outdated. Copy the dll in the folder locate in C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common\

Be sure grab the cudart32.dll not the 64 one because you need think Alice: Madness Returns comes out in 2011 which 64-bit still haven’t came out.

PS: (The dll that showed to me have a version number over the cudart32. It might showed like this “cudart32_65.dll” but it is just fine.)

After you copied it. Head through back to the Alice game directory and paste it in “<path-to-game>\Binaries\Win32.”
I MEAN PASTE NOT REPLACE OR RENAME ANY FILES IN IT.

Worked for me on Origin and I own the Complete Collection one. uwu

And~~~ you done now you run ur game on physX in high setting all over. Have fun :D

For the frame rate issue. I’m just keep default in 31 FPS Because I’m worried that high fps may get even more bugs in the game. The same logic in Grand Theft Auto 4 which it caps you in 30 fps to prevent bugs.

(Reply me if you find out high FPS doesn’t affect the game experience) :))

𝑀𝑒𝓁𝑜𝒹𝓎님이 먼저 게시:

This has to be the NVIDIA physX driver dll outdated. Copy the dll in the folder locate in C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common\

Be sure grab the cudart32.dll not the 64 one because you need think Alice: Madness Returns comes out in 2011 which 64-bit still haven’t came out.

PS: (The dll that showed to me have a version number over the cudart32. It might showed like this “cudart32_65.dll” but it is just fine.)

After you copied it. Head through back to the Alice game directory and paste it in “<path-to-game>\Binaries\Win32.”
I MEAN PASTE NOT REPLACE OR RENAME ANY FILES IN IT.

Worked for me on Origin and I own the Complete Collection one. uwu

And~~~ you done now you run ur game on physX in high setting all over. Have fun :D

In my experience setting Physx to high absolutely crashes the game over time.

Honestly it's incredible what a garbage port this is, seriously I've rewritten like half the ♥♥♥♥♥♥♥ AliceEngine.ini file and yet I still can't figure out how to stop the ♥♥♥♥♥♥♥ 1-2 second long random freezes that can occur (especially during the Vale of Doom section of Chapter 3).

In my experience setting Physx to high absolutely crashes the game over time.

Honestly it's incredible what a garbage port this is, seriously I've rewritten like half the ♥♥♥♥♥♥♥ AliceEngine.ini file and yet I still can't figure out how to stop the ♥♥♥♥♥♥♥ 1-2 second long random freezes that can occur (especially during the Vale of Doom section of Chapter 3).

u mean lag spike? this can't be fixed in the .ini file. Same as me when I'm playing Grand Theft Auto Online. Get a good graphic card might helped. ヾ(•ω•`)o

𝑀𝑒𝓁𝑜𝒹𝓎님이 먼저 게시:

In my experience setting Physx to high absolutely crashes the game over time.

Honestly it's incredible what a garbage port this is, seriously I've rewritten like half the ♥♥♥♥♥♥♥ AliceEngine.ini file and yet I still can't figure out how to stop the ♥♥♥♥♥♥♥ 1-2 second long random freezes that can occur (especially during the Vale of Doom section of Chapter 3).

u mean lag spike? this can't be fixed in the .ini file. Same as me when I'm playing Grand Theft Auto Online. Get a good graphic card might helped. ヾ(•ω•`)o

Haha, I'm on an RTX 2070 and an i5-9600k, game's on an SSD. The PC port's simply not salvageable with all these engine bugs, I'm actually not surprised that even famously money hungry EA doesn't sell this on Steam anymore.

Haha, I'm on an RTX 2070 and an i5-9600k, game's on an SSD. The PC port's simply not salvageable with all these engine bugs, I'm actually not surprised that even famously money hungry EA doesn't sell this on Steam anymore.

okie

Btw. nope, these are not "lag spikes", lag is usually caused by packet loss or ping spikes / ping fluctuation in online games, Alice Madness Returns is a fully offline single player experience so the term "lag" doesn't apply anywhere here. I said "random freezes" because that's what it's actually is: it's not the usual UE3 asset streaming stutter, it's not a frametime issue, the game simply STOPS for a second and then continues (or occasionally it even crashes).

It's the kind of garbage Arkham Knight got mass refunded for.

True

Zaxx님이 먼저 게시:

Btw. nope, these are not "lag spikes", lag is usually caused by packet loss or ping spikes / ping fluctuation in online games, Alice Madness Returns is a fully offline single player experience so the term "lag" doesn't apply anywhere here. I said "random freezes" because that's what it's actually is: it's not the usual UE3 asset streaming stutter, it's not a frametime issue, the game simply STOPS for a second and then continues (or occasionally it even crashes).

It's the kind of garbage Arkham Knight got mass refunded for.

Anyway a heads up to this since as far as I know everyone has this issue: you can fix it. It's caused by EA's ♥♥♥♥♥♥ DRM and doing two things (yes, both of them) fully solves the issue:

- You have to rename (or delete) that "EACoreServer.exe" to something else in the Binaries/Win32/Core folder. This shortens the amount of time the game will hang for so I guess it disables like half the DRM checks.

- You have to crack the game, yep, you heard it right, pirates come to the rescue.

Honestly there's so much bad information on this game out there that I might end up writing a guide on it because overall I pretty much managed to fix up the port too.

Anyway a heads up to this since as far as I know everyone has this issue: you can fix it. It's caused by EA's ♥♥♥♥♥♥ DRM and doing two things (yes, both of them) fully solves the issue:

- You have to rename (or delete) that "EACoreServer.exe" to something else in the Binaries/Win32/Core folder. This shortens the amount of time the game will hang for so I guess it disables like half the DRM checks.

- You have to crack the game, yep, you heard it right, pirates come to the rescue.

Honestly there's so much bad information on this game out there that I might end up writing a guide on it because overall I pretty much managed to fix up the port too.

ok but reinstall the physX driver seem to fix the issue for me

𝑀𝑒𝓁𝑜𝒹𝓎님이 먼저 게시:

ok but reinstall the physX driver seem to fix the issue for me

PhysX has nothing to do with the issue I posted about. I did suspect PhysX at first because you actually can't turn it off (setting PhysX to low just defaults to a very low PhysX setting that forces the simulation to run on the CPU) but nope, PhysX is actually finely implemented, everything else is ♥♥♥♥.

Also: you don't have to "re-install" PhysX if it's installed fine on your machine, the only thing that helps (or rather might help since honestly it's all anecdotal at this point) is renaming or deleting the PhysXCore.dll file in the Binaries/Win32 folder would. This causes the game to just start using the PhysX driver that is installed on your machine instead of what is provided to the game's directory. Won't really affect anything though in terms of PhysX performance, might help with edge cases of incompatibility.

The same goes for the dll fix you've posted: it can happen that somehow cudart32.dll isn't present in the game's directory after an install so it helps the edge cases but otherwise it affects nil sadly.

What can affect PhysX performance are some settings in the AliceEngine.ini. PhysXGPUHeapSize for example allocates more VRAM to the PhysX core which does help performance in some "there's a lot of stuff on the screen" scenarios so increasing that to something like 128 megabytes from the default is a good idea with more recent GPUs (if you increase it too much the performance will drop though). There's another setting called PhysXMeshCacheSize which improves the mesh quality of PhysX objects if increased but that also means a potential performance hit so it's better to just leave that at the default value of 8 megs.

But reinstall it already helped me. No crash at the beginning after the intro.

oh and one more thingy is. The game keep minimizes itself after a certain number of minutes. Any solution?

𝑀𝑒𝓁𝑜𝒹𝓎님이 먼저 게시:

oh and one more thingy is. The game keep minimizes itself after a certain number of minutes. Any solution?

Minimizes itself? Like Alt-Tabbing would? Have no idea, that thankfully never happened to me.

:(