Search the Community

Hello, After the latest update, I noticed that the English cockpit mods no longer work, and there is no dropdown in the Special menu to even select a cockpit skin. I looked into this and found that all of the Mirage textures are now in \Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\Mirage-F1\Textures. Furthermore, the regular textures are split into 2 separate .zip folders, and the Normal Maps and Roughmets are also in their own separate .zip folders. This is different than the original folder structure for cockpit texture mods normally utilized by the Saved Games folder (\DCS.openbeta\Liveries\Cockpit-F1EE\English Cockpit). I did set up a folder package that directs to the new location for the textures with the English Cockpit and it worked, but it does not pass IC due to it being in the installation folder. I'm working on figuring out how to get this to work by utilizing the Saved Games folder. If anyone has any info on this, please feel free to add your thoughts!

I have a convoy sent to ON ROAD. I am using two flags and the radio menu to stop and start them, using an advanced Trigger Action of HOLD /? with a STOP CONDITION of the GO flag being true. Nearby this convoy I have a CLIENT helo with 14 infantry spawned stationary right next to the helo for boarding. As soon as the mission starts the first unit in both groups goes for an extended walk / drive about - despite the infantry having no waypoint to go to prior to embarkation and the front car of the convoy going in circles in the opposite direction of the first waypoint. The first infantry stands on the opposite side of the helo from the stationary other 13 members of the group and runs around in a small circle forever - at least until instructed to embark. The car eventually drives towards waypoint one and the ones behind eventually get the idea to follow, but then when I issue the stop command, instead of them all stopping, they drive OFF ROAD through gardens, across railway lines and other roads that weren't on the waypoint list in order to 'stack closer' to the lead vehicle, but then they screw that up and break into about 3 groups, some not moving, some getting stuck in the scenery and some eventually getting closer to the lead vehicle than the default starting spacing forced upon us all. When you send GO again, the front ones follow the waypoint on road (mostly) but the back ones don't know what to do or where to go, eventually the start moving and then when you say stop again they cross country, through buildings, gardens, car parks and everything and again, get stuck. HOW is this correct and acceptable? If they were all set to OFF ROAD, whilst still utterly awful, going direct to 'stack up' (which they still shouldn't do) would be slightly more acceptable, but when they are constrained to 'ON ROAD' this type of behaviour shouldn't even be possible. Here is a video of it on YouTube showing just how broken and screwed up the pathing is: https://youtu.be/8H3vcy--B-g And how unreliable it is when you have a convoy and need it to stay together as it moves into the target zone. You can't even trust your units will make it there to be fighting efficient!

Also mein Joy Stick funktioniert mit allen Knöpfen usw, aber sobald ich den nach hinten, rechts, links oder vorne ziehe fängt der Joy Stick im Cockpit des Flugzeugs an von der Position in der sich mein echter Joy Stick befindet wieder zurück in die Mitte zu springen und das mehrmals die Sekunde. ich hoffe sehr, jemand kann mir helfen und schon vielen Dank im voraus! VID_20220808_145044 (1).mp4

PART 1 Hello and welcome to my Thrustmaster Warthog throttle pinky switch replacement guide. I live in the UK and have found it difficult to find any information with regards to replacing the pinky switch in the UK specifically. I found numerous vids and advice on HOW to replace it, but not WHERE I could source the correct switch from in the UK. This guide presumes you are comfortable taking apart your beloved throttle and have access to, and can use, a soldering iron. No special tools are required. If you're reading this you probably already know that there are an abundance of SPDT switches out there, and if you don't know what one of those is, like I didn't, just google it. It'll make more sense. I found it difficult to decipher all the sizes and switch types so I wanted to share exactly WHAT switch I used and WHERE it came from at a very reasonable price. So lets get to it.... THE SWITCH From a reputable electronics company, RS Components. RS stock number: 7347139 REMOVAL OF SWITCH To remove, undo the 2 phillips screws holding the left throttle together. They are located on the INBOARD side of the throttle. The OUTBOARD panel that the switch sits in should now start to come away from the body of the throttle. ***NOTE - IF THE INBOARD PLASTIC PANELSTARTS TO COME AWAY, TRY TO PREVENT THIS FROM HAPPENING. THAT PART ISN'T DESIGNED TO COME AWAY WITHOUT FURTHER DISSASSEMBLY. You will find 2 black spacers inside that will become loose once the screws are fully removed. Take those out and keep them safe with the screws. At this point don't worry about which way around they go as I'll specify that later on. I'm going to have to break this post up into stages as my images are too big and limited to a max of 5MB per post.

I'm new to DCS. I believe it's an outstanding flight sim. But my perspective on the game took a major hit when I loaded up a REPLAY track and discovered to my horror that the replay does not reflect my actual gameplay (i.e. I crashed in the replay when I did not in the original playthrough). For a game like DCS with its relatively high price points, the lack of a fully functional replay track is an embarrassment. After conducting a due diligence, I was surprised to learn that this replay bug has been around for years, not months or even days, but years. In light of this, I cannot recommend this game to my friends or colleagues in good conscience. The devs should know better. The devs should be better. Do your customers and community better and fix the broken replay system once and for all. Thank you.

As reported months ago, the issue is still present in the game, it's way less than before but STILL there. Shadows are on High. Reinstalled Windows 2 times, changed GPU Drivers nothing helped.

Hello, It's all in the title, after posting a dozens of times to report that massive issue, the issue is STILL THERE after MONTHS of patch. I already sent dozens of tracks and screenshot showing the issue, this is not reported because people don't pay attention but I got this issue on 75% of my flights and when I have the issue EVERYONE in the lobby have it too. I have a RTX 3080, tried dozens of drivers, reinstalled windows 2 times, reinstalled DCS, changed every DCS settings. One of the last screenshots was taken in December of 2022!! 4YA_Cau_PVE2_V2.46[JAN_FEW]-20230422-141815.trk 4YA_Cau_PVE2_V2.46[JAN_FEW]-20230422-141655.trk options.lua

I haven't played the game for a few years since it was called DCS World Open Beta, and I purchased a number of DLCs for it back then. Today, I reinstalled it, noticed it was called DCS World Steam Edition, and now none of those DLCs are working, saying they are unauthorized. How do I authrorize them in the latest version? Considering what I paid for them, I'd hate to think I lost them all.

Someone was asking about this box in the main M.E. channel. As I was explaining it for them, I tested it out, because you know... DCS and the DCS ME manual can be deceiving... Here's the script I created to create a CONDITIONAL that returns either a TRUE or a FALSE. groupConditionTestScript.lua It IS loaded via the 'Initialisation Script' box in the Trigger Rules dialog as per the manual. It is called from the CONDITION box on the GROUP Inspector just to the left of the % spawn box. Even if you edit this script to always return true and set the % to 100, the group will never spawn. Either the manual is grossly misleading, or this is broken. Here's the test mission: groupCONDITION.miz It SHOULD just spawn a helo group if the CONDITION returns true (it's an RNG from 0 to 10, anything over 5 is a TRUE - check the DCS.log to see if the script is called and what the return value is) but either way, the game NEVER spawns the group.