![]() |
|
|
|
#1
|
|||
|
After the patch that introduced sit aggro (two patches ago as of this moment, I believe) I crash a lot more often. I didn't change any settings, install new programs, or anything like that. All I did was update p99 patch files as I normally would.
The really weird thing for me is that its a bit less common (considering it rarely ever happened at all before, its still a notiiceable difference since downloading that patch) for me to crash while zoning, but I crash about 90% of the time I use the /camp command. If I do, about 9/10 attempts will result in a client crash. I can't even use /q either, it just causes a client crash message to pop up and I have to open everquest again. As of right now, and for the last month or two, the only way I can exit game without a client crash followed by a 1018 is to first /camp as usual and wait for my character to camp then alt-F4 to close EQ before the client crash message shows up. Ill post that log file immediately after I experience this again, as I'm stuck at work right.now.
__________________
-Aftermath-
Tasslehof - 60 Druid Barlow - 60 monk Blueberrii - 60 Mage Gigglepurr - 60 Shaman Kids - 60 Rogue Fornfamnad - 60 Cleric | ||
|
#2
|
|||
|
I regularly get zoning crashes. The most reliable way for me to reproduce them is:
- Run under WinEQ2 - Begin zoning process - Click outside the EQ window (I have 3 tiled screens as my desktop, regular multi-monitor not a 3x spanned one using Eyefinity or the like) - Click back into the EQ window before zoning has completed, EQ crashes - If I wait until zoning has completed everything is OK This is not a "windows thinks EQ has crashed because it doesn't respond as it is busy loading stuff" kind of thing, but rather the process immediately terminating. This is running on Win 7 Ultimate SP1, 64x on Intel i5 2500K @ 3.60 GHz, 32GB ram, GeForce GTX 780. Choice of storage for EQ-P1999 doesn't seem to affect it (tried both SSD and classic disks). Connection-wise I get about 45ms with no packet loss on Teksavvy cable (ON) on Rogers cable infrastructure.
__________________
Blue Server || My WTS/WTT/WTB list
| ||
|
#3
|
||||
|
Quote:
I tab out when I'm zoning to check wiki or forums or something. Clicking outside the EQ window 9/10 times makes the client crash. | |||
|
#4
|
|||
|
Crashing while zoning happens about 20% of the time, no pattern to it except some zones are worse than others. Zoning into Felwithe from G'fay I crash more often than not.
__________________
^*^ Aveenia ^*^ - Druid TEAL
^*^ Aveenia Inverse ^*^ - Druid 38 BLUE (RIP) | ||
|
#5
|
|||
|
I was having an issue on my laptop (running windows 8), I had slow zone times and would crash during some of them. This was not happening on my desktop computer that was running windows vista 64 bit so I figured it had something to do with windows 8. Also anytime I would camp on one toon to switch to another I would crash. This is what fixed the problem for me and hopefully fix it for anyone else experiencing this problem.
1st be using latest version of wineq 2nd make the wineq default eq1 shortcut and have the icon on your desktop 3rd right click on that icon then click "troubleshoot" 4th accept the option they provide of running it in windows xp service pack 3 mode. This corrected all the issues I was having and I haven't crashed once since I did this 3 days ago. Also, my zone times are much faster. | ||
|
#6
|
|||
|
That 'solution' has been posted many many times in this thread, and does not solve the problem for a lot of people.
| ||
|
#7
|
|||
|
That's awful
| ||
|
#8
|
|||
|
Six crashes at character select (so far, I haven't stopped yet) and one crash attempting to port into Overthere in the last half hour. Yeah, there's still a problem.
I wish there was some kind of indication that the guys still look at this issue at all. | ||
|
#9
|
||||
|
Quote:
The problem is that there is no obvious common denominator between all of your computers/connections, which makes it exceedingly difficult to nail down the exact problem. Troubleshooting an error like this is usually a process involving hundreds of people - or potentially thousands after the game is released, if the bug slips through Q&A because it only appears in <1% of users, as it does here. I would try running the game on different systems if available. If crashes continue to happen, it would point to a network or software problem (if both PC's have similar software). If crashes are reduced, it would point to a mix of hardware/software/networking. If they cease completely, its likely hardware/software. I know some of you have done extensive testing, and I know that a few of you have even posted the results of your test in this thread. I would highly recommend anyone experiencing this issue to submit ALL your test parameters, giving as much detail as possible as to the tests themselves. This will help us understand what's working and whats not. | |||
|
#10
|
|||
|
This is mostly anecdotal but before the bounce Friday this was getting worse and worse, after the bounce I have only crashed once while zoning and I have been playing quite a lot & zoning quite a lot doing ports.
__________________
^*^ Aveenia ^*^ - Druid TEAL
^*^ Aveenia Inverse ^*^ - Druid 38 BLUE (RIP) | ||
![]() |
|
|