Sorry if this has been discussed before. I'm trying to streamline my WASD unit movement. Does anyone know if Key Pressed still generates network traffic for every key every player presses, even when you define a certain player and key? I was just thinking if that's the case, it would be better to have one key press trigger which determines the player and returns the key pressed. Thoughts? Thanks anyway.
if the trigger exists, all presses and releases from all players are traffic, thats what the note says in editor.
If that is the case, then the only activity conjoured by extra triggers is local, though you may be better off using one trigger regardless.
So in summary, if you use the trigger once, you may as well use it a hundred times, their not going to duplicate the same client server data for sake of two triggers, just reuse that data.
The reason for the net-traffic is that all triggers are run server side. That is why using the Data Editor is so important because that is the best way to control the client side actions. Unfortunately, key events are limited to triggers and hotkeys right now. After I finish my current project I am thinking of exploring solutions for this within the data editor.
triggers can not possibly be run server side?
they would need to be able to provide atleast 1 GHz peak per player, which would be about 600 THz ...
Regardless, wherever the processing is done required data is only going to be sent once, so again, net traffic can't be increased by calling the event multiple times.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Sorry if this has been discussed before. I'm trying to streamline my WASD unit movement. Does anyone know if Key Pressed still generates network traffic for every key every player presses, even when you define a certain player and key? I was just thinking if that's the case, it would be better to have one key press trigger which determines the player and returns the key pressed. Thoughts? Thanks anyway.
if the trigger exists, all presses and releases from all players are traffic, thats what the note says in editor. If that is the case, then the only activity conjoured by extra triggers is local, though you may be better off using one trigger regardless.
So in summary, if you use the trigger once, you may as well use it a hundred times, their not going to duplicate the same client server data for sake of two triggers, just reuse that data.
The reason for the net-traffic is that all triggers are run server side. That is why using the Data Editor is so important because that is the best way to control the client side actions. Unfortunately, key events are limited to triggers and hotkeys right now. After I finish my current project I am thinking of exploring solutions for this within the data editor.
triggers can not possibly be run server side? they would need to be able to provide atleast 1 GHz peak per player, which would be about 600 THz ...
Regardless, wherever the processing is done required data is only going to be sent once, so again, net traffic can't be increased by calling the event multiple times.