AltimorTASDK
Sorry for spamming issues, it was dumb and immature.
Sorry for spamming issues, this is the only way I know to contact you @AltimorTASDK I appreciate what you have done in the past and now thinking about it realize how you did us all a favor fixing or making the software in the first place. I use kovaaks a lot and i am working on placing better in fortnite and improving. I swapped my sens after the software became incompatible with fortnite. I would appreciate it highly if you could possibly find a fix to the issue or make a new version when you find the time. Sorry once again, spamming issues was childish. I closed all issues I spammed @AltimorTASDK
@justahelper Do you know of a way for me to find my exact sens without having to get someone else who hasn’t played? Like something that I can understand well, I’m not a coder at all and have 0 experience and I really need to practice my aim to improve and I’m just kind of stuck.
@Intention1x honestly the exact precision isn't super important anyway, at least if your not on a super high DPI... eg 1000+. my accuracy different between say 0.050 (400 dpi) vs 0.05231232321 is negligible. I would also try aim lab, you get the full 3rd person view and better statistics/feedback on what you need to improve and can tailor training to fix it.
@clearbucketLabs thanks for the response, i personally do not think aim training is worth practicing for fortnite if it is not the same sens. When you take large flicks that small increment can make a huge difference so training the wrong sens for fortnite would be bad imo.
I really need this software to be working, please fix it in your free time
https://www.reddit.com/r/FPSAimTrainer/comments/d3169l/client_settings_editor_broken/
@Intention1x just stop it, it's enough. If I was Altimor and I saw all you comments, any desire to fix the app would disappear immediately. And since this is an app that he makes in his free time, for no money, he needs to have the desire to actually work on it.
Just to help you stay quiet, I saw this posted already but you can try https://www.youtube.com/watch?v=GbIn7FKfphQ. Its a script by Kovaaks which should get you as close as possible to your real sensitivity.
Finally I think you are underestimating how much work fixing this is. I've only taken a quick look at UE source code zlib and serialization methods, and decided that I would not have the time to reverse engineer it. You indicating to be willing to pay $15 translated to an hourly salary for the work needed would result in almost nothing. So just be quiet, hope he fixes it and if he does be very thankful.
Okay im sorry @AltimorTASDK , i didn't think he was seeing the stuff, sorry again your right. i have no excuses, thank you for the temporary solution.
The latest update also changes the sensitivity settings to percent now. not sure if they're stored the same though.
If they handle it the same as controller sensitivities then they are Unsigned integers or Float's. I had to change my sensitivity settings before through this app and couldn't at first because the app couldn't handle UInt32.
I ended up adding my own rows with the same name except with a Float type and removing the original. Fortnite had no problem interpreting this.
This application breaks the settings completely, and If I click the Controller Settings on Fortnite client, then it will be crashed. I tried to figure out why it happened by watching the log files many times. And I finally figured out! It because the this application will change the gamepad settings to unsupported format. so Fortnite Game Client cannot parse it and crashes. I want author of this application to make it able to delete the file at least to reset the all settings. or just support the latest version file format of settings file.
This application breaks the settings completely, and If I click the Controller Settings on Fortnite client, then it will be crashed. I tried to figure out why it happened by watching the log files many times. And I finally figured out! It because the this application will change the gamepad settings to unsupported format. so Fortnite Game Client cannot parse it and crashes. I want author of this application to make it able to delete the file at least to reset the all settings. or just support the latest version file format of settings file.
Your probably opening an old legacy file and saving it as the new file which is unsupported. this app does not even load the latest format at all... obviously it would crash if you saved it as the wrong format.
I'm still using a saved old version to upload to the cloud and for now it works. I use this app to set some controller binds I can't within Fornite so different from most of you I guess. Unfortunately anytime I go into options I need to reupload it and I can't make use of some of the new settings since I don't know their names within the config.
@AltimorTASDK Have you maybe had a chance to look into the issue already?
This application breaks the settings completely, and If I click the Controller Settings on Fortnite client, then it will be crashed. I tried to figure out why it happened by watching the log files many times. And I finally figured out! It because the this application will change the gamepad settings to unsupported format. so Fortnite Game Client cannot parse it and crashes. I want author of this application to make it able to delete the file at least to reset the all settings. or just support the latest version file format of settings file.
Your probably opening an old legacy file and saving it as the new file which is unsupported. this app does not even load the latest format at all... obviously it would crash if you saved it as the wrong format.
I got the bearer token of oauth by stealing token with fiddler and requested HTTP DELETE method to /id/ClientSettings.sav and I deleted it manually and It fixed
Client settings is no longer needed
Sent from my iPhone
On Jan 3, 2020, at 10:42 AM, 4g3v [email protected] wrote:
I might have fixed this issue. Use this version and tell me if there are still any problems. https://github.com/4g3v/ClientSettingsEditor/releases/tag/1.6
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.