Valk

On a lot of parking spots the aircrew doesn't respond. I was unable to rearm and to place/remove wheel chocks. Strange thing is that it depends on the parking spot. The eastern spots are okay, but parking spots on the western part of the airbase pose problem. Tried it with slot 6, 8, 30, 44. Those definitely pose problems. Parking spots 100 and up are okay.

I don’t want to be disrespectful towards T-Day but there is a post where he apparently was happy with the at that moment current G-onset, but a year later the G-onset appeared to be too slow after all as it was improved (OB changelog 17/03/22). https://www.digitalcombatsimulator.com/en/news/changelog/openbeta/2.7.11.21408.1/#:~:text=DCS%3A F-16C,engine setting%2C etc. I’m no 4000 hours Viper pilot and I don’t know how it feels (which should be irrelevant anyway because data should be the driving factor) , but I see what I see in those demo pilot cockpit video’s, and that’s an instantaneous stop of the roll. No inertia, no wobbles. And that’s not what I expierence anymore since the FM and FLCS update. I’m just hoping it won’t take another year before ED realizes that the roll inertia needs improving, because we know and deep down ED knows it as well that it isn’t correct now. It's just a question of not admitting it, IMO.

Yeah, there is still roll inertia.

Yes, I've tried the M2k and you are right. It behaves more like the pre-FM updatet Viper. Also, thanks for uploading your track files. Hope ED can sort it out, now they see that there are multiple people experiencing the same problem

Here are my track files. I think the FSSB stick definitetly has something to do with. I've tried doing 1/4 rolls with my old thrustmaster warthog base and the roll inertia feels less pronounced. But like SC Panda said in the other post, the Mirage 2000 feels more like what Viper used to be before the FM update (see third track file). Thank you for looking in to this and I hope the team can sort it out. Viper quarter rolls with FSSB.trk Viper quarter rolls with TM warthog base.trk Mirage 2K quarter rolls with FSSB.trk

I appreciate the quick response. When I release the pressure on my FSSB stick the roll doesn't immediately stop. It's not that the roll drags on forever, but It defenitly doesn't behave like it used to before the FM update and it doesn't correspond to what I see in those cockpit videos. If I want to do 1/4 rolls I now have to counter them with opposite pressure, what to my knownledge shouldn't be necessary with a FSS stick.

There is an update in that other post. Now the current "as is" FM behaviour is considered correct although it's quite the opposite of what was initially considered correct. I hope ED sheds some light on how they came to that new conclusion, because it baffles me.

I don't post often, but I felt that I should, because I really can't understand. This completly contradicts what you (ED) stated in 2019 when you confirmed that there was no roll inertia (what IMO is confirmed with cockpit footage of demo pilots). Now after the FM update there is plenty of roll inertia. And now you say that the current behaviour "feels" correct. What is that based on because you always say you work with data and not on how it "feels"? Like I said, there are plenty of cockpit videos that shows there is no roll inertia when doing 1/4 rolls. (This topic is also being discussed in another post with links to multiple cockpit videos of demo pilots doing 1/4 rolls). Can you please shed some light on what made the team now say it is correct as is? I appreciate ED's striving for constant improvements in getting the FM as realistic as possible, but to me it feels you are cutting a corner here. (FWIW, I'm also a FSSB user.)

Couldn't have written it any better. I'm also a FSSB R3L user and this is my experience as well (although the stick shouldn't matter that much). I know, it's still WIP, but for me personally, this issue really more than offsets the recent improvements.

Thank you! In the mean time I've been experimenting a bit myself. I created these code lines for 3-way switches. But I haven't been able to code something for the ECM # buttons that works with numpads that don't have fixed on and off positions, because they register only momentary inputs. The first press on the numpad key toggles the ECM # button on, but the second press doesn't toggle it off. I 'v'e used your code and changed the value_up to 1.0, because otherwise it automatically toggles back to off when releasing the numpad key. Probably it's something pretty easy, but I'm a total noob at coding Most important thing for me was the 3-way switches, so thanks for putting me in the right direction.

I would appreciate it a lot if you could.

Resetting the database partially solved it. I get 'salute' to work, but 'request refueling' doesn't work: recipient texaco is currently not available. If I go through the comms menu (F-keys) and request refuelling manually and later on give the 'ready pre-contact' the voice comman, that gets understood and recognized.

VSPX is unchecked. For most programs I make screenshots of my settings, so if a problem pops up I can easily check if something has changed. So I've definitely already checked. But in this case no settings have changed. It's all still the same, obviously except for the new functionality with the dustom path (which I've set according to my situation: OB -standalone).

No, it's not that either. Voice attack understands what I'm saying. My pronunciation isn't getting butchered by the speech recognition engine:) And it happens to commands that have been working for ages.

It's not that. It doesn't recognize 'salute', 'request rearming' and a lot of other commands that used to work perfectly prior to the update with the real ATC plugin.