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

Reipatcher stop a few second after launch without doing anything #681

Open
petit142 opened this issue Mar 7, 2025 · 0 comments
Open

Reipatcher stop a few second after launch without doing anything #681

petit142 opened this issue Mar 7, 2025 · 0 comments

Comments

@petit142
Copy link

petit142 commented Mar 7, 2025

Hello i currently cant translate unity game anymore, i was using reipatcher around a year ago together with translator ++ to translate unity game and it worked perfectly this time thought i couldn't patch the game with reipatcher whenever i tried it with translator ++ it just opened the directory of the game instead of the game and after more research on reipatcher without finding why. I uninstalled translator ++ altogether with xunityautotranslator (so i think it did uninstalled reipatcher too) and started again this time with the reipatcher from this github and without translator ++.

the problem i encountered is at the step 3, executing SetupReiPatcherAndAutoTranslator.exe i put it in the file of the game with the unitycrash.exe and the game.exe, but when i launch SetupReiPatcherAndAutoTranslator.exe it open a cmd console... dont write anything, it just open.... and it close down a few second after, from what i know normally it should start a lot of code, make new directory and work well pretty easily. (same result as before uninstalling everything when i tried without going through translator ++)

i tried administrator right, opening it with the game but it didn't change anything. Also i dont know if it's relevant but game already patched with reipatcher still work and are being translated, (thought i cant patch them again if i take off the patch)

i guess the problem is on my part since it worked before and not anymore with a big gap in time (maybe i installed other thing that make it not work anymore? maybe i have a plug manager that i dont know is one and didn't have before? can it result in that? is avast cleanup or driver update a plug manager?) but i couldn't find the solution on my own so i wonder if anyone can help me find out why and how can it be solved. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant