imacken

I hear what you are saying, and if this was a new feature or bug, I could accept those reasons. This is something that people have been banging on about - not just on this thread - for OVER 2 YEARS. Since day one. There have been many update opportunities for UGRA to have incorporated this trivial fix. This is not the first time that they have shown a disregard for customers. I'm sure we all remember the original Normandy map saga and the frustration felt by many customers there.

The mission.miz? Do you mean a specific mission? Putting it in a module kneeboard is better, as at least then you get it in all missions for that aircraft. But still, it's far from ideal as it pops up in every terrain. The sooner UGRA fix this, the better for all of us.

I give up. We are talking about a one line trivial fix here that should have been there since day one! It’s hardly going to stretch the resources of the mighty UGRA to test it out. See my last post for the ongoing broken promises.

Thanks, but I think you're missing the point. We have been waiting over 2 years for this one-line fix. Back in August, @MAESTR0 told me that the fix was made internally but that it would have to wait till the October update. That deadline passed with no update, and then he told me that they needed to test it, but they were too busy with Normandy 2 to do it. (I offered to test it for him, but I didn't receive a reply.) This is a trivial fix that should have been in this map from day one like all others (except Marianas, but that was quickly fixed). We can all be nice and polite about this, and talk about continuing patience (for another 2 years?), but really, this is poor from UGRA.

@Minskythanks a lot for all your work on this. If only the Syria map kneeboard worked, all would be good!

Why do you say that?

There is no permanent 'update day'. The last one was on a Thursday, sometimes it's Friday and sometimes it's Wednesday.

Funnily enough, not included in today's patch either.

@NineLinebeen 3 months now. Have you had a chance to look at this yet?

Don’t really know why you are being so kind to UGRA. They have made promises to publish the one-line fix long before Normandy 2 took over. In any case, this is hardly a resource draining task!

Well, guess what? Yes, another update has passed and no sign of the one line fix to the Syria map. This is beyond belief now @MAESTR0. If you say you haven't got the time to test the fix because of Normandy 2, then please send me the file, and I'll test it out for you.

Couldn't see a 2.7 forum, so I'm posting here. Just noticed today when I was checking back on something in the Stable 2.7 version, that Active Pause cannot be bound to warbird modules, e.g. Spitfire, P-51, Bf-109, as there is no entry for it in Controls. Now, it is there for jets etc, so I'm wondering what is going on. I'm pretty sure we used to be able to bind Active Pause in the UI Layer - as it is in 2.8 - but that bind is currently greyed out.

Seems to be working fine. I’ve tried a few cold starts and take off IA missions. Thanks again!

Yep, 0 doesn't work, but 1 does. I'm happy with that. Thanks for all your help!

Actually, I think it's optionsDb.lua. Just trying it out now.

which dlg?

I get that, but it shouldn't affect the slider to go to 0%. It would keep everyone happy!

Re-reading your post, we are almost talking about the same thing. That's exactly the way I do it, except that the axis-to-button is coded to raw values based on below 0%, i.e. past the idle detent.

Thank you for that. what an idiot I am! Yes, the 3% helps, but it would be nice to have the lower limit at 0% as that is where the detent is set in the CM3. The recommended method of binding throttle detent in the CM3 is to set the detent at 0% in the VPC software and have buttons for idle/off past that point. No need to save buttons on the CM3, there are 128 available! This method works perfectly in all modules except the M2000. I always wondered why I didn't have full movement in this module, but now I know.

For some time, I wondered why my throttle wasn't registering any movement forward for the first 15% or so past the idele detent. I recently just noticed the setting in the Special Menu for Detent Cutoff. That has a minimum of 15. Now, for those of us with Virpil CM3 throttles, the standard method of setting the idle detent, is to have 0% output at the detent, and a button for idle/cutoff below that. Works perfectly in all modules except the M2000. That is because RAZBAM will not allow the slider to go below 15%. How do I make a request to them to allow this to go to 0% to fix this issue? It can still be set to 15% as default in settings.

Personally, I have never had any issues with any version, but the latest few builds have had lots of new facilities, improvements, etc. Try it out. You can always go back.

Can I ask, why don’t you just use a mod manager to do all that? Before any DCS update, I just one click uninstall my kneeboard mods in Open Mod Manager, then one click to install again. Yes, deleting those Caucasus and Nevada airfield files is always the first thing I do after any update! More patient? We’ve been waiting 2 years for this one line fix!

Can you please explain what you mean by that? Sounds interesting.

What difference would that make? It’s just this map that is an issue, and that is simply because Ugra haven’t been bothered to add in one line of code in the last 2 years to make this work!

Unfortunately, @MAESTR0has said that they are too busy with Normandy 2 to deal with testing Syria’s kneeboard fix. After all this time? Really unacceptable.