MacroQuest64

Non CTD when doing manually, but did CTD repeatedly working on the Faction script for SH, or even when running my pathtest.mac that I was using to verify that the pathing was right. (Alternately, and this may be due to my mapfilter settings is CTD on /doortarget.)

I have not done a HUGE amount of testing, but enough that I know it has something to do with the /face command.

If I did something like /face loc 0,0 or /face loc 100,100 there was no problem. As soon as I tried to face a loc like /face loc 0,1500 it would face the loc and look up! Stranger still is that it would look up at different angles depending on the number of the loc.

If you want me to test this further, and post a log, I will. Just tell me how to make a small macro that will log /echo and I'll make it echo each loc I have it face and manually /echo approximately how far up or down it looks.

/face nolook

?

Is there anything to look at in a LOC? No Z axis.

Could it be that's not a loc? Or maybe you have the numbers reversed?

Nope, not the numbers. I have them written down, the ones I was testing for and rechecked and tried it and even moved around and tried, always same thing, looked up on the loc, but again only numbers like xyz, 1400. Never bothered checking each ton, but you get the idea.

Either way if it's causing a CTD it's a problem. Can you post a dump, along with specific "stand here and type this" type instructions to reproduce it?

edit: Sorry, I missed that this was caused only in a macro. maybe pare down the macro as much as you can to yield the crashing part and post that as well?

Acutally, I think I found the CTD was related to /doortarget, but I need to check some more things first.

aChallenged1 wrote:Acutally, I think I found the CTD was related to /doortarget, but I need to check some more things first.

I'm guessing you may have tried just typing /doortarget in game and finding this. If so, it probably CTD'd you for the same reason as /itemtarget does (if you have certain stuff in your hud)

/doortarget works for me. I use it to find the PoK portals all the time (/doortarget PoK, /face)

/doortarget alone hasn't ctd'd me either. Haven't used it in a macro.

Mimatas wrote:/doortarget works for me. I use it to find the PoK portals all the time (/doortarget PoK, /face)

/doortarget alone hasn't ctd'd me either. Haven't used it in a macro.

Say you have a mq2hud with something in it. I think it was MaxRangeTo, so I read somwehere, would cause CTD because doors / items don't really have a melee range.

Hmm.. didn't read that.. but I believe it. I've got HUD turned off for now.

Well that sucks. I'll have to play around with my current HUD and see what I can find. It very well could be related to that, the CTD issue. Thanks for pointing it out.

just hit F11 or w/e the ping meter button is, while you run whatever it is your having troubles with

Ok, if I use /face nolook loc 100,1500 it will face properly. Infact with nolook in place it did quite well.

Now, I turned off the HUD (F11) as suggested, and that did not fix the problem when I run the macro with just the pathing run, nor with the full macro. As soon as I start it and it starts the movments to get it where it needs to go, it looks up, and when it gets to the door, which it cannot open since it is out of targeting area on screen, it CTDs. I do not know if the advpath.inc has a call for /doortarget, if it does, then that is why I crash.

I have yet to try unloading mq2map and seeing if that clears it up.

Just updating before we take off for the rest of the day and part of tomorrow. Hope someone can shed light on this.