Anyone else having problems with exodus causing you to crash and die? Has happened 3 of 3 times this week. I see the loading to zone_x but then I crash. When I logg in I am dead (

Just to say it now - I've been at low health (5%) and hight health (over 70%) so I can't say it's because I died from spell or such. And.... once I see that zoning message I would at least expect to me pop at SS.

Happened to me the other day. LONG LONG loading screen (5 mins) upon which I am disconnected and come back dead. The rest of the party lived and were moved to succor point.

Used it half dozen times after this and it worked NP.

-Cass

Used last night twice in DoN missions with no problems.

I've had an interesting experience - when I cast Succor, a few times, my group has been succor'd out, but I was not... ? It happened once in PoStorms, and I forget the other place it happened.

About 50% of the time recently using Exodus Im crashing (usual 5 minutes zone and then disconnect. Relog to be naked at bind).

I figured it was a problem at my end...

I dont have that noticed with exodus, but with just crossing zone lines.

Namely in tactics, when running to the zone in the pit, i zone with 5% to 50% hp left, get "you enter plane of tranquility", just to zone really long and end up at bind spot.

@Mari: *big grin* you are lucky that it only happened to you twice - evacs have a chance to leave group members behind, and most often it is the evacer! (heard they reduced the probability, did that happen or was it wishful thinking?)

Delete the zone files that you are crashing in and patch.

The reason you crash is because you die while zoning, and EQ gets confused and doesn't know where to send you, so just throws its hands up in the air and says screw it after thinking about it for 5-10 min.

Do you have spyware blaster installed on your machine?

That doesn't matter.

I've had this happen a couple times to me recently to, at different %'s of health.
I agree with Aluaeia, and figured EQ just gets confused and doesnt know where to send ya and just crashes. I've died many times while zoning after an exodus and never crashed, but recently I have had 3 incidents(2 of which I was above 50% health) myself...it's really disappointing to see LOADING, PLEASE WAIT...You are entering *zone you were in*<ZONE in were you><ZONE in were you>, just to crash and come back at bind (

Happend to me yesterday for first time while i was in sebilis low on health. I zoned at 40 % crashed and still was dead when i came back. Exodus is giving me a hard time lately, most of the time you still die when you hit exodus at 10 % and when you are at bindpoint exodus is down. This is a lame ass bug that needs to be fixed.

Happened again Tuesday. I was at 24% health so I couldn't have died by the mob. This is getting very old.

I do have a spyware program but it doesn't do anything but scan when I tell it to. Now Norton anti-virus could cause a crash. But why would I be dead?

In order for me to die, the exodus would have to not actually be moveing me from the zone even though the 'loading' message is on my screen and it's frozen.

This has happened to me three times already. Twice I was in fairly low health when I hit Exodus and crashed but I still couldn't find a logical reason why I died. Yesterday, however, I was in a full group in MPG and we had a bad pull. Two party members died and I hit Exodus. My system froze up and crashed. When I logged back into game, I was dead at my bind point as were the other 3 members who were still alive when I evac'd. The real crapper was that I had over 7,000 hitpoints when I evac'd and got the Denari creates a mystic portal message. I should not have died, period. This stupid bug created an annoying 30 minute corpse run and caused my group to break up. At this point Exodus is virtually useless. I sure hope it gets fixed soon.

The reason you crash is because you die while zoning, and EQ gets confused and doesn't know where to send you, so just throws its hands up in the air and says screw it after thinking about it for 5-10 min.



Yes, that's the answer. You hit exodus, mob kills you before you actually zone, server can't figure out whether you're going to succor point or bind & you crash.

The problem of being left behind, or others being left behind, from exodus or succor & even port spells is getting rather irritating though.

The problem of being left behind, or others being left behind, from exodus or succor & even port spells is getting rather irritating though.

There's an innate failure chance for all evac type spells (egress, succor, exodus, wind of the xxx, etc), This was originally implemented to offset the fast casting time (relatively) on the evac spells as opposed to normal ports. Similarly, port spells dont' leave people behind, ever. (remember, even though we dont get a port version of wind of the north/south or Succor, they still count as evacs for purposes of failure, some people may remember when you could only cast wind of the north/south from inside dungeons... port to DL, run to KC and wind to EJ to run to sebilis :x )

We had this in MPG the other night. We evaced, two of our party got out, the rest went linkdead while zoning and despite the fact they were not very low on health when we saw there "soandso creates a mystic portal" messages, when they came back from LD they were dead at the camp.

It appears as if a game save is not made at the time you cast exodus. If you crash while zoning after casting exodus you return to the point of last game save usually in the situation you were trying to exodus from originally. This has not always been the case but I have noticed this occuring alot recently.

I have had this problem as well. I would say it crashes because i die while zoning but usually that means I land at bind point and the exodus hits so I always evac in my bind zone. Maybe they tried to fix that and now you just crash instead. /shrug

[QUOTE=Sianni]Yes, that's the answer. You hit exodus, mob kills you before you actually zone, server can't figure out whether you're going to succor point or bind & you crash.

QUOTE]

The reason I don't think this is the problem (or only problem) is I have hit Exodus when I am over 50% health. So why would I die? This was not in a OoW zone where I can die in one hit. It was in DoN on a simple solo collect in Lavaspinners. A named Drake spawned just when I collected my last item and I didn't feel like messing with it so I Exodus.

And on another similar time in Lavaspinners I decided to use egress (because I can't trust Exodus) and everything works fine. Did this 2 times with no problem. All were on the same named.

If I was at real low health I can see maybe where I died to one last hit even after I see the loading zone message. But that is not the case. And I feel once that message comes up I should be ok. I remember using Exodus in LDoN with like 8 plus mobs hitting me and it worked just fine even at low health /shrug

Yeah, I don't think it's crashing because you die, it seems to me, that it's just a zone-crash bug that happens when you hit exodus, and it never actually zones you. You get the loading screen on the client, but in actuality, your client crashes and the server does not send you to the safe spot, but instead leaves you at the spot where you had aggro, LD. And if you already have aggro, you get mobs beating on you until you die or win, and can log back on.

Its getting worse, it does not only affect the caster. Today i was 2 boxing a bit and had to exodus cause a small train and my pc with warrior on crashed and died, this time i zoned fine. Lame ass bug

Yes, that's the answer. You hit exodus, mob kills you before you actually zone, server can't figure out whether you're going to succor point or bind & you crash.
If this were the case, where the Client thinks you Exodus OK, but the Server says you didn't, why is Exodus spent? It seems that Exodus either goes off and you zone, or it doesn't and you die.

In all cases when this happens to me, I find my corpse back with the MoB - indicating that the Server never thought Exodus went off, but why is the ability spent then?

haven't been on druid for about 2 weeks, logged in today took out a named in MPG but an add killed some of the grp off..hit exodus and boom same bull**** as before. This is really irritating it is definately a bug and needs to get fixed.

This is now beyond a joke......

Better off buying insta gate pots it seems. Insta gate at 10% or less and live. Exodus at anywhere from 20% - 80% and die...

I am sure this is a genuine bug . I find it hard to believe that it is due to death whilst exodussing.

Of course I have had the old , well known problem of folk being left behind on succors/exodus , but I have only noticed this new problem since DoN was released.

At least 4 times I have cast exodus and seen the message that a portal was made , got the zoning message to imply that exodus was successful , then crashed while zoning to discover that I had died. On a couple of occasions I was not being hit and was on full health ( just evacced because of a bad pull where we had no CC).

It has also happened twice to a group member that I apparently evacced safely. Once was an SK who got the zoning screen to imply successful exodus ,but LDed on zoning and his corpse was left at the fight spot ; However , his fully buffed and eqipped pet popped at his bind point in PoTranq . When he logged back in after reloading , the pet latched back onto him, lol.

I am sure this is a genuine bug . I find it hard to believe that it is due to death whilst exodussing.

Of course I have had the old , well known problem of folk being left behind on succors/exodus , but I have only noticed this new problem since DoN was released.

At least 4 times I have cast exodus and seen the message that a portal was made , got the zoning message to imply that exodus was successful , then crashed while zoning to discover that I had died. On a couple of occasions I was not being hit and was on full health ( just evacced because of a bad pull where we had no CC).

It has also happened twice to a group member that I apparently evacced safely. Once was an SK who got the zoning screen to imply successful exodus ,but LDed on zoning and his corpse was left at the fight spot ; However , his fully buffed and eqipped pet popped at his bind point in PoTranq . When he logged back in after reloading , the pet latched back onto him, lol.

Two things you brought up here I want to say sparked my brain...

1) It does seem to be that since DoN came out, this has been happening over 95% of the time when you cast Exodus.

2) Is RSS I had a SK that also died as you mentioned after evac and came back after LD with pet fully buffed and equipped.

