virgo47

Is there no tooltip on it? I've seen these in a couple of situations: Binding uses a modifier that was not configured - this is likely not your case. When this happens the offending binding is not even shown, so it can appear on an empty cell as well. Conflicting binding. This happens to me when I import a diff file (Input config) that does not remove the default binding for the plane and uses the same binding for something else as well. If it is in the same config, just try to press that combo repeatedly (click on the table first to focus on it) - it should cycle through all the bindings for the same combo. Conflicting binding with another layer, e.g. UI Layer. Obviously, different aircraft configs don't conflict with each other, but some config layers are used at the same time (plane + UI Layer, not sure about others). Strange cases. Sometimes I see it, restarting the game helps, or saving/loading the input config, etc. This can be caused by loading a diff file for another config (by accident or with a good reason) or when the changes in the system/aircraft defaults binding suddenly (e.g. after the DCS update) collide with your existing stuff in Config/Input.

I believe that realism and monitor (or VR displays, or whatever) don't work together well if you don't do something special about the visibility. People could see things further and smaller than what current monitors can provide, and some kind of smudge or something should be visible if it could have been visible in real, even if the 3D engine would not be able to provide it. Current dots are terrible because I see things better far off than when they get closer and the dot disappears. But something should be there, otherwise we would not see things that can be seen in real. It will never be 100% realistic anyway, if nothing else simply because of FOV vs monitor and many other reasons. And it will never work the same (and as well) for all users with various devices. But current solution doesn't seem to cover the mid-range very well and overblows the far end. And, what's even worse, does not seem to work in a comparable fashion across various devices - too far from it. This makes the whole discussion even harder.

I half agree and half not here. I agree that lever bound to axis is fine as long as the axis is reliable (no jitter), or you play around the problems as you did. I personally use thumbwheel on the STECS, which is not super ergonomics, but good enough for the throttle in UH-1H - and I use it just for fun when I want to practice governor failure - when four axis to control is not enough and you want the fifth . But I'm a newbie with Gazelle, I don't even see a governor switch there, so for me any precise control of this lever is not necessary - keys are enough. I use that feature that syncs the axis to cockpit controls and if I left the axis for fuel flow in the wrong position for Gazelle (e.g. playing a different plane before), I'd immediately found out, I'd need to fix the physical position of the axis - and annoyingly, restart the mission, because of the Starter switch not being ON. So, yes, it works with axis, and if your axis is reliable, it works well - but with cockpit sync you need to double-check your axes (or at least this axis) before starting/unpausing the mission. That said, is it really practical and/or necessary to have it on HOTAS axis? Do you use fuel flow for something in other situations than startup and shutdown? (Of course, it is still a valid personal preference. Whatever works for whoever.)

I also discovered the problem with a tiny movement of the fuel flow lever back shutting down the helo without any way to fix it. If the starter switch is ON (which, as previously mentioned, is NOT by default when hot starting), no problem, the RPM goes up again. But, strangely, if it's not ON, and it starts to shut down because of the tiniest fuel flow lever movement - putting starter ON at this moment does not help. This is quite frustrating and confusing really. I had the lever on HOTAS axis, but (again, as mentioned in this thread) this is obviously a wrong decision for this helo.

In an unexpected twist of events, I discovered a similar problem with UH-1H: So, perhaps, this is not Gazelle specific, but something generic with DCS FM radios - or something both modules share at least?

Recently I noticed a funny behavior of an FM radio in Gazelle (don't let the preview fool you, it's not about Mission Editor): I was quite surprised to discover - totally randomly really - very similar behavior in UH-1H, which let me think it's perhaps not module-specific. What I see in both cases is "two-stage behavior": the transmission stays noisy, whatever I do... and then, after something changes... the transmission is quiet, but I can bring it back noisy - and then make it clean! The set of switches is different in both helos, but the behavior doesn't seem to make any sense at all. Let's see the video: Notice how just changing the frequency makes the radio NOT working - but it's recoverable through the "noisy" squelch position - and suddenly, one can only have clean sound as well. Any meddling with the frequency selector "breaks" it again until you recover it with the procedure again. I don't think any radio works like that - especially considering, that at first I merely tuned 47Mhz and it started receiving something (although with noise). The trackfile and mission are attached. uh1h-funny-fm.trk uh1h-fm-radio-problems.miz

Good that it can be done with script, but one more input for altitude + AGL/MGL (with default AGL 0) would be indeed welcome. I have a tower on a non-prominent hill (in the area without any prominent hills) and the sound is clearly blocked even when I see most of the tower. This would help without the need for scripting.

It would be cool if the manual simply stated something like: "(Not available in this UH-1 variant.)" Or something. Now I only assume it's not available.

Just a quick update - the patch fixed the problem! And I messed with that VHF volume after all, probably mistaking VHF NAV with VHF (non-NAV), I'll post final set when I go through all ctr controls. For now, thank you VERY MUCH for the fix - and for inverted sliders!

@xoomigo Thank you - I can confirm the reverse sliders now work! However, I have bad news as well - any switch now sends NaN instead of normal values. If I import plugin from 09-15, it sends numbers: Command Sent: mgdc_l-39_ac_front_master_arm [MGDC_L-39_AC_FRONT_MASTER_ARM 1] Command Sent: mgdc_l-39_ac_front_master_arm [MGDC_L-39_AC_FRONT_MASTER_ARM 0] Current plugin sends this (different switch, but all do the same): Command Sent: mgdc_l-39_ac_front_asp_fkp [MGDC_L-39_AC_FRONT_ASP_FKP NaN] Command Sent: mgdc_l-39_ac_front_master_arm [MGDC_L-39_AC_FRONT_MASTER_ARM NaN] This crashes DCS instantly. So somehow we need the best from both versions. I'd recommend pulling the last version out of the upload page for the reputation sake. Finally, as a minor thing, I found that VHF volume is also inverted, I don't know how I missed it (maybe my head was inverted), so the set of changes for UH-1H is: ADF_GAIN|adf_gain|ADF Gain|6|3200|=ictr(65535)|100 INT_VOL|int_vol|Intercom Volume|6|3200|=ictr(65535)|100 UHF_VOL|uhf_vol|UHF Volume Control|6|3200|=ictr(65535)|100 VHFCOMM_VOL|vhfcomm_vol|VHF Volume Control (step size less than 8192 may not work)|6|8192|=ictr(65535)|100 VHFFM_VOL|vhffm_vol|VHF FM Volume Control|6|3200|=ictr(65535)|100 VHFNAV_VOL|vhfnav_vol|VHF NAV Volume Control (step size less than 8192 may not work)|6|8192|=ictr(65535)|100 Sorry if you felt under pressure, no need to rush, the capability is awesome and I'll wait for it. Or you can send me the stuff privately and I'll test it before release, if you want.

FM radio is described in the manual from p112, and the model is simplified, it should work fine for a few preset channels. However, I found some issues with the radio - some of them are tricky to replicate, as the radio seems to change the behaviour a bit: At first, it's playing whatever is on the first preset - but with excessive noise. TST is not different from other three "ON" positions. If you turn it off, it's quiet, and after turning it on again, it still behaves the same. All four positions are the same, playing the current preset channel with some noise. If I change the preset to another one, it's quiet - this may be OK, I don't have any station on the other preset. If I change it back - it is still quiet. Waiting don't help. Turning it off and on does not help either. However, I can start receiving the preset channel again if I go to TST - I can hear it with noise. And if I go to other ON positions - suddenly I can hear it without any noise as well! BTW: TST does not play the 1kHz tone as advertised. To summarize the behavior - in order to hear the preset correctly, you have to change to another one, than back, then go to TST and than to any ON position. I'm attaching the mission file and track file - and this video (which is the same mission, but not the same as track file): Lastly, a minor problem, but it got me confused for a bit - the mission editor shows AM for FM preset frequencies. The manual (p113) shows an old screenshot from the Mission editor, and it shows FM. Now it looks like this: gazelle-funny-fm.trk gazelle-radio-problems.miz

This is one of the first things I noticed after I had bought the module. I use Pedal Trim Type: Fade In/Fade Out (BTW: a neat option!) and the indicator shows the pedal white indicator in the middle after trim - while cyclic works as expected. Luckily, it's just an indicator issue, so it seems. But it's confusing nonetheless.

I was following the second training mission (weapons) and a few things attracted my attention: TV display related BCV panel power has three positions, yet only A and M seems to work. Confusingly though, page 40 mentions the other position as well: Should it work or not? The slew controls are hardly usable - with a ministick (axes) close to unusable. Anytime the other axis interferes with the one in motion, the one in motion stops immediately. So even a tiniest amount of vertical axis stops the fully deflected horizontal axis. Strangely, some combinations seem to work and sometimes the cross goes diagonally, but in general - it's unusable. The same seems to apply to the slew keys. If I hold right and tap up for a while, the cursor stops, although I'm still holding right. I attached the track file, it's the second training mission, I didn't bother to take off to make it easier, but that seems to make no difference. ALI position skipped is shown quite soon, TV cursor screen is towards the end (waiting for the cooling). no-ali-twitchy-slew.trk

