CTD: Targetting Self

A forum for reporting bugs NOT related to custom plugins.

Moderator: MacroQuest Developers

User avatar
Rage
orc pawn
orc pawn
Posts: 17
Joined: Sat Oct 19, 2002 2:15 am
Location: San Diego, CA USA

CTD: Targetting Self

Post by Rage » Thu Dec 04, 2003 12:55 am

Fresh compile, Tuesday December 02 2003 afternoon build

I was playing EQ with my paladin with MQ2 just fine.. decided to log on my druid as well (both characters under EQW)... been playing normally with lots of video lag (normal for me 2boxing)... except:

As I was nearing my hunting spot (Paludal), my client crashed with a window that read some sort of .c failure. I shrugged it off until it happened 3 times in a row, whenever I tried to log in my paladin.

I then ran only one EQW with MQ2, and I was playing fine until I hit F1, which crashed me with the same .c error.

Lax
We're not worthy!
We're not worthy!
Posts: 3524
Joined: Thu Oct 17, 2002 1:01 pm
Location: ISBoxer
Contact:

Post by Lax » Thu Dec 04, 2003 1:17 am

afternoon build? i did one early morning and one evening, so which one is afternoon? ;) just give the number. 1203a or 1203?
Lax Lacks
Master of MQ2 Disaster
Purveyor of premium, EULA-safe MMORPG Multiboxing Software
* Multiboxing with ISBoxer: Quick Start Video
* EQPlayNice, WinEQ 2.0

Jabber
a lesser mummy
a lesser mummy
Posts: 32
Joined: Sat Aug 23, 2003 2:45 pm

CTD

Post by Jabber » Thu Dec 04, 2003 11:18 am

I was getting the same CTD on the 1203 version when i targeted myself, but the 1203a one seems to be fine.

Jab.

User avatar
Rage
orc pawn
orc pawn
Posts: 17
Joined: Sat Oct 19, 2002 2:15 am
Location: San Diego, CA USA

Post by Rage » Thu Dec 04, 2003 2:02 pm

1203 non-A I believe

you update too often :p