Cannot load via commands - "Options Error"

[HomersDonut]

Hi Keyclone.

I've had a read through all the recent threads but haven't been able to find another occurance of this. The problem I'm getting is when using commands & maximiser to load 2 instances of EQ2. This has occured for both the 1.7f and 1.7g releases. Here is the scenario... If I create a new command, it loads up in the specified region with the correct game settings. If I create another command for the 2nd instance (which is being run from a different directory) and then launch them both, they will both load but will both be using the game settings from the 2nd instance. Next is where it really goes downhill... the commands don't work again but throw an eror instead. The error is "The options definition file failed to load. This generally indicates that your patch was corrupted for some reason. Try a complete scan, and if that doesn't help then you may need to reinstall."

I guess my first question is whether this error is being generated by keyclone.exe or everquest2.exe? My assumption is that it is everquest2.exe since keyclone doesn't provide any kind of scan option, not to mention the fact that no WOW players are experiencing it. That being the case, then why does it happen when launched from Keyclone and not directly? I'm trying to think of a suitable analogy here, but it seems like trying to launch an application via a shortcut that has a 'Start in' folder incorrectly set. FYI, if I recreate the command ('shortcut'), it works again until I either close Keyclone or create another command from a different folder. One thing I haven't tested for is whether it makes any difference by typing the command directly instead of using the browse button.

If TDK is reading, I'm curious if he has come across similar issues while playing with maximiser/commands. Let me know if you need other info from me Keyclone, or whether there is other testing I can perform. BTW, looking forward to seeing Keyclone natively handle EQ2 without needing Innerspace. /wink /nudge /nod

[keyclone]

G'evening HD,

my guess would be the error is generated by EQ2

if you want to use 2 separate directories... then you need to create 2 separate commands... each launching from a different directory.
also, make sure to specify different region names so the windows will appear in separate locations

as for native kc-eq support... yes, it is at the top of the list now

[HomersDonut]

Thanks for the quick response Keyclone.

I have 2 KC commands setup. Each one uses the exe from a different directory. Each is set to a different region.


[commands]
count=2
command_00=Box1
action_00="D:\program files\Sony\EverQuest II\EverQuest2.exe"
keymap_00=
region_00=Region0
uname_00=0.''
cpu_00=10000000
maxfps_00=0.0
excludeRR_00=0
alwaysOnTop_00=0
lockInForeground_00=1
command_01=Box2
action_01="D:\program files\Sony\EverBox2\EverQuest2.exe"
keymap_01=
region_01=Region1
uname_01=0.''
cpu_01=10000000
maxfps_01=0.0
excludeRR_01=0
alwaysOnTop_01=0
lockInForeground_01=0

[regions]
count=2
region_name_00='Region0'
region_00=1,0,0,1439,873,0,0
region_pip_00=0,(120.4.4)
region_name_01='Region1'
region_01=1,1441,0,2880,873,0,0
region_pip_01=0,(121.4.4)


Where I previously mentioned that both instances would load with the settings from the second instance, I believe it would be more correct to say that it takes the settings (for things like UI, etc) from the most recently created command, regardless of which directory the executable was actually launched from. I would need to do some more tests with this though to be sure. Since I'm still at work, what I will do tonight is test the following:
1. Delete all existing commands.
2. Create the command to launch the first instance
3. Launch first instance via command - confirm settings being used.
4. Restart Keyclone - confirm whether first command still works.
5. Create 2nd command (after recreating 1st if necessary)
6. Launch both instances via commands - confirm settings.
7. Restart Keyclone - confirm both commands again.

Will let you know how it goes.

Cheers, HD

[HomersDonut]

Hi Keyclone.

Here are the steps and results of my further testing. The setup consists of 2 instances of EQ2 running out of 2 separate directories. Each instance is configured with different UI settings so as to tell them apart. All previous KC commands have been removed though the maximiser regions remain.

1. A KC command with a path/executable that has been typed in fails.
2. That same command that has had the executable entered via the Browse button works as expected and with the correct UI settings and in the correct region.
3. After restarting Keyclone that command no longer works. Re-browsing to the same executable allows the command to start working again.
4. Created the 2nd KC command by browsing to the executable in the 2nd directory. This command works with the correct (ie, the different) UI settings of that instance. It is loaded in the correct region.
5. Reloading the 1st instance loads up in the correct region, but is now using the UI settings of the 2nd instance.
6. Reload Keyclone - neither command works. Re-browse the 1st command to the executable in the 1st directory. Both commands load in their respective regions but are both now using the UI settings of the 1st instance.
7. Reload Keyclone. Both commands again fail. Re-browse the 2nd command to the executable in the 2nd directory. Again, both commands load in the respective regions but now with the UI settings of the 2nd instance.
8. Reload Keyclone. Both commands again fail. Re-browse the 1st command to the executable in the 2nd directory and re-browse the 2nd command to the executable of the 1st directory. ie, both directories have been swapped. Both commands load in their respective regions but with the UI settings of the 1st instance (since it was the last directory browsed to)

I hope that helps shed some light on where things may be coming unglued.

Thanks and keep up the great work. :)

[keyclone]

i have made a few mods to keyclone that will ensure it starts in the expected directory. (it was wow specific before)

the next version should resolve this problem for you.

[HomersDonut]

Excellent :D
Thanks for your efforts :thumbsup: