Robin885

same issue here. After each flight or even instantly when flying the f4 or f5

You might have seen them perform at different airshows in 2023 and 2024, the Voltige Victor are now proud to present their latest demo at the Château de Versailles. This video aims to be a tribute and salutes the great professionalism of the Voltige Victor, whose presence at airshows from 1990 to 2003 made the public dream. This flight, with never seen views before, will make you feel like you are riding with them through the Split Air team. Suit up and strap in tight, you will need it, and enjoy the show. https://youtu.be/ZkFKkYxqM_E

Full left to full right in a second makes sense, the problem is that at the current rate it does actually take more than a second to go from center to full deflection. I’m not sure, looking at the video you have shared, that the pilot is applying quick elevated pressure to the stick compared to the one I shared. In the video I have linked, the most important part is at 14:32. The pilot brings the wings level after a 90° bank, then pitches up to about 30-40° nose up to finish the demo. Both of those attitude changes are done much faster than currently possible. We have actually tried to make it look as close to this video as possible, but it just won’t work in DCS, the input is too slow. Not by much, but the difference is there, both in roll rate and pitch rate. If I may add also, related to another potential issue, at 07:02, the pilot tests the trim in pitch going full nose down to full nose up ("Le trim testé, réglé" translates to "Trim tested and set"). The rate at which the trim moves the stick is much different than observed in game. It is mostly linear all the way to the edges where it gets apparently slower, which is the inverse to the behavior observed in DCS currently. Hard to prove with just this video, but it does seem like the trim behavior is not correct in-game.

The following video contains footage of the Voltige Victor aerobatics team. I have set the link to redirect to the final part of that show, which is the "dynamic" part. In this part, all the way to the landing pattern, the stick deflections are maximal. We can even see the stick at some points. https://youtu.be/r8o6yDm_Uf4?si=zY_FugknUfZYisfC&t=13m46s In this sequence, the instantaneous roll and pitch rates are much higher than what can be observed in DCS since the last patch, and most importantly, the inputs are instantaneous. I understand this workaround gives the feeling of having the plane working against your input for better accuracy, but they actually make violent inputs impossible in game while they definitely are in real life.

Hi everyone, The Mirage F1 has a bug (imo) with regards to the pitch axis, which has been made even worse in the 2.9.6 update. As we can see in the following video, the pitch trim is non-linear. When in level flight, around the neutral point of the stick, the stabilizers move very slowly. However, when the stick gets closer to its deflection limits, the trim gets super sensitive and the stabilizers move much quicker with the same button press than it would when the stick is centered. In the second part of the video, the trim indicator clearly shows the change in sensitivity as the stick moves to the full aft position. In this test, I am only moving the stick by the use of the trim button when pitching up, no physical stick deflection is made on my side. Note that it can also be observed when pitching down.

Hi, I've recently finished mission 14 which I must say, was one of my favourite missions I have flown in a DCS campaign, head on a swivel for more than an hour. However, I was running on fumes at the end because bucket refused to give me more than 500 pounds at both the ingress and egress. In both cases Olive tanked first and got her 3k, and I was left with only 500 or so. He then retracted the basket, and disapeared from the comms menu.

Hi, I recently bought a new PC and planned to use DCS at it's full potential. However, I find the Extreme Visibility Range setting to just not be enough. Hence I started to look for ways to improve it by fiddling with the lua files. I managed to find the graphics.lua file in the installation and modified the extreme setting from 1.5 to 3. Now 3D models do load further than before however, if they load in the distance, then closer ones will disappear, making it very weird looking. So, I'm asking here is there anyway to properly buff the visibility range in DCS? I noticed a readme file with the graphics.lua explainging that we should now create a autoexec file the the saved games but I couldn't make it work. Here what it looks like with the corresponding setting: distancFactor = { Extreme = 3; distancFactor = { Extreme = 1.5; There it is. As you can see, the top picture does have a further visibility distance but the closer 3D models just don't appear. Does anyone have any idea? Thank you very much.

Yeah I do have this noisy/grainy effect on screen too. I can’t find where it’s coming from, I did a full DCS reinstall but it did not fix the problem.

Hi everyone, I'm not sure if it's a bug or not, I'm posting here to get the opinion of others. Since the 2.9 update came out, I noticed a decrease in the visibility distance of terrain objects (building, houses, trees, vegetations...), and I feel like it is much lower than before. I spent two days fidling with the graphics in-game, trying to make sense of the FAQ regarding the changes in 2.9, but I just can't make the game look like it did before the update. Note that the visibility distance option does work, there is a substancial difference between low and extreme, yet it looks like it was downgraded at all options. Also, I have the impression that a grain effect has also appeared on screen and I feel like it comes from the vegetation's shadows. Once again, I'd like to have the opinion of other players to see if I'm just acting psychotic or if something did changed. I also tried to fiddle with the options but couldn't find a good setting. Thanks and have a lovely afternoon everyone.

Unfortunately, given the fact that I have very little time to access my setup, I wasn’t really wishing to spend more time on it. I understand this is an ED problem, and I will be sure to come back to it once it’s fixed, or when I have the time to troubleshoot it. I love the P-47 and your campaigns are beyond awesome, so be reassured that I will go through it eventually However, as I was looking for people on the forums having the same problems, I came across your "Fortresses over Europe" multiplayer mission. I’ve spent all the rest of my weekend playing on it, it was awesome. Are you planning to make a similar mission when Normandy 2 comes out? Long range escort missions in multiplayer is just one of the things I would love so much.

I tried going as fast as I could, Halstead Red 1 and 2 managed to taxi without trouble, but my element lead wouldn't move as the other P-47s were taking off at the same time. So we had to wait a solid 3-4 minutes before crossing the runway to taxi to the takeoff point. Unfortunately by that time another P-47 flight was waiting aswell and so I was stuck with the same bug, except it was Red 3 that was stuck this time, not Red 1.

Thank you for the quick answer. I will try saying I'm ready earlier, and warm the engine on my way to the runway. A temporary fix is better than no fix

Hi, I've just bought the campaign after the 2.8 update, but on the first flyable mission the AI won't takeoff after taxiing. I'll retry this afternoon, but it looks like the mission is over before even starting without being able to takeoff.

Concur, and it actually does it when the button is bound to a RIO keybind too. As the pilot keybind overrides it, RIO Keybinds do not work as they affect the pilots buttons instead.

Pilot: JTFF | Robin | 354th Rio: JTFF | Kilowatt | VF84 F-14A