All Activity

Das geht problemlos, ja. Außerdem sollte Multiplayer inzwischen auch mit IPv6 möglich sein.

one thing i would add time and time again people are asking about fuzes and how they are modelled in game, and what each fuze does in relation. This is something that ED need to document, with each fuze and specifically state what this is in relation to the game (so those that dont know can educate themselves). When i was last having a discussion about this i said they would be in the manual as knew what they where, and was surprised to be told they were not either in the base game manual , a supplement or the aircraft module. Is this still the case for both western and russian fuses? I would also expand this to weapons in general - its something that most kids will not have a clue about (thankfully).

Just remembered that also this could be due to monitor features like Gaming HDR and some other enhancements, which my monitor has too, all of which I disabled because it was giving me inconsistency in image brightness, something like a flicker, so maybe if you have monitor that has these features try turning it all off.

Du hast doch bestimmt irgendwelche DCS module? Dann hast Du auch einen Account. Oder fliegst Du nur Su-25 und T-51 auf Caucasus und Mariannas? EDIT: Ach so…das läuft dann über Steam…hmm…

Der Chipsatz ist eine Eigene Welt, am Besten lies dich da mal rein. Vielleicht auch hier, ist gut beschrieben : Chipsätze Vergleich MSI Blog Ja, das Tomahawk wäre es eigentlich auch geworden, aber ja.... Ich gebe es zu, ich habe mich da wirklich vom Carbone verleiten lasse Beide sind sicher eine gute Wahl.

apart from the roughly 15 steps you dropped, yeah sounds about right….

Hm, maybe you have bit of hardware issue (video card or monitor, maybe even the cable between the 2)? On something slightly different, my dcs runs pretty smooth but yesterday I was setting up VoiceAttack so I set dcs to non full screen, smaller than monitor native resolution, and after switching back and forth between the applications I noticed dcs getting very stuttery even while I had vsync 120 fps which was weird, I thought maybe because I had 4 Mig-29a in the mission it overwhelmed my video card but turns out it didn't, I restarted the pc and after that it was smooth again in the same mission. So I don't know, maybe theres bit of memory leak or something when dcs switches from one view to another as it did with me switching from dcs to VoiceAttack? Maybe try a different cable first, I'd also check if possibly video card is running too hot, running out of vram... anything like that... even changing settings in dcs... computers can have tons of things causing issues and most of us here know this. Good luck in finding what causes it

Is the U-2 flyable now

It works in the mission editor as well.

Thanks again for posting. I will try it tomorrow - is it only possible to load the tank in the rearm menue? Other configurations you could load in the Mission Editor wäre you can change the liveries.

And that's why we ask for more clarification, guy. It could or could not have anything to do with the blanking circuit itself but some other part of the system. We need the dev to give us more detail on their reason and what information they used to reference it. I said the thread was looping back to the "circuit exists" point. Not the later *actual* point of debate. We all know it has a blanking circuit.

I’m surprised they even put it in when the MiG has nothing to do with this information

Ok, einen ED Account habe ich demzufolge höchstwahrscheinlich noch nicht, da ich mich wie gesagt nie angemeldet hab. Das geht aber problemlos oder?

Hello everyone. The game is updated to version 2.9.20.15384 (24/09/2025). I launch the game and try a mission I created with the new "Mig-29A Fulcrum." After a very long wait, a Windows window appears saying the game has stopped working. Obviously, the game worked perfectly until yesterday, and I haven't done anything new on my PC since yesterday. I'm attaching the log file. However, since I updated the game to the latest version, the loading times to get into action have gotten much longer (well over 5 minutes), so much so that, just before the game crashes, a very long wait seems "normal" to me, and then... everything freezes!!!!! dcs.log

As per title, why when im taxiing do i get low frame rate compared to all the other maps? Im running a 4090 and a 7800x3d using HP Reverb G2 dcs is also on a dedicated wd Black 4TB m.2 and theres loads of space free Once im in the air it seems ok. Previously i tried the Phatom and it crashed several times before i even moved from parking. Again all other maps seem fine.

As per title, why when im taxiing do i get low frame rate compared to all the other maps? Im running a 4090 and a 7800x3d using HP Reverb G2 dcs is also on a dedicated wd Black 4TB m.2 and theres loads of space free Once im in the air it seems ok. Previously i tried the Phatom and it crashed several times before i even moved from parking. Again all other maps seem fine.

My video here goes through least fuel consumption speeds for each altitude

After update when game is loading the the cursor starts fkickering, goes big to small also game stutters with it. I also upgraded video card to rx 7600, so that could also be some problem. Settings are set to default in AMD software. Any ideas what to do

@BIGNEWY, this is an issue more associated with the Mission Editor. How would a track file & log help in this regard? I'll work on it but the results may appear disjointed.

AH! They have to detect a target. Gotcha. Thanks. I did tell them to fire on a spot IIRC. (I actually can barely run this mission on my machine ... yet i want to add infantry and support units) I found that the rearming takes 30-40 seconds per missile. By the end of the battle they haven't fully reloaded.

If you check the controls indicator (RCTL + Enter) or the in-cockpit torque gauge, does it react when you keep raising the collective? IMO it's really important that you don't move around the ground with a skid still in contact with it. That'll feel like a completely different flight model and will only teach you bad habits. Keep pulling the collective until you're really and truly airborne, and adjust collective as needed to stay airborne. In your track, when I take control, the helo will do a stable IGE hover with a touch above 70% on the torque gauge, and with 75% it'll climb a bit, see track. Gazelle_Hover.trk

Немного подушним Для писателей руководства: 1. Пункт 3 и 4 / 8 и 9 можно слить в один. 2 Те же пункты. У самолёта нет правого/левого крыла. Крыло одно

Oh, I didn't see that. The prefix C (or A or B or other) is only used on certain maps, for example PersianGulf. In Causacuse, it's not necessary, so you should write it like this: parking_id = { [""] = {1, 31}, }, For comparison, I'm sending you a parking that uses the prefix C.

Не вводите людей в заблуждение. Кнопки "связь" в настройках нет, есть категория, а кнопка "Микрофон, кнопка радио" как раз по умолчанию назначена на комбинацию "Ralt + \".

That is because mouse actions and head movement on the UI isnt really captured during replays by DCS. That also leads to the tracks not working as expected, for example the aircraft taking off with a dead engine and not firing any weapons. You can either control the the Jester Wheel via keybinds (for example the CW/CCW/Enter binds) or recreate your actions while the replay plays by pressing ESC and then mouse clicking on the right actions.