All Activity

Fully tracking this is going to be unpopular and probably not happen as a majority of players fly at 30,000ft looking at their MFD with a feed from their targeting pod. BUT! for those low and slower aircraft that actually see more then 3 pixels of a ground vehicle. I think it would be appropriate if we can have modified vehicles with mine rollers, bird cages, and Duke system antennas. Since these were widely used in Afghanistan and Iraq, this would give campaign and mission makers more tools to play with. And for those that have been over there it might just sell it even more seeing a vehicle with a duke antenna wobbling around. Possibly a better "combat" skin with sand caked vehicles as well. Just another wish to the wish list.

Bumping for an update estimate on this issue. It's happening for way too long now!

Maybe I'm just asking for too much but I like the autorudder. It makes for coordinated turns which is most of the time what I want. I'd like to be able to have it automatically be overpowered when I give a rudder input with my twist stick, though. Is there anyway you can add this? Just make it so any user rudder input disables the autorudder feature temporarily OR make autorudder have a toggle outside the special menu for in-game.

Probably not as popular but some non combat vehicles would add to the realism and emersion to the digital battlefield. These are modern US vehicles since that's what I know. Maybe someone else can chime in as well for other countries. As a mission maker I would 100% use these. Medical: M997 Field Litter Ambulance (FLA) medical hmmwv M133 Medical evacuation vehicle (MEV) medical Stryker Bonus (not a ground unit but on the topic of medical) UH-60L or UH-60M Medevac AI. Possible reskin of the current in game 60A. Or just reskin the 60A since it's dated. Support: M88A2 "Wrecker" Armored Recovery Vehicle. Essential in armor units, Abrams, Brads for example. M984A4 "Wrecker" Recovery Truck. LMTV version, used practically in all units with vehicles, HMMWV, Strykers for example. Other: M1117 Armored Security vehicle. Mainly used by military police, common at check points. M149A2 AKA the water buffalo. Heck yes.

I was aware of this problem. Previously, it was connected to the A-4 module. The fact is that there is no sound only in multiplayer and not all units. For example, the air defense has a sound...

Ah, it's the terrain way out there that's the concern, then.

I'll post one where I have them dropping all 4 way short of the target. I haven't saved any where they go dumb, though. In actual missions I have 8 pairs of Mossies hitting various targets. All 16 of them drop 100-250m short of the target. AI-11s-delay.trk

Airbus A-400M: Drogue Basket tanker so hornet friendly.

Hello I think i played mission 2 15 times meanwhile and i never get a hit on the SA-2. I tried everything possible. My wingmen are shot out of the sky and myself too. My Shrikes are always hitting the dirt before hitting the SA-2 regardless at what distance i'm shooting at and regardless how good the signal is. This is soooo frustrating. I'm really fed up with this!! What am i doing wrong??

Thanks @_Hoss, but VCTF-58 does not, as they say, have a regular time for meetings but we do have people who meet casually on the server. One might think there would be at least one online squadron including carrier ops would have a regular mission night once/wk. Maybe one of these days

Both the HUD and the VDI have separate ILS/ACL switches.

See screenshot. I don't understand why my TV shows what seems to be correct ILS indication, but my HUD is showing it dead centered, where I'm clearly completely misaligned. Nevermind, I think I found a switch I needed to flick as well.

I increased almost every setting and it fixed it. I do not know which one did the trick

Ahh, OK I didn't realize that you were talking about multiplayer servers ... I never fly on those because more than a simulation experience, it turns DCS into a gaming experience, and I have no interest in that, opting instead on flying single player with missions made by the community or myself.

For general mission and training ops, I find the F-15EX stick and Orion 2 base just fine. But for formation flying with a lot of pitch and roll change, and for A/A refueling, it's the biggest pain in the ass I've encountered. I have both a TM Warthog stick and VKB Space Combat edition that I think I'm going to switch to while I wait for the force sensing base to come. I find the fine control on this particular base with the default springs and cams nearly useless for AAR...that said, some have mastered it but for me (in the F-16 module, uh uh, I'm done.

