All Activity

Ich habe es persönlich in der F/A-18 probiert… Es funktioniert eben nur unzuverlässig. Manchmal ja, manchmal nein…bzw dann erst beim 10. Versuch. Ist nur mein Erfahrungswert…vielleicht geht es mit Leap Motion ja tatsächlich besser.

OK I have found that the AFCS start up takes control of the stick and deflects it. So the way that works for me is to completely let go of the stick while it's going through the start. I can imagine a FF stick might be an issue? but I don't know.

Ekran Fail track Mig29 Ekran Fail.trk

Hello, I'm getting a lot fps stuttering while in main menu & mission editor. Tried to delete metashaders2 and fxo folder, not worked, repair too. dcs.log

Thank you

This maybe?

when i stay online after launching it works, but offline no

I've not tested on Germany / other sand maps, as the Apache campaigns I'm playing are set in Syria, so they may be worse/better/same. Helos are not ED's priority clearly and its not an issue for fixed wing flyers who view terrain as something you take off from, land on or drop metal things on. To be fair, MSFS2020/2024 both look awful low down in some areas. Close up photogrammetry is a nightmare of mashed textures. Try NY central park in a Helo. Its Lile Jurassic Park made in Minecraft. Every MSFS demo is someone flying round NYC in a cessna from 2000ft+ where it looks lovely. You cant see the helo flyers puking in their VR headsets.

Dir ist bewusst, dass das Bedienen der Schalter nur in ED-eigenen Modulen, in der F4 und Kiowa funktioniert? und was passiert genau, wenn du einen Schalter bedienen willst?

Did you check if pylons have drag? Drag is far more important then weight. Worth to remember it's EA right now.

Windows event viewer shows no problems (I found a similar topic that hints at drive errors - but mine is not showing any)

FYI I managed to change the countermeasures program to 4 flares only for MAN 1 program and 4 chaff only for MAN 2 program by editing the ALE45PRG lua file in the scripts folder of the module (Mods\aircraft\...), just be aware that the original values will be rewritten after each update. I use Ovgme to swap my custom file with the original after each update, easy fix !

Then I guess is a problem with metric system and english cockpit.

Modeling real life, both, strong sides and limitations, is the beauty of full fidelity modules and DCS overall.

Go to options and then select the NS430. There you can select and unselect where you want the module to be visible in the cockpit on modules that allow it to be integrated.

I rolled back the BIOS to an August 2024 version, and DCS load times have improved a lot, pretty much on par with the benchmarks I got when disabling HT. I have an Asus ROG Strix Z790-F Gaming WiFi II. The BIOS version is 1503 dated 2024/08/08.

Same problem. From DCS discord: Rename folder Misison Editor in Savegames. Game will create new one. Than finally I can jump to mission. Also I transfered these files to "new created MissionEd. folder" Someting is wrong in this folder, that blocked loading to missions and map. But not everyone has this problem.

Hello! I trie to update the second time now. As you can see the updater is downloading and unpacking more then possible... should I cancel it? How do I update now? I do not want to reinstall as I have a ton of stuff like button assignments to a lot of hardware - it would take forever to redo it. Thank you

I was strictly speaking for what seems to work in DCS right now. But you are of course right. I wonder how much turbulent airflow the cowl flaps produce and if that may affect the risk for stalls at slow speeds, or what other reasons for specific procedures may exist. Of course cooling is reduced with approach speeds, but so is the heat output from an engine that is almost at idle basically..... Either way - I can't judge the realism, but I can make it work for me in DCS to at least use the Corsair without issues.

I'd like to use this thread to ask ED to kindly look at the sync issues of long range weapons (Harpoon, Slam, Slam-ER), which are present since the addition of those weapons to the game. The issue: Long range weapons are not synched in multiplayer environment, which will cause the following issues: 1. The flight path of the weapons looks completely different to each player. Only the player that launched the missile will see the accurate flight path via F6. 2. Not all players see the weapons hitting the target. 3. When SLAM/SLAM-ER is used, a hit can only be validated by the data link pod of the user. Other players will see the missile missing the target, but will occasionally see the target explode if it hit. Why does this matter? In a sterile environment, you won't notice most of those issues. However, it has a great impact on missions in which other units interact with those weapons. AI units that interact with those weapons usually try to shoot them down (SAMS or Ships), and this is where the sync matters. Imagine the following scenario: 1. 4 SLAM-ERs are used to strike a pre planned target. 2. Player B sees player A's missile intercepted by an SA-15 on the way. 3. Player A does not see his missile intercepted, because to him, the missile never came close to the SA-15. 4. Player A's missile eventually hit the intended target. 5. From player A's perspective, the SA-15 never fired a single shot. However, player B clearly saw it intercept the missile, which means it used at least one missile to try and intercept. 6. The number of available missiles of the SA-15 is now not synched between clients. The actions of the SAM (launches in this case) were also not synched between players. The following Tacview track shows the same scenario. If you look at it, almost all missiles miss (except the ones launched by me, which perfectly shows the desync), when in reality most of them hit the target. The SA-15 and Pantsir shown in this track, recorded from my POV, essentially launch on phantom missiles that fly over the target area, wasting ammo on nothing. Tacview-20250913-215434-DCS-Client-Syria_Operation_Polaris_v0.1.zip.acmi The flight path of those weapons should be synched in mp, just like A2A missiles. Otherwise, it just causes more randomness down the line. All players should see SAMS doing the exact same things at the exact same time. especially when it comes to launches.

Are you playing in 1080p? Go 4K and increase the GFX settings. Yes, you can get 330 fps (even though DCS can start to glitch when approaching 300 from my observations), but there is absolutely no point to it. Cap it at 120 (or maybe the default 180) and be happy. Every headroom beyond that is better invested in resolution and visual fidelity. And, risking to repeat myself, those number are meaningless, unless you specify the scenery and your settings.

You are?

If you go to the exterior view as the aircraft is lowered from a levitation (it's shaking as it does so too, which is a bad sign), as it's coming to the end of a repair, you'll see it mis-aligns with (the tail-wheel drops below) ground level/carrier deck, this results in a sudden jolt as it realigns and I believe this keeps the tail-wheel in a perpetually damaged state. So it cannot freely castor as it should. Wind etc is irrelevant. The tail-wheel never 'works fine' as you say, never has, not for anyone. This is precisely what the Patch notes refer to as having been fixed, and it hasn't. The video below shows how the aircraft should handle with an unlocked tail wheel.

There is only one proper solution to improve readability of HUD elements (and gauges in general), and I don't mean that in a condescenting or ridicule way - Zoom in (a "realistic" zoom-factor or fov would be between 60-80 depending on the size and distance to your screen) and/or get a bigger screen. Some things, like the Mig's HUD in this case but many instruments in most Aircraft, are really hard to read on screen.

Also ich kann nir sagen, dass meine Quest Pro augenscheinlich die Hand und jeden einzelnen Finger sehr gut trackt. Jedenfalls sieht der Handschuh in DCS genauso aus wie meine Hand in der jeweiligen Haltung. Aber wenn ich dann einen Schalter oder Button bedienen will ist Fehlanzeige…