Leprechaun Causing Crash

T_Immortalus · 03-24-2012 12:26 AM

I went through some AE farming session tonight, and every run I would crash right after entering.

I first thought it was just the usual "incarnate leading the team, team status error, random lost packet and resulting slow crash".

Then, I had a run where I didn't crash. Something was different.
I noticed the leader didn't have the leprechaun out.

So, I told the leader to put out the leprechaun. I didn't crash that whole run.

Ok, so the leprechaun was not entirely the issue.

Next run, I told the leader to immediately summon the leprechaun, first thing upon entering, like he/she had done every run that I crashed.
Sure enough, I crashed immediately when the second group was aggroed, as expected.

The mission was 511104 in the usual Crown of Glory arc, "defeat Hector's generals", huge cave map.

It was most definitely caused by summoning the leprechaun before anything else happened in the mission, but I am unsure how specifically.

newchemicals · 03-24-2012 03:38 AM

You have some rotten luck with crashes T_I

I'm glad I didn't fork over 800pp for that expensive boutique pet. It actually has another bug according to another person who bought the thing.

H: Blaster 50, Defender 50, Tank 50, Scrapper 50, Controller 50, PB 50, WS 50
V: Brute 50, Corruptor 50, MM 50, Dominator 50, Stalker 50, AW 50, AS 50
Top 4: Controller, Brute, Scrapper, Corruptor
Bottom 4: (Peacebringer) way below everything else, Mastermind, Dominator, Blaster
CoH in WQHD

T_Immortalus · 03-24-2012 04:08 AM

Quote:

Originally Posted by newchemicals

You have some rotten luck with crashes T_I

It's all those lost packets on my already not so fast internet.

Plus, I think I'm special.

LOL

Although, it is a good thing that I am in the situation I am in. It brings out these problems that would otherwise go unnoticed until they become even larger and problematic for everyone someday.
You don't test anything under "ideal conditions" after all; you test near the point of failure to ensure that "ideal conditions" will never get close to seeing problems.

Edit:
I wish they would hire me to test for them.

I like finding and figuring out these issues even if they hamper play.

newchemicals · 03-24-2012 12:35 PM

Maybe you should post CoH helper of your machine. So we can help fix your issues and/or know what parts to avoid.

H: Blaster 50, Defender 50, Tank 50, Scrapper 50, Controller 50, PB 50, WS 50
V: Brute 50, Corruptor 50, MM 50, Dominator 50, Stalker 50, AW 50, AS 50
Top 4: Controller, Brute, Scrapper, Corruptor
Bottom 4: (Peacebringer) way below everything else, Mastermind, Dominator, Blaster
CoH in WQHD

T_Immortalus · 03-26-2012 10:28 PM

If it was a problem with my computer then it would not be limited to such specific circumstances.

The only times I ever crash are when I am teaming, or have teamed(since team status still tracks me as "on team" after leaving the team, probably a bug with the mechanic to allow returning to a team after DC on task forces, especially with LFG), with level shifted incarnates, at least when they lead the team or somebody summons the leprechaun immediately on entering a mission before anything else is done(after I have entered as well, since summoning him before I enter a mission has not been tested yet except for the fact that I do not crash after coming back from a crash with him still out).

Anyway, they're very specific times that have very specific circumstances.

Edit:
My computer also never crashes, just the game.
I do have the occasional "driver has stopped working and reset" with CoH, but it actually doesn't crash the game or the computer and is so quick that I wouldn't notice if I looked away for a second. I surmise this is the OpenGL time-out error as it says "nvogl32.dll"(assuming "Nvidia OpenGL 32-bit" library, which could be an issue because my operating system is 64-bit but it works fine) as the file associated with the error, but it's so rare that I don't remember exactly what it says.

Edit 2:
Actually, the LFG function is probably why team status broke. Leagues allow you to come back from a DC and still be on the league, so long as you started some league event, but you don't come back to the same team. Perhaps, the game can't reconcile "what team you were on" with "the new team you are on", or can't reconcile the fact that your team can change within the league.
I know every time you enter a trial you have to reorganize the league window. Perhaps, this sets up a lot of people for a crash because they are "not on the team they were on record as being on".
That makes sense.