virgo47

Ah, now I understand what you meant... on the fly in the editor and map, got it.

Yeah, I report it as a bug, because the tooltip clearly lies to us. It's not critical and it's true I don't need to restart the game after the change. But I'd be careful calling it "on the fly" in case of flight simulator. Gameplay options are not available inside the mission - for obvious reasons, as it would be difficult to magically change the instrument/cockpit. Still, for players switching between eastern and western planes it would be nice to have this as a plane setting, not a global one.

I know that Kursant campaign warns about Imperial vs Metric, but I believe it's a bug that the cockpit air speed gauge totally changes when switching this option: Notice what the tooltip says - "NOT change indication in the cockpits". I believe that switching the gauge from metric to imperial for a single plain should be in its Special section. Doesn't the Units option also change things in the editor, etc.? Why can't I have Imperial selected for other purposes and stick to metric for L-39 (and similar aircrafts) only for immersion?

It does work properly now in openbeta! Yeah! https://www.digitalcombatsimulator.com/en/news/changelog/openbeta/2.8.3.37854.1/

Thanks for the clarification. I don't know why I haven't checked the manual as I mostly do. P-51D manual says it clearly - they are spring loaded indeed. That means the bug is not affecting me as a keyboard user, only the mouse user, I see. It's not a biggie then. But of course, the things like this are confusing.

Hi, I noticed people mentioned this in other threads, but I don't see the one for it, so I'm writing it. Both switches for Radiator Air Controls have 4 positions when used with mouse - and can stay in any of them. But with bindings (e.g. LAlt/LCtrl+A/S) these seem to be spring loaded - plus there is no binding for the central position either. EDIT: The binding behavior is correct, the mouse is wrong.

Flaps are fixed, I can confirm that, which is great. But I can hardly hide my disappointment about radiator switches and canopy open not working via keyboard/buttons. But at least something was fixed. Thanks.

Hi, Flappie, thanks for your time! I replayed your track and it has cut transmission on my computer - see 1:15 in this video: Now, to correct the description - changing channels to wrong and back doesn't seem to affect it (my mistake), but I can reproduce it super simple even with empty mission, Kutaisi hot start, I can communicate with tower (\ or radio thumb button which I use predominantly in L-39, doesn't seem to matter) - everything works. Then I flip RDO switch off, try a single communication... dramatic silence, as expected... then I turn the RDO back on, try the communication again - and the result is cut transmission, as demonstrated in the video. I attach the logs from the time I replayed your TRK. I can create my TRK as well, if needed. I don't think I have crazy custom modules - just Tacview and DCS-BIOS for external controllers. And A-4. dcs.log.zip

If I start a plane (L-39C/ZA in my case) on the Caucasus, I try to communicate with the ATC (R-832M menu, F5, F1, F3 to request startup)... nothing is heard because I didn't turn on the radio or have a wrong channel. As expected... OK, I set it all right, try again and this time I see the response message, but I only hear the first word (if at all) from the actual voice message. All the subsequent messages have sound cut off after they hardly start or I can't hear anything at all. The text messages are fine. No other sound issues on my end, this clearly is somehow broken after a failed previous ATC comm attempt. Anyone else with similar problems?

Perfect, thank you very much - that is the name I was missing. Now I can easily find the explanation and it all makes sense.

Hi Flappie, thanks for response! My problem is GPU, not CPU related. It's not a big deal, just surprising. A few numbers for illustration. Standing on the RWY in a hot L39 doing nothing, totally empty mission - my CPU/GPU % is ~16/80. When I turn on the NS430 popup with its default (CDI) screen: CPU/GPU is ~17/97 (CPU is clearly a bit higher, but not much, but GPU jumped by 17%) With NS430 on a map screen: ~17/95, no change in CPU, but for whatever reason, this screen is less GPU intensive(?) The terrain screen - more or less as the map. That means various menu or other screens are easily more GPU intensive than map/terrain. But the popup itself takes anywhere around 15% of my humble 3060 GPU. I'm attaching day and night mission tracks, but while these reflect the actions, they don't show the resizing of the popup which creates many more brightness "effects". BTW: As for the cyan border mentioned - I'm not implying it should be everywhere. The wrap-over of the pixels is the problem (seems like some +/-1 error to a humble programmer like me). Even in original GNS430 the map upper edge does not have the cyan border - it's OK. That's why I've created the following video demonstration as well: Hope that helps and shows it clearly enough. ns430-night-brightness-problems.trk ns430-brightness-strobing-problems.trk

Hi guys I always wondered what are the thin sheets extruding from the bottom of the horizontal stabilizer on L-39? I couldn't find the answer anywhere, perhaps because I don't know the right words for the question. Also, what kind of antenna is it at the end? I've seen a picture with L-39 antennas in the real-life L-39 manual, but there is nothing at the stabilizer tips:

Answering the final unnumbered question - how to switch to another waypoint. I couldn't find it because one has to search for words like "leg" and "activate". Press FLP - to display active flight plan Push right knob - to show the cursor/highlight Rotate big right knob - to select the destination WP Press Menu - Activate Leg? should be highlighted Press Enter twice, done

I don't understand it... on the module page https://www.digitalcombatsimulator.com/en/shop/modules/ns430/ it says in one clear bullet: "Serves as both a communications radio, navigation radio, and GPS receiver" Does the module in its popup form do anything besides GPS? If not then the sentence (and also others in the description) should be changed not to deceive the customers. There should be clear clarification what is and is not modeled. Don't get me wrong, GPS is fine, but I expected more from the description. If it does offer anything from COM/NAV, it is not covered sufficiently in the manual. But it seems it really does not have any COM/NAV. But that you likely find out after the purchase.

Hi, I'm pretty new to this module although I watched some videos and tried to read some docs, many things are a matter of in-game experiments, because the NS430 manual is quite brief. I have a few questions with a hope that more experienced NS430 users can answer them easily: I'm using the popup version. I was surprised that the popup took the my GPU % from 85% all the way up to 100% (so perhaps it would want to take even more). Is it normal? What is so GPU intensive on the popup version? Was it always like this or can this be some regression? The issue with overall DCS darkness with the popup was reported... but I also have a problem with NS430 display being too bright in the night. Letters separation is very bad, but this seems to be a simulation issue (glow is added), not the display content. So I wanted to adjust it - but couldn't get any reasonable results. With some settings, the cyan borders suddenly go away - is it normal? Also, should not Auto backlight/contrast do better job? In the attached picture, (1) I wanted to change Auto to Manual - this works very strange, first ENT allows to change the value from Auto to Manual, but when I confirm, it flips it to the other value - not the one shown. In other words, to change the value you just press ENT twice, but that seems counterintuitive. It's still value input - why does it choose the value that is not there? There is also the top line pixels (2) mirroring the bottom of the display - some of them blinking (e.g. mirroring blinking MSG). This is not present on every screen, sometimes it's covered by a cyan border. But it's on NAVmap. Is this a bug or reproduction of bug from a real GNS430? Finally I have one navigation question I couldn't find answer to yet... If I have a flight plan and I'm navigating to let's say WPT2, is there a way to quickly switch to another leg and use next WPT3 as my go to waypoint? I know it's not really a following path, but still, I'd love to know how to switch WP quickly and so far didn't see it anywhere. Thanks for any answer

I just wanted to open a thread whether it's normal that cursor moves so slow on the map - but this seems to be the problem. When I turn the mousewheel slower, it actually works better/faster. When I go fast the cursor is - counterintuitively - super slow. The problem is even more mysterious because I hear more/faster clicks, so one does blame the cursor sensitivity or what, which is not the problem. Also, too bad I can't just press the key and hold it for wheels, some sort of auto-repeat would be a godsend. Using a POV-hat with some modifier works fine for selecting pages, but it is a pain for moving the cursor (or entering letters for that matter). I know it's not "realistic" per-se, but we can't really touch the unit either.

Yeah, if I had known about this gamma bug I'd have probably waited with a purchase as well. Otherwise a little neat module, especially for older planes. EDIT: I played with the popup a bit, needed it larger for a while and noticed that the screen brightness changed. It also changes when one of the blue menus come up and go away. And when I made NS430 popup smaller, the whole screen started flashing crazy fast.

I've noticed this too for hot start quite often. My custom simple mission with "Takeoff from parking hot" always fails the generators first, then I have to wait and re-enable the autopilot. The same happened with Instant Action called Free Flight that actually started parked hot at Sukhumi. I'm using Synchronize Cockpit Controls with HOTAS option and when I turned it off it didn't happen. I thought I have everything set as I want to - throttle up, collective down... no other axis does anything, right? Wrong! On my TM16000 the axis on the base was predefined as Main Rotor Brake Lever! And depending where this "unused" axis was I got the generator failure (or not). Now sure, the helo could hot start a bit more stable, engine needles are doing funny stuff when it starts and main rotor gets to 90% which makes me nervous, but not having the brake lever accidentally bound, moved randomly and synchronized to the cockpit at start... that seem to help.

Just chiming in with some translations from the Russian cockpit (HKTB is in fact more like NKTV): H=N направление (~napravleniye = direction) K=K крен (~kren = roll, bank) T=T тангаж (~tangazh = pitch) B=V высота (~vysota = altitude) Of course, the meaning was covered by the previous replies, but I was really curious what those letters mean (seeing H and B I guessed these are really N and V but in Cyrillic) - and I wanted to know the words in original. As I couldn't find it anywhere else, I'm just adding the info here.

Guys, I'm not sure how many of you are flying L-39, but here is my main page for it (TPZ file is attached): Now, as mentioned previously, there is also a companion AUX page where mostly the lower middle section is replaced by engine and emergency controls - but it is prohibitively inconvenient to import it as of now, because it shares a lot of buttons with the main page, but these get disconnected (Value ids are not merged, but duplicated, hopefully Touch Portal guys will fix that). The ideas behind this page: Definitely use tablet, mobile phone is not suitable for any serious page. I wanted to control both L-39C and ZA variants from a single page. I could make two separate pages (maybe I will), but most of the controls are shared. Green tinted buttons are ZA only, so they are easy to distinguish. Controls are roughly positioned as in the cockpit - of course with some limitations. Main switches are in L-39C layout, two ZA switches are added under them on the right. Armament buttons are kinda ZA layout, but left vertical panel and the pedestal are merged. But everything is there, even Deblock guns, which otherwise has no control shortcut in game! So now you can shoot at planes even under 400 km/h. Thanks to the later DCS-COINS updates, we can also control various knobs like light intensity! But this is only one way, because Touch Portal does not provide the other direction. RESET Critical Buttons can be used to flip first 10 main switches + some other stuff (like Flight recorder) on and off, to help you sync the page with current flying condition. It's not perfect, but better than nothing. Similarly, you can fix flaps and gear state by tapping on them. Heading is true, in the L-39 fashion, speed is metric (as it should be ) but altitude is only available in feet. There are no meters provided by DCS-COINS/BIOS at this moment. I hope you will find the page useful. Let me know if you have any problems with it. If you want to change something you're free to do so - it's up to you, I like it this way. dcs-l39-main.tpz

I have no TrackIR and just out of curiosity was checking options using Android phone. That lead me to opentrack. I tried it with PC camera (actually a DroidCam using the Android phone) - but the results were less than ideal, very jittery. But perhaps the problem was using neuralnet in opentrack with a camera (and probably not placed and lit ideally either). Then there were other Android options for opentrack: Head Tracker for OpenTrack - free, but I didn't get it, it seems it's using the accelerometer, not the camera, but I may be wrong... TrackAR for openTrack (funny, how everyone is caplitalizing different letters in the name of the project ) - around 3 EUR and SmoothTrack for around 10 EUR I went for TrackAR and while the UI is underwhelming (no axes shown) it actually worked quite well for me. So I spent a day to make it run and another weekend to make a video about it. Maybe it will not cover your situation, but I hope it helps: In my setup I wanted to use a phone under the monitor, either horizontal or vertical. And I was also interested in "hybrid setup" - for some flying I'm lazy to setup the head tracking and want to be able to disable it. All these things are covered in the video.

I have a similar problem. I'm experimenting with OpenTrack for the first time and I can stop tracking there with a keybind - but that does not allow me to move the view with mouse or with already assign buttons. I have to go to Adjust Controls and click on the dropdown menu triangle in the TrackIR column header to Disable it in there. Having a button shortcut would be great. The problem is that DCS has no idea I paused the tracking in the opentrack. There should be a way to pause the tracking actually in DCS.

When I was discovering Caucasus aerodromes, I always went for wind 5 m/s roughly in the opposite direction of the preferred runway for that aerodrome. That reversed most of them, and turned on the right NDBs - or disabled NDBs if they were only on one side. I have the following kneeboard pages from all this testing, I'm not sure how understandable they are without explanation. I also used and tested the information from those great DimOn frequency/aerodromes maps. Mine are much rougher and are also more focused on L-39 (like the radio channels).

I set up the hot start mission with wind to reverse the preferred RWY which is 32 for Soganlug. I was already on the runway. But whatever runway you go, it doesn't make sense. It sends you around - which is expected, but tells you to land on the opposite runway than the one you start - which is bogus.

No, no... I'll add the image. I asked Lochini and it navigated me to roughly my current position - as you can see, it makes sense to land on 13 from there. But when I asked Soganlug, it sends me all the way somewhere to the point (2) (roughly) - and then it sends me to runway 14 (blue arrow). How does that make any sense? I'm already way beyond runway 14, I'd need to land on the opposite runway. The messages for both directions have reversed landing runways for Soganlug. As for various aerodromes, I tried them all on Caucasus, without wind and with wind in both directions. I compiled my personal kneeboard for that and I know that some aerodromes are one way (Gelendzhik, Sochi, Batumi and Nalchik) regardless of the wind, but Soganlug is "normal" except for the message. In the mission on the picture there is no wind, Soganlug prefers RWY 32 in that case, Lochini RWY 13. That's also the direction of the hot start on each aerodrome if you create a simple mission for it.