LeCuvier Posted December 17, 2019 Posted December 17, 2019 (edited) I have noticed repeatedly that there was something strange: 1. after cold start she would not start rolling 2. after touchdown (in a mission starting in the air) she would veer to the right despite tailwheel locked and full left pedals Today again I experienced a difficult landing and could hardly avoid getting off the runway to the right . So I decided to get to the bottom of this. I did a landing instant action and when I saw she wanted to turn right I tipped just slightly on the right toebrake. And that fixed it for this landing. Next I did a cold-start instant action and when I opened the throttle she did not move, even when I increased the rev rate to 2000 RPM. Only after I stepped on the right toebrake very gently, the lady started rolling. So what I observe is that the right wheelbrake is blocked at mission start, and needs to be "unblocked" by stepping shortly on the right toebrake. I would think that this is a bug. It certainly hasn't been like this from the beginning. It is easy to work around if you know it, but for a rookie pilot it adds to the difficulty of landing the Dora where no additional difficulty is needed. And it also makes the start of taxying awkward. Track attached. PS: Track is from OB Edit: I could not reproduce the problem in the stable version, and when I re-started OB I could not reproduce it there. So it's a bit elusive; but I can confirm that I've seen it several times in the recent past.FW-190D9 Blocked Right Brake 20121217.trk Edited December 17, 2019 by LeCuvier LeCuvier Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5
Art-J Posted December 17, 2019 Posted December 17, 2019 Do you have "Synchronize controls with HOTAS" option turned on in your game? I've never encountered such a problem with Dora in my DCS, but saw similar things when that synchronization was turned off - although I admit that affected more analog axes at once then. i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.
grafspee Posted December 18, 2019 Posted December 18, 2019 Just tap brakes then so they will reset position. System specs: I7 14700KF, Gigabyte Z790 Aorus Elite, 64GB DDR4 3600MHz, Gigabyte RTX 4090,Win 11, 48" OLED LG TV + 42" LG LED monitor
LeCuvier Posted December 18, 2019 Author Posted December 18, 2019 Do you have "Synchronize controls with HOTAS" option turned on in your game? . Yes, always ON LeCuvier Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5
LeCuvier Posted December 18, 2019 Author Posted December 18, 2019 Just tap brakes then so they will reset position. That's my work-around as I said. But it's inconsistent behaviour and not realistic. It should be fixed. LeCuvier Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5
LeCuvier Posted December 18, 2019 Author Posted December 18, 2019 (edited) Clarification: a strange story This is a strange story, and if you don't have the patience for detail, skip it! 1. I have bound a switch on my throttle to the switch command "Wheelbrake both" for use as a parking brake during the warm-up period. 2. For normal braking during taxi, takeoff and landing I use the wheelbrake axis commands. 3. The switch is mostly in the ON position at mission start because I forget to set it OFF. But the option ""Synchronize controls with HOTAS at mission start" does not work with the FW-190 most of the time, and so most of the time it has no effect. 4. The problem occurred when, exceptionally, the synch at mission start had worked (or I had flipped the brake switch to ON after mission start???). The brake then is ON until you override it with the brake axis. 5. If you have not used the brake axis then inconsistent logic between left and right brake kicks in. That logic is: If you have brake axis commands bound to pedals then the switch command "Wheel brakes both" acts only on the right hand brake. This is why the FW-190 veered right after touchdown. 6. The FW-190A8 has exactly the same brake logic. Conclusion: I don't know whether the inconsistent logic between left and right brake should be considered as a bug. After all, the developer may say that you should not bind both axes and switch for brakes. So I don't want to make a fuss about it. I know now how to handle it, and I will certainly keep the dual binding for the Anton, because it has extremely long warm-up time and I don't want to get cramps in my feet from pushing the brake pedals for 10 minutes. I'm posting this detail because I don't want people to chase the wrong problem. Edited December 18, 2019 by LeCuvier LeCuvier Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5
Art-J Posted December 18, 2019 Posted December 18, 2019 Thanks, I've never used "wheel brakes both" command, so I didn't know it might cause similar issue. That's a very valuable observation. In my opinion it should be classified as a bug indeed. i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.
LeCuvier Posted December 26, 2019 Author Posted December 26, 2019 Problem seems to be fixed I tried this today in OB, both for the Dora and the Anton, and I could not reproduce the problem. I suppose the developers fixed it. LeCuvier Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5
Recommended Posts