Un-slippery player movement, netgame testing needed

[Nash]

http://dl.dropbox.com/u/47355875/lol.wad

I'd like to know how this WAD performs in an actual netgame (coop or DM). This is a globally-loaded library; just run it in stock Doom/Doom 2.

Made with ZDoom r3322.

I'd seriously test this myself, but I need someone else on the internet to test it with, and apparently no one was interested when I was on IRC, so I'm posting it here. I'm interested in finding out how does it perform on games played over the internet.

For example, does the player movement lag horribly online?

EDIT: I realize diagonal movements don't work. The file was whipped up real quick in 2 minutes, and I'm too tired to fix it now.

[wildweasel]

Neat. Now if only it were easier to adjust the view and weapon bobbing to be less Doom-like, I'd ask you if I could use the finished version of this in a mod of my own. Unfortunately I've nobody to test it with.

[Nash]

The thing that concerns me is that it uses a call to SetActorVelocity every tick to remove the sliding physics, and I don't know how this would perform over the internet.

[wildweasel]

I suppose I should also ask, then, if it's intentional that the Run key does not work.

[Nash]

As I said, WAD was hastily whipped up in 2 minutes last night because I was only interested in finding out how constant calls to SetActorVelocity would perform over the internet.

The WAD is in no way meant for production.

[edward850]

The thing that concerns me is that it uses a call to SetActorVelocity every tick to remove the sliding physics, and I don't know how this would perform over the internet.

It will appear a little dodgy in any playable games. As the latency with other players increases, the local movement area becomes bigger. This, of course, will never take into account any ACS scripts currently active (and those will always occur in the 'future' anyway). It doesn't matter however, because the moment it becomes annoying, you're already playing in a ludicrously high latency game anyway (ludicrously high for zdoom's primitive netcode, that is), and your position constantly snapping would be the least of your concerns.

[Nash]

Tested this with edward... conclusion: runs like shit on our 300ms-latency game. :D

I won't bother making this work for online play then.

[NeuralStunner]

Pretty sure there was a feature suggestion floating around for customized Player acceleration/decelleration.