imacken

Yep, I did from the first mission where all the bindings were blank. Still working!

Ok, so good news for me, and maybe you guys as well. I resolved my problem by loading the profile for each device WHEN IN A CW MISSION from the SpitfireLFMkIX folder. Now, the CW version has all the bindings correct at all times, even on first mission load. Even better, I can confirm that any binding change made in either non-CW or CW is applied to both successfully. I hope this will work for you as well.

Thanks. Sure, that’s a workaround, but it’s not the answer to the issue. The point is that for years it worked, and now it also works if I select a non CW mission before a CW one. Then, all the binds work in CW and non-CW. If I select a CW mission first after loading DCS, then all binds in both CW and non-CW are completely gone! Also, if I adopted the copy and paste approach, how could I make a change to CW binds without changing non-CW?

Haven't tried Spitfire missions for a while so I don't know when this behaviour started. If I look at the Spitfire binds either from the main DCS UI or after loading a non-CW mission, I see the correct bindings - s1 attachment for an example - and they work in CW and non-CW missions OK as was always the norm. However, if I load a CW mission first after loading DCS, then all my binds disappear from the Spitfire - see c2 attachment - for all missions. I don't have a CW option in the controls dropdown - see s3 attachment - and I have never seen this behaviour in all the years I've owned the Spit module. Anyone able to throw some light on this?

I take your point, but these 3 way switches are too module specific for a generic throttle, and have no functionality that can't be achieved with a 'normal' switch using DCS binds. For example, the Viper dogfight 3 way switch has dogfight/center and missile override/center binds which give the same functionality as the 3 way dogfight/center/missile override switch. I agree that having 2 analogue dials instead of the current button activated encoders would be a big boost. (As an aside, convert your rotary dials to axes. That goes a long way towards having analogue dials, but funnily enough, doesn't work well with the Viper antenna elevation know for some reason. Works nicely with HUD or HMD brightness, etc. though.)

What would you like to see in a CM4 that the CM3 doesn't have?

Yes, thank you so much for the update. You've made a lot of people happy!

If you go back a page or two, you’ll find several pages on this. The app crashes for everyone when you try and use the AH-64D.

That is not my experience. I returned mine months ago, but I borrowed one from a friend this weekend and tried again. I see the exact same juddering when head is rock steady in MSFS as I do in DCS. I have tried a zillion combinations on settings as well.

I've got good news, @MAESTR0 has messaged me to say that the kneeboard will be added and available in the next update! Yeah!

The training missions come on board gradually during the beta phase.

Ah OK, sorry, the question wasn't suspicious at all. I see what you mean. The analogue ministick can be used as axes or buttons or both. Completely configurable in the VPC software.

I'll leave it a couple of days and them try contacting him again to see what progress there has been.

Not really sure why you are asking this? Bind them in the same way as other sticks. I use the TMS with the hat similar to the Warthog stick TMS, the CMS with the hat in the same position as the Warthog CMS and for DMS I use buttons defined on the ministick next to the TMS hat.

So, I messaged @MAESTR0on this, and he sent me a very helpful reply. Said he would look into it today! Looks hopeful.

Interesting, why don't we all send him a message?

If only I knew who @MAESTR0was!

Repeat of the above post following today's update.

Fixed in today's update.

Guys, obviously if you don't want to use JP that is entirely up to you, but let me just comment on a couple of things. Firstly, getting it from github couldn't be simpler, just go to JoystickProfiler/Builds at master · Holdi601/JoystickProfiler · GitHub and download the latest version. You will not be 'screwed' by a - very unlikely - change in DCS's controls format. If that happened, then you would be in the exact same position you are in now. JP and DCS work totally independent of each other. I can honestly say, that JP is a life saver for any DCS user. The ability to simply swap your devices in the case of a GUID change - which happens a lot with firmware updates - is worth the few minutes of installing alone. If you don't want to use any of the huge number of functions this software has, all you need to do is install JP, tell it where your DCS install is, import your bindings and save the profile. Even at that very basic level, you are saved all the grief of a GUID change, as if that happens, when you run JP, it will ask you if you would like to replace the 'new' device with one of your existing ones. Select the previous one, export bindings to DCS and you are done! Couldn't be simpler. Even just using that once saves you hours of rebinding. And, there are many many other incredibly useful time saving functions.

As I have said before, the answer to this problem is JoyPro. It is THE essential utility for DCS binding. In the case of a GUID change - as here - it’s a one click job to swap your binds to the new ID and export to DCS.

Crazy that they are still not fixed by ED, but the workaround is easy, Don. Just load them into ME and save them. Sorted! Only needs doing once.

Sure you didn't load and save them as the workaround to get them working? Still borked in latest OB for me and others.

@glen.a.williamson's solution is easier. Just load and save in ME. Works for them all.

Have you tried 'Import Bindings'?