Jump to content

Recommended Posts

Posted

All force feedback effects seem to be missing since updating to the latest open beta version. I have tried the default keymapping for FFB on/off (Ralt+Rshift+J), but still nothing - no center force, no FFB trim.



 

 

 

Tested only in multiplayer & cold start so far. Other modules work fine.

 

Can anyone else confirm this ?

PC: MSI X670E Carbon | Ryzen 7700x( o.c. 16x5.5 ) | 64Gb DDR5 5400 RAM (o.c 6000) | Geforce 1080Ti FTW3 | MSFFB2 + DIY rudder pedals | OS: Win10-64bit

DCS modules: Ka-50 (2) | UH-1 | P-51 | FW-190D-9 | MiG-15 | MiG-21 | Mirage 2000C | L-39 | FC3 | F-5E | F-14 | Mi-24P | Mirage F1 

Posted

Yes, l can confirm this. Beta, multiplayer, with update and no other new settings.

Module: viel zu viele...

Warte auf: Fulda Gap, MiG-23, xy (4th. Gen RED) und mehr neue und alte Propeller wie P-38, Corsair, DC-3, Transall, Tucano usw.

 

Projekt: OpenFlightSchool -> Thread

Posted

A buddy of mine who uses the MSFF2 joystick has the same issue since this weeks beta update.

Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit

DCS Panavia Tornado (IDS) really needs to be a thing!

Tornado3 small.jpg

Posted

We're investigating this and FMS issues guys. As soon as I get some info, you will be first to hear.

AMD Ryzen 5900X @ 4.95 Ghz / Asus Crosshair VII X470 / 32 GB DDR4 3600 Mhz Cl16 / Radeon 6800XT / Samsung 960 EVO M.2 SSD / Creative SoundBlaster AE-9 / HP Reverb G2 / VIRPIL T-50CM /
Thrustmaster TPR Pendular Rudder Pedals / Audio Technica ATH-MSR7

Posted

Thanks for the replies

 

 

Hope this bug gets fixed soon as it makes one of my favourite modules unflyable. If that happens well before the next beta update, i hope you offer the fix here on forum - like a file download and manual replacement (if it's possible).

PC: MSI X670E Carbon | Ryzen 7700x( o.c. 16x5.5 ) | 64Gb DDR5 5400 RAM (o.c 6000) | Geforce 1080Ti FTW3 | MSFFB2 + DIY rudder pedals | OS: Win10-64bit

DCS modules: Ka-50 (2) | UH-1 | P-51 | FW-190D-9 | MiG-15 | MiG-21 | Mirage 2000C | L-39 | FC3 | F-5E | F-14 | Mi-24P | Mirage F1 

Posted
We're investigating this and FMS issues guys. As soon as I get some info, you will be first to hear.

 

Thanks for letting us know it's being looked at. A bit more transparency about areas being looked at and possible changes would be amazing. We as users shouldn't be dictating what is and isn't realistic, for the most part we don't have the knowledge and experience. We as users should also not be dictating what is good or not good about the flight model based on how easy or hard it is to fly. A more open discussion and maybe FM roadmap would be fantastic though.

 

Language like " unflyable" and "broken" isn't helpful when Devs are trying to improve something for the sake of their users.

Posted

I'm sorry but I do not have any more information myself.

AMD Ryzen 5900X @ 4.95 Ghz / Asus Crosshair VII X470 / 32 GB DDR4 3600 Mhz Cl16 / Radeon 6800XT / Samsung 960 EVO M.2 SSD / Creative SoundBlaster AE-9 / HP Reverb G2 / VIRPIL T-50CM /
Thrustmaster TPR Pendular Rudder Pedals / Audio Technica ATH-MSR7

Posted

Same here, FFB gone :(

i9 13900K @5.5GHz, Z790 Gigabyte Aorus Master, RTX4090 Waterforce, 64 GB DDR5 @5600, PSVR2, Pico 4 Ultra, HOTAS & Rudder: all Virpil with Rhino FFB base made by VPforce, DCS: all modules

Posted

You start it, select joy, change the axes, and assign the button to enable (Init dinput).

Spring force-100. Damper as you like.

You go into the game and click this button-the program picks up FFB.

Posted

An update was made it seems in the Avionics.dll and broke the MiG21 :(

 

Cannot make the SimFFB work.. I am missing something here .. thx

Fly it like you stole it..

  • Recently Browsing   0 members

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