virgo47

I'm going through a user's mission for the cold start on Godauta, with the NDB 395.00 and code XC. This NDB is in the map sector FH27 (or FH2873 if zoomed in all the way). I checked the morse code of the NDB of the Godauta - which should be the morse code for XC (callsign of the NDB). But I was surprised that the morse code of the sector (morse code for FH27) was heard instead. I don't think various planes should receive different Morse codes for the same NDB, so I assume this is a bug. Also, the loop of the NDB is quite fast (compared to other planes) - unless I'm misled by the longer transmission of the (longer) code itself.

I also noticed this. I use encoders for RSBN channels in other planes with the system, but this doesn't work well in MiG-21, as it requires a long press time to do the tick - this results in many clicks of the encoder to change a channel by one. I found some custom commands using bigger value_pressed value, but this results in the same lazy behavior, just with different jump (e.g. 10 channels). This makes only the mouse a viable solution for fast clicking to the channel buttons. Would it be possible to make it encoder-friendly? I don't like the lazy feeling on the buttons/keys either, so it should not make that experience worse.

This is perhaps a more general question, but I don't know where to ask it - and as I'm trying to solve MiG-21 Radio squelch on/off binding, I'll ask here. I have Squech on and off commands available for binding: {cockpit_device_id = devices.RADIO, down = device_commands.Squelch, value_down = 0, name = _('Squelch Off'), category = _('Radio Communications')}, {cockpit_device_id = devices.RADIO, down = device_commands.Squelch, value_down = 1, name = _('Squelch On'), category = _('Radio Communications')}, There is no obvious on/off toggle for binding. I tried to search for something about this topic, but the results were quite noisy, mostly related to the "toggle switch" on some joysticks and how to deal with them - but that's not related. Is there a way how to construct a binding for toggle? Is it some different value or something else? Or is it simply not provided by the module coding?

Not a fix, but a workaround without the need to modify the installation directory directly: Well, actually, there is a mod, so it touches the installation directory, but OVGME+Quaggles' Command Injector makes this all much easier now - and after that you only add to the Saved Games, so it's much cleaner (no edit of the Mod in DCS install anymore).

Great! BTW: it probably goes over multiple missions, I encountered it in the 3rd one as well (although there it is merely an aesthetic problem). Are you aware of that?

Thanks to @Rudel_chw and his gentle nudge I found a reasonable solution/workaround: Install https://github.com/iquercorb/OpenModMan (newer mod manager by the same author as OvGME). https://wiki.hoggitworld.com/view/OVGME if you don't have it (I didn't) for better management of mods that go to your DCS installation directory. I checked this video on why and how, there are probably others, but it is quite simple and useful. Good value proposition. It's not strictly necessary to use mod manager, but it's a good idea for cleaner mod installation and uninstallation (e.g. before DCS updates). Download https://github.com/Quaggles/dcs-input-command-injector mod, put it into the "mods" dir you created for OpenModMan and enable it. The rest happens in your Saved Games/<dcs> directory - which is a great thing. Create InputCommands\MiG-21bis\Input\MiG-21\mouse directory there. The first part (InputCommands) is the root of the "patches" that Quaggles input injector uses, the rest is the structure that copies the Input file structure under <dcs-installation>\Mods\aircraft. Copy the provided default.lua there. I added just a few commands I wanted, but you can copy anything from <dcs-install>\Mods\aircraft\MIG-21bis\Input\MiG-21\keyboard\default.lua - assuming the action is available for the keyboard. When copying, remove the binding (combos) part from the line, e.g. from: {combos={{key='NumEnter'}},down=iCommandViewAngleDefault,name=_('Zoom normal'),category=_('View')}, make {down=iCommandViewAngleDefault,name=_('Zoom normal'),category=_('View')}, It's OK to leave the trailing comma, don't worry. Example for clickable cockpit command: {down = iCommandCockpitClickModeOnOff, name = _('Mouse cursor cockpit mode'), category = {_('General'), _('Custom')}}, There are even projects providing some bindings, e.g. https://github.com/Munkwolf/dcs-community-keybinds/tree/main/InputCommands, but there is not much for MiG-21 mouse in this case. The provided file DOES NOT assign the actions to the mouse yet, although it can be done as well (providing the proper combos, I guess). However, now you can assign it in the DCS. The cell in the mouse column is enabled and can be assigned. Works very well and it's not such a hassle as I'd expect. On a side note, I was surprised that some modules (e.g. L-39) don't have any defaults for the mouse in the DCS installation directory, yet it works somehow. This is probably a mystery of a different implementation of those modules. default.lua

First an apology for the overly dark and not fair assessment. I play mostly a bit in the evening, mostly single player, and I like to go through the single player content. That is what affects the experience a lot. I've heard MiG-21 in the sky is a good module and I'm looking forward to get there. I understand that keeping up with the DCS updates is difficult. If the plane is done, I don't want new features or even variants of the plane. Even if I wish something, I don't feel entitled to that and don't judge based on that. I've heard some devs do it, which is great, but I'm a different kind of SW developer too, so I understand the burden and priorities, etc. What bothers me most are the bugs... and yes, also missing binding capabilities. Not implemented there is "prohibited" on my end. That said... Thanks for the tip. I'll check those lua fixes you mention, although I don't understand why I have to do it. But I will, because I want the mouse to be consistent across modules. Nice mission and you're right. Of course, I can't do missions like these for a new plane, where I struggle with buggy training missions instead. I took the wrong path. In general, I know you do a lot for the community, I'm not able to on that level, I at least report bugs. And I don't expect them to be fixed anytime soon - although sometimes I'm surprised. Recently a few of the reported bugs in a few modules I considered frozen got fixed. I appreciate when that happens. To clarify a bit - I didn't talk about MiG-21 here necessarily as I barely started with it, it was more about CE2. However, the most recent change log contained: "Added 3 customizable mouse inputs: Comm menu, Zoom in slow, Zoom out slow" for both CE2 and MiG-21, so... there is still hope. I don't want to comment on the module price, but when I buy something now, I have no idea where it will be in 10 years. I haven't been enjoying the module for 10 years yet. After 10 years I'd consider the cost amortized, I guess. As for my abandonware remark, I felt that way about NS430 or Yak-52 (very little development for an early access module, although there were at least some bug fixes lately, so again, there is hope). I admit CE2 is not there yet and I hope it will not be. I appreciate your response and thank you for the information. And again, I'm sorry about the outburst.

I tried the second training mission and followed the taxi instructions only to encounter this obstacle: Now I'm stuck in the grass, not even max power helps me.

I'm not here to judge the charts and realism shown above, but I tried two modules from Magnitude 3 - that is both of those released. I even considered buying the CE2 just for fun (because it is), but I have one main gripe with DCS, regardless of the module and the vendor - and that's the long-standing bugs. ED is a master of those, but CE2 has a couple of those as well. The displays for the radio and fuel flying around the view... I'm not even going to the flight model - I'm no real pilot. I just want something that feels maintained over time. Now I'm trialling MiG-21. It was a whim, really, it could have been F1 or M2000, but I decided to try MiG-21 for a change - without even considering the creator behind it. I'm sure the module has its strengths, otherwise, it would not be on the store (let's forget about things like NS430 or some other support modules we just don't know where they go and when/if they actually get there). But I was let down by a few things in just a few minutes - before getting to the flying: I can't bind elementary things to the mouse as I can for other modules (Zoom normal, single mouse button click to toggle the clickable cockpit, etc... why is it even prohibited to bind any button to the mouse?!)... and then the brutally unprofessional tone of the first tutorial mission. I mean, I'm generally a fun(ny) guy, but that was way over top, not to mention the "fun" stuff took away the space that could have been more informational for a new pilot. (Yeah, I know there is a manual.) I generally root for any team of any size that delivers, but I root much more for those that (by the way) show how it is possible to care for older modules too. How can I be sure the Corsair will not be in CE2 state any time soon? Now, granted, there are real life issues, I mean, if you get out of business (because anything unexpected happens in a life of any one member of the said small team), I can understand that. But at there should be some continuity. Some month in a year when you fix old bugs or something. Or declare the module officially as abandoned, I don't know. But I wish to know the status of the modules. And yes, many of ED's modules are in (or close to) "abandonware" status as well. Nothing is for ever. But I'd like to now about it.

I totally forgot this is possible, because I always rebind it to a single BTN3 (middle button) press. Thanks. But it is still annoying I can't rebind it to my liking. This is my first moment in the module, I wanted to set mouse as in any other module, and I can't set things like Zoom normal to mouse or clickable cockpit toggle to a single press of some mouse button. I didn't expect such a deviation from the ED's modules.

Why can't be this bound to a mouse button? Is this a regression or was it like this from the start? Mouse is the last column and it is disabled. It is quite annoying to have it different from any other plane - and it's so obvious I want to toggle it with the hand on the mouse.

