-
Notifications
You must be signed in to change notification settings - Fork 169
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
144 fps patch #194
Comments
You can already accomplish this either by downloading the FPS unlocker and setting it in place of akebi in settings, or setting the config in GIMI 3dmigoto's d3dx.ini for refresh rate and launching with that, which also is set in settings. |
Yes Carrom Pool Mod apk, It is good fearture to add |
@TukanDev its rust dll time. |
this worked great for me up until 1.5.4 which added XXMI Args Support
on 1.5.4 some change to akebi launch has been made, and FPS unlocker will no longer load. i was able to resolve the issue by uninstalling, deleting cultivation in user appdata roaming, and installing 1.5.3 3dmigoto and FPSUnlocker running perfectly on 1.5.3 |
1.5.4 has not changed akebi handling, only 3dmigoto handling when XXMI is used. GIMI is not affected. I presume you wouldn't normally add "xxmi" to your fps unlocker path or executable name, but if you did then that would be why your handling has changed. |
sorry for the confusion, i was speculating that some change had been made because i can't understand why else it stopped working if no change was made then i'm not sure why 1.5.4 can't launch the same fps unlocker exe as akebi on my windows 10 pc, even when i uncheck migoto in extras it simply fails to launch and instead just boots up the game at 60 fps since i do not use xxmi, i assume there is no difference for me in continuing to use 1.5.3? to be clear i have disabled RSA patch, and do not use grasscutter or mongodb, since i only use cultivation to launch my actual genshin game (official server) with mods and high fps |
1.5.4 only added handling for XXMI, so if you're not using that then you're all good to keep on using 1.5.3. I have checked running fps unlocker with 3dmigoto on 1.5.4 and confirmed the fps unlocker works as expected with no issues on my end. If you do update back to 1.5.4 in the future, just double check if "xxmi" exists anywhere in the folder path for the fps unlocker. If it does then it could be causing issues from that. So 1.5.3 won't be missing out on anything, unless at some point you switch to using XXMI for 3dmigoto. |
it might be a good feature to add
The text was updated successfully, but these errors were encountered: