Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: Metaphor: ReFantazio ASI Loader loads crash handler #484

Open
mnepk opened this issue Nov 12, 2024 · 7 comments
Open

Bug: Metaphor: ReFantazio ASI Loader loads crash handler #484

mnepk opened this issue Nov 12, 2024 · 7 comments
Labels
bug Something isn't working untriaged No decision has been made by the developers.

Comments

@mnepk
Copy link

mnepk commented Nov 12, 2024

Describe the Bug
When attempting to start the game "Metaphor: ReFantazio" via API loader, an error occurs by the loader trying to load crash_handler.exe in a subdirectory of the game.
The game starts normally after closing the error message however.

To Reproduce
Steps to reproduce the behaviour:

  1. Deploy API loader on Reloaded-II
  2. Start the game on Steam

Expected Behaviour
The API loader loads only the excutable for the game (METAPHOR.exe), without loading the crash handler (\bin\crash_handler.exe).

Screenshots
The error message:
error

Log files (created simultaneously)
log1
log2

Additional Context
It occurred on Windows 10, with no mods loaded.
ASI loader dll file is named WINMM.dll.

@mnepk mnepk added bug Something isn't working untriaged No decision has been made by the developers. labels Nov 12, 2024
@mnepk mnepk changed the title Bug: Metaphor: RefantaZio ASI Loader loads crash handler Bug: Metaphor: ReFantazio ASI Loader loads crash handler Nov 12, 2024
@Sewer56
Copy link
Member

Sewer56 commented Nov 12, 2024

Game has Denuvo, I'm not personally touching it with a 10000000 foot pole. I don't support the destruction of game preservation.

In any case, you can probably ask @AnimatedSwine37 or @DeathChaos25 for a patch to disable the crash handler. While it's unclear why it's getting triggered, MetafaEssentials should probably kill it by default, so devs don't get random crashes on modded copies sent to them.

@mnepk
Copy link
Author

mnepk commented Nov 12, 2024

Game has Denuvo, I'm not personally touching it with a 10000000 foot pole. I don't support the destruction of game preservation.

In any case, you can probably ask @AnimatedSwine37 or @DeathChaos25 for a patch to disable the crash handler. While it's unclear why it's getting triggered, MetafaEssentials should probably kill it by default, so devs don't get random crashes on modded copies sent to them.

Thank you for your reply.

Oh, I didn't notice this being a Denuvo matter.
I'm not willing to disable Denuvo, I'm just annoyed by the error occurring every time I launch the game, and the game itself is running without issues after closing the error message.

Other games with Denuvo, Persona 5 Royal for example, have no problems like this, so I wonder why this happens for Metaphor only...

@AnimatedSwine37
Copy link
Contributor

That's strange, I'm fairly sure the other PC persona games have a crash handler exe like this as well but I've never seen an error like this with them.

I'm not really involved in metaphor modding at all so far (I've never even launched it with mods) so hopefully DC will look at it. If it is just preventing that process from being run it'll hopefully be easy to change.

@Sewer56
Copy link
Member

Sewer56 commented Nov 13, 2024

@mnepk It's not a Denuvo matter, but I just refuse to support it for moral reasons.

@AnimatedSwine37 in any case yeah, regardless of cause, I'd just kill the game code that launches the crash handler. Don't want to be spammimg devs with crash dumps of modded games in any case.

@DeathChaos25
Copy link
Contributor

I could not locate where the game was calling crash handler as the executable is not seemingly accessed directly via name.

However you can delete the crash handler with 0 consequences and be rid of this problem entirely, which is what I resorted to.

@Sewer56
Copy link
Member

Sewer56 commented Nov 13, 2024

Can you not force induce a crash, for example by dereferencing 0x0 in your code?

From there you can check what calls CreateProcess and trace back.

@mnepk mnepk closed this as completed Nov 13, 2024
@mnepk mnepk reopened this Nov 13, 2024
@mnepk
Copy link
Author

mnepk commented Nov 13, 2024

Thank you all for your responses.

I confirmed that the error is evitable by deleting or renaming the handler, something like crash_handler.exe.bak, but I want to keep the files in their original state if possible.

Also, for additional information, the error doesn’t occur when I use launch application function on Reloaded-II.
Well, maybe the only and biggest problem about this is that I prefer to use steam launcher much more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working untriaged No decision has been made by the developers.
Projects
None yet
Development

No branches or pull requests

4 participants