Just tried it after the latest OB patch (2.9.2) and the problem still persists. I definitely clicked on Normandy 2.0 Trial - and that is what my licenses show (no other Normandy there, I checked all the pages): Yet, the modules download shows: And after the 40+ gig download... Better luck next time. Half a year is not that long after all.

This is very good info, but it seems to be left out in the current version of DCS L-39 manual - why is that? Anyway, I'd like to use L-39 for some aerobatics in a structured manner - but I can't find anything relevant to the L-39 aerobatics. At least nothing at the level of details shown above for the loop. Do you know about some list of figures and the recommended flight parameters for them? I know I can (and will) experiment, but I'd welcome any recommendations. DCS-specific or real-life based material, I don't care.

I believe the Zoom Normal (default) and the initial one should be the same - determined by the default view (13 or 14 depending on head-tracking or VR on/off). That makes sense, but the initial view was broken for some time, and Zoom Normal was broken until the first snap view (or some other tricks, I don't know) was used. Now it works as I'd expect the game to work. Zoom Normal is consistent and the initial zoom is the same.

I went over the planes I fly most at this moment (L-39, F-86 and some FC3 ones) and reset the default view for them (press View Center, move/zoom the view as required, then Save Cockpit Angles). All the default views on these planes were saved correctly and seem to work the next time I enter the plane. View Center and Zoom normal also work as expected after I change the direction or zoom. After that, I just copied the view [13] to [14] as well, so I have the same default with head-tracking and I was done. I tested the Zoom Normal, works fine. Recentering the head-tracking puts me into the default view direction, also works fine. So the transition is annoying, but afterwards it works with or without head-tracking - at least on my end. I hope it will last longer than to another update.

I can confirm it works now. If I recall correctly, it was the magneto switch step missing, although I couldn't figure it out in the mission file. I don't remember ever turning it off before (or being prompted to). The switches were actually the very last step before the announcement that the mission is over. Great! Thanks for the fix.

OK, a little addendum... I reset my default view (with RAlt+Num0) and it seems to work... Does it mean that default views for all the planes "just" need to be re-stored? Other stored snap views actually work fine. Even after DCS restart the default view re-set for L-39C seems to work fine - even right after the start. But if anything was fixed (because something definitely changed!) I didn't see any "default", "view" or "FOV" mentioned in the release notes.

Mind you though, that after this you select the snap view with VIEW keys, not snap-view bindings. At least that's how it works for me.

Jeez, perhaps I read all your post wrong from the start. I focused on the F/A-18C vs other planes difference... Silly me. So the question is: Does F/A-18 AB really start at 74-75%? Isn't it more like 82% of the throttle? I don't know really. What I can confirm is that around 75% it looks like this in the cockpit: On the outside, the nozzles just started to open and there is NOT a flame visible. The flame comes out around 82-83% indeed, and the cockpit reads: Just a slightly lower throttle cuts the flames and FF drops to <140, and then it drops quite quickly all the way to the 75%, from there lower the FF change seems to be slower and slower. So it SEEMS the marked detent on 75% for F/A-18C (and also widely repeated in the users' research) does not match the flame at least. We can agree on that. But I'm no SME on the topic. The nozzle starts to open sooner, the flame comes later... perhaps the first AB stage does not produce any visible flame? So sorry for jumping in with an explanation for a no-problem and let's wait for answers from experts.

The AB position on the throttle is different for various planes. The info I use is from this post: Both modules you mentioned use AB detent on 80% of the throttle. F/A-18C states 74 in the table - although I personally use 75% as I don't see any spike in the fuel flow there yet. Now you have two options: Create a different detent HW setup if you can - e.g. with STECS throttle. Change the throttle curve. I use a single bracket for all AB planes (at least for now), I set it up with F/A-18C by some luck, so I don't need any curve there. But for other planes (F-15C, F-5E, Mig-29) I need it. I switch the throttle to Slider (1), often need to check Invert (2) too, and set the Curvature (3), so that the Output (4) shows the number from the table above (-80 for F-15C 20/80). If it is just a bit less, then your max military power without AB is a tad lower, if it's more, than you're in AB before the detent. The curvature is not super granular, it probably can be set more exact in the Lua config file, but let's not go there. I'm happy with curvature. Note that planes with higher AB than your HW setup will have inverse curve (e.g. Mig-29 has positive 14 in my case). I set one throttle on dual engine, test it in cockpit, move it one more/less as I fancy, check that AB stage sound (prominent with F-15C) really goes when I move over the detent - and when I'm happy I set the other engine the same way. Double check it, just in case your HW is not totally symmetric. The question is WHERE should your HW detent be. One can push it towards the end a bit, but then you just "turn it on" and barely have enough room to enjoy all the stages (e.g. 5 in F-15C). I'm fine with 75% on my STECS (the detent physically starts around mark 80 and ends around mark 90, but 80 is not 80% because of the stop/idle detent). There is a small, but still sufficient room if I want to fine-tune the AB power. As a side note, I use detent for engine stop/idle and add just a bit of deadzone for that area, to be really idle with some tolerance.

Just open the miz file as a ZIP (e.g. Ctrl+PgDn in Total Commander, or rename it to *.zip and open normally). But your mission is fine, there is no Config directory, hence no View subdirectory either. It was just a guess why the behavior might have changed for you. But a bad guess this time. Did you have any problems with Bf-109 initial/default view before? I don't know/have the plane so I don't know whether it's one of those that is normally OK. I don't even know whether I should expect this initial-vs-default FOV problem to be totally consistent. It should not exist in the first place anyway. I don't know exactly how the Config/View might appear in the mission, but it is quite regular stuff in user files, and it's good to know that it is easy to fix with MIZ being just a ZIP file. Anyway, wrong lead, back to the topic.

Besides confusing "initial FOV" not matching the "default FOV" in many planes, there is a possibility, that your mission file contains saved views. This can further complicate any investigation - if you try it with such a mission. Most proper missions don't do that - as it breaks user's own snap views - but it happens often accidentally. I'm not sure exactly how (perhaps when you fly the mission in the editor?), but long story short - the best practice is NOT to include Config/View directory in the missions except for extremely specific reasons I can't imagine right now. Check your mission whether it's "view-free" not to distort your observations.

Yeah, I will use the press-n-hold action of course. It is not a big deal, I'll manage. When I talk about consistency, I definitely don't mean consistency between the actual planes, but more about the controls in-game. Unless one has a spare 3-way switch (I have only one at the moment and actually use it for gears, some of them also having 3-way lever) the question of how momentary presses translate to the actual action are relevant. And yes, press-n-hold is also a valid solution. But options are always good. It's good when you have a multiposition switch and can bind all the positions, have additional up/down/cycle bindings, etc. The strange inconsistency in F-86F is even when you compare the toggle action that holds in the position and skips the center position altogether. I tried to find something on the topic on the internet, but no luck at the moment. Some of them still fly (not sure about the variant though), so perhaps a direct question could help but I don't know the guys. With this I consider it solved as it is obviously by design. No prob, that's how it still works. There is a binding for the centre position, but you need it only if you use that Flaps Up/Down toggle that actually stays in those positions. Up and Down separate actions still work as described above - press-n-hold, returning after release or latching after a very short press.

I see whar you mean, but this than only works with a 3-way hotas switch properly. But it should work with buttons as well just as in any other module or any other non-spring switch. I understand the flap lever action now. Mig-15 or Yak-52 are similar in this way. But is the real F86 lever spring-loaded or not? It doesn't seem so. In that case the momentary buttons/keys should just change its position just as with any other switch or lever. 3-positions gear levers (L-39, Yak-52) work like this, so if the pilot can leave/latch the lever there it should be possible even with buttons as well. Edit: Or we should have binding alternatives for both styles. Latch and self-returning.

Thanks for the info, I started with Chuck's guide where I didn't see this mentioned, but indeed, this is mentioned in the manual on page 56. So that is good at least. Now I can also see the thread: How to use flaps correctly? However, from the real F86 snippets mentioned in that discussion, it doesn't look like the real F86 has this lever spring loaded in any way. So this control quirk is an arbitrary decision of the designers that is quite inconsistent with other planes with the multi-position flap lever (e.g. MiG-15, also from Belsimtek, although, granted, its 4-position lever works not quite the same). I can confirm that the short press works - but quite strangely, it is not totally consistent. It somehow depends on the animation: If the lever is in the centre position, the press must be very short. If the lever is in the opposite position, the press can be a bit longer - until the lever reaches the target position. If the lever is IN position already, the press moves it into the centre position. I'm not saying it's unusable - but it is definitely very counter-intuitive and totally different without the basis in the real plane. How can a short press of UP go UP and then the next press to the centre again? It eventually works as a toggle. With STOP position having a distinct binding, this seems to be a more broken system than a good one.