All Activity

I was excited to see this good news,but I guess it will be in another update soon...not the one we just had.

The "A" and "+" keys on the KU are delayed between pressing the key and it appearing on the display. This can cause mis-inputs when typing too fast. While most key presses are nearly instantaneous to appear on the KU display, "A" and "+" are delayed by almost a half-second. The bug occurs in both the Pilot and CPG seat. To reproduce using the Clickable cockpit: Slow game speed to 1/2 or 1/4 (To make the effect more observable.) Compare the difference between pressing on an affected key and a normal key. 2025-08-16 23-54-33.mkv

Thank you. I was just today wondering if I should ask you if you will have some time to port your Mig-21 training missions to another map,perhaps the Kola map.Glad to hear that you are on your way back to the Mig.In the meantime,I really got a lot out of your F1 Mirage training/ILS tutorials.

Left click in the box works for me ...

Sometimes even slower than that. Vipers and Phantoms do it at 175kts which is ridiculous.

Hhhmm. I can't seem to download the attached mission. Sent from my SM-G998B using Tapatalk

Welcome to DCS. You’ll get better feedback on this topic if you post in the VR section rather than one for audio bugs.

Hello everyone! I am looking to upgrade my VR setup for DCS World and would love some advice on the best virtual reality headsets for flight simulation. I am particularly interested in headsets that offer high visual clarity, comfort for long sessions, accurate tracking, and good performance with high-end GPUs. I have heard good things about the HP Reverb G2, Valve Index, and Oculus Quest 2, but I would like to know what the community prefers based on real experience. Any tips on optimizing VR settings in DCS World would also be greatly appreciated. Thanks in advance!

@jonsky7, Wow! This thread has some longevity to it! Kudos. I used it to reposition my kneeboard. It worked like a charm!

solved by using a vpn.

So here's a quick flight I did just now doing a Cold Start flight. Ignore my engine cutting out half-way through because I forgot to watch my main fuel gauge, and the Free Flight doesn't give you much of a tank of gas. Anyway: It appears that sometimes WEP just...doesn't turn on. I think this is connected to my observation of the water pressure gauge suddenly flatlining. You only see pressure on the gauge if ADI is actually on, and this coincides with my observations of the MAP. There were times where I pushed the throttle full throttle and ADI clearly didn't engage. I received no increased power, and the water gauge sits at 0. Others, if I pushed past the in-game detent it kicked in and the MAP needle jumped. From what I can tell, if you're at full RPMs you WILL overrev the engine when WEP turns on. This includes at altitudes where WEP is supposed to use 2700RPM. ADI_Issues2.trk

Да нет, место есть. Возможно, проверю на вирусы, уберу все моды. Спасибо! Тоже вариант, спасибо!

August 2028. During the F/A-18 training - starting cold from the airfield - my system froze and I had to do a hard reboot. I sent my log to ED and they noted... -------------- Yes, we did check the log you provided, and right before the freeze we see the following error: 2025-08-14 ERROR SCRIPTING (Main): Mission script error: [string "l10n/DEFAULT/mist_4_5_104.lua"]:1163: Object doesn't exist stack traceback: [C]: ? [C]: in function 'getPosition' [string "l10n/DEFAULT/mist_4_5_104.lua"]:1163: in function 'f' [string "l10n/DEFAULT/mist_4_5_104.lua"]:1701: in function 'onEvent' [string "Scripts/World/EventHandlers.lua"]:13: in function <[string "Scripts/World/EventHandlers.lua"]:11> This means a mission script is trying to get the position of an object that no longer exists in the mission. Most often, this happens if a mission uses a custom script or trigger that isn’t checking whether the object still exists before calling getPosition. --------------

I don't know what happened. It seems to have resolved itself...I didn't do anything, and the problem was persistent over several days. Perhaps if it happens again, I'll be able to figure out what's going on.

