virgo47

In case of NS 430, I'd be surprised if it worked in 5-10 years... Now with MiG-29 I give it a bit more chance, but I'm still waiting for the radio and comms advertised on the product page. As for this report, maybe the strobing and brightness problems were addressed? I'm not sure, really.

Just to clarify, I was a not hovering or something, I was just making the final turn at a few hundreds of ft AGL. Not close to the ground/water at all.

Also, when attempting the final landing to the frigate, I accidentally overflew it and Peter/CO was happy I landed and I could finish the mission, still in the air. Probably some altitude check for that trigger would be handy.

I noticed that the same audio is used for these two messages: The second message has the audio from the first one repeated.

I can return to DCS, no problem with that. The problem is that when I switch between two apps on different monitors, e.g. a browser and DCS, the DCS goes behind all the other apps on that monitor. It didn't do that with Windows 10. It's not a problem to return to DCS, just that DCS is not left on top of other windows that I don't alt-tab to.

Definitely a Windows 11 issue. I've never encountered it with Windows 10, but after the upgrade (which I'd willingly), any time I alt-tab from DCS, it goes to the bottom of all the apps. For "normal" apps it shows alt-tab switcher right away, for games (and I don't have exclusive full-screen, so DCS is as Windows-friendly as it gets) it first switches the game all the way back, without even showing the switcher. Then another tab-tap shows the switching widget, but DCS is already all the way back. The workaround is to minimize everything on the same monitor, so I can alt-tab to another app on the 2nd monitor and do my stuff while still seeing the game. E.g. to GreenShot/snip something, etc. This is beyond stupid, as most of Windows 11 is.

After some recent update, another terrain problem near the first one (Adana dam): The dip was not there before, now it's under water level. And even from this position in F2 view I can still confirm that the first problem ("miniwaterfall") is still there. The island is actually very close to this position.

This indeed is very confusing, especially on the first few occasions. After that, one is prepared to understand what is going on, but it's still an immersion breaker. I'd rather have no ships than ships that "inflate" in front of me.

I was thinking about this as well, but this happens after all my internal tanks are used a bit, none is full. And we're talking of ~20% equivalent of all internal fuel lost in 10s. Is that realistic? Finally, if this really happens legitimately, shouldn't there be some outside effect, spray or something?

I've been around for just a short time (relatively) and have seen some Czech guys here and there (Youtube, forums), and there is a CZ channel on "DCS by Eagle Dynamics" Discord server, but nothing for Slovaks. So I'd love to hear from Slovak DCS guys, especially from Bratislava (where I dwell). There are a few reasons why: We may just go for a bear (or Kofola or whatever) and discuss whatever (planes or politics). Maybe you have some HW I'd love to try before I buy (I'm not ashamed to admit this is one of the reasons for this post - but not the only one!). I don't know. I don't want to propose a wing/squadron because that asks for a lot of time and I'm not sure I have that one (besides some obligations to another squadron already). So perhaps just talk about DCS in our "sprache"... I mean "jazyk". If you see this and you are for anything from the short list above, chime in! Or add some more ideas to the list!

I found this thread after getting stuck in one custom training mission where it merely said to contact the ground crew with \ after the engine was started. Ground crew was totally deaf of course. I had to flip this switch up, as suggested above. Funny, there is also ICS binding (1st stage radio trigger), but that didn't help. The switch is the key.

I tried this mission a couple of times, but it stops responding after I set the distance in DISS. It seems that the following trigger "87 ID OFF-------------------------------------------" succeeds - the cockpit highlight is removed. But nothing happens after it. Track is attached. There seems to be a trigger with the check of one parameter to remove the highlight, but then there is check of four parameters, I don't know exactly what they are, so I suspect one of them not being met. But to me, it's unclear how to satisfy those. Mi-8MTV2 Training - Doppler.miz_11102025_01-57.trk

And a checkbox "run by default". Joking aside, they are very slow indeed. They don't hurry from fire either.

This was originally mentioned in this thread, but I believe it's a bug: Original observations: I've experimented with the drop tanks during the last few days and they are definitely a bit peculiar. I've written a script to see the fuel level in messages regularly (only overall, but better than nothing) to see whether the fuel somehow disappears or what. I always burn a bit of left-wing tank to get around 75 mark and it never gets to F, so I hope there is no problem on this front. The mission is my custom free flight and the stories vary: I've flown ~angels 20 on the left drop tank, I switched to the right tank drop tank and lost fuel pressure within seconds, although there was no chance I spent the whole fuel. Repeated on at least two flights, no idea what was wrong. (I have no info on the fuel level for these cases, it was before I added the script.) I've active-paused the plane after the mission start at angels 6, fuel 157% (100% is for full internal fuel), went over all the tanks, starting with a bit from the wing left, then the combats one after another... fuel pressure dropped when expected based on the fuel %, I switched through all of them and went all the way to 0. The plane "flew" for over 5 hours, no problem. (I used time accel of course.) I went over Caucasus again, ~angels 30, used the both left and right drop tank just a bit, then switched to the right drop tank for good when I was ~140% of fuel. The missing 17% went a bit from the left wing and both combat tanks. Neither of the combat tanks could have been empty by this time, it's mathematically impossible. The fuel reported going down all the way to 92%... it worked like there was some kind of interconnect between the drop tanks, because the moment the fuel pressure dropped, I switched to the left combat tank - and it was empty too! I have no explanation for this behavior, the only normal case seemed the experiment in active pause. I don't know how altitude is involved in all this, reportedly the altitude can make the engine management harder, but I guess you want to use drop tanks first even when you escort bombers in high altitude - and you probably want to fly high to fly further, but I'm not an expert on this. Later test with track and fuel message each 10s: I've made another test, this time at higher altitude, although I'm not sure how important that is. First I went for active-pause test and accelerated time, no problems at all, switching went exactly as expected. Start at 157% of fuel, switch to left combat tank at 152%, then - as calculated and expected - fuel pressure dropped around 123%, so I switched to R combat tank, and then around 95% (first 5% went from the left wing tank) I switched to internal tanks. No problem. Second time I decided to fly actually fly it and also switch more often from tank to tank, but make notes what happens when. To my surprise, things went wrong quickly... again, around 152% I went for L combat tank, then around 143% I switched to R combat tank. I lost a plane for a moment, but I don't believe the maneuvers were that excessive, but... suddenly I lost 50 gals in 10 seconds: There is nothing in the Score window, I wasn't sure about some malfunction... I made and checked the track again, whether I'd see anything in those moments... nothing obvious in an external view. But 50 gals were lost. Strangely, from the gauges it seemed like some internal fuel was lost as well. So, naturally, I suspected the maneuvers. I restarted the mission and tried pretty crazy things... but I couldn't replicate it. Track file is attached. p51d-lost-fueltrk.trk

Yeah, the problem with these things often is that at first one doesn't know whether it's a bug or not. Me, for instance, could not clearly see what and when is what happening and it took literally hours to somewhat replicate it, not to mention writing some internal fuel script output that I wouldn't have written otherwise. I'll try to repost under bugs although my faith is not strong. But without a bug report it's even weaker, of course. I'm on it. Edit - here it is: