Spongey Movement?

[Calimaw]

When Im using the Sandbox editor for 2.0 and I attempt to move (holding rightclick, + W A S D) I will move in the correct direction, and back again in a rapid fashion, similar to being on an angry bungee cord.

[Niosop]

Happens to a lot of us. Rebooting your computer seems to fix it

[Calimaw]

Will do so (I haven't rebooted in a long while).

 

Thanks!

[TylerH]

I found out that Leadwerks does a few things that, overtime, kill your computer and all Leadwerks apps (until you restart):

 

- Something is wrong with the OpenAL implementation, it eats up all the buffers and for some reason won't close them all when the application is terminated, so over time, no other audio applications can use them (if they use OPenAL), and your speakers will start to play load-pitched static, and the sounds from Leadwerks that were cached (usually from the editor I hear the underwater loop and the barrel impact sounds).

 

- Overtime, the amount of RAM Leadwerks is using increases, and even after ending the processes or closing the programs, that RAM usage is still there.

 

- Overtime, the Application Speed degrades (THIS IS WHAT CAUSES THE JERKY MOVEMENT). Anything in any Leadwerks application that is modified by AppSpeed, will have that jerky movement, rotation, interpolation, etc. I can't say what causes this, but I can assume that the timer Leadwerks is using internally degrades after a while for whatever reason, and you start to get ridiculous AppSpeed returns: It will fluctuate, for me, anywhere between -5 and 500000, until I restart.

[Josh]

I am not aware of any memory leaks. If you find one, please let me know.

[DaDonik]

I just tried out what happens when i run my wip-game over 2 hours. Using the task manager to check the RAM usage, there was no change at all.

The game uses entity callbacks and messages all the time.

 

Can't say anything about behaviour of AppSpeed, as i use my own timer

[TylerH]

Josh:

 

Can you compile a version of the editor using a Debug build? May make it easy to find any leaks if there are in fact any.

 

I just couldn't think of any other reason for the exponential decay of the AppSpeed over time (I am talking days to weeks of having the editor application open).