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
Custom command fork does not work as expected #255
Comments
Hi. I guess you forgot to enable "Custom command mode" - the checkbox directly above "Custom command". edit: added words, to make a complete sentence :) |
Bloodstained Ritual of the Night.log This is the log I got. It seems to be doing something but it doesn't work at all. Does 'starting regularly' mean it is started with vanilla Wine perhaps? |
So the exe is found and stl attempts to start it. In this case it is no stl problem, but probably simply a missing dependency of the exe (maybe a specific dotnet version?). |
I don't have the game, but just digged out your exe from the net and started it with a different game. |
I wonder if this exe's error logs can be, in fact, logged. Can there be a commandline instance (cmd.exe)? |
Wasn't @home. I guess you found this meanwhile yourself. |
Hello. I am trying to run a custom Windows executable file (Bloodstained RoTN Widescreen Patch) before a game of mine (Bloodstained RoTN) launches (so I need to fork the custom command into background). While using the GUI, setting the custom command to fork does not run the patch at all. I assume this is where you'd put game patchers (like the community-made widescreen memory-hack ones). Am I missing something?
The text was updated successfully, but these errors were encountered: