SnapRoll

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

I don't use VR, but Alt-Enter does also not work for me any longer. For WWII, because of spotting, I ran DCS in a 1440p window and switched to 4k borderless window via Alt-Enter. Now it seems DCS does not catch Alt-Enter at all.

Right click on the icon in the task bar --> "Open Settings". You only need to start the first SimShaker Window the rest starts automatically once you start DCS.

It could be the firmware, it happend to me many times. It looks dead (no green LED), but once reloaded, all is fine again. Try this: https://dreamsimteam.blogspot.com/p/jetseat-firmware-reload-procedure.html

Hey Meatshield Thanks a lot for this plugin. It finally makes these switches usable for me. I was really hoping the 2022 firmware will bring such an improvement, but unfortunately it didn't. @VirPil, if you are listening, please, add this functionality to the firmware. It really makes no sense for a 4-way config to loose the signal if you keep pressing to one side and can't keep the finger 100% steady in the middle of this direction. SnapRoll

By the way, have you deleted your fxo and metashaders directories after the last NVIDIA driver update? I've seen some strange anomalies in the past when I've forgotten to do that.

Try: Depth of Field: OFF Motion Blur: OFF Anisotropic Filtering: 16x Visib Range: Extreme Maybe: SSLR: OFF SSAO: OFF Use MSAA or SSAA, probably not both (I have not tested that)

I’ve seen this strange behavior and it had to do with how long the “press” was happening. Back then I was using Target, the default pulse of a button press was too short to register some actions in the F/A-18 as example. It would register in the setup menu but not while flying. I had to specifically extend the time of the pulse or change it to a “press”. In your case it might be that your buttons have deteriorated to a point where there is no constant contact while you press your button. If it just gives a short pulse or flickers, it might well be that you see this register in the setup menu, but in game it would not do anything. Check with a joystick tester if your button presses are constant or if it is just a pulse or flickers.

Hi folks Wags latest ATC video just remined me of this thread. I personally just got accustomed to ignoring the ball when getting close. Pieterras excellent manual states this: Fly the ball all the way to touchdown. Landing should be a surprise. This just seems impossible with the current implementation.

After losing lock in TWS when the radar gimbal is nearing its maximum travel limit, radar elevation is limited thereafter. In my track I switch between RWS and TWS after losing lock. In RWS I can still move the radar elevation to the very top, in TWS the upper quarter of the range is no more accessible. TWS_elevation_limited.trk

Have you tried what I described in the third post? After mission start --> no reflections from behind the seat (correct) Remove Pilot Seat --> no reflections from behind the seat (wrong) Change position to Gunner (while Pilot Seat is still removed) Change position back to Pilot --> reflections from behind the seat are visible (correct) Make Pilot Seat visible --> reflections from behind the seat are visible (wrong) It should add/remove those reflections as you make the Pilot Seat disappear and visible again, not after you changed to the gunner and back.

After restarting the mission these reflections were gone and I had troubles reproducing them. They appear when you remove the seat, change to the gunner seat and come back to the pilot. If you want to get rid of them, make the seat visible again, change to the gunner and back and all is fine. So basically, they are not changing while you are sitting in the cockpit and you make the seat disappear and visible again. But something is off with these reflections anyway, those panels should not be reflected on the map in any case.

Ok, I did not see it properly before, as I am just using a POV hat and no TrackIR. When moving the head position up and down and left and right it is all visible on the dials. It comes definitely from back there. The yellow pipe should for sure not be visible. There is definitely something odd with these background reflections, as there are as example these panels visible on the map that don’t even are in the line of sight of it.

There are some strange reflections on the dashboard. One is that yellow line and the other the moving blue part of the Doppler Indicator. A possible source for this might be in the back of the seat. I suppose the yellow line should not be visible, the blue part might be even possible. It still looks weird, because it is moving when you turn your head.

As in the title, I suppose this should be bound to the switches volume slider.