Not a problem, you can also go enjoy dynamic foveated rendering with DCS in your PSVR2 with the release of Bnuuy's PSVR2Toolkit, which can be used in conjunction with Quad-Views-Foveated in DCS! Anywhere you go, you can't get rid of me

Can someone post a screenshot within the cockpit showing the location of the damned WEP master switch? Can't find it... Also, is there a new manual?? The original early access one kinda sucks.

I know the map 145gb after install How big is the download file before it installed

Same here! Flew in single player, Dogfight a 190 and managed to shoot it down, all the while checking out the gauges, which were in the blue. Did a carrier bolter and then came around again with hook down. Landed. Took off again, engine gauges blue, mixture full rich. Suddenly engine quits and down to the drink! (Rich mixture cools any engine, I know that from years of flying a real life Continental O200 and lycomings of all sizes) The whole idea of having radial engines was that they were very reliable, even when damaged because no "coolant" was lost. Cylinders could in theory be shot away or perforated by bullets yet the engines would still run, or so the tales go... Same issue with the P47... With this F4U if you sneeze, you seize! This cannot be historically accurate. Seems like a bug. (Also, in the new update they mention a "WEP" master switch.. where is it? And is it for the water Methanol injection or were they abbreviating "weapons"?)

Does The Team have any suggestions for areas to test based on the crash dump? I ran ~10 test over the past 2 days and still have not narrowed it down. I understand The Team haven't infinite resources, but any help can be reciprocated by the community so that we can hopefully get to the bottom of this. -Tested with NO SA-11 to see if resolved...no luck. -Tested with NO SA-10 to see if resolved...no luck. -Tested with NO NASAMS to see if resolved...no luck. -Tested with NO SA-19 to see if resolved...no luck. -Tested with NO SA-15 to see if resolved...no luck. -Tested with NO AI Hellfire Ks to see if resolved...no luck.

Ok, many thanks Don. I'll try it later today. Cheers! Sent from my SM-G998B using Tapatalk

Yes it would be great and having an earlier generation Harrier has always been something I have wanted too. Without any indicators from any 3rd party developers I think it will remain on the wish list (with a laundry list of many aircraft) but hey - this is what this is for - expressing our wish lists!

I forgot about the mod. Here's another one using built-in aircraft only. Eventually, water pressure just cuts immediately to 0 and the 3-minute warning light is never coming on. ADI_Issues1.trk

After a longnull day of Mission Building Testing and lots of Saves I end up getting this message. About 3 times now after the last update. It will only Happen after you save your work and then Start to Play the Mission. I Can Save the mission Exit the Mission Editor but I must EXIT the Game and restart DCS World for this message to Stop. The mission will load fine with all the last Saved version edits. But you must exit the game because doing just a reload of the mission after exit to Main Menu will still cause this message.

Admins, apologies if this is in the wrong section so please feel free to move it if you need to. _____________________ if you are running an RTX 3090 and on the latest Nvidia driver (580.97 as of August 16, 2025) and CANNOT get into safe mode, this might help you. problem: cannot get into safe mode what is happening: - In windows 11. - press start > select power icon to restart > hover mouse over restart > hold down left-shift and click restart to bring up troubleshooting window - trouble shooting window comes up, no problem so far. - Select Troubleshoot > select Advanced Options > select Startup Settings > select Restart. No problem so far……. BUT! The system boots to a black screen and there is no blue screen that allows you to select option 4 or 5 to boot into safe mode. Here is how I fixed it. - pressed Enter > Rebooted back into windows 11 - Used “Direct Driver Uninstaller” to uninstall the latest Nvidia driver (580.97) - tried booting into safe mode again and this time it worked. I got into safe mode and used DDU again as a failsafe to remove every single trace of that POS driver. - Now back to windows 11 - installed driver version 576.52 - Tested again and I was able to boot into safe mode. fixed! Nvidia seems to have crapped the bed with their latest drivers. I don’t care what anyone says, to me it looks like they are so into trying to revive the 50 series cards that their latest drivers are absolute shiiite for 3090 users. anyways, hope this helps someone.