virgo47

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.