Jump to content

base and rudder are not centered after spawning


ariyaner

Recommended Posts

hey
i have VPC T-50CM2 and

VPC Rudder Pedals

when i spawn or respawn in single and multiplayer they are flip out to the left

i have to touch both axis to center them

 

unboxing "synch HOTAS" fix it - but is no solution for me

any idea´s

also we have only 4 axis to buttons funktions ? , - why not more

Screen_210512_171103.png

  • Thanks 1
Link to comment
Share on other sites

This is most probably not a VPC issue.

My controls & seat

 

Main controls: , BRD-N v4 Flightstick (Kreml C5 controller), TM Warthog Throttle (Kreml F3 controller), BRD-F2 Restyling Bf-109 Pedals w. damper, TrackIR5, Gametrix KW-908 (integrated into RAV4 seat)

Stick grips:

Thrustmaster Warthog

Thrustmaster Cougar (x2)

Thrustmaster F-16 FLCS

BRD KG13

 

Standby controls:

BRD-M2 Mi-8 Pedals (Ruddermaster controller)

BRD-N v3 Flightstick w. exch. grip upgrade (Kreml C5 controller)

Thrustmaster Cougar Throttle

Pilot seat

 

 

Link to comment
Share on other sites

Don't think this is a Virpil problem . I have all CH hotas and rudder pedals , and have gotten in the habit of cycling all axes after opening DCS , after experiencing similar problems . 

9700k @ stock , Aorus Pro Z390 wifi , 32gb 3200 mhz CL16 , 1tb EVO 970 , MSI RX 6800XT Gaming X TRIO , Seasonic Prime 850w Gold , Coolermaster H500m , Noctua NH-D15S , CH Pro throttle and T50CM2/WarBrD base on Foxxmounts , CH pedals , Reverb G2v2

Link to comment
Share on other sites

  • 2 weeks later...

I recognized the same ‘issue‘ as soon as the sync HOTAS option is activated, wich I prefer to get the button states with my Warthog throttle synced.

Primary for DCS and other flightsims: i9 12900K@default OC on MSI Z790 Tomahawk (MS-7D91) | 64 GB DDR5-5600 | Asus TUF RTX3090 Gaming OC | 1x 38"@3840x1600 | 1x 27"@2560x1440 | Windows10Pro64

Spoiler

Secondary: i7 11700k@5.1GHz on MSI Z590 Gaming Force MB| 64 GB DDR4-3200 | PowerColor RX6900XTU Red Devil | 1x 32"@2560*1440 + 1x24"@1980*1200 | Windows10Pro64

Backup: i7 6700K@4.8GHz | 64 GB DDR4-2400 | PowerColor RX5700XT Red Devil | SSD-500/1000GB | 1x49" 32:9 Asus X49VQ 3840x1080 | Windows10Pro64

Flightsim Input Devices: VPC: ACE2 Rudder / WarBRD Base / T-50CM2 Base with 50mm ext. / Alpha-R, Mongoos T-50CM, WarBRD and VFX Grip / T-50CM3 Throttle | VPC Sharka-50 + #2 Controle Panel | TM Cougar MFD-Frames| Rift S - Secondary: TM HOTAS WARTHOG/Cougar Throttle+Stick, F-18-Grip | TM TPR Rudder | DelanClip/PS3-CAM IR-Tracker

Link to comment
Share on other sites

On 5/23/2021 at 11:14 PM, schmiefel said:

I recognized the same ‘issue‘ as soon as the sync HOTAS option is activated, wich I prefer to get the button states with my Warthog throttle synced.

 

This is the issue, and have been like this for years. The problem is that hall sensors are so precise and don't have much jitter plus a deadzone when centered build into the firmware. Therefor you need to move them before the game will recognise the position. Or turn off ''SYNC'' option.

[sIGPIC][/sIGPIC]

Win10 64, Asus Maximus VIII Formula, i5 6600K, Geforce 980 GTX Ti, 32 GB Ram, Samsung EVO SSD.

