SnapRoll

I've just ran into the same problem. My workaround was to wait at the position with "wait for Crew Member 7" until the JBD of Cat3 was down. Then just continue and position yourself behind Cat4. Do not follow the plane directors until your there, they want to crash you into things. Eventually the plane director on Cat4 will guide you in as usual and you can take off in time.

This is an AI. It's The Gauntlet instant action mission of the Siria map, second aircraft (Mig-19). A barrel roll is not even necessary. It is just the initial fast pitch up of the target that causes this.

Settings: Ripple 6, Impact Spacing 300ft Results in 150ft spacing on the ground. Bomb Carpet Length: 231m ~ 760ft, 5x spaces = 152ft each impact_spacing.trk

Aim9x.trk

I've had/still have the same problem. By the looks of it the latest patch introduced this viewAngleVertical which is set to 0.000000 and it seems as long as the default view has this is set to 0, it messes things up. When you enter a certain aircraft the first time since the last update, your default view is zoomed out by too much. All you have to do now is zoom back in to where you want it to be and save the default view with {RAlt + Num0}. After that, all seems to be perfect, like it was before this bug was introduced. I have tested it with the Spit and F-16 so far. All other SnapViews don't seem to be affected by this and do not need to be redone. All I wish now is that it would set this on all other aircraft to the appropriate level automatically so I do not have to set this manually for all.

On the Open Beta Installer download page it says: File name: DCS_World_OpenBeta_web.exe File size: 11.95 Mb MD5: 36cdabc76b458505875ebd33b20b8646 I get: 70FF052CDE38E28B5335F649D0A31AD8 Which is correct?

it is called DCS_updater.exe, not _updater.exe

It has to do with FXAA being a post-process. Google: FXAA screenshot

Did you actually enable the extra axis in vJoyConf? Only the ones with ticks are available in your virtual joystick and visible to Joystick Gremlin. Once you configured your virtual joystick with enough axis and buttons as you need, then you can start Joystick Gremlin and start mapping your physical buttons and axis to the virtual one. But to be honest, I do not see the benefit of combining 3 physical to one virtual device. What are you trying to achieve?

I forgot to mention that you can configure up to 16 vJoy devices. Look at the taps in green at the top. In my example I have 3x vJoy devices. So even with the older version you could configure more than 8 axis. Cheers

You need to configure them in vJoyConf.

Hi f4l0 There is still something wrong with the panel shake. Sometimes I get this extreme output bursts to the JetSeat even tough I have it set to 25% only. I suppose you put some cap in so SSA does not crash any more, but it seems there is a range where there is actual and excessive output. Again I tried to reproduce this, and it seems that it has to do with wind. But it is not consistent. I created a mission with start from ground and some wind. Sometimes PanelShake shows 0.0.0 and sometimes it has crazy numbers like in the attached picture (in this example SSA did not output any panel shake). Is this a DCS bug, did the DCS export variables change or is this some calculation error in SSA? Thanks

Many thanks for the fix!

I also often get these errors with the Bf-109. It is not very consistent, and I cannot reproduce them 100%, but they happen a lot. I am using SSA Beta 2.4.3.0. I am kind of surprised that the stable is at 2.5.0.0. @f4l0, why is that?

It is all described in the manual.... https://ts.thrustmaster.com/download/accessories/pc/mfd/mfd cougar pack_user manual.pdf Page 8/18 and 9/18