imacken

I'm somewhat surprised to see that these training missions are still messed up in the latest update. Can't be used.

More than happy to do that, of course, but I can't see it would be useful to you unless you have the same devices as me. It's been so long since I started using JP that I can't remember how to start! But pretty sure I started with importing the bindings from DCS to JP. Have you tried that? Sorry, I might be wrong on that. As I said, it been so long - 2 years? - since I first started with JP so I really can't remember exactly.

Do you mean my profile? I don't have a .rl file.

Personally, I have a relation for each button/axis in JoyPro. i find that is easier to organise, and more efficient as their are much fewer relations than doing it by function.

That often happens. Try again, builds just take a while to register sometimes.

Sad to report that there is still no fix in today's big update.

Ok, thanks for trying.

What a relief!

@BIGNEWY has been really helpful in bumping this over the last 2 years, but I'm afraid it has made no difference. UGRA seem to be a law unto themselves. I'm kind of surprised that ED are not able to do more than just jog UGRA's memory from time to time, but obviously, I know nothing about the contractual arrangements! Does anybody know any way of contacting UGRA directly?

Yep, it's been mentioned before. People have tried to make the adjustment but no luck. The fact that it appears to be a one line fix makes this all the more frustrating. I say again, I will never buy anything by Ugra again. Appalling standard of service with their 2 maps. No customer contact in these forums at all.

Sorry, but this is trying to find a solution to a problem that doesn't exist. Just don't bind the centre press, and, et voila, you have a 4 way hat!

Exactly that!

VPC firmware/software updates often contain changes to functionality that are not mentioned in the changelogs. IMO, the latest - 20220623 - is the best version as it has new functions regarding setting detents, defining buttons and other stuff. Just follow @dburne's advice on exporting/importing profiles and @speed-of-heat's on JoyPro and you'll be OK. (JoyPro is THE essential utility for everything to do with DCS, IMO.)

Sounds to me like the Windows GUID might have changed since you last used your VPC kit. This would mean you would lose your DCS binds. But there are ways round this. (BTW, you don't lose your VPC settings if you do a recalibration of axes.) Always, always save your VPC profile before updating the firmware. Then, you are always able to load the old profile to retain your settings. (Recalibrate axes is also recommended.) With respect to the GUID changing, there are 2 ways round this. firstly, you can import your old device profiles in DCS. however, that is a pain as you have to do that for every module and every device. Still, it is quicker than rebinding. The second, and by far the best solution for the future, is to use a fantastic utility called JoyPro. Among other amazing functions regarding DCS binding, it does a one click reassignment of devices when there is an GUID change. Links here JoystickProfiler/Builds at master · Holdi601/JoystickProfiler · GitHub

Sorry, there was no jibe taken, or need to make your point ‘better’. I was simply saying that whatever works best for you is what is right for you.

To use the old cliché, whatever works for you is what's right for you. Personally, the idea of adjusting/removing/replacing etc. the physical detents and shift states etc. every time I changed module types is too much hassle. 'My' method works really nicely, and your comment about restricting the movement for modules that don't use AB is kind of a moot point. I mean in practice, that makes no difference, and you're only using the section between detents for jets with AB in normal use all the time anyway. Also, your point about discrepancies in throttle %ages is easily resolved in the software, and is completely eliminated when the throttles are linked anyway, which they are almost all the time when flying jets, except for start up.

We've been saying that for 2 years now. It's disgraceful that this apparently trivial fix has not been implemented by Ugra.

Yep, and some of the Apache Training Missions are borked, so this would definitely not be a good build to move to stable. I'm a little surprised that there wasn't a hot fix for the TM issue as there will be quite a few new Apache buyers atm.

Yep, already been reported.

Mod managers are just a personal preference. I use Open Mod Manager as I prefer the interface and easy of use compared to jsgme (bit old now) or ovgme.

Because it is more stable on a mount and all my other devices - control panels, throttles, button boxes - are on mounts.

Yes, before I bought desk mounts, I used both the Alpha and CM2 on the desk. I’m quite tall, but I had no problem with using the slightly taller CM2 on the desk despite what some people say. It may be different for you.

I have owned both, and I sold my CM2 as I hugely preferred the Alpha. The tactility is much better, and it just sits so well in the hand compared to the CM2. The flip trigger was better in terms of movement and feel, as was the brake lever. The Alpha seems stronger and better built, etc. I’ve never understood this ‘better for space sim’ thing. I mean, why? Perfect for all modules in DCS and all other sims. PS. I also had the VKB Gunfighter 3 with MCG Pro, and I sent it back too!

I probably will never buy another map by Ugra. Their performance in terms of customer support both here and on Normandy is pretty appalling, in my opinion. None existent really.

That's good news, thanks.