How do I stop archebuddy from loading the game in highest settings? Even when I turn the high settings off ingame, its still on high settings until I restart archeage but even then, archebuddy will just reload my archeage in highest settings making my multi session key useless since I cannot load more
Archebuddy High settings default?
- Thread starter Silyss
- Start date
Seabass Chu
New Member
- Joined
- Mar 19, 2015
- Messages
- 61
- Reaction score
- 0
turn the high settings off in game, then log out to character selection screen then exit game. Afterwards, it should work fine 
It worked for me.
If that doesn't work, then quit archebuddy and open AA via glyph normally, then switch to lowest settings once more, then log out and exit game. that should do it
It worked for me.
If that doesn't work, then quit archebuddy and open AA via glyph normally, then switch to lowest settings once more, then log out and exit game. that should do it
Seabass Chu
New Member
- Joined
- Mar 19, 2015
- Messages
- 61
- Reaction score
- 0
UPDATE:
IF RUNNING MULTIPLE SESSIONS, MANUALLY CONFIGURE EACH ACCOUNT TO LOW SETTINGS, THEN EXIT OUT OF EACH ONE IN ORDER FOR THE CHANGES TO APPLY
(changing one to lowest settings won't make all other accounts become low settings as well. you need to change each one after you log in)
EDIT: it's no longer working for me. All of my accounts will individually log on as the lowest settings. However, if i'm botting multiple accounts, only the first one will use lowest setting. All the following ones after that will be high settings. Out please help with this! thanks!
IF RUNNING MULTIPLE SESSIONS, MANUALLY CONFIGURE EACH ACCOUNT TO LOW SETTINGS, THEN EXIT OUT OF EACH ONE IN ORDER FOR THE CHANGES TO APPLY
(changing one to lowest settings won't make all other accounts become low settings as well. you need to change each one after you log in)
EDIT: it's no longer working for me. All of my accounts will individually log on as the lowest settings. However, if i'm botting multiple accounts, only the first one will use lowest setting. All the following ones after that will be high settings. Out please help with this! thanks!
Last edited:
exactly. doesnt work anymore, and 0ut is neglecting to communicate with the subscribers who have paid for this program, we cant use it because it isnt working properly. yet no fix, and no status update or any word on him trying to fix it...
where is the love. ?
where is the love. ?
Hey,
This no longer works, I have tried it now with several different combinations, but no work. 1st account settings will be saved by 2nd account will be Very High settings no matter hwat I have changed.
But when I boot my 2nd account from Glyph, the settings are saved. But when I boot 2nd account via AB, the settings goes back to Very High. I believe this is something to do with AB.
Edit: Some testings, if I switch 1st account with 2nd account, then the 2nd account that gets booted gets its settings set to Very High. (TL;DR: 2nd account and + ALWAYS set to Very High settings)
The Very High settings are SO hardcore that my "Nividia Graphic card has recovered from a failure". It is literally killing my graphic card
Last edited:
hehe yeah 6 bots today temporary kill my old graphic nvidia gts-250
when i get up my PC still running but i have black screen on monitor and info "no video output" or some like this xD when i restart PC still have black screen and no video output xD
i smoke two cigarettes and waited few min and ufff PC now work xD
Quick update, i figured out the problem, i did not write a tool to automate a workaround yet. But the issue is that the client seem to take an exclusive lock on its config database now (so the 2nd client cant read it and default to vhigh).
Using a tool to unlock files, there are many out here, i did not dig too deep, I'm using UNLOCKER 1.9.2 BY CEDRICK 'NITCH' COLLOMB but be carefull, while the application itself is clean, the installer try to change your homepage / offer to install crap. You can skip all the crap on it, its not forced, but read before clicking to be safe (or just wait till out fix it in inside AB or i finalise an automated tool for it).
Basically, using a file unlocker, after running each client (except the last one no point here), you must unlock all files inside documents/Archeage/USER/udf/, before starting the next client. Be warned that this mean that if you change the config when more than one client are open, you will corrupt your option database, in which case the only fix is to delete the USER/udf/ folder.
So a step by step assuming you dont care about the original configs would be (they are likely to be lost either way)
To Set everything up:
1. Delete Documents/Archeage/USER/udf/ while the clients are shutdown
2. Start a single client and set your configs like you want them, then exit the client properly (wait the 10sec timer). This should write a few files in USER/udf a file like 000002.log and a MANIFEST along others
3. Restart your single client and double check that your configs loaded properly the shut it down again
4. Backup your USER/udf directory so you can easily restore it if your configs corrupt themself.
And then to start your clients:
1. Start the first client
2. Unlock the directory and all files inside "documents/Archeage/USER/udf/"
3. Start your next client
4. Repeat 2-3 for as many clients as wanted
5. enjoy all your clients at low.
As i said, this is only the manual process, sometime in the next few days, if OUT doesnt write a fix directly inside AB, i will release a small tool that will automate the process to start multiple clients (the setup part would still be required but thats a one time thing).
The Change in the client from a shared lock to an exclusive lock on those file, was likely an attempt by XL to reduce the risk of the option database getting corrupted, since the game doesnt seem to be able to fix it on its own (and then all your config changes reset every restart AB or not until you delete the USER/udf/ folder)
Using a tool to unlock files, there are many out here, i did not dig too deep, I'm using UNLOCKER 1.9.2 BY CEDRICK 'NITCH' COLLOMB but be carefull, while the application itself is clean, the installer try to change your homepage / offer to install crap. You can skip all the crap on it, its not forced, but read before clicking to be safe (or just wait till out fix it in inside AB or i finalise an automated tool for it).
Basically, using a file unlocker, after running each client (except the last one no point here), you must unlock all files inside documents/Archeage/USER/udf/, before starting the next client. Be warned that this mean that if you change the config when more than one client are open, you will corrupt your option database, in which case the only fix is to delete the USER/udf/ folder.
So a step by step assuming you dont care about the original configs would be (they are likely to be lost either way)
To Set everything up:
1. Delete Documents/Archeage/USER/udf/ while the clients are shutdown
2. Start a single client and set your configs like you want them, then exit the client properly (wait the 10sec timer). This should write a few files in USER/udf a file like 000002.log and a MANIFEST along others
3. Restart your single client and double check that your configs loaded properly the shut it down again
4. Backup your USER/udf directory so you can easily restore it if your configs corrupt themself.
And then to start your clients:
1. Start the first client
2. Unlock the directory and all files inside "documents/Archeage/USER/udf/"
3. Start your next client
4. Repeat 2-3 for as many clients as wanted
5. enjoy all your clients at low.
As i said, this is only the manual process, sometime in the next few days, if OUT doesnt write a fix directly inside AB, i will release a small tool that will automate the process to start multiple clients (the setup part would still be required but thats a one time thing).
The Change in the client from a shared lock to an exclusive lock on those file, was likely an attempt by XL to reduce the risk of the option database getting corrupted, since the game doesnt seem to be able to fix it on its own (and then all your config changes reset every restart AB or not until you delete the USER/udf/ folder)
Last edited:
ludijak559
Member
- Joined
- Nov 23, 2012
- Messages
- 273
- Reaction score
- 2
cant download that unlocker chrome is blocking it as a harmful file
just find another similar software or wait for me to be done (or hope OUT fix it before me xD). I did warn about the fact the installer was unclean / containing spyware. Altho the spyware install are not forced (they arent done behind your back) they still are in, hence chrome not liking it.
maddmike407
New Member
- Joined
- Feb 3, 2013
- Messages
- 3
- Reaction score
- 0
I have used unlocker before when deleting system files. When trying to use it on the udf file is says there is no locking handle and give me the same 3 options im used to seeing (delete, move, rename)
as promised, for those who have the issue with their multipleclient ending up on default instead of the config they have on the first client. This is a rather lazy write, i only spent around 10 minutes on it but it should get the job done (it did in my tests and its all that matter for me).
http://www.jeypc.com/dl/AAMultiClientConfigUnlocker.zip
This contain an exe and the c++ source used to build it.
Its just something i wrote quickly for myself, i have no intentions to support it, but if others want to improve / use it, be my guests. I do not intend for it to be a permanent solution and instead merely a way for multiclienting to work ok while OUT figure the best approach to fix it.
@Out if you do use this approach to fix the multiple client not loading the configs, you can call UnlockAndClean() just before launching a new client. This would work out much better than my current approach since i have no way to prevent launch while the cleanup / unlock is being done. It would also mean that launching a single client using AB would not cause that client config to become read only.
To use this tool. You must first setup everything (one time thing)
- remove your "C:\ArcheAge0\Documents\USER\udf" to start from a clean slate.
- start a single Archeage client (AB or not does not matter). Change your graphic configuration to whatever you want (probably would work with audio config as well but im not sure) then close the game using the exit game option then wait the 10 sec.
- start the single client again. Connect all the way and exit again (this is so archeage will actually commit its recent database binary log to the options database before we start multiclienting.
- (optional) copy your clean "C:\ArcheAge0\Documents\USER\udf" directory, just in case in become corrupted for one reason or another, you can always replace it back with your backup and revert to your configs.
Once thats done, your ready to use the tool,
- when no client are running (1 client running should work but untested) , run AAMulticlientConfig.exe it will open a console window and start watching for archeage.
- start your first client then wait at least 2 minutes (the tool will tell you once its ready for another client, ideally give it at least 3 minutes between clients to be safe).
- start your next client and wait another 2-3 minutes. rince and repeat as often as you want.
You only need 1 AAMulticlientconfig.exe process running, it will keep on running and keep an eye to fix / avoid fuckup on your archeage options database.
When the tool is running, the game configs will likely not save (but some part may and it may cause your option database to corrupt and as such revert to your default setting on next client start so just dont mess with options when the tool is running).
Edit: It doesnt seem to be needed anymore.
http://www.jeypc.com/dl/AAMultiClientConfigUnlocker.zip
This contain an exe and the c++ source used to build it.
Its just something i wrote quickly for myself, i have no intentions to support it, but if others want to improve / use it, be my guests. I do not intend for it to be a permanent solution and instead merely a way for multiclienting to work ok while OUT figure the best approach to fix it.
@Out if you do use this approach to fix the multiple client not loading the configs, you can call UnlockAndClean() just before launching a new client. This would work out much better than my current approach since i have no way to prevent launch while the cleanup / unlock is being done. It would also mean that launching a single client using AB would not cause that client config to become read only.
To use this tool. You must first setup everything (one time thing)
- remove your "C:\ArcheAge0\Documents\USER\udf" to start from a clean slate.
- start a single Archeage client (AB or not does not matter). Change your graphic configuration to whatever you want (probably would work with audio config as well but im not sure) then close the game using the exit game option then wait the 10 sec.
- start the single client again. Connect all the way and exit again (this is so archeage will actually commit its recent database binary log to the options database before we start multiclienting.
- (optional) copy your clean "C:\ArcheAge0\Documents\USER\udf" directory, just in case in become corrupted for one reason or another, you can always replace it back with your backup and revert to your configs.
Once thats done, your ready to use the tool,
- when no client are running (1 client running should work but untested) , run AAMulticlientConfig.exe it will open a console window and start watching for archeage.
- start your first client then wait at least 2 minutes (the tool will tell you once its ready for another client, ideally give it at least 3 minutes between clients to be safe).
- start your next client and wait another 2-3 minutes. rince and repeat as often as you want.
You only need 1 AAMulticlientconfig.exe process running, it will keep on running and keep an eye to fix / avoid fuckup on your archeage options database.
When the tool is running, the game configs will likely not save (but some part may and it may cause your option database to corrupt and as such revert to your default setting on next client start so just dont mess with options when the tool is running).
Edit: It doesnt seem to be needed anymore.
Last edited: