Nash: Not having to package an entire new executable and pk3s seems to be a rather huge reason why not! D:
edward850 wrote:While there is indeed no performance issues, you have some major issues with trying to control player velocity with movement. Namely that you are. This is decidedly incompatible with network prediction...
Was there supposed to be something after the words "you are"? Or do you mean "Namely you are trying to control..."?
If so,just off the top of my head there are the main mechanics that I'm using:
1. using DECORATE (A_ChangeVelocity, A_ScaleVelocity) to thrust a player
2. using ACS (ThrustThing(Z)) to thrust a player
3. using ACS to change the player's speed property
4. setting the player's movement speed in the DECORATE playerpawn
Which of these are affected by the network prediction?
(Also, would changing player pitch/angle be affected by network prediction as well?)
EDIT: Saw the vid you PM'd me. Playing HD for that long on short notice without consulting the manual or the quickstart guide first... I am impressed. D:
(things you guys apparently had to play without: reloading, shotgun chambering (altfire), fire select on assault rifles, sprinting)
Maybe it's because I'm sneaking in peeks at the vid while at work, but it's a little hard to tell which movement problems are the prediction problems and which are you guys trying to get used to the movement changes. How much did disabling prediction help?