virgo47

TL;DR: Does not relate to SnapViews.lua saving. Annoying FOV after mission load, but not serious. Now the details: I guess I got lost in my experiments with default view and editing SnapViews.lua manually while doing so. This actually does not have anything with saving the file. Every time I set my preferred view and its FOV, it is saved nicely into the file, but without HOTAS sync the initial FOV is always higher. E.g., default view FOV 20 will give you 28.2 after the mission loads, 89 will show 108.8, etc. It's not even linear! With HOTAS sync, this can be mitigated, if you have a zoom axis and it is centered perfectly on your preferred FOV - which is possible with some tweaking. Strangely though, some planes (e.g. TF-51D) do not read the zoom axis after the mission start. So you still need to tap Zoom normal or touch the axis. No problem. It would be nice if the FOV after mission start was the default view FOV. There clearly is some relation - can't it be 1:1 for a change?

Hello guys! This has been the first time I'd ever flown F/A-18C Hornet - and I used the first training mission for that. After the talk, I started to fly through the gates. I don't mind gates as a training prop, I know them from Su-25T, there are some issues with them (especially when you miss one ;-)), but in overall they are OK. However, after a few gates here, you can't see the next gates in the bright sky - unless you know the mission by heart I guess, which is not the point. You still can't see them. Strangely, the next gate does NOT scale up as it does in Su-25T or L-39 training missions. I guess this smallness is the biggest problem. It would really be great if the color of the gates could be adjustable - be it a player, or just by the mission author. E.g. red would be better here. Please, consider these things, because the mission would be quite fun and instructive - but when you see the gate too late you have to fly a circle to get to it again and it really sucks. The Hornet seems great, BTW, love it.

Exactly, this is for explicitly saved profiles which can be done from the dropdown menu accessed with the little triangle next to the device name in the Controls setup. This way your files (e.g. for backup reasons) are nicely separated.

EDITED: Default view is fine, just initial FOV changes for whatever reasons. I've just encountered a problem with default initial FOV. If I set the FOV for in-game and save the default view, it shows the right view under [13] FOV. But if I edit it in the file and change it, the plane has a different initial FOV after the mission starts (somehow higher, there seems to be some shift). Strangely, when I change the FOV now and save it again, the right default FOV is used as an initial FOV after the mission start, again. Even if I change anything else in the file, the default initial FOVs are broken - for other planes as well (probably for all the planes)! This means that any backup/restore of this file always breaks all the default starting FOVs. After the first fright (and first version of the report) I tried Zoom normal and the expected value of FOV is set (relief). Initial FOV can be worked around by zoom axis curve to tune the center position FOV, with the HOTAS sync at the mission start enabled.

Yeah, you're right - works fine on the latest version. I'm sorry about it, I need to get used to manual updating before reporting anything. I'm looking forward to auto-updater for MT or MT becoming the mainstream version.

I'm curious about the Y-axis range and how is it modelled. For Su-25T in particular, but the question is probably related to other planes too. I have my stick with some curves, but both X and Y axis are set in the same way. If I pull the stick completely, I see this in the controls indicator: If I push, the stick in the cockpit stops moving, when the indicator shows: But even beyond this point, I can see not only indicator change, but also see/feel the action, all the way up to this indicator status: Looking at the outside view, the elevators clearly move in the whole range. Why does the indicator look asymmetric and should I care? Is the action realistic? Why does the stick stop mid-way while pushing? Is this in any way related to Special options like this one in F-5? Thanks for any insight into the topic. And yes, I know that 99+% of the time I don't push that much and planes probably don't like it either.

Revisiting this after many months with 2.8 and the contrast seems better. Pictures are not aligned, this one is more up close, but it is also overcast, like before. But the brightness and contrast are both much better and I'm actually seeing what I'm shooting at. So I guess it's somehow resolved.

I've tried Su-25T after some time and I've noticed that there is one too many г - one of them obviously instead of K.

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.