Well, 50s is perhaps a bit exaggerated, but it's not impressively modern for sure. And likely anything sophisticated comes from Kazakhstan. (I mean France, of course.)

In my case, the pressure showing 0 happened in a hot UH-1H client slot. But I couldn't reproduce it with the same slot afterwards.

Hi, I PM'd you with the demonstration video.

You're right about the accent, it's pretty strong, but I watch the channel regularly and one will get used to it eventually.

Yeah, definitely, this video was very good - and the plane, oh... just about perfect!

In my case, one year later, I'm still using STECS daily. I don't see any quality problems yet. Of course, sometimes I miss something (e.g. the Standard base has way too many buttons and very few actual switches), but whatever this throttle does, it seems to do it well. I enjoy the easily accessible tension screws and swappable detents, both I use quite a lot. All the reservations still apply, of course - the throttle is top-heavy towards the max position, I'd welcome more axes on the grip, etc. As I don't have any other throttle except for my broken TWCS, I use STECS only and until it breaks, I'll stick to it. What then? I have no idea. Hopefully, they will give us better STECS, better defined 5-way hats, etc. Otherwise, I may try another product, just to see the difference.

These are all sad graphical bugs, the "long hand" definitely affects the gameplay as well if you go for that immersion. I'd like to see them fixed as it really looks ugly when you look around. But this "new" one is a sad regression that takes away some feedback from us. Perhaps not the twisty grip, but the distance scale does. If we "integrated" the bugs over time, even if their weight (severity) was low, it would be an immense value of bugginess for sure. And, L-39 is not even the worst module. But I really don't understand why it's fixable by a simple LUA change, yet we can't get it to the release. What is ED afraid of, that doing something will make the module worse than doing nothing? Because that would be a terrible message about the fragility/code quality.

Hi Xoomigo, I've tried the patch, I see the new patched EXE in my TPP, it all looks OK: I reimported it into Touch Portal, but when I try it, it doesn't work. With verbose output, I still see 65535 with slider maxed up, not 0. I've had my UH-1H.pp already modified, I identified these changes (two of those are the same as you provided): ADF_GAIN|adf_gain|ADF Gain|6|3200|=ictr(65535)|0 INT_VOL|int_vol|Intercom Volume|6|3200|=ictr(65535)|0 UHF_VOL|uhf_vol|UHF Volume Control|6|3200|=ictr(65535)|0 VHFFM_VOL|vhffm_vol|VHF FM Volume Control|6|3200|=ictr(65535)|0 VHFNAV_VOL|vhfnav_vol|VHF NAV Volume Control (step size less than 8192 may not work)|6|8192|=ictr(65535)|0 Is there something else I can try to see what is wrong?

Ops... silly me, I copied the one from the zip having both zip and dir next to each other! I tested this fix and the error is gone, thanks. I'm looking forward to that ictr= fix as that will make the volume sliders in UH-1H work as expected (some of them at least, e.g. that VHFFM_VOL is affected).

Oh... I never cared THAT much about new features and I'm willing to wait. But with this perspective, I now see their bug-fixing schedule in a different light! (The problem is my expectations and less patience for bugs than for features.)

I didn't have problems with the antivirus (using MS default one for Windows). I deleted the whole DCS-BIOS folder from my Saved Games\...\Scripts and started the installer again. After installation, the dir is created fresh (15:57 was current local time): The BIOS.lua file was in its original form. After selecting modules, the installer changed the file, commenting out all unused modules. As long as I selected only F-5, it was OK - I could repeatedly open and "Next" the Select Modules windows. When I selected NS430, it accepted it the first time, but the next cycle (Select Modules, Next) showed the error again. Next, I reopen the Select Modules again, unselected NS430 and selected my modules - and the error appeared again. But the next cycles (when NS430 was deselected after entering the page) were fine again. It seems it doesn't like when NS430 is ticked when I open that Select Modules page. I also noticed a brief moment that the changed checkbox shortly shows its original state after I press Next, not even NS430 but Yak-52 as well. Not sure what that is (some model/UI sync?). Now, obviously, this is no showstopper as the module does not work properly anyway (on DCS-BIOS side, if I understand it correctly). BTW: What makes you say that my BIOS.lua was not modified by the setup? I see the lines edited every time I confirm the Select Modules window.

I suspected NS430 somehow. File is included, it differs from the original BIOS.lua only in commented-out modules (and LF vs CRLF, but that is inconsequential, I guess). BIOS.lua