Jump to content

Recommended Posts

Posted (edited)

Hi guys,

 

So after finding some time to finally try update 1.2.3 I've noticed that my TM cuts out intermittently. DCS:BS2 does not recognise any input (usually when I'm very low level). See the trk file provided. At the end before I crash you'll see the WH stops responding.

 

I've provided a TARGET device analyser file that shows input right throughout that flight. I then spent 20 minutes in teh control panel joystick properties watching the input of my WH as I moved it around. No problems there.

 

I've been playing BMS, CloD, RoF and hence felt the itch for DCS come again (it goes in circles) and there has been no problems in any of those games with the WH cutting out.

 

I've recreated my TARGET script and used the provided stock BS script and every time it's the same result - DCS loses input.

 

This has only started happening with the 1.2.3 update. That is the only thing that has changed.

 

Has anyone else experienced control loss with the 1.2.3 update? And if it's at all possible can ED have a look into this. If not I'll just wait for future updates, plenty of other sims to keep me going but it is still disappointing.

control_loss.trk

Edited by WynnTTr
Posted

WynnTTr,

 

I've been switching from BMS to DCS and back over the last little while and occasionally some of the functions drop off in DCS when I switch from BMS to DCS. All I do is unplug the throttle/joystick, restart the computer, then plug the throttle and joystick back in. It seems to reset the TM:WH and all seems fine. Once I had to re-install the TM:WH driver after a switch.

 

I do not use TARGET with DCS, only for BMS. Hope that helps.

[sIGPIC][/sIGPIC]

i7 10700K OC 5.1GHZ / 500GB SSD & 1TB M:2 & 4TB HDD / MSI Gaming MB / GTX 1080 / 32GB RAM / Win 10 / TrackIR 4 Pro / CH Pedals / TM Warthog

  • Recently Browsing   0 members

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