[SOLVED] Sim-eth-es architecture for an attack system

[asser_fahrenholz]

@pspeed

The problem with your current approach of a separate rotate() and thrust() is that you are now tripling the number of RPC calls you are making per frame. If you are worried about only sending things when they change then you can always have a dirty flag… but as it stands if you are moving the mouse (or using the joystick) and thrusting at the same time then you are sending three RPC calls 60 times a second.

So, to keep it in a single RPC call, I would use the keyboard input to set flags as to what is pressed, and use those flags in the update-method.

[pspeed]

@asser_fahrenholz

So, to keep it in a single RPC call, I would use the keyboard input to set flags as to what is pressed, and use those flags in the update-method.

…which is just like what the original sim-eth-es code did, no?

[asser_fahrenholz]

@pspeed

…which is just like what the original sim-eth-es code did, no?

Absolutely. Break it and fix it right? Good to know I end up the same place as you did. Of course, with your guidance that is to be expected

[asser_fahrenholz]

To round this off, I ended up with having an ES based movement system (no shipdrivers/controldrivers) with no calculations on the clientside, integrated to the Body-publishing system you have set up:) Thanks for the walkthrough @pspeed!

May not have achieved much in the game, but it was fun messing with. Now, onwards to new features.

[pspeed]

Glad you made progress.