FlyPT Mover

I have a huge request to the creator of FlyPTmover , could he please look into the issue of limiting platform movements when receiving high pitch and roll data from DCS if we use "roll speed" and "pitch speed" to control motion platform movements.
I looked through some ".mover" configuration files I found on the internet but most are related to flying in MSFS 2020 where this situation does not occur, while I only fly in DCS which has its own specificity of situations occurring in it and generated values of "roll speed" and "pitch speed" . In addition, I recently spoke with a MotionXP 6DOF user who confirmed that at the time of shooting down when the aircraft rapidly changes its position in space he has to turn off the movement of his 6DOF to avoid violent movements. Attempts to limit with CROP, MAXCROP, MINCROP , SPIKE filters do not yield good results.
Yesterday, looking for a solution, I came across a plugin for asseto corsa that simply disables data transfer after exceeding a certain value ( in this case G force) https://www.overtake.gg/downloads/flypt-source-changer.62133/
The question is whether it is possible to add such a filter in which by selecting a value you could turn off telemetry processing until the value returns to normal?
It could also be that I just don't know how to use filters , that's why I attach my .mover profile and recorded fragment of flight with high values of "roll speed" and "pitch speed" maybe someone smarter than me will find some time to watch it and possibly correct my obvious mistakes .
And one auxiliary question, what could be the reason for the fact that with the set limit of 4 degrees of arm movement in reality the arms rotate in the range of about 45 degrees ? it would seem that after entering 2DOF geometry according to reality the range of motion should be mapped 1:1 ?

Is there any way to make EA WRC work while we wait for the new release? thanks

What I really need is help on adding a rotating actuator to my existing 2dof setup in Flyptmover to have as yaw/traction loss?
Do I just add another Rig alongside my 2dof one? If I select 3dof with rotating actuator I get


My rig does notlook anything like this?? I have two motors on the front and one on the back for yaw.

Do i just add a single rotating actuator to exising setup


If so how do you configure it for Yaw???

Very confusing??

Please try this: (I could not test...)

In the folder \Documents\My Games\WRC\telemetry\udp
Create a file named FlyPTMover353.json anfd put the following text inside:

Code:

{
    "versions":
    {
        "schema": 1,
        "data": 3
    },
    "id": "FlyPTMover",
    "header":
    {
        "channels": []
    },
    "packets": [
        {
            "id": "session_update",
            "channels": [
                "game_total_time",
                "vehicle_position_x",
                "vehicle_position_x",
                "vehicle_position_x",
                "vehicle_position_x",
                "vehicle_position_y",
                "vehicle_position_z",
                "vehicle_speed",
                "vehicle_velocity_x",
                "vehicle_velocity_y",
                "vehicle_velocity_z",
                "vehicle_left_direction_x",
                "vehicle_left_direction_y",
                "vehicle_left_direction_z",              
                "vehicle_forward_direction_x",
                "vehicle_forward_direction_y",
                "vehicle_forward_direction_z",              
                "vehicle_hub_position_bl",
                "vehicle_hub_position_br",
                "vehicle_hub_position_fl",
                "vehicle_hub_position_fr",              
                "vehicle_hub_velocity_bl",
                "vehicle_hub_velocity_br",
                "vehicle_hub_velocity_fl",
                "vehicle_hub_velocity_fr",              
                "vehicle_cp_forward_speed_bl",
                "vehicle_cp_forward_speed_br",
                "vehicle_cp_forward_speed_fl",
                "vehicle_cp_forward_speed_fr",
                "vehicle_throttle",
                "vehicle_steering",
                "vehicle_brake",
                "vehicle_clutch",
                "vehicle_gear_index",
                "vehicle_acceleration_x",
                "vehicle_acceleration_y",
                "vehicle_acceleration_z",
                "vehicle_engine_rpm_current",
                "vehicle_brake_temperature_bl",
                "vehicle_brake_temperature_bl",
                "vehicle_brake_temperature_bl",
                "vehicle_brake_temperature_bl",
                "vehicle_brake_temperature_bl",
                "vehicle_brake_temperature_bl",
                "vehicle_brake_temperature_bl",
                "vehicle_brake_temperature_bl",
                "vehicle_brake_temperature_bl",
                "vehicle_brake_temperature_bl",
                "vehicle_brake_temperature_bl",
                "vehicle_brake_temperature_bl",
                "vehicle_brake_temperature_bl",
                "vehicle_brake_temperature_bl",
                "vehicle_brake_temperature_br",
                "vehicle_brake_temperature_fl",
                "vehicle_brake_temperature_fr",
                "vehicle_brake_temperature_fr",
                "vehicle_brake_temperature_fr",
                "vehicle_brake_temperature_fr",
                "vehicle_brake_temperature_fr",
                "vehicle_brake_temperature_fr",
                "vehicle_brake_temperature_fr",
                "vehicle_brake_temperature_fr",
            ]
        }
    ]
}

Now go to the folder \Documents\My Games\WRC\telemetry
and open the file Config.json
Add the following to the file:

Code:

                   
            {
                "structure": "FlyPTMover353",
                "packet": "session_update",
                "ip": "127.0.0.1",
                "port": 20777,
                "frequencyHz": -1,
                "bEnabled": true
            },

Attention!!!, you are adding this inside the packets, it will be something like this:

Code:

        "packets": [
            {
                "structure": "FlyPTMover353",
                "packet": "session_update",
                "ip": "127.0.0.1",
                "port": 20777,
                "frequencyHz": -1,
                "bEnabled": true
            },
            {
                "structure": "wrc",
                "packet": "session_update",
                "ip": "127.0.0.1",
                "port": 20777,
                "frequencyHz": -1,
                "bEnabled": false
            },
            {
                "structure": "wrc_experimental",
                "packet": "session_start",
                "ip": "127.0.0.1",
                "port": 20778,
                "frequencyHz": 0,
                "bEnabled": false

Try and give me some feedback.

Can you post a picture of the rig?
One of the solutions is to add a direct just for traction. If you are using VR, you loose compensation by using directs