Problem - Clients crashes or not starting

[Razkle]

Since about 2 months now I have noticed that while running isboxer and adding new clients after MQ2 is in memory that I get 2 issues, either eqclient.exe never launches (not the Launchpad) or it launches then black screen locks (crashes) or reports that eq has stopped responding. I have tested this over and over and it seems to only happen when mq2 is in memory AND I try to launch eqclient, almost like eqclient can see the addon or a plugin in it. Can we get a revamp of known good vs known bad plugins? I ONLY use REDGUIDES stuff so no weirdness or active hacks. I am pretty confident that I know what I am doing, well most days. But I am at a loss to pinpoint the issue. This happens on 11 different machines running both win7 and win10 so its not a win issue, I believe it is a plugin vs eqclient issue... I do not use fps or eqnav, just the base core+eqbc really...

[Plugins]
mq2aaspend=1
mq2advpath=1
mq2autoaccept=1
mq2bzsrch=1
mq2cast=1
mq2chatwnd=1
mq2combat=1
mq2custombinds=1
mq2debuffs=1
mq2dpsadv=1
mq2eqbc=1
mq2eqbugfix=1
mq2events=1
mq2exchange=1
mq2hud=1
mq2itemdisplay=1
mq2log=1
mq2map=1
mq2melee=1
mq2moveutils=1
mq2nonagwindows=1
mq2notepad=1
mq2posse=1
mq2rez=1
mq2spawnmaster=1
mq2tooltip=1
mq2twist=1
mq2bufftool=1

 

[DriveCrash]

Try these:

[Plugins]
mq2aaspend=0
mq2combat=0

Also, disable MQ2's FPS plugin and the ViewScreen port thing (ack don't remember the name). ISBoxer has a built in FPS controller to boost performance, and the two could be conflicting. Enable these one at a time until you pinpoint the culprit.

MQ2Combat is basicly superseded by MQ2Melee btw, unless you have old macros you shouldn't need it.

 

[Razkle]

will try the combat remove, I never use fps.... I use aaspend though

 

[Maskoi]

there is a fix for MQ2AAspend I will upload a new compile tomorrow

 

[riot]

What's wrong with AASpend? I''ve been using it without issue (other than purchasing AAs in the wrong order!)

 

[Maskoi]

its crashing in some instances

 

[Razkle]

aaspend causes your client to crash randomly, but its livable, I just need to straighten out the no - loading / crashing on loading

 

[mackal]

What's wrong with AASpend? I''ve been using it without issue (other than purchasing AAs in the wrong order!)

I wanted my own MQ2AASpend, so I wrote my own https://github.com/mackal/MQ2AAPurchase

It should crash or buy in wrong order. I think it works the same as RG's MQ2AASpend, but missing things I didn't want to write (brute mode)

If someone wants to put up a build until Maskoi gets MQ2AASpend working, I wouldn't mind. Just need to change something in the INI and you should be good to go (the section it looks in for AAs is MQ2AAPurchase_List)

 

[DriveCrash]

aaspend causes your client to crash randomly, but its livable, I just need to straighten out the no - loading / crashing on loading

Well, I can tell you I launch EQ with MQ in memory all the time, and never have the no loading issue. I have however noticed at times the eqclient.exe takes longer to start when MQ2 is loaded, but it's nothing major. Are you running all your clients through ISBoxer from one EQ install folder? I have 3 folders for 6 accounts to divide the work.. two are on SSD and one is on a physical drive.. but I also don't use ISBoxer.

Update for ISBoxer? Update video card? Zip everything up to a backup folder and install clean? Good luck!

 

[Razkle]

I have 3 folders for 6 accounts to divide the work

Not sure how you are having the work divided in memory as memory does not care where it reads from, it is just faster off the SSD but once in memory the original location is mute. Once eqclient gets me to char select all is well, all my issues on 11 machines, running both win7 and win10 are before char select screen, it is like some check being made is causing a lockup. yes I run isboxer and that may be the issue, but I will never know if I don't walk through the process as I am doing here and hopefully someone else is also having the same issue. With any problem you look at all the facts, you narrow down known issues and possible causes then you remove things one at a time until you find the culprit, then you kick it in the face like Holly Holms does!

- - - Updated - - -

at this point my gut tells me it is a plugin as sometimes I get a client crash when I open Launchpad (to update so the bypass works) as well. isboxer is in memory but not being used for that instance. So it COULD be isboxer I guess but I am pretty sure its something in the checks eq does for active memory stuff, so that's why I posted my plugin list

 

[DriveCrash]

Sorry, I forgot you had said you have the same problem across computers and OS's. That eliminates most of my suggestions.

EQ launches through launchpad and directly with just MQ2 loaded without problems. EQ launches just fine with only ISBoxer loaded. So the problem cannot be something in the EQ client checking for an active addon in memory or otherwise, it has to be a conflict between ISBoxer and MQ2, but only at startup. Will eqclient.exe load if you kill the MQ2 program in the tray, and leave it running on clients that are already logged in? (IE: don't /unload when you kill mq2).. If so, then it's something with MQ2 trying to do it's insertion?
Perhaps if you kill the tray icon, fire up EQ clients with ISBoxer running, then re-run mq2 for insertion, it would be a "workaround"?

Sorry if I'm not being helpful.. I have finals on the brain.

 

[Razkle]

I am always happy to have someone to bounce ideas/solutions off of, so thanks for that...

EQ via Launchpad while mq2 is loaded crashes within a second of clicking the icon with crash report (not sent) about 25% od the time and without mq2 loaded 0% of the time. I have narrowed it down to not an isboxer issue from that alone. That is why I was looking into plugins as I know there is a current thread on evil plugins and accidental ones like mq2cast

 

[Razkle]

before this last update crashing like a bitch, now whatever changed in this update no more crashing on load.... yeah! it is fixed! I can only assume it was something eqclient did not like in mq2 on my side

 

[DriveCrash]

before this last update crashing like a bitch, now whatever changed in this update no more crashing on load.... yeah! it is fixed! I can only assume it was something eqclient did not like in mq2 on my side

YAY!! Glad to hear it!

 

[tms]

I have allways the problem, that 1-3 instances on EQ crash at startup, just after entering the psw and before the server selection. After the first few crashes they stop and all works fine.

 

[Razkle]

did it clear up for you now as well? mine did it CONSTANTLY on all machines before this last patch now all is well!

 

[Fenworth]

I was having a problem with this a few months ago. I don't remember the specifics, but it had to do with a recent change in ISBoxer. I benefited from someone's thread on the ISBoxer web page which had me download the beta version of ISBoxer patch; one of the settings on the ISBoxer patcher. That fixed the crashing of EQ client. Maybe IsBoxer has officially issued the patch and that's why it fixed itself?