modengine2 crashes on initialization if process affinity is managed by another tool

[BlueDawn226]

So i extracted the modengine2 folder inside the "game" folder of AC6, I try open the game (with steam already open) with "launchmod_armoredcore6.bat" and then the game opens with a white screen and the game cursor, then about 2 seconds after, it changes to pitch black without cursor and 2 second after i get kick to the desktop. No error message or prompt, and same result trying with or without mods. Any fix or solution?

I have a steam copy of AC6 in my D: drive, also im on a pc with a intel 12700k cpu and amd 6650 xt gpu (i dont know if it is relevant) i link the last log generated by modengine if it helps modengine_2023-12-14.log

[MaximilianThermidor]

Interesting, yours got further than mine it just instantly closes for me. No idea how to fix it.

[BlueDawn226]

Ok so after a lot of troubleshooting i find the issue. Turns out mod engine doesnt like working with project lasso active or similar programs. I just deactivate it and everything works now I feel a little stupid right now XD

[MaximilianThermidor]

Interesting. I still haven't been able to get it to work. I don't have project lasso.

[BlueDawn226]

Make sure cpu affinity is not changed in ac6 process by any program, let the .exe access all the cores. My ac6.exe had access to all cores except cpu 0 and that made it to crash Thats all i discovered

[DAOWAce]

Turns out mod engine doesnt like working with project lasso

Are you shitting me..

Why on earth is it interacting with a process management utility like this? I've never seen this happen until now, and was ripping my hair out trying to figure out why MO2 just kept closing either ER or AR6 (0xc0000005 in event log). Process Lasso is a staple on my system, been using it for over a decade and it's become practically a requirement for modern CPUs to perform optimally in games (forcing non-SMT or single CCD or non-E cores).

Whoever's maintaining this, please provide some input as to what's happening. We can run the utility after game startup, but not during initialization. Makes no sense.

[BlueDawn226]

Turns out mod engine doesnt like working with project lasso

Are you shitting me..

Why on earth is it interacting with a process management utility like this? I've never seen this happen until now, and was ripping my hair out trying to figure out why MO2 just kept closing either ER or AR6 (0xc0000005 in event log). Process Lasso is a staple on my system, been using it for over a decade and it's become practically a requirement for modern CPUs to perform optimally in games (forcing non-SMT or single CCD or non-E cores).

Whoever's maintaining this, please provide some input as to what's happening. We can run the utility after game startup, but not during initialization. Makes no sense.

I just change ac6.exe cpu affinity - always - select cpu affinity - check all available cpu in project lasso, now it works perfectly with lasso active so no need to uninstall it

[detrituszero]

For me, AC6 wouldn't launch through modengine2 apparently because the CPU priority was set to 'normal' when launching normally but set to 'below normal' when launching with the modengine2 launcher for some reason. When I set that to also normal or higher, it started working again, though I don't know why it switched to 'below normal' priority in the first place. Also it does launch perfectly fine with project lasso open for me.

[DAOWAce]

Maintainer seems to have merged a commit 3 days ago, so maybe they're coming back to update the tool. Seems version 2.2 was pushed in the source last month but never created as a build.

Can you change the title of this to better represent the actual issue? like "modengine2 crashes on initialization if process affinity is managed by another tool"