Trubert

For the last month or two I've had an annoying bug playing DCS in VR (doesn't occur in pancake). Whenever I launch the game, the view is offset vertically by about a screen height, maybe a little more. All I can see is the top of the plane's wing in the hangar, not the intakes or (more importantly) the menu. There is a simple workaround which is to recentre the VR view using Num5 or in my case a HOTAS bind. No further problems when playing after this, and startup views in all aircraft are fine, it's just the launch menu. I'm playing in SteamVR over Quest 2 and Virtual Desktop for the link. System specs probably not relevant but are 5800X3D, 64GB RAM, 7900XTX on latest drivers. A minor bug, but feels like this should be a simple fix in a config file somewhere. Can anyone help?

Thanks chaos - I did wonder if that was the case reading around. Here's hoping for a fix soon, it's needed.

Question about what I see in fog, specifically at ground level. Apologies if this is already addressed in other posts; I saw only posts about clouds (which look fine to me). Whenever I'm at low level in fog, I think particularly at night or if the sun is at a low angle, I get really weird ghostly-pale effects for buildings. Often this looks much lighter than ambient lighting should allow. A couple of screenshots attached. Both are from the MiG-21bis instant action mission for PRMG landing at Nalchik (not my finest landing, but I was in a hurry!). One is through the canopy and toward the sun; the other is with canopy lifted and away from the sun to eliminate possible lighting effects. The effects are the same for the PRMG landing mission in other regions (I think it's Syria that has a PRMG landing instant action, but might be Persian Gulf). They don't seem sensitive to changing system settings like lens flare or anisotropy, but I realise there are thousands of possible combinations of settings. I get the same effect in VR or on screen; screen is of course a little sharper (but the weird lighting is still there). I'm using the latest regular 2.7 release via Steam, not the open beta. My question is whether this is a bug; whether it's something I can fix by editing settings, or whether it's just a quirk of the current weather system that will be fixed in future updates. Thanks in advance!

Further update - pretty sure I fixed this now. Several play-throughs of the MIG-29 landing without a single crash even on HIGH detail setting. Still getting the texture not found error: 2021-12-30 11:32:35.474 ERROR_ONCE DX11BACKEND: texture 'mi_8_tex_spec' not found. Asked from '' But the game runs fine, with the odd transient framerate dip for 1 sec or so. Made two changes that seem to have fixed this: 1) Further drop in GFX clock and voltage to a max of 1800 MHz and 975 mV (with aggressive cooling etc). 2) Enabling Radeon Chill FPS limiter (setting to min 30 max 100 FPS). Got one isolated crash without this; enabling it stopped crashes altogether (as far as I can tell anyway). Answer was definitely clock/voltage on the 5700XT though. Log file attached if anyone cares to dig through. Thanks for all your help. Btw - any reason DCS is so sensitive to GPU clock/voltage? It's by far not the most demanding game I play graphically, but this is the only game that crashes. dcs.log

And update - switching to HIGH detail settings seems to make no difference (if anything last run went longer than most). So it's probably not that. Game is running consistently a bit longer than before; I get to land (or at least crash) my MIG-29 in the FCS instant action mission and usually start a second go-round. Makes me think the underclock/undervolt has helped; anyone have tested settings for 5700XT?

Update. I've uninstalled graphics driver in safemode, reboot and clean install latest driver with default settings. I have undervolted the GPU (down clock to max 1900 MHz and 1000 mV from >2050 MHz / 1200 mV; plenty of web reports of 1900/1000 working well) and set fan cooling profile to be more aggressive. I've uninstalled and reinstalled the game and run with built in LOW detail settings to minimise stress on the GPU. GPU tested stable with built in AMD tool in the driver, temps way down to c. 80 degrees at junction (from >90). Result - the game runs a few minutes longer before crashing with exactly the same symptoms (hard crash to black screen / reboot needed). So it's progress of a sort, but not enough. Any further tips before I raise a support ticket? dcs - clean install game and drivers, low detail, underclock.log dcs - clean install game and drivers, low detail.log

Thanks - will post here after reinstall and manual underclock of GPU. By disconnects do you mean the DX11BACKEND error?

Thanks for quick reply - yes it has a factory OC. I have tried using the 'undervolt' setting in the driver software which dials it back as you say, but no joy. I can try doing that again with manual settings; currently clean-reinstalling the game from Steam just to eliminate that possibility. Also I'm pretty sure it was working on the same graphics card previously with a different driver version. (Can't remember exactly when I upgraded to this card, otherwise I'd be certain.)

Hi all, hoping you can help. I have a constant hard crash problem during any gameplay. Loading to menu is fine, loading the mission is fine, mission consistently starts fine, but after 1-5 mins, my system is guaranteed to crash. One in 10 times it'll CTD, but normally it freezes altogether and I have to reboot. Game has worked previously without problems, on this exact hardware - so that and the error log make me think it may be a dodgy AMD driver or setting. But can't work out what to switch around. System should have plenty of power: Intel 8700K (6 core/12 thread), 32GB RAM, 5700XT 8GB. Only mod installed is FC3. Using latest AMD drivers, and sometimes Oculus Quest 2 with Virtual Desktop link - but crash occurs whether in VR or just on my regular monitor. I've done what I can with Google and looking around this forum: clean install graphics driver; Steam file integrity check; undervolt GPU (using default setting in Radeon driver software); dial up cooling on GPU (was getting to 90-95 junction temperature, though that should be well within spec for the card); reduce detail levels in game. None of it has made any difference at all. Log is attached. Every single time it ends with the ERROR_ONCE DX11BACKEND error in the final line (which has also usually occurred a couple of times earlier in the log): 2021-12-27 14:05:32.790 ERROR_ONCE DX11BACKEND: texture 'mi_8_tex_spec' not found. Asked from '' Sometimes the texture name varies (you can see this a couple of lines earlier in the log), but this is the consistent feature of the logs. Interestingly (to me as a non expert) it also always concludes with Asked from '' without specifying from where. Thanks in advance! dcs.log