Link to comment
Share on other sites

14 minutes ago, Svend_Dellepude said:

 

This is the issue, and have been like this for years. The problem is that hall sensors are so precise and don't have much jitter plus a deadzone when centered build into the firmware. Therefor you need to move them before the game will recognise the position. Or turn off ''SYNC'' option.

That's an interesting and convincing information. The only thing that makes me wonder, why only the hall sensor controlled VPC stick is affected by this and not the VPC ACE rudder as well that also uses hall sensors and is perfectly centered, when entering the jet. Plus doing a cold start this effect doesn't happen for the stick, too, maybe because no AC systems are powered then. Maybe I'll check when a hot start from ramp is done.

Primary for DCS and other flightsims: i9 12900K@default OC on MSI Z790 Tomahawk (MS-7D91) | 64 GB DDR5-5600 | Asus TUF RTX3090 Gaming OC | 1x 38"@3840x1600 | 1x 27"@2560x1440 | Windows10Pro64

Spoiler

Secondary: i7 11700k@5.1GHz on MSI Z590 Gaming Force MB| 64 GB DDR4-3200 | PowerColor RX6900XTU Red Devil | 1x 32"@2560*1440 + 1x24"@1980*1200 | Windows10Pro64

Backup: i7 6700K@4.8GHz | 64 GB DDR4-2400 | PowerColor RX5700XT Red Devil | SSD-500/1000GB | 1x49" 32:9 Asus X49VQ 3840x1080 | Windows10Pro64

Flightsim Input Devices: VPC: ACE2 Rudder / WarBRD Base / T-50CM2 Base with 50mm ext. / Alpha-R, Mongoos T-50CM, WarBRD and VFX Grip / T-50CM3 Throttle | VPC Sharka-50 + #2 Controle Panel | TM Cougar MFD-Frames| Rift S - Secondary: TM HOTAS WARTHOG/Cougar Throttle+Stick, F-18-Grip | TM TPR Rudder | DelanClip/PS3-CAM IR-Tracker

Link to comment
Share on other sites

Good question. Maybe there is something with the way the axis are programmed in DCS ( not in options but within the programme) or maybe you moved the rudders during loading. Don't actually remember if the latter is possible, I turned SYNC off many years ago after discovering this issue.

[sIGPIC][/sIGPIC]

Win10 64, Asus Maximus VIII Formula, i5 6600K, Geforce 980 GTX Ti, 32 GB Ram, Samsung EVO SSD.

Link to comment
Share on other sites

Another thing that came to my mind is, when doing the tutorial missions starting in the air the sim is on active pause at first and then this 'issue' doesn't happen as well when active pause is cancelled. So there seem to be some more logic in play besides the sync HOTAS stuff...

Primary for DCS and other flightsims: i9 12900K@default OC on MSI Z790 Tomahawk (MS-7D91) | 64 GB DDR5-5600 | Asus TUF RTX3090 Gaming OC | 1x 38"@3840x1600 | 1x 27"@2560x1440 | Windows10Pro64

Spoiler

Secondary: i7 11700k@5.1GHz on MSI Z590 Gaming Force MB| 64 GB DDR4-3200 | PowerColor RX6900XTU Red Devil | 1x 32"@2560*1440 + 1x24"@1980*1200 | Windows10Pro64

Backup: i7 6700K@4.8GHz | 64 GB DDR4-2400 | PowerColor RX5700XT Red Devil | SSD-500/1000GB | 1x49" 32:9 Asus X49VQ 3840x1080 | Windows10Pro64

Flightsim Input Devices: VPC: ACE2 Rudder / WarBRD Base / T-50CM2 Base with 50mm ext. / Alpha-R, Mongoos T-50CM, WarBRD and VFX Grip / T-50CM3 Throttle | VPC Sharka-50 + #2 Controle Panel | TM Cougar MFD-Frames| Rift S - Secondary: TM HOTAS WARTHOG/Cougar Throttle+Stick, F-18-Grip | TM TPR Rudder | DelanClip/PS3-CAM IR-Tracker

