virgo47

@Rudel_chw Check this:

Thanks for the info... it's a bit sad, of course.

In a cold UH-1H I just turn on the battery and set up UHF + Intercom. I want to use UHF preset for the current aerodrome. When all is set, I try to contact the aerodrome and ask for startup permission. Immediatelly, the UHF selector goes from preset to MAN and the frequency display changes for a while - but the communication does not work. I don't have this problem when starting hot. Track attached. uh1h-funny-uhf.trk

Hi guys, I'm not sure if this is new or not, but with the latest patch the mousewheel up/down works totally inconsistent. I'd assume that mousewheel UP is "more" - more volume, higher frequency. If this assumption fails, I'd assume that it's less because... CCW (not intuitive with mouse at all) - but this is all wrong. Currently the mouswheel is inconsistent. Luckily, the mousewheel up and down do the opposite operations, so at least this is covered. Currently: NAV-COMM radio - mouse wheel up is CW, higher frequency. I like it. VHF COMM - mouse wheel up is CCW, lower frequency - bad. EDIT: is this connected to this? UHF frequency rotaries - mouse wheel up is CCW - bad. UHF preset channel - no mouse wheel - would be handy here, only clicking works. UHF volume - mouswheel up is CCW - less volume - bad. Intercom volume (the main one) - mouswheel up is CW - more volume - good. FM COMM frequency - no mousewheel support - would be handy, of course. FM COMM volume - MW-UP is CW - good! ADF gain and tune - MW-UP is CW - good! Just for completeness, I checked the instruments panel and overhead, mousewheel up is CW everywhere else - good! Please, fix this mess, because it makes the experience quite terrible.

I envy you guys... I still have only 6 there!

I'm not OP, but I fly Albatros quite often and I don't see it as a bug, it's a natural need of L-39 for regular trimming. EDIT: Tested it now with the current patch, trimming seems OK.

Hello, I'm fresh after today's hotfix. I wanted to trial the AF map (I'm actually grateful, we have this option, kudos for that!). Previously there was some confusion with Normandy - which was about versions. Now, with AF we've got another kind of confusion. After clicking on trial, I got two modules to download - the whole map and the SW part. Obviously (to me) I downloaded the whole map. Nothing happened. I had to download the SW as well... Now after a few trials and errors, one can probably figure it out, but it is unnecessarily confusing, often thanks to other errors: I had 7 available modules in the Launcher, yet nothing "available" was shown to me. Never mind, I'll try in the game instead. There were just 2 modules available in the game - both versions of AF map. "I want the big one!" Wrong... nothing happened. So obviously, I went for the other version as well. Please, don't ask me what the 7 available modules were supposed to be, I have no idea. It might have been something FC related, I just don't know. How should it work? Is it necessary to read quite extensive FAQ before one can use the map without a hassle? Does it work the same after you buy it? Why doesn't the "big" map automagically imply all the other modules without confusing me (as a (potential) customer) what I bought, showing me "smaller maps" as available modules as well? Or perhaps you should introduce some kind of info/help/tooltip right into the module manager. At this moment I have little trust into what I see in the module manager, especially when it comes to parts of bigger packages. Nothing in AF FAQ makes it absolutely clear... I understand I'll have only SW part in high-res, but why do I see it as a separate product I didn't want? Perhaps it's just a trial-related confusion, I don't know.

After the last patch, I like the new options and graphics on the map, but to me (as a programmer) it feels "synchronized" - one thing waiting for the other. The slot selection is VERY slow. The slot selection dialog should work fast, instead it feels like it's waiting for the map in the background to draw all the stuff. The map enhancements during slot selection are great, I love it, but it should not slow down other things.

To be sure: Do you mean on the client or the server?

In the hunt for the answer, I found this video today as well. I also doubted the depressed position stays depressed without power (that is, after figuring out the DC power is needed), but this may be also DCS modelling thing - that it is toggle instead of push to hold, even when cold. As it is not my original "problem", I consider this issue solved. Thanks/sorry for your time guys, perhaps there could be power mentioned in the manual where the button is described (as it is in the real manual), but that's another topic.

That would be my guess as well. It doesn't behave this way in DCS, as it still toggles just fine without the power. But I don't know what the internal mechanism is. However, I've learnt something today (again). Perhaps it will help someone else if they find it.

My question in the last post was whether the IDLE switch depends on the power, I couldn't find it in the manual (at least not in an obvious manner), but yes, power must be on for it to operate. TM 55-1520-210-10, Change 17, 2-4 states: That explains why it works properly only with power. As I don't know how it should behave without the power (e.g. does it mean you can't twist the throttle to STOP? or just that the protection is not there?), I guess it's not a bug. You don't encounter this when you follow the procedure, because the power is always there. I was experimenting with throttle controls in the cold aircraft, that's how I got to this mess.

Stop switch is only the little switch above the throttle that unlocks the possibility to go below ground idle level. This is also the minimal level you can use with the axis, if it's lower it doesn't react to axis at all, but that one is a feature. That's where the key binding for throttle UP/DOWN come in (warning, mine are NOT default bindings, normally they are without LCtrl)... I opened your track file, took control and just using the throttle key bindings I could go to the STOP position, no problem. That is, in any position 1. press the Stop Switch (End by default), 2. press and hold Throttle DOWN binding (PageDown by default). It got to below the protected position (below the red line): The problem is, when I try the same in the cold started mission (mine or the first training), I can't get to that position - the STOP button seems to be depressed, but the DOWN binding doesn't go under the IDLE position. But this is not about how the mission is started really: If I go through the starting procedure, the helo is hot, I can go to the STOP throttle position again. So I started to experiment - and the thing is: If the battery switch is OFF, you can't turn the throttle to the STOP position. Is that realistic? It works fine with electric power, be it battery or ground power. Is that stop switch somehow electricity-dependent?

AFAIK, the throttle axis only works from ground idle to max throttle, and when one wants to go lower, we need to press the Throttle Stop Switch, and then Throttle Levers - DOWN again. This works fine when starting hot. But after the cold start, it does not work anymore. I depress the stop button and throttle down doesn't go lower anyway. TRK from cold start training mission attached. (Not much is visible, but I tried both the keys and mouse rotate.) EDIT - solution/quick explanation: This button's internal working requires DC power. uh1h-cant-stop-throttle-after-cold-start.trk

500 is a temporary error, I understand it is very frustrating, but you should try again. It is a bit shameful that ED can't figure out a reliable and fast enough logging to the account. Please, try again, it works for me now. Logging in is done by the launcher now, so give it some time to do so before launching the game, otherwise it will ask if you really want to start it before logging.

I know, I own it. Waypoints in FC planes are simplified based on the mission editor, you can't do anything about them in the plane itself whatever the plane can do in real life. Next waypoint obviously does something and the HSI reacts. So I just reported the current experience and inconsistency of the behavior.

Hello, great to hear from you! I'm attaching my "patch" for L-39, it's only default value changes - DCS-BIOS does not support it in their configs. My DCS-BIOS contributions are for different entries (mostly back cockpit switches) so if you didn't change the PP structure you can use the patch as-is. L-39.pp.mods

If you have any old panels, they will work, but the DCS-COINS actions there are obsolete and non-editable now. If you need to change something, just delete it and find the new version of the related action.

The problem is not that modules have TACAN on when starting hot. The problem is that no FC module used TACAN (I believe) and now F-5E FC behaves like full-fidelity F-5E start, without any way to turn the sound off. I believe the TACAN being on while hot starting at a TACAN-available aerodrome is a good default. Just like other nav aids being tuned to the aerodrome where you start. EDIT: But this should not be applied to FC3 aircrafts unless they support TACAN. Which they generally don't.

I see what you mean now, it's Audible Warning Reset action for FC planes. But that doesn't work for this one either.

You better say what action you mean, I have nothing bound to that and I'm not sure what it's supposed to do. I checked F-5E default keyboard config Lua, nothing with 'N' there either, neither in UiLayer keyboard config. So it doesn't do anything in the mission, I tried.

No, there are no TACAN controls, only typical FC waypoint up/down. I believe this is an omission from the full-fidelity module and the TACAN. I wasn't sure in my original post, but I believe there should be no TACAN controls - and no TACAN sound either. That would be FC style.

I believe it is. Probably the easiest thing is to simply hard-code the TACAN code silent, we don't have this kind of nav-listening in other simplified models either. This only seems to affect hot-started plane (ramp or on takeoff) on airfields with TCN station. No sound for "ground hot" planes, even on airfield with TCN, nor cold planes, nor flying ones, obviously. Video (first TCN code around 0:44): Test mission with slots clearly named, including yes/no-tcn in the name, is attached. I wanted to make a TRK, but while it seems possible to save multi-client TRK, there is no error when attempting to, the trk is not created. f5fc-test.miz

I went through most sections sans various View and camera-related stuff, do you know what exactly? Or by "Controls" you mean something else?

In hot started aircraft, the Next waypoint shortcut does something at first, Previous waypoint does not do anything. But after I select any of the modes available in the plain (1, 2, 4 and 7 keys by default), neither of the Next/Previous waypoint shortcuts work anymore.