Polo

I'm seeing this on an AMD Vega 64 and HTC Vive. Suspecting it's related to the AMD drivers. Also if I turn on MSAA the menus disappear entirely upon hitting 'fly again' or CTRL+r in the mission: https://forums.eagle.ru/showthread.php?t=213389

I'm getting something similar with my Vive and Vega 64 GPU. From some basic testing it seems to be tied in to whether I'm using MSAA or not in-game. If I run x2 or x4 MSAA then it happens, without MSAA it hasn't done it yet. This is testing by using CTRL+r to restart a SP mission. Are you running MSAA?

The Vive has ASW controlled in SteamVR - I'm at work so can't put up a screenshot, but it's under the Developer option in the SteamVR Settings. Once you turn this off then frame rates between 45 and 90 will occur, although there is a doubling-up effect depending on the frame rate fluctuations.

Pretty sure it's always been like this, only the selected Maverick's seekerhead moves at any one time.

I've found Trifire 7970s work quite well (go from 25fps to 70ish fps) in both DCS 1.5 and 2.0. I did have to use Medium visibility distance (large tanked FPS from 70 to 35) and also having mirrors ON increased FPS by quite a bit. Stuttering was neither here nor there. This was using the 'AFR-Compatible' Crossfire Profile Setting in the AMD Crimson settings.

Did you try with mirrors turned on? For some reason having mirrors on greatly increases my FPS. Counterintuitive I know...

So far running TriFire (Crossfire 3x7970s) fairly well in DCS World (both 1.5 and 2.0). Using the 'AFR Compatible' CrossfireX profile seems to resolve most of the flickering. Model visibility needs to be off and am using the latest 17.1.1 Crimson ReLive drivers. What I have found has an impact is to have Cockpit mirrors ON...I'm seeing FPS jump from 45 - 80 when toggling the mirrors back on in some cases. This is running 5760x1200, 512 every frame for textures. Turning Tesselation Mode in the Radeon settings to 'Use application settings' might have helped. I'm using the Medium preset settings in DCS World.

There is one thing that you may need to do extra work to fix up though, which is the disk drive folder reference(s) for any in progress or completed campaigns.

At this point in time it isn't possible to get DCS to work in full screen mode across multiple monitors unless they are all part of an 'Eyefinity group' (or NVidia equivalent) and seen as a single screen. The only way (at least that I know) to have multiple monitors working is windowed mode spanning the full desktop area. With my setup (3 separate 'displays') if I hit fullscreen it crams compresses the image to show everything on my main display. There is the reference to a 'displays' array in the multi monitor files (I think the 3cameras.lua file has it, but at work and cannot check) but I don't believe it is either implemented or enabled. This would then allow choosing which screen shows what (I reckon you could enable stereo mode on the main screen and just normal rendering on the others)

In the 3Cameras.lua fie under Config\MonitorSetup there is a reference to a displays array which seems to say that DCS can have access to all separate monitors on a multiple monitor setup. This could be very interesting as it may allow the use of full screen mode along with multiple monitors (very useful for Crossfire users) At the moment if trying to force the use of the displays array dcs.log reports that it is a null array. Is this something that has been implemented yet and if so how do we get access to it, or is it not yet ready?

I can confirm that it is related to being in actual full screen where Crossfire is enabled - the model visibility related stuttering disappears when going back to borderless window mode.

Same here! (just tested)

If I was to hazard a guess you are running windows in a non-bezel corrected resolution (i.e. 5760x1200) rather than 6000x1200. Hit Alt+Enter (try Left Alt and if nothing happens then Right Alt) to actually force DCS to go into full screen mode and see what happens. Note that you may have 'full screen' selected in the options menu but you still need to hit alt+enter to actually enter full screen mode.

This will spread the UI across all 3 monitors (i.e. ViewPorts.Center) so that the bug where it is compressed by 1/3 when using 1screen with 3 screens doesn't occur.

And don't turn off Tesselation in your graphic drivers control panel like I did...

It looks like the exported displays are not having their background exported and hence we get the bleed through of the background. I modified my config so that the MFDs were exported onto an area of my default viewport (i.e. the background was constantly updating) and it displayed no problem but as a transparent image. The F15C radar was perfectly visible when done this way. It looks like DCS doesn't wipe the background clear in between frames (and never has) and this shows up when there is no rendering occurring behind.

Try pulling the power out from the back for a short period of time (until the light goes out) then put it back in and see if that clears it. Mine has had to have this done from time to time.

Can't say I have the issue (no Saitek controllers or X99 motherboard) but have you tried using a PCI-Express USB card? If it is the chipset that is incompatible then a separate chipset on a card might avoid the issue.

Sounds like the TV compensates for overscan (from the good old CRT days) Check whether the TV has a setting to turn it off, or if there is another HDMI port that one may possibly avoid the issue. If no go maybe you're better off running DCS windowed mode after compensating the desktop size.

Please put me down for DCS Hawk.

There is acutally a problem with the latest Warthog Throttle Firmware LEDs and that analog wheel. Only solution I know is to turn the Throttle's LEDs either to Full Brightness or Off and the spiking stops.

Found this same problem last night while doing a cold start - switch made noise but didn't move. Had assumed (wrongly) it was tied into the datalink. Looked it up in the current manual - page 6-78 (153 in the PDF) section 6-53 'Radio and data link power control panel' states it has no function.

To change Nav points is (I think) LCTRL + ~ (next to the '1' key on the top LHS of my keyboard) - am at work at the moment so can't confirm. With Autopilots there are key bindings for all the Su-25T type modes for the F-15C (i.e. Alt Hold) but I can't say I've gone through closely to work out what works and what doesn't.

Not sure with the Asus Xonar DGX, but on my Auzentech X-Fi Forte I have the buttkicker hooked into the front speaker output and have speakers not mute when switching to headphones. Also front speakers set to 'large' so that they output the lower frequencies.

MFD exporting works for me with the SU27 but it goes on the opposite MFD than the F15 does (F15 radar goes to the LHS MFD, SU27 goes to the RHS MFD)