Treasure Hunting Crashes

[JoshuaLee]

I was going to put this in the technical support thread but I wanted to put it somewhere where it would be viewed by more. I think since the Razor update there has been a series of crashes when you are treasure hunting, espcially levels 3+. I have talked to several people who say the same.

It's like you either crash when the monsters spawn or in midfight even when everything seems to be fine. And the puzzling thing about it is that anyone in that vicinity crashes as well. Me and a friend were doing these tmaps and coincidently crashed at the same exact time. Now we crash at the same time everytime and it makes no sense at all.

Just putting it out there so when you do a treasure map be prepared. It's been going on for a couple nights and I don't know how to fix it or avoid it.

[poogoblin]

This happened to me on a lvl 3 as well, fyi. Luckily I had everything provoked onto something when it did this...I couldn't make heads or tales why it did this, it wasn't from a newly spawned creature or a large influx of creatures on my screen at the time.

[Mikel123]

Happened to me as well, a bunch of times. Level 5's for me, I thought it had something to do with the Balrons or something!

[JoshuaLee]

It seems to be fine with level ones and level twos, I did several of each and it never happened. It must only be Lvl 3+

[Lor]

I also have crashed/died a couple times recently while doing treasure maps.

[platypus]

Haven't done a TMap recently, but I've been crashing in Aceopolis frequently on random accounts. Sometimes its the account that I'm playing, sometimes its an account I'm AFK on. It has happened 10+ times per day, and only seems to occur when >4 players or mobs are onscreen. This has only been happening for the last 3 days or so. Not sure if this is related, but I've also had massive resyncing issues in the past few days (like having to resync every 30 seconds or so during PvP). It has to be a Razor issue because I haven't switched clients or anything.

[tekai]

Aceopolis crash caused the death of poor Olmanriver a few days ago. was quite the loss.

Then I crashed in hythloth balrons earlier today.

These seem to be area specific?

[GomerPyle]

I have been crashing once every couple hours with t2a balrons when I go there. Seemed to happen the instant they died. Other than that, I've crashed a couple times at wbb randomly. Also I don't think I ever crashed prior to the update around Sept 11th or 13th if that has anything to do with it.

[Triumph]

when i say 'claim' at the stable where i keep my dragons i often crash, doesnt surprise me though with 55 monsters instantly appaering on the screen.

[dog1706]

happened to me as well on a 3

Thankfully I got the kill shot on the dread spider right before I crashed.

Tmap spot 188

crashed a tiny bit NE of there fighting the dread.



Also I've been getting a lil lag when dropping an item. Drag just fine, there is some delay for the item to appear. Just lost an MIB to it. Tried closing backpack and bank and reopening and the sh*t is gone.
Waste of a good mib.

[Boone]

Yeah, I've been crashing repeatedly at Ophidian Lair. Not a good place to crash.

[Mikel123]

I just crashed on a level 4 treasure map. This is about 7 crashes in my last 6 maps.

[Derrick]

The only thing I can think of that may be causing this that was in this patch is the creature hues changes, however this doesn't explain ophids who have no hue.

I'm aware that some hues do cause some clients to crash sometimes, usually this is due to a client side issue though and a reinstall usually fixes it. This hue thing has been very rare.

There have been a couple other threads about crashes and I've asked that if possible someone log packets in Razor when they are anticipating a crash, like at ophids if it happens every time. I'd like to know the last packet sent to the client before the crash which should narrow things down a bit.

If anyone successfully packet logs a crash, please PM me the last few packets from the log (which can be opened in notepad)

Packet logging in Razor can be enabled in the More Options Tab, lower right hand corner.

It's not recommended to leave packet logging on for very long, as the files can grow enormous.

Thanks!