EnumVisibleObjects problem

[skra]

i'm only startig it when i'm ingame

You need to ensure the device is the correct one

can you give me a hint on how to do that?

[adaephon]

Aha, you are using WPF, are you?
In that case.. Doesn't WPF also use DirectX? Which means that WPF will also have its own EndScene that it's calling. That pretty much means that you might be calling the functions from the WPF EndScene call.
You need to ensure the device is the correct one.

Not necessarily, on Vista or 7, WPF uses Direct3D9Ex and creates an Ex device which I believe has separate EndScene method call, thus hooking would only hook WoW's device. Not 100% sure though.

[MaiN]

i'm only startig it when i'm ingame

can you give me a hint on how to do that?

Either you extract the pointer WPF uses, or you find the pointer WoW uses.

Not necessarily, on Vista or 7, WPF uses Direct3D9Ex and creates an Ex device which I believe has separate EndScene method call, thus hooking would only hook WoW's device. Not 100% sure though.

That is correct, but it needs to be fixed anyway for XP.

[TOM_RUS]

Replace

IntPtr endSceneAddr = DirectX.GetEndScenePointer();

with

IntPtr endSceneAddr = m.GetObjectVtableFunction(m.Read<IntPtr>(0x00C776B8, 0x397C), 42);

than add to ObjectManager class:

        private static ulong ActivePlayer
        {
            get { return GetActivePlayerDelegate(); }
        }

        public static bool IsInWorld
        {
            get { return ActivePlayer != 0; }
        }

and replace:

ObjectManager.Pulse();

with

if(ObjectManager.IsInWorld)
    ObjectManager.Pulse();

and report back if it still crashing at 0x0047B95F.

[MaiN]

Replace
IntPtr endSceneAddr = DirectX.GetEndScenePointer();
with
IntPtr endSceneAddr = m.GetObjectVtableFunction(m.Read<IntPtr>(0x00C776B8, 0x397C), 42);

Those will be the exact same addresses.
Anyways, as TOM_RUS suggested, the device pointer is at [[0xC776B8] + 0x397C] - you can check the 'this' ptr against that to be sure it's WoW's device.

[Robske]

Aha, you are using WPF, are you?
In that case.. Doesn't WPF also use DirectX? Which means that WPF will also have its own EndScene that it's calling. That pretty much means that you might be calling the functions from the WPF EndScene call.
You need to ensure the device is the correct one.

Same device iirc

[!@^^@!]

How should he even be able to hook the WPF endscene? because he shouldn't be injecting a WPF window directly, but rather inject a lib and let that create instances of objectmanager and hooking endscene then create a thread to launch the injected WPF window in

[MaiN]

Same device iirc

Hmm? I don't think so. :O

How should he even be able to hook the WPF endscene? because he shouldn't be injecting a WPF window directly, but rather inject a lib and let that create instances of objectmanager and hooking endscene then create a thread to launch the injected WPF window in

WPF is still running in the same application domain as WoW's device is. That means they will both call the same EndScene function, with different 'this' parameters.

[!@^^@!]

Ah okay i wasn't aware of that... but i wonder if that might be what causes my WPF window to crash wow when i resize it...

[MaiN]

Ah okay i wasn't aware of that... but i wonder if that might be what causes my WPF window to crash wow when i resize it...

Then Robske might be right that it's the same device.

[Robske]

Ah okay i wasn't aware of that... but i wonder if that might be what causes my WPF window to crash wow when i resize it...

That is not caused by WPF. In all likelyhood you aren't managing your resources properly. Look into OnLostDevice & OnResetDevice.

[skra]

and report back if it still crashing at 0x0047B95F.

well it isnt crashing anymore ^^ ActivePlayer is 0 =/

[Apoc]

As MaiN somewhat pointed out, certain elements of WPF will use DirectX directly. So you'll need to filter out the calls. You'll have EndScene being called from 2 different devices, but using the same function. (That's how vfuncs work!) You'll need to grab WoW's EndScene pointer first (easiest way is to check the current thread ID against WoW's main thread. Your GUI shouldn't be running off WoW's main thread anyway). If it's WoW's device, do all your bot logic. Otherwise, just let it pass through, as it's WPF rendering its controls.

[skra]

thanks apoc i'll try that now

[skra]

i'ts probably a stupid question but how do i determine which one the mainthread is?