imacken

Excellent piece of work. A real enhancement of the original. I hope you don't mind, but I edited your code for a QWERTY version with a couple of layout changes. Another good thing is that we don't need the original clear extension as you have it built in. We still have the weird behaviour with backspace going as mentioned earlier in this thread, but no biggie. QWERTY keypad.zip

So, as I said above, it's best to go to the penultimate existing waypoint so that the new wp goes to the end of the existing and nothing is overwritten.

Doesn't seem to work that way for me. It increments by 2 from your currently selected WPT, and I think that's what is saying in his notes.

It's a standalone install overwriting your existing one. BTW, I recommend removing the ns430 extension. It causes some weird issues.

One thing we have to watch though, is that it inserts the WPT as an increment of 2 FROM WHEREVER you are currently set on the HSI. So, for example if you are on WPT 1, it will insert as WPT 3. Now, if you have any data on that point already, it will be overwritten. So, it is essential to have the waypoint you are on set to your last WPT (or the one before as it increments by 2) BEFORE you hit Insert.

The link is in Binary's post on the previous page.

This is really great. If only it had the Extensions. We need a merge of the 2 versions!

I'm one of those too!

I rather keep them separate, just in case. If there are module changes or if I have made changes to the binds, then I always remember to copy the input folder across to keep them synced. Obviously, if a new module appears in OB, then that folder is just ignored by the stable install. I have never done the conversion this way as I have always had 2 installs, but I'm 99% sure the answer is yes! Always keep backups of your Saved Games folders, just in case.

Yes, see my post above yours.

You select the build - only one in this case - from the drop down and go to 'Adv Updater Options' tab, then select 'Update to latest Beta version'.

I think there can be an issue if we were back in the old days of DCS when stable was many versions behind. Then there might be an occasional incompatibility, but, as I said before, I have never had an issue when copying the whole config folder (which includes all the input binds folder) and the MissionEditor (containing the logbook) folder from OB to stable. Stable is only a OB build that is one or two behind these days and as long as they are on the same main version, e.g. 2.7, than I can't see any real issues copying back and fore between them.

Honestly, I've never had a problem with just copying selected folders back and fore. Tbh, I just keep the stable install as a backup if an OB patch has bad bugs. Doesn't happen very often in the last couple of years, I'm pleased to say!

Settings, logbook, input settings are always copied across (and working perfectly) when I simply copy the config, missions and MissionEditor folders from one to the other.

I’m away from my PC for a couple of days, but the modules that work and don’t work are listed in my first post. The A-10C and F-14 are injected axis commands, but the Harrier and Mirage 2000 are not. All of the lighting axis panel binds on the Harrier and M2000 exhibit this behaviour. None of the non-lighting axis binds do on the same modules. Any device used is the same.

Thanks Skate, but I don’t think that’s the issue at all. This occurs with any device, any axis, only on lighting axis binds and only in 3 or 4 modules.

Thanks again. Yep, as I said above, as soon as I can replicate the issue I’ll post a track.

Always on a cold start, but I’ve tried all evening to replicate the issue, and I can’t! Strange as I’ve seen this happen quite often. I’ll keep trying.

Of course. I just thought there might be a standard thing that caused this. The next time it happens I'll post a track. It has something to do with INS alignment, but I just can't replicate it every time. It's obviously something I'm doing. Weird.

Quite often, AUTO does not appear for me on the HSI. Clearly, this is something I am doing/not doing in startup for this to happen. Can someone explain what is causing this?

As I was advised by @speed-of-heat recently, just remove the ns430.lua file and that issue disappears, at least for supported modules.

Well, either way, I think it needs fixing. Hopefully, now we'll get a response from @BIGNEWYor @NineLine on this. I know it's not major, but it is annoying, and a pain if/when you need to rebind the lighting controls. BTW, the workaround I posted above with user curves starting at 50% (instead of 0%) in 5% increments is a better way than changing the saturations. That leads to unbalanced responses.

Ok, thanks for that.

You need to watch Skate’s video in his first post. It’s a bit out of date, but the basics are still the same.

You define your own presets within this utility. You can have quite a few. Can’t remember exactly, but it’s at least 5 or 6.