It does not seem so. I tested all livery locations I am aware of but .zip files are not recognized by DCS. It must be stored as .dds within seperate directories. @Rudel_chw .zip to .dds size ratio varies. May be I picked an extreme example. However, I do not understand why DCS restores Liveries as .zip files to CoreMods or Mods/aircraft folders but does not unzip them. They are useless as .zip files for DCS. There are hundreds of them in DCS World/CoreMods/aircraft/<aircraft name>/Liveries and Saved Games/DCS/Liveries/<aircraft name>. I moved and unzipped them all to Saved Games/DCS/Liveries/<aircraft name>. Of course that increased their total size by approx. 2x or 3x but at least DCS recognizes them now.

I'm back on DCS after some time off and I had to reinstall the game entirely (the patch was as big as the game, so my drive couldn't take the download on top of the already installed game). I'm not sure what setting I need to fix to have the mirrors stop looking horrible like that. I recall them being quite decent, but now it's ultra pixelated. I wasn't able to make Print Screen work or to take any screenshot, but trust me, it's really horrible.

The problem is that almost no servers list an F-16 on the REDFOR. Almost never happens .......Who cares about Mig-29s in BLUFOR. It would be the last choice after FA-18 or F-16.....REDFOR doesn't have an effective Fox 3 missile besides the SD-10. The R-77 is a total wasted of wing space...Very limited range, very easily defeated. Death spiral....

not a huge drawback not having a HMD in the daytime anyway since the light is often so bright it becomes difficult to see :). Since there's no HMD, will the gunsight reticle be more of a fictitious display or will it have a mechanical swing down arrangement like in the huey?

Have you considered that a given aircraft can fly on either "blue" or "red" sides? .. an F-16 can fly for REDFOR with a Venezuelan livery, a Mig-29 can fly for BLUEFOR with a luftwaffe livery, and so on. You are putting on your own force-jacket when setting up your coalition's countries, instead of using your imagination and devising mission situations that are balanced for both sides.

@mla306, another user just reported similar behaviour, and has same stack trace as you, in the Eagle Dynamics DCS Discord server bug forum. I've dropped your log and link to your post there as well if it helps them further. The user who posted there stated that this occurred for them in multiplayer, so not just this mission. The key thing they've highlighted, and they tested a few things, was that this occurred when asking George to switch to rockets... and the rockets are the M151 ones with the M433 Resistance Capacitance (RC) Fuze. Can you check in the mission editor for that mission 1 (you said the others were fine), if it's possible, to see what the weapons loadout is for that Apache to see if it's the same. If you can't access that in the mission editor yourself then post this info back to Stone Sky. Would recommend asking them anyway. If not the same rocket type and fuze then see what it is for you, ask Stone Sky if needed, and report back. I can pass this onto the other user and see if they can replicate with that loadout as well. I'll try this in the next few days myself as well.

Here is a summary of how to install DCS on Linux (Steam version): 1. Install protontricks with flatpak: https://github.com/flathub/com.github.Matoking.protontricks?tab=readme-ov-file#protontricks-for-flatpak This means you should install flatpak as described on the webpage before you install protontricks with the Linux terminal: flatpak install flathub com.github.Matoking.protontricks (It is recommended to use flatpak, because some Linux distros may not support newer protontricks versions required for the steam client.) 2. Add a few command prompt aliases: https://github.com/Matoking/protontricks?tab=readme-ov-file#flatpak-recommended echo "alias protontricks='flatpak run com.github.Matoking.protontricks'" >> ~/.bashrc echo "alias protontricks-launch='flatpak run --command=protontricks-launch com.github.Matoking.protontricks'" >> ~/.bashrc 3. Now you can follow the hoggit guide by running the command protontricks 223750 d3dcompiler_47 in the Linux terminal. In the launch option of the DCS steam properties you should add WINEDLLOVERRIDES='wbemprox=n' %command% or else DCS is not going to launch at all. 4. The DCS launcher does not run properly in Linux (you will see a black box on startup). In order to disable the launcher you need an editor to open the file "options.lua" in the install folder "Steam/steamapps/common/DCSWorld/MissionEditor/data/scripts" of DCS. Then you replace ["launcher"] = true with ["launcher"] = false 5. Start DCS in Steam. It should now run without getting stuck in an infinite loading loop.