Havner

I've seen this mentioned in the newsletter, but not in the 2.5.1 changelog. Is there supposed to be any difference? For instance launching the Su-25T training mission for Vikhr and Mercury pod I see virtually no difference. It's still pitch black compared to 1.5 and 2.5 without deferred shading. Mercury pod is also almost unusable. In 1.5 and 2.5 without DS you could see the ground very clearly. In 2.5 with DS and 2.5.1 it looks like the contrast is waaaay up. Black ground with white sharp object here and there and virtually no colors in between.

Agreed. Happy though that at least for now it's going in the right direction. Awaiting further news.

You're welcome. Do the TTM files work?

Hi AKA_Clutter I sat down to it. The first issue with LUA failing was due to MI-8 having the same keys in multiple categories. I just picked the first defined in keyboard.lua, so a corresponding key will be in only one, but it will still be there. I also installed all the modules there are (including ones I do not have) and remade the program a little to work for everything. The mod list in LUA file works a little bit differently now, as it doesn't specify a whole module but every single variant. In general you need to pass a directory that contains name.lua file. It will take the variant name from that file. 'Mods/aircraft/Uh-1H/Input/UH-1H/', 'Mods/aircraft/Uh-1H/Input/UH-1H_easy/', 'Mods/aircraft/Uh-1H/Input/UH-1H_Gunner/', 'Mods/aircraft/Uh-1H/Input/UH-1H_TrackIR_Gunner/',I added all currently existing modules to the list and re-uploaded the generated ZIP file from the first post. github has been updated as well. As to why your phase2 hangs I have no idea. It works for me without problems. If you still need to generate them myself in the future and you stumble upon this try debugging it. Compile with -g param and run through GDB to see what is going on. There are several tutorials on the net how to do that. I added some output to phase2 so one can see what it is parsing at the moment. Have fun. Also please let me know if the generated TTM files work. I have no means to check that myself ATM.

Or just create an entry in pluginsEnabled.lua which is built-in and supported functionality that works fine (except TF-51 now), is outside of the main DCS dir and does survive a sim upgrade. Hmm, which one do I prefer?

With all due respect, it was a working functionality that got broken. Saying you don't need/want it while others do is counterproductive. I like to keep my icons on the main menu clean. I also remove modules I don't own (and not planning to buy). Otherwise it gets too crowdy out there nowadays.

Are you planning on fixing that? I'd like to have TF-51 disabled.

Still not fixed in today's patch.

You did that ok. I tried to be as strict with errors or strange input as possible. Hence the program will give up when it encounters something that it doesn't understand not to produce a skewed macro. Almost every new module had something awkward. I've fixed it for all the ones I own. Can't remember right now (without looking at the code) what this error means exactly. I'll download the C-101 and the Hawk over the next few days and will try to fix that. Shouldn't be too hard. notepad++ is fine, order shouldn't matter. That's fine.

Because they require compiling them by hand in a cygwin environment and then running from a command line. Not everybody is keen on doing that :-) One set of macros will use numerical codes for the keys so you don't immediately know what key it is referring to. The others will use macros for them (e.g. USB[XX] vs USB_some_letter). If you just want to use those macros there is no difference. If you want to look at the macros and know what keys they are actually mapping there is.

Not through any SDK but just by modifying LUA input files in DCS. There are threads on this forum that tell you how to do that. I've done that for a lot of switches myself for all the planes I own. But this has nothing to do with the program in question anyway. I myself use a mixed profiles. Some things done by TARGET, some other by modified LUA files.

When you install TARGET software, in its scripts are macro files for various planes from FC and old DCS that basically translate keys into names so you can use those names when creating your profile. Those files are very much outdated and there used to be a software once that could regenerate them but it doesn't work anymore. My program is just an update for that functionality. 1. Yes, it reads those LUA files from DCS and generates those macros. 2. Exactly 3. This depends whether there are any differences between 1.5 and 2.0. In most cases those 2 versions are updated pretty much together so I think doing this once (e.g. on 1.5) should be enough Bear in mind that this is just a command line tool that requires cygwin to be compiled. It's not nice windows GUI application, that's why I actually generated those files and uploaded them. They have been done quite some time ago and I don't own all DCS modules so can't do that for every plane. If you won't be able to do this yourself give me a shout, I'll update them. As I think of it now in theory I could do this for all planes, as I don't need to own them. I can download them without a serial. I won't of course be able to fly them, but the LUA files will be there. Anyway, it's been some time since I've looked at this tool. Let me know if you need some help. EDIT: but this program is not a must to create TARGET profiles in any way. It just makes them look nicer and easier to maintain when the key definitions change. You can just regenerate macros, don't need to hunt down your keys in the profile you made.

On a specific example, pitot heat switch and air start switch: 1. Before (with the old control scheme) the device_commands.PitoHeatMain worked with 1.0 and 0.0 values (up and down). Now, whatever the value it always toggles. So it's impossible to create a good "function" for a 2 state warthog switch. Similarly with the airstart. BUT, with the airstart you also added a _2pos variant that behaves like before. So now we have: - device_commands.PitoHeatMain - always toggles - device_commands.AirStart - always toggles - device_commands.AirStart_2pos - specific value, great for warthog switches 2. Add _2pos variants to all switches where it makes sense. I can see you already did for some (after the original input change there were none). But some are still missing, e.g.: - all the pitot switches - airbrake

DCS: F-86F Official EN Flight Manual Preview Contradiction is that above the text quoted by me you describe the operation of this lever (together with the screenshot of it). Sent from my iPad using Tapatalk

Page 53: The mergency brake retraction lever has been removed in 1.5.3 update 1.

It's because I just recently got myself to properly learn the F-86F :) Great to hear it's fixed!

The stick and throttle controls (trim, gun, weapon release, NWS, speed brake, electrical caging, mic button) do not animate when they are used.

Fixed now

Ok, valuable info as I'm planning to learn it thoroughly soon. And I usually put the brakes on a pedal axis, even if there is just one as in MiG-21. Will test.

Bunyap. How could I have missed that? ;-) Thank mate.

Is this possible now? I remember seeing it in some changelog with a short WIP video of it. Has this been implemented already? Anyone has a video of it? Youtube search gave me no results. I haven't learned MiG-21 enough yet to try it myself but was very curious about the effect.

It's been a long time since I remembered the frequencies, but very low frequency radio waves that's been used over the world for normal radio (maybe they still are) could travel to the opposite side of the Earth because they bounced of off the upper layers of atmosphere. No LOS there. No idea whether this is the case with NDB, but physically it's completely possible.

It says: "Need another product" and there is no BUY button. I do have both, BS2 and A-10C bound and activated. Same thing even with Su-27 campaign even though I have it bought and bound. But it doesn't show me my key in the shop.

He's referring to those that only got one campaign out of two (bought Nevada a little bit later) and were supposed to choose which one they want.

I also can't get VOR to work on the Huey with the latest 2.0 the way I can on 1.5.2. So it would seem so. Sent from my iPad using Tapatalk