Link to comment
Share on other sites

7 hours ago, Svend_Dellepude said:

 I turned SYNC off many years ago after discovering this issue.

 

Same here (only not so many years ago). Turning SYNC off solves the problem of axis being in a certain position on respawn. It's not VPC related, had a TM Cougar and now a TM Warthog (with VPC base), both had the problem (my Cougar had a hall sensor mod) and the issue is still there when when SYNC is ticked. It's not a VPC issue but a DCS one.

 

Win11 Pro 64-bit, Ryzen 5800X3D, Corsair H115i, Gigabyte X570S UD, EVGA 3080Ti XC3 Ultra 12GB, 64 GB DDR4 G.Skill 3600. Monitors: LG 27GL850-B27 2560x1440 + Samsung SyncMaster 2443 1920x1200, HOTAS: Warthog with Virpil WarBRD base, MFG Crosswind combat pedals, TrackIR4, Rift-S.

Personal Wish List: A6 Intruder, Vietnam theater, decent ATC module, better VR performance!

Link to comment
Share on other sites

Something comes to mind. @schmiefel Do you have any other controllers assigned to the axis in question? Like button boxes or other peripherals that doesn't have any physical axis? By default DCS assigns axis of any controller to pitch and roll, even if the controller doesn't have any. 

[sIGPIC][/sIGPIC]

Win10 64, Asus Maximus VIII Formula, i5 6600K, Geforce 980 GTX Ti, 32 GB Ram, Samsung EVO SSD.

Link to comment
Share on other sites

5 minutes ago, Svend_Dellepude said:

Something comes to mind. @schmiefel Do you have any other controllers assigned to the axis in question? Like button boxes or other peripherals that doesn't have any physical axis? By default DCS assigns axis of any controller to pitch and roll, even if the controller doesn't have any. 

I will check this, but as I tend to clean all default controller settings when configuring a plane, I doubt that there should be some ‘faulty‘ default assignments been left.

Primary for DCS and other flightsims: i9 12900K@default OC on MSI Z790 Tomahawk (MS-7D91) | 64 GB DDR5-5600 | Asus TUF RTX3090 Gaming OC | 1x 38"@3840x1600 | 1x 27"@2560x1440 | Windows10Pro64

Spoiler

Secondary: i7 11700k@5.1GHz on MSI Z590 Gaming Force MB| 64 GB DDR4-3200 | PowerColor RX6900XTU Red Devil | 1x 32"@2560*1440 + 1x24"@1980*1200 | Windows10Pro64

Backup: i7 6700K@4.8GHz | 64 GB DDR4-2400 | PowerColor RX5700XT Red Devil | SSD-500/1000GB | 1x49" 32:9 Asus X49VQ 3840x1080 | Windows10Pro64

Flightsim Input Devices: VPC: ACE2 Rudder / WarBRD Base / T-50CM2 Base with 50mm ext. / Alpha-R, Mongoos T-50CM, WarBRD and VFX Grip / T-50CM3 Throttle | VPC Sharka-50 + #2 Controle Panel | TM Cougar MFD-Frames| Rift S - Secondary: TM HOTAS WARTHOG/Cougar Throttle+Stick, F-18-Grip | TM TPR Rudder | DelanClip/PS3-CAM IR-Tracker

Link to comment
Share on other sites

Yesterday i discovered the following:

 

When both of my Thrustmaster MFDs are connected i have the problem with the not synced axis (only in F-18, P-51 and Mig-21 and only with the „Hotas Sync“ activated). As soon as i disconnect one MFD, the problem is gone...

 

Really weird behaviour, maybe i do some more testing tonight.

  • Thanks 1
Link to comment
Share on other sites

  • 2 weeks later...
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...