CGWorld_C::Intersect

[ramey]

Hello. I'm curious if anyone would mind giving me a push in the right direction.

I'm looking for suitable flags for CGWorld_C::Intersect.

I have tried all of the flags WoW uses, however I have the feeling that the DWORD passed is used as bit flags, but only guessing because of the weird values passed to CGWorld_C::Intersect.

I'm pretty tired now, so I'm going to head to bed. Thanks in advance.

[barthen]

I think you're looking for this:

enum CGWorldFrame::HIT_FILTER {
  HIT_TEST_NOTHING = 0x0,
  HIT_TEST_GROUND = 0x1,
  HIT_TEST_OBJECTS = 0x2,
  HIT_TEST_UNITS = 0x4,
  HIT_TEST_PLAYERS = 0x8,
  HIT_TEST_ME = 0x10,
  HIT_TEST_PARTY = 0x10000,
  HIT_TEST_FRIENDS = 0x20000,
  HIT_TEST_ENEMIES = 0x40000,
  HIT_TEST_LIVE = 0x100000,
  HIT_TEST_DEAD = 0x200000,
  HIT_TEST_ALL_OBJS_EXCEPT_ME = 0xe,
  HIT_TEST_ALL_OBJS = 0x1e,
  HIT_TEST_ALL_EXCEPT_ME = 0xf,
  HIT_TEST_ALL = 0x1f,
};

And the return value should be one of this:

enum CGWorldFrame::HIT_TYPE {
  HIT_NONE = 0x0,
  HIT_GROUND = 0x1,
  HIT_OBJECT = 0x2,
};

I hope that's what you need

[Apoc]

CGWorld_C::Intersect is just a proxy call for TraceLine

Also, try 0x00100171 for the flags.

       /// <summary>
        /// pOptional is apparently another WOWPOS pointer. But is always passed as 0.
        /// (WOWPOS according to WoWX, 0 according to... everyone else...)
        /// </summary>
        /// <param name="pEnd">The end Point.</param>
        /// <param name="pStart">The start Point.</param>
        /// <param name="pResult">The resulting intersection point.</param>
        /// <param name="pDistance">The distance to the intersection, if any. Pass a ref to a float == 1f</param>
        /// <param name="dwFlag">TraceLine flags.</param>
        /// <param name="pOptional">Pass 0!</param>
        /// <returns></returns>
        [UnmanagedFunctionPointer(CallingConvention.Cdecl)]
        private delegate CGWorldFrameHitType TraceLine(
            ref Point pEnd, ref Point pStart, ref Point pResult, ref float pDistance, uint dwFlag, uint pOptional);

Keep in mind; you should never call TraceLine without increasing the Z val of you/your target by at least Me.Scale or Me.Target.Scale. Otherwise you'll intersect the ground where you stand. (Not the desired outcome)

[ramey]

I think you're looking for this:

enum CGWorldFrame::HIT_FILTER {
  HIT_TEST_NOTHING = 0x0,
  HIT_TEST_GROUND = 0x1,
  HIT_TEST_OBJECTS = 0x2,
  HIT_TEST_UNITS = 0x4,
  HIT_TEST_PLAYERS = 0x8,
  HIT_TEST_ME = 0x10,
  HIT_TEST_PARTY = 0x10000,
  HIT_TEST_FRIENDS = 0x20000,
  HIT_TEST_ENEMIES = 0x40000,
  HIT_TEST_LIVE = 0x100000,
  HIT_TEST_DEAD = 0x200000,
  HIT_TEST_ALL_OBJS_EXCEPT_ME = 0xe,
  HIT_TEST_ALL_OBJS = 0x1e,
  HIT_TEST_ALL_EXCEPT_ME = 0xf,
  HIT_TEST_ALL = 0x1f,
};

And the return value should be one of this:

enum CGWorldFrame::HIT_TYPE {
  HIT_NONE = 0x0,
  HIT_GROUND = 0x1,
  HIT_OBJECT = 0x2,
};

I hope that's what you need

Thanks a lot for this. Where did you go about finding it if you don't mind? Thanks again!

CGWorld_C::Intersect is just a proxy call for TraceLine

Also, try 0x00100171 for the flags.

       /// <summary>
        /// pOptional is apparently another WOWPOS pointer. But is always passed as 0.
        /// (WOWPOS according to WoWX, 0 according to... everyone else...)
        /// </summary>
        /// <param name="pEnd">The end Point.</param>
        /// <param name="pStart">The start Point.</param>
        /// <param name="pResult">The resulting intersection point.</param>
        /// <param name="pDistance">The distance to the intersection, if any. Pass a ref to a float == 1f</param>
        /// <param name="dwFlag">TraceLine flags.</param>
        /// <param name="pOptional">Pass 0!</param>
        /// <returns></returns>
        [UnmanagedFunctionPointer(CallingConvention.Cdecl)]
        private delegate CGWorldFrameHitType TraceLine(
            ref Point pEnd, ref Point pStart, ref Point pResult, ref float pDistance, uint dwFlag, uint pOptional);

Keep in mind; you should never call TraceLine without increasing the Z val of you/your target by at least Me.Scale or Me.Target.Scale. Otherwise you'll intersect the ground where you stand. (Not the desired outcome)

Thanks for the scale info. Are spells checked from "eye position", because thats what it would be if scale was added?

Thank you both again. Will rep you both.

[Cypher]

CGWorld_C::Intersect is just a proxy call for TraceLine

Also, try 0x00100171 for the flags.

       /// <summary>
        /// pOptional is apparently another WOWPOS pointer. But is always passed as 0.
        /// (WOWPOS according to WoWX, 0 according to... everyone else...)
        /// </summary>
        /// <param name="pEnd">The end Point.</param>
        /// <param name="pStart">The start Point.</param>
        /// <param name="pResult">The resulting intersection point.</param>
        /// <param name="pDistance">The distance to the intersection, if any. Pass a ref to a float == 1f</param>
        /// <param name="dwFlag">TraceLine flags.</param>
        /// <param name="pOptional">Pass 0!</param>
        /// <returns></returns>
        [UnmanagedFunctionPointer(CallingConvention.Cdecl)]
        private delegate CGWorldFrameHitType TraceLine(
            ref Point pEnd, ref Point pStart, ref Point pResult, ref float pDistance, uint dwFlag, uint pOptional);

Keep in mind; you should never call TraceLine without increasing the Z val of you/your target by at least Me.Scale or Me.Target.Scale. Otherwise you'll intersect the ground where you stand. (Not the desired outcome)

Pretty sure you should be using Me.Height not Me.Scale. Me.Height is your actual collision height, the one that's used in collision checks, using Me.Scale (assuming that you havn't named Me.Height incorrectly) would cause incorrect results in certain situations.

[zzgw]

Man, how did you manage to RE it so far to understand the flags? Or is it mostly from the old exe with debugging symbols?

[ramey]

Man, how did you manage to RE it so far to understand the flags? Or is it mostly from the old exe with debugging symbols?

Pretty doubtful. My money is on Mangos or alike

[Cypher]

Pretty doubtful. My money is on Mangos or alike

My money is on the alpha client.

[ramey]

My money is on the alpha client.

Now that I think about it you're probably right, but the flags weren't what I was looking for.

EDIT: Just realised that Apoc had mentioned what I actually needed, but I found it on my own. Thanks Apoc, too bad I didn't pay any attention.

[amadmonk]

Apoc knows of what he speaks. I had some real problems with Traceline recently, and 0x100171 is the magic number (although that wasn't my problem).

[Cypher]

Apoc knows of what he speaks. I had some real problems with Traceline recently, and 0x100171 is the magic number (although that wasn't my problem).

Apoc fails.

He had problems with it too originally and I told him to use that flag because he was using a completely different one. He then claimed that the flag I sent him didn't work. A week or so later I asked him if he resolved it and he said "yeah I got it working with this flag '0x100171'". Which was the same ****ing flag I sent him to begin with. >_>

Then naturally he said it wasn't, so I dug up chat logs and I was right.

In short: Apoc fails at calling Intersect.

[ggg898]

I had problems with traceline too, never got it to work before so I forgot about it, so many thanks for the info and flag values in this thread (though I cant say I understand how 0x100171 is constructed from the bit values in the previous posts...)

One question though, is there an easy way to find the height of the characters Cypher is mentioning in the previous post (Me.Height) or or do you have to parse m2 model or something?

[Cypher]

I had problems with traceline too, never got it to work before so I forgot about it, so many thanks for the info and flag values in this thread (though I cant say I understand how 0x100171 is constructed from the bit values in the previous posts...)

One question though, is there an easy way to find the height of the characters Cypher is mentioning in the previous post (Me.Height) or or do you have to parse m2 model or something?

It's stored in the player structure. (Obviously it has to be stored somewhere easy to get to as it's used in collision tests and what-not)

It's not all that difficult to find if you realize that your collision height changes when certain things happen.

I'll leave it as an exercise to you as to work out when these changes occur, and how to reproduce them to track down the offset.

[ggg898]

Fair enough, thanks.

[Apoc]

Pretty sure you should be using Me.Height not Me.Scale. Me.Height is your actual collision height, the one that's used in collision checks, using Me.Scale (assuming that you havn't named Me.Height incorrectly) would cause incorrect results in certain situations.

I typically use Me.Scale as it gives enough of a 'boost' to the Z axis to give good LoS results. However, Me.Height would probably be more effective (and less buggy at that). You could even just hard-code it to be +1.3-2.0f to the Z and still be pretty much fine.