vfa132

With the F18. Using cable there is significant improvement of FPS and video in both flatscreen and VR. However, using Virtual Desktop the flatscreen works just like cable but in VR the screen is distorted (not a full screen). Lenovo laptop with GTX1660ti, i7-9750H @ 2.60GHz, 16MB, not overclocked, and Quest 2. Used the same settings for all.

That fixed it. No flicker but all the controls in all aircraft are returned to default. I guess it created a new module using info from the DCS World OpenBeta folder that's on my SSD? I think the flicker problem is definitely related to the zoom function. For some reason the zoom started working while flickering and sometimes would stabilize zoomed until suddenly it flicked to normal zoom. Could be something related to my F18 control setup, but the problem continued with my HOTAS zoom functions removed and just using the basic key functions. And there have been no zoom issues with other aircraft. Can I recover the controls settings?

I have TrackIr but have not used it recently. I uninstalled it and nothing changed. The first of my attached track files (-3) is playing back your track file. The flickering started spontaneously with no key entries. The other track (-3a) is another playback of your track file. When I made the key entries the aircraft went into a death spiral. I ran the sim in VR. No flickering. When I restarted in flat screen it still flickered. F18 flicker-3.trk F18 flicker-3a.trk

I have the keyboard * / connected to HOTAS for slow zoom. I have attached another track file showing the effect of those keys (no effect) on the slow zoom and the effect using the Rshift / * for normal zoom (enlarged flicker) as well as the effect of those same keys when applied in an external view (they work). I also removed the HOTAS link with no change. F18 flicker-2.trk

The track and log files are attached. It's not Steam and I ran a slow repair. F18 flicker.trk dcs.log

Suddenly while in flight in DCS 2.7.3 and while viewing the cockpit the entire screen, including the surrounding terrain, started to flicker heavily. The aircraft flies and operates normally (except the internal view zoom function is gone) and there is no flicker in the external view. I've closed/opened DCS, rebooted Windows 10, changed missions (including add-ons, on the ground, and aboard ship), changed locations, run the DCS repair function, and uninstalled/reinstalled the F18 module. This happens only with the F18 -- other aircraft are normal. I'd like to fix this without going through the long DCS uninstall/reinstall only to find that the problem is still there. Any ideas?

My update of 2.7 stable to 2.7.3 with my modules took 12 hours. Many of my settings as well as generic settings were erased. For one there is no option of an axis command for the L/R/U/D view – it can't be linked to HOTAS. I had to reprogram my HOTAS commands. The only aircraft in the Marianas is the F18 with only instant action – all my others are blank. I ran the fast and slow repairs. No change. Windows 10; Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz; NVIDEA GeForce GTX 1660Ti; broadband 100+ gb/s

Apparently so. The effect of differing resolutions is described in the manual, but only about screen size. Nothing about side effects. I wonder why the game developers didn't include such a valuable feature.

I decided to start from scratch. I uninstalled and reinstalled DCS (now 2.7.2 non-beta) without installing any aircraft or other mods. I started the game with my monitor at its native resolution (2560x1440) without changing any game settings (full screen not checked). The game started at non-full screen (windowed) with resolution 1920x1080. I opened the TF-51. All the clicks worked. I selected Alt+Enter. It went to full screen and no clicks worked. Then I changed my monitor to match the game (1920x1080) and it opened in full screen and everything worked. Then I checked full screen and nothing changed. Bottom line: Ok with matching resolution settings, not when they differ, which really effects the playability of the game. When I start the game with TrackIR running TrackIR reverts to its default settings, which I can't change without a working window capability. Sorry about the long detailed explanation, but since apparently nobody else is having this problem it must be me or my system doing it and I don't know anything else to try. It all worked in 2.5.6 and I'm using the same system. Anybody have any ideas? Can I go back to 2.5.6?

OK, since I can't get a windowed screen to work, how do set up TrackIR?

My monitor native resolution is 2560x1440. With DCS set to the same the LAlt+Enter keys have no effect except a flicker as if it's opening a window, but with no change in the screen. When I change DCS to 1920x1080 I have a window available but with no clickable cockpit in full screen. It's the same whether the full screen option in DCS is checked or not. I also removed my Oculus VR system and hardware to see if that's the problem. No change. I think the resolution trick worked in 2.5.6.

Is there any way to open DCS in a window that allows switching between windowed and full screen like in MSFS 2020 and FSX? Setting the screen and DCS to different resolutions (DCS 1920x1080, monitor 2560x1440) as described in the DCS manual does it, but the full screen loses the clickable cockpit. It's the same whether or not Full Screen is selected in DCS. Sure is frustrating to have to shut down and restart to change settings, etc. Am I missing something?

Sometimes on the ground or inflight the cockpit mouse click simply quits. It reverts to the yellow cross with no functions. Happens for no apparent reason. The only fix is to keep trying and it comes back, again for no reason. V2.0.0 beta 5

The Windows 10 task manager performance tab reports the GPU functions. What's involved in profiling (with Windows 10 home 64-bit)?

It's an HP Pavilion Wave 600, which is sort of like a laptop on a desk. Anyway, there's no way to connect directly.

The monitor is connected via DVI to the Intel graphics and the AMD is connected through it, so I can't disable the Intel. But if that's a problem how do the FSX and P3D apps work with the AMD?

DCS World will not utilize my discrete AMD Radeon R9 M380 graphics; it operates with the integrated Intel HD530 only. The AMD driver does not detect the DCS game, and even when the game is added manually using the Radeon switchable graphics screens it has no effect. The Radeon screen displays the high performance option but the Windows 10 task manager shows the game using the power saving Intel driver only. FSX and P3D both use the AMD graphics, both the graphics drivers are current, and this happens with both DCS 1.5.8 and 2.5.0. Maybe DCS thinks the Intel driver is better?