Constant Crash w/ EQ2Bot after Update

S

Syliac

Active Member
EQ2Bot constantly crashes the game after EXT update. As soon as your in combat Crash to Desktop. :confused:

Didn't realize it was a test build never logged into IRC... :rolleyes:
 
Last edited:
Nuprecon

Nuprecon

Active Member
its wide spread, it was a very large patch and the build that is out is a test build.

As per IRC

Code: 
[21:39] CyberTech: a lot of things are going to be broken, ama asked for crash reports to be posted. be sure to use the proper method to report.  much changed in EQ2 this round.
[21:39] CyberTech: !crash
[21:40] CyberTech: !wiki crash
[21:40] isxGames: 1. Crash Reporting: http://eq2.isxgames.com/wiki/index.php?title=Crash_Reporting
Which takes us to the Eve crash instructions, but the same applies for EQ2

http://eve.isxgames.com/wiki/index.php?title=Crash_Reporting
 
K

Korp

Active Member
I haven't had any luck with the craft bot either since the update, same constant crash problems.

Just mentioning it, I can't load up the debugger for various reasons, so I can't provide much in the way of help.
 
C

coolman

Active Member
I can't even use radar!!


LavishScript Execution Stack:
-----------------------------------
ui -reload -skin eq2 extensions/isxeq2radar

Running Scripts:
-----------------------------------
 
F

fryfrog

Well-Known Member
I asked in IRC if any dumps were needed for debugging the problem and someone told me that it was resolved. So just be sure to update isxeq2 by loading it the normal way.

I verified, eq2bot worked fine after.
 
M

Multicharacter

Senior Member
The old style harvester is crashing for me when it finishes following a path and starts to shut down the script. Going to try to narrow down the exact command causing the crash before doing a bug report.
 
C

coolman

Active Member
Frequently crash while using eq2bot. Sometimes it works no problem, sometimes it crash with no debug detail, just crash to desktop, no hint.
 
Pygar

Pygar

EQ2Bot Specialist
If you've patched isxeq2, innerspace, and eq2bot to latest versions, it should be working fine.

I ran eq2bot for about 20 hours this weekend without a single crash. If you are crashing AND you've updated everything, I'm going to need to have exact steps needed to reproduce it.

I'd be inclined to instruct you to delete your entire innerspace tree and resintall everything first though, as I don't believe there is any problem with the bot, extension, or innerspace at this time.
 
C

coolman

Active Member
Now I know the reason.

Dual core!!

Use one core get no problem, SOE just changed something , if you didn't chose multi core ,EQ2 will only use the first core. And if you open 5 EQ2 accounts, they only use one core, and very slowly!!! LAGGY !!!!

SOE did this towards Innerspace??
 
W

wired203

Active Member
I still dual box after GU51 and use single core and both sessions go to there respective single core with no problem.

How are you setting the cores up? Are you using the post launch command for it or are you just using isboxer and clicking the little checkbox.
 
P

Plavok

Active Member
My client crashes whenever a crafting-session is finished and the little jingle should be played. I just got this error today and didn't change anything (haven't updated isx or eq2 since yesterday).
 
Nuprecon

Nuprecon

Active Member
Plavok said:
My client crashes whenever a crafting-session is finished and the little jingle should be played. I just got this error today and didn't change anything (haven't updated isx or eq2 since yesterday).
Click to expand...
Does it happen every time? Or just some times?
 
C

coolman

Active Member
wired203 said:
I still dual box after GU51 and use single core and both sessions go to there respective single core with no problem.

How are you setting the cores up? Are you using the post launch command for it or are you just using isboxer and clicking the little checkbox.
Click to expand...

dual box no problem, but 6 box get a big problem. one 2.8G cpu won't support 6 eq2 sessions. but 4core*2.8G get no problem.
 
W

wired203

Active Member
I was referring to dual boxing with a dual core and each session going to each core all happy like.
My eq2 profiles have had multicore turned off on them for some time as it acted out bad with bots when they first applied it.
 
P

Plavok

Active Member
Plavok said:
It happened all the time. But then I disabled multi-core support and after the next crash (activating non-multi-core after restarting), it didn't crash anymore.
Click to expand...
And I'm back to crashing all the time, guess the multi-core setting didn't help after all and I was just lucky yesterday.. ;-)
 
M

Multicharacter

Senior Member
coolman said:
Now I know the reason.

Dual core!!

Use one core get no problem, SOE just changed something , if you didn't chose multi core ,EQ2 will only use the first core. And if you open 5 EQ2 accounts, they only use one core, and very slowly!!! LAGGY !!!!

SOE did this towards Innerspace??
Click to expand...
Do it exclusively because of Innerspace? No.

But it makes sense that if you tell the game you only have 1 CPU/core that it then assigns the game to CPU0 automatically. You can use IS's affinity command to change that however you want though.
 
V

Valerian

ISX Specialist
Multicharacter said:
Do it exclusively because of Innerspace? No.

But it makes sense that if you tell the game you only have 1 CPU/core that it then assigns the game to CPU0 automatically. You can use IS's affinity command to change that however you want though.
Click to expand...
Actually, it makes more sense to let the OS determine affinity regardless. Whether you set it to single core or multicore, (by default) the OS should have the final ruling on which CPU(s) are used by the program, since the OS also has other processes running and presumably knows the best place to run the program.

Beyond the OS, there are always the task manager and IS for the user to fine tune the choices of the OS, but the game itself shouldn't choose based on a hardcoded value.

Having the program itself set its affinity based on some arbitrary checkbox in the options seems pretty stupid, especially since they seem to have hardcoded CPU0.
 
M

Multicharacter

Senior Member
Valerian said:
Beyond the OS, there are always the task manager and IS for the user to fine tune the choices of the OS, but the game itself shouldn't choose based on a hardcoded value.

Having the program itself set its affinity based on some arbitrary checkbox in the options seems pretty stupid, especially since they seem to have hardcoded CPU0.
Click to expand...
Well, all I know is I have multicore turned off, and yet 2 clients keep my dual core at 100% each, so IS is still assigning one to CPU0 and the other to CPU1 successfully.

Edit: As for the crash - I believe it's the "Announce" command. The crashing doesn't happen every time the command is used, but frequently enough that I noticed the distinct lack of crashing when I had commented out all the 'announce' commands in the scripts I use.
 
T

thrakos

Active Member
This is a known issue. Lax has resolved it. If you download (today) the developers version of Innerspace, Lax added the command "proclock". Run this command in your inner-space terminal, then run your "proc 1 on 2 on 3 off 4 off" command and that session will run on those procs until you exit the session.

I confirmed this last night using ISXBoxer, Innerspace & EQ2bot. My system went from Core0 pegged @ 100%, all other cores idle, running 8fps in the main window and 3fps in the background... to All cores ~ 80% utilization with 45fps in the main window and 15fps (locked) in the background. (6-boxing eq2). It's like playing a different game, smooth and sexy.

ISXBoxer Beta.31 & the next spin of innerspace will have all the proper fixes in place, as per Lax's post in this thread: http://www.lavishsoft.com/forum/viewtopic.php?t=4194

rock on
 
You must log in or register to reply here.
Top Bottom