The other night we were in the instanced delveb zone, had a pull go wrong and exodus was used. The shammy and the bst both went LD and died while the others evacced fine. The bst had his loaded pet pop up with him in pok after a few minutes when he logged back in. Im not sure if it made a difference....but the shammy and bst were on dial up and the rest of the group had faster conections..........



Sliggoth, druid/ tradeskiller of Lanys-seventh

Interestingly the SK in my incident was in RSS too ( he was not on dial up , neither am , btw )

Anyway, I have reported it as bug , and will repeatedly do so each time it happens from now on : )

I've had Exodus now for a couple years and from reading these posts I have been extrememly lucky. I've never, and group memebers have never crashed or been left behind. If I had to guess I would say I've used Exodus over a 100 times. Could the server have anything to do with it?

Again... Exodus go Crash

About 12:25 AM on 4-5-05
in RSS - King Fight this time
5 person Group in raid
- I was 100% health
- #2 100%
- #3 78%
- #4 100%
- #5 100%
We All Crashed!!!!

takes about 5 min to crash
lost about 50 min recovery

Most people in raid in an Exodus group also went LD/crash !!!!

Bristlebane Server

Nothing worse than this.

I was getting beat down and tried to Exodus out. I hit the hot key a couple times and nothing happened - I'm dead. I reapear at my bind point - and immediately - my exodus goes off. Screen freezes up -yup - I'm dead again.

