Quote: "Also, correct me if I'm wrong, I thought his plug-in didn't have any commands that use keyboard or joystick input from within the DLL."
You are correct. No his plug in does not. My inputs come from the DGK, dbScanCode(), dbUpKey() and the like.
I am sure that some where the memory leak is something I put in the program. I have started to use Class, they are really good at telling me when I made a mistake (program crash).
This is something more subtle, something is overriding the EzRoate Euros. This is not the first time this has happened. The first symptom occurs when I press the keys or do changes to models orientation. Something causes the erous to return a error the gives me the location of 1#EEEE as the X and Y position of my model, but only when I use the keyboard or joystick as a input device. The code is still working of passively for other objects (like missiles following their target). These are free of the keyboard/joystick code. My program has grown to larger size and the code is not all that easy just to drop in and have a people peck over it.
Currently I dropped the Ez Roate code off of the player model, brought back a generic simple code and the model stays where it is suppose to be, just not as smoothly. I might try another degree of separation, make adjustments on where the object will be then let the other part that still works with the Ez Rotate process the players model.
My question has anybody else who has used EzRotate ran into a similar situation. EzRotate has made my life a lot easier.
There are many answers but just one question" ~ Jerilith the Mad