virgo47

The de-ice check (right console hidden under IFF) light is dark when not lit, but its "body" disappears when the light is on. Only the glow is visible: Happens in both variants.

I can't confirm this. Both variants taxi-turn just like before, both with wheel brake axis and button. Do you have any mods or something like that? Even seemingly unrelated mods can affect modules in unexpected ways sometimes. Also, check with Controls indicator, whether there is no other input on the rudder for instance.

The title says it all. I have bindings for Emergency Wheel Brake - Down/Up and they work in reverse in each cockpit. I assume that Down is forwards and Up is backwards - that is up engages the brakes. In that case the rear cockpit seems to be working right, and the front one has it reversed. But in any case it is very confusing when hopping between the cockpits. I nearly rearranged my bindings because of this. Applies to both variants.

I'm just confirming that it works fine on my end. It really sounds strange. I can use LAlt+C and also another custom binding on my mouse. No problem.

If you don't see a regular flow of events from DCS in the verbose output, there is definitely something not right between COINS and DCS-BIOS or, more likely, between DCS-BIOS and DCS. However, I can't help with that that much. Did you uninstall DCS BIOS or just try to reinstall it? It's better to uninstall it first and then try again. After you uninstall it, inspect your Saved Games/<dcs>/Scripts folder for any remnants.

That means you're not using COINS and its powers. In most cases previously, I had problems with DCS BIOS itself. COINS can install it for you, but sometimes something got stuck and I had to uninstall DCS BIOS, clean up relevant lines in Saved Games/<dcs>/Scripts/Export.lua and reinstall BIOS again (the right version used by COINS). I don't have exact steps for this, sometimes it was kinda messing around until it all started working. Last time there were no problems really.

Thank you, great stuff! I wanted to understand it because I was creating an element for it on my Android panel and was wondering when/how the other letter (I/O) can be highlighted when the switch is the opposite way. Now I tested it and it works as you mentioned, the landing gear is the key, and if the approach is not right, then the I/O changes back and forth. Do you know how does it know that I'm ±30° to the runway? Does it use some other system for it? Because this kind of NDB should ignore the actual azimuth or am I wrong?

In the L-39 manual, p154, one can read this about the mode switch selector of RKL-41: “C AUT” (Compass automatic) and “C MAN” (Compass Manual) are RKL primary operating modes, NDBs’ direction determines automatically. The only difference is that in “C MAN” mode there is no automatic switching from outer NDBs to the near one. My question is: How exactly does that C AUT switching from outer to inner NDB show? I flew over the outer NDB of Mozdok aerodrome, the radio compass turned around to 18 and nothing else happened. I thought that highlighted O next to the beacon switch would change to highlighted I or something and also that my radio compass would start tracking the other beacon (which clearly points to 15 when I switch to it manually). I can't find more specific info about this automatic working of NDB. Please, L-39 pilots, if you know more, let me know.

Funny, I had much fewer problems with the Touch Portal app delay when editing the buttons (without any changes or updates), so it's actually pretty good since I mentioned it in the post! I'm now revamping my L-39 pages using some own Photoshop experiments for icons, I'm quite excited about it, so hopefully in a week or two I'll be ready to publish it. So far so good with the TP and COINS, everything seems to be working!

You run the exe from another directory. Go to Desktop\DCS-COINS\Munt.G_DCS-COINS first, then run it from there and it will work. It's sensitive to the current working dir. BTW: mentioned on the User file page: ... 3. Type "cd " and followed by your DCS-COIN install folder, and hit ENTER. 4. Type "DCS-COINS -v" to run in verbose mode. In this case the instructions matter. Happy "COINSing".

When using Forward key, it travels something above 1000 km/h. When using Fast forward key, the speed is ~120 km/h. With Slow forward key, it is 28800 km/h - the fastest one. I tried forward/backward and camera height (all speeds are lower, which is a feature) - all is flipped, I guess left/right is also affected. Fast is slow and slow is fast. Can anyone confirm? If so, can ED just flip the labels, please?

Hola @xoomigo, now I've got something to do for the next few days or weeks. First touches look promising. True, I had to switch the actions, but the events seem to work without changes, so it's not SUCH a pain. I don't understand the note about 5-second loading time, so far the experience is snappy for me - when does it occur? EDIT: Never mind, now I see it. It's not 5-sec. It's ever longer with each button edited. It seems to be COINS related. When I delete the plugin, TP click on button is fast again (for non-related buttons), but with your plugin, the click on buttons (even unrelated ones) seems to be slower and slower. From a simple look to Task Manager, I can't understand it, the plugin doesn't seem to take CPU or much memory, neither TP memory is going up and CPU is not excessive... Can it be caused by all the new available actions and actually being a TP4 scaling problem? One minor issue I spotted right away after migrating my first switch is that the default in the select box is none of the actual values: The default in this case is OFF, but I need to change it to [0] OFF for it to actually work. Not sure whether it's module-specific, but I saw it on both of the first buttons I migrated. Also, if possible, please, make it an open-source eventually, just in case. I'm not seeing anything bad happening to you (God forbid), but I know from my own experience, that sometimes enough is enough with any project, or something with higher priority appears, or whatever - and then we're all hostages with unusable pages. Maybe nobody forks it... but at least anybody can. Thanks for coming alive with this project, there is also a competition for Matric available now (quite serious, as Matric can do more in some cases), but I already started this endeavour with TP and I like it even with some TP-inherent limitations. TP gets better as well, so we don't know where the road will lead us in the end. I hope for the best.

I've just found this the bad way as well... Back should not kick you out of the current seat. It is a serious UX problem. I clicked the Choose Slot accidentally instead of Adjust Controls - and as I had the mouse in my hand already, I naturally clicked Back. If I press the Escape key, no problem. Why is Back doing something different than Escape? It may make sense before you choose any slot, but not when you are already in one. There should be a clear cancel button (call it back or not) and another one clearly labelled such as Leave slot or Choose Coalition, anything that sounds "dangerous" enough - perhaps even with a confirmation to get out of the seat (but that is not such a big deal if the label and function are clear). Sad end to my evening, next time I'll try to be more careful. But UI should not be misleading, especially when better alternatives are quite obvious.

Thanks a lot! I suspected this needle, but your quotation adds a lot of clarity to it.

Hello aviators! In the real-life manual for P-47 (AAF Manual No. 50-5), in the Instrument flying section (p 88, left column, bottom) there is one of the exercises worded as: What exactly is that "half needle width turn"? I can't google anything around it (except for some completely different hand-craft not related to flying ), some obscure suggestions were related to VOR navigation and fine course correction - but how is that "half-needle-width"? What needle? Turn needle? Compass needle?

I believe that's a matter of preference, spare money and how well the Warthog works for you at this moment. I wanted dual throttle, but if TWCS kept working as new, I'd probably wait (price sensitivity). Because it failed (constant pot maintenance needed, TDC unreliable) I decided to upgrade and STECS Standard was my natural choice. I also considered Virpil's throttle. I recently compared STECS Standard with both Virpil (theoretically, as I don't have it, but did some research about it when considering it) and TWCS (more from the upgrade perspective, as these are not comparable):

I'm looking forward to it, I really like this as a universal and flexible addition to HOTAS. Great to hear from you.

Tried to repair my struts after a botched landing... and after three minutes the plane went up like a UFO, everything looked brand new... and bang! Struts broken again. And that's how I found this thread.

The latest version available from GitHub causes problems with F-15C binding since 2.9.0: There seems to be a recent fix for dev_install.lua, but I'm not going to hot-patch a mod. I've seen some video (forgot the link) with some promising progress, it seems like they want to make the mod even more immersive, but I'd like to hear more. Also, the mod had an annoying popup in-game with at least some of the shopping options not really working. I'm not sure about the state of the mod. What I liked about it most, actually, was not the clickability itself (although cool), but the tooltips on particular controls. That is the documentation/exploratory function of the mod. A lot of research went into this mod, really cool.

I was also wondering how UV works. There seems to be nothing about it in the manual (or not easy to search). I never understood why the top position "turns it off!", but later I figured out the meaning of START - and also noticed, that the rheostat moves back a notch. I'm curious whether the real thing is spring-loaded or temporarily latched somehow. This makes it difficult to use with an axis because the max position on the axis is not the max position before starter (unless I experiment with some saturation which I might). Using inc/dec button action is perhaps better. But that one makes it also difficult to stop before the starter positon. Perhaps the start should be different binding and leave only the rest of the travel for inc/dec or axis mapping. Tough stuff. Finally, the CB, it seems to do the bad stuff only in START position, but that would make sense. When it pops out of it to the normal max position I have much harder time to pop the CB.

@f-18hornet Thanks for the report, today I also noticed, that also normal bindings to select the channels A-D do not only press it, but also unselect it on the other press. Is that a feature? These can toggle infinitely (unlike the power off that gets stuck in the unpushed state and is not possible to push it with the binding anymore).

Oh yes, please. Of course, it's not critical, but I've noticed that WW2 manuals for P-47 instruct not to leave the parking brake set "under no circumstances" (EDIT: this is cold weather procedure to avoid freezing.). Chocks would make a lot of sense. Also in current P-47 videos, you see the chocks used and removed just before the taxi.

I also encountered the missing binding and no toggle option. BTW: In P-51D there is also a reset function, is there nothing like it in P-47D? Do I have to cycle it using cage/uncage?

Hello P-47 pilots! I checked the manual and Chuck's guide, but except for mentions, there is nothing specific about this interconnect. I was just curious, when is it used, how, etc. This also led me to this Il-2 thread and comment: https://forum.il2sturmovik.com/topic/71432-p-47d-interconnect-throttle-and-prop-controls-onoff-lsht-i/ This would suggest that DCS's both-way lock between these two is... different at least if not wrong(?). Is it a variant? To me the pitch-control and throttle together don't make sense (but I'm pretty new to all the propeller stuff and still amazed by how different the planes can be). One way protection to avoid RPM under throttle makes sense though. So the two questions - is it really a both ways lock? And: How and when is it used?

Yeah, I was also wondering about it. Neither the keybinds, nor the Undercarriage axis allow N position (the axis merely flips the lever in extreme positions). So it's probably not modelled.