Shouting for a rezz in PoT is fairly embarrasing! :)

I bug reported it but not really expecting much.

So apparently warping to safe spot has a higher survivability rate than exodus. That's really just sad.

Another tale of wow i'm afraid:mad:

I was just in POV when i was getting beat upon bad my mobs. I was in a group of 3 and pressed exodus with 3% health remaining....

Other two peeps zoned out fine.... like the other posters i waited about 5 mins and found myself at the server select screen(

I am now a naked drood.......

FYI this is the first time this has happened to me..... but is sure annoying anyhow.

Hope they fix it soon....

This might be even worse...

Parked with a bunch of guildies at the RCoD zoneline, trying to form a raid to take down the warrior epic mob. While raid is forming, someone pulls 3 mobs, and no one is prepared. Healers and tanks go down.

I am...no lie...2 feet from the zone to Bloodfields. I have no aggro, and I'm on a mount. I am invis'd but it's dropping.

I turn, go right past the mobs, at 100% health, ether skin up (wizzie damage absorbing rune), and get the "entering the Bloodfields" message. Takes a while to zone, but always does in OoW...and bam! I'm naked and dead at the 5 stones. I never hit exodus. I was AT the zoneline.

I can't say how thoroughly pissed I was...raid buffed and runed they probably tore through 7k hps or so WHILE I ZONED???

I feel with ya, the other day i was in akheva for a small epic fight and decided to pop some of the traps. So with one of the biggest trains ever behind me i decided to just outrun them for a few seconds and egress. By the time Egress was allready finished casting the first mobs reached the melee range but i got the zoning message. Then my PC freezed and eq locked me for FULL 20 minuts at the loading/LD screen. Absolutaly nothing worked and i dont reset my computer. So after waiting LONG 20 minuts it kicked me to server screen and i could log back. That pissed me off, not only couldnt i help with the epic fight, i was 10 minuts late for raid missing MGBS and **** too.