I modified a little and deleted a lot of variables etc. because i have only interest in a fps mode.
I build 4 Triggers for every direction one.
The Main Problem is, which map is not important, that the last command for the new camera position is instant so i have everytime a non smooth movement. When i use the another camera command over x seconds with speed... its very smooth but in the movement time i lose mouse control ...
I looked at your Triggers and have a few question.
Only 2 Triggersevents for the Button (up&down) is because of the network traffic is clear but why do you use so many variables (boolsche operators)?
Is it good to make only ONE Big Trigger with a lot of commands and a refresh in 0.0 Realtime or is it better to make 4 Triggers (maximal 2 at the same time) and only with 1/3 or 1/4 size? In the case that only 1 button is pushed the "perfomance" will be better or?
Do you know a way to measure the efficience of a trigger method like a runtest or something?
I modified a little and deleted a lot of variables etc. because i have only interest in a fps mode.
I build 4 Triggers for every direction one.
The Main Problem is, which map is not important, that the last command for the new camera position is instant so i have everytime a non smooth movement. When i use the another camera command over x seconds with speed... its very smooth but in the movement time i lose mouse control ...
I looked at your Triggers and have a few question.
Only 2 Triggersevents for the Button (up&down) is because of the network traffic is clear but why do you use so many variables (boolsche operators)?
Is it good to make only ONE Big Trigger with a lot of commands and a refresh in 0.0 Realtime or is it better to make 4 Triggers (maximal 2 at the same time) and only with 1/3 or 1/4 size? In the case that only 1 button is pushed the "perfomance" will be better or?
Do you know a way to measure the efficience of a trigger method like a runtest or something?