virgo47

I've just spent around hour of hunting this strange behaviour, why it happens, it wasn't easy to google the right keywords, but here I'm after all, removing Config from the mission file helped and I'm fine. But I definitely consider this a bug! Why would a mission creator force his custom snapviews upon me? That doesn't make any sense at all. While we're at it - I see two clearly snap-view related files in the Config/View directory, the other two (Server and View) - are these fine to delete as well? Is there any possible added value in Config/View in the mission file or is it just a misfortunate mission editor behaviour?

I also struggled with the central smoke. I'd say this is the best thread on it: I found it a few minutes after I figured it out based on this thread. All you need is: CB Armament System Power Switch ON Weapon Button Fire Safety (off) The speed above 310 give-or-take. There is the Stand alert signal - but not if you switch the gunsight off in your L-39C. Fire to trigger on and off. As mentioned, off works also only above that speed, because it goes via gun systems. So a bit tricky, but doable.

@upyr1Yup, I ended up with music in DCS muted as well. I liked the intro music, but it's not a big deal really, everything else works fine - even in the editor.

Music in mission editor? That is definitely not a good idea. I realized that the first moment I started to work with messages and sounds. I would not miss any music in editor even when I don't work with sounds. It's reasonable to turn it off in the mission editor, I'm surprised this is even an issue.

I tried it and it definitely is less annoying and more rewarding - even with that robotic voice... which I actually understand. Thanks.

Exactly @Rudel_chw, I'm glad I'm not the only one feeling this way. I eventually figured out that "throttle up with brakes + climb steeply at first" but it is very rigid indeed. Not to mention the gates later for which I wish at least the next gate is clearly marked so the player knows immediately they missed one: Sure, after couple of hours with DCS training missions one eventually develops that feeling "hm, I haven't heard from the guy for a while, I should definitely go and find the big missed gate now". Now, even this can be considered fun to a degree... but that's it... it's only to SOME degree. After that it's not much of a fun. But hey, at least we can fly without getting killed on every crash, right?

@upyr1 Yeah, that would be my wet dream too :-)... when I get lost going back for the missed gate, sometimes I'm not really sure which way to go next. Now this would probably not have happened if I hadn't have to go back for many kilometers in some misty mission + I should probably know my direction better, but in any case, three colors would be totally ideal. But the next gate being highlighted clearly is the most critical part.

This is the first "answer" I googled to that question. Why people so happily answer "never mind, I got it!" and disappear for ever? The answer is in this thread: https://forum.dcs.world/topic/125585-data-during-replay-switch/ It is in Special options for L-39, but these are available only outside of the game, so you have to go to main menu to set it. Fast toggle on some keybind would be great, but it's not a big deal - especially when one just wants to get rid of it in the first place.

I totally agree, I can more or less do the course, but if I miss the gate, then the mission is not following me, so - if I want to hear that lovely Russian voice and learn I did a хороша работа - I need to follow the distraction - whether I want or not. I like flying free practice too, no problem with that, of course.

In training missions it's very easy to miss a gate narrowly and not be sure about it. One has to fly away for a while to see the gate "grow" to see the mistake. And also, one has to be aware of the possibility. I'm now constantly questioning myself "did I really make it properly?" and checking the situation in pause, which is not adding anything to the game (or simulation). Simply marking the next gate with a different color would help tremendously. Often the next gate is very close, so it does not visibly grow. Especially missions with pattern turns/circles are prone to narrow misses. I realize it's my mistake eventually - but being able to know I'm still good or not immediately without going on and thinking "hm, there are no messages for a while, probably I missed one", would help a lot. I believe a color of the next gate is not a big feature to implement, but it's a big feature to have for a trainee.

I have a strange problem with second training mission - Circling Pattern and Landing. For the first two days I was trying the mission I had no problem (beginners luck I guess), but today, I'm a bit quicker, I know that everything is set, so I go on and take off... and no gates appear. I tried it couple of times, once it appeared but I immediately missed the second gate without even seeing it, but otherwise I have no luck. It says "Clean up the jet..." but no gates. I was investigating further, it probably helps to start with wheel breaks engaged. Also, I'd normally wait a bit for the flaps (cleaning the configuration), but they seem to be crucial to display the gates. I consider this timing super silly - I'd make it through the first gates OK if I saw them from the get go... Instead I often get the gate shown way over my nose - so OK, I know I screwed up somehow, but the feedback is way too late and totally useless. Do you have any tips to make it more consistent, or is it only "rinse and repeat" using the only right style?

I'm flying it and I plan to fly it more, no problem there, but sure, it is annoying. I also use Pause a lot (not active one) to keep the titles there longer to read them, at least for the first few runs of a new mission. It's annoying, definitely. Very.

Thanks for the replies guys. I know about the modified mission, but I can stand the Russian voice, no problem - I eventually learn what he says (or remember the text) after all those repetitions of the missions. I was just genuinely surprised that ED gave us ONLY Russian voice-over - which feels rather silly, really.

There is not as far as I know. Even worse, you have no indication that you missed some mandatory gate + the next gate is bigger, but that is not always clear enough from closer - different color for past, current and future gates would be even better. I don't remember how many times I flew the training mission and nothing was happening because I narrowly missed one gate. Very frustrating. EDIT: I made a wishlist thread about it here:

This is exactly what I'm just looking for - to adjust existing snap view - which is a killer feature especially for non-VR/non-tracking users - one has to recreate it from the current position. Ability to snap+stay would be extremely helpful for these cases. And funny, I got to this thread via search for the meaning of " Cockpit panel view in" as well, it seems it just works like Custom snap view 0. Not sure what else it should do.

I've just bought L-39 Albatros an I was shocked it's only available in Russian. It might have as well be only in Czech (as it is a Czech(oslovakian) plane anyway) - at least I would understand that. So it's reading only with annoying through the radio voice, which is a pity, compared to free or FC3 planes. I hope the rest of the surprises will be only for the better. BTW: From the long-term users, what is the experience with released module (not in preview anymore) - are there any updates/improvements ever done, or are they generally fire and forget?

Hello guys... I'm not sure how realistic it is, but when I compare the view from the Su-25T cockpit and view from the outside (F2 or other external view), the difference in contrast is often extreme. Let's talk about my "favourite" Training mission for gun pods, where I have to hit something black on black. I'm not sure whether it depends on my setup (Win10, RX570), but it looks like this: The same stuff from outside looks like this (zoom is not exactly 1:1, but I hope the idea is clear): The thing gets even more obvious as I get closer - I literally shoot blind (I navigate based on incoming fire actually), but from the outside the vehicle is pretty clear. Now, I understand the glass (or any optical medium) can darken the image, but are Su-25T pilots really that much crippled in that contrast like I see on my screen? I'd bet the human optical system can do better. But it can't when my screen is already showing me black on black. Is it only my system or do other people have similar experience? I understand the "realism" in simulation - but in reality I can see much better than this, even through pretty dark windscreen on my car for instance. Sure, I have no Russian HUD, but my eyes can adapt in real life. But they can't when the game decides I can't see anything before my eyes actually see it.

I'm not sure about the Score Window for Huey, but normally it should show the Score Window (the one shown after the mission as well) - for whatever reason I've got this under Su-25T plane I'm just flying, instead of the UI Layer where I'd expect it. BDA show/hide is "battle damage assessment" - those are the messages shown on the right side when you damage something. It probably has to be enabled in the Options as well (available only in main menu options, not inside the mission).

I got here via search when I decided to try some saturation for pedals with Su-25T (will see about other planes). My reasoning is that even with a curve even hardly noticeable moves with feet are quite noticeable in-game, especially on the runway. I'm still not settled about the saturation, so I guess it's personal. I'm not sure I need 100% rudder with this plane during flight anyway (but I can be mistaken). There is another phenomena with these pedals though - I don't know whether it's the pedals or DCS, but when I start playing I just pause the game and move pedals left/right from one extreme to the other because the first moves are extreme. It goes to 100% in-game when I'm far from the end of the rails. Perhaps it's some calibration thing, but I always do this before playing for real. The effect is clearly visible with control indicators and also in axis assignment, it is kinda over-saturated at first.

This one really is funny. Some sources, including Wikipedia, mention 9A1472 (one, four, ...), other sources - including DCS - uses 9A4172 (four, one...). "Google battle" with search result count is mostly 50:50 (not that it necessarily indicates where the truth is), so I have no idea what it really is called. In any case, it makes the searching for more info more... interesting, I guess?

I use current openbeta 2.7, but even with non-beta I had the same problem during my roughly 2-months of playing DCS. I use Su-25T, but the smoke seems to be the issue. Granted, my RX570 8GB is oldish, but normally I have 20-30 FPS which is OK for me. I lowered many details, but I don't know what makes the smoke less dense. In my case when the smoke is too much, the game freezes with Steam overlay FPS indicator showing anything from 1-5 FPS. The sound goes on, if I was shooting guns, their sound is stuck. I can go to task bar and end the application, in which case it actually switches to DCS with its dialog whether I want to quit and this works. But nothing else does. Except for quitting and sound, the game is totally frozen. GPU runs around 100% at that time. It always happens with smoke or some similar particle effect in the screen. Happens when I switch to ground unit that is smoking, or when bombs explode, when my plane is on flame, etc.

I prefer binding on joystick even in clickable cockpits (at least at this moment) and noticed after the first cold-start tutorial all these things - flaps, strange Radiator oil/coolant behaviour (doesn't stay in open/close position) and canopy (both binds open). Flaps is cosmetics mostly as they step nicely, canopy is quite bad, really.

I found this topic after experiencing the strange behaviors of these toggles. You can click them with the mouse - and they stay in Open or Close position. But using keybinds or joystick buttons they return to neutral after release, which is inconsistent with cockpit clicking. Auto shortcuts works fine. TF-51D seems to have multiple keyboard/button bugs when not clicking with the mouse, this seems to be one of them.