Nose wheel steering locks pressed

[nessuno0505]

Sometimes I release my nose wheel steering assigned hotas button but I still can control the nose Gear as If I keep it pressed. It's an occasional bug, not always happening, but I've experienced It more than a couple of times. Dcs 2.5 release.

[imacken]

I have the opposite problem, so many times when I’m landing or taking off, the NWS just doesn’t work and I end up in the grass.

So frustrating after a long successful mission!

I really think the NWS needs to be looked at by Belsimtek.

[PhilSkyfire]

And I thought, the pinky button is faulty, but it seems, this is some other issue. Pledging for a fix here, too,

[imacken]

What concerns me is that we hardly ever see contributions from Belsimtek here. This issue has been reported on several times, and we haven’t had any real response from the devs to suggest anything is being done about the issue.

[Sarge55]

Might be pulling a bunch of OT working on the Hornet right now to get it out the door for early access. Then do the clean up of bugs on released aircraft.

 

Kinda like RAZBAM focusing on the Harrier and leaving the Mirage bugs for fixing later... at least I hope they get back to it.

[nessuno0505]

I do not agree with this politics: an already released module should be cleaned from bugs and finished before the work on a new One, but this is only my opinion I think there's nothing I can do and so I'll wait...

[imacken]

I do not agree with this politics: an already released module should be cleaned from bugs and finished before the work on a new One, but this is only my opinion I think there's nothing I can do and so I'll wait...

Although I agree with you, unfortunately, chasing bugs doesn't produce revenue.

I'm not even keen on the whole early access thing. Even though we get modules/terrains at a discount, I feel that there must be so much revenue generated in the early days that there is a temptation to not squash bugs, and fulfil pre-release feature promises, but to move on to the next new project.

ED are probably a small team, and are stretched to the limit with 2.5 issues, Persian Gulf, F-18, etc. This leads to situations like the Spitfire still being in beta after a year and a half, for example. Resources being diverted away from finishing modules that are probably not producing much revenue any more.

Just my opinion, and I'm sure ED know how to run their business better than I do, but some user frustration is inevitable.

This applies to BST as well. In my opinion, I am sure they are all tied up helping with F-18, hence, any fixes to F-5E are on hold for the moment. Again, I'm only surmising.

Edited April 20, 2018 by imacken

[nessuno0505]

I think you're right. Maybe now with 2.5 it is an even bigger issue: a lot of bugs that were solved or never existed in 1.5.8 jumped out with 2.5. And now we are waiting for a 2.5.1 upgrade to better manage memory, that is for sure a bigger issue than a TACAN needing reset or a stuck landing gear. I was eager to have 2.5 release version and when it came out I just uninstalled open beta branch and 1.5.8 and went for 2.5 release alone: finally just a single version of DCS! So maybe I was a bit disappointed to find out that 2.5 release is exactly the same last 2.5 open beta upgrade. And now I have to wait open beta phase before having my upgrades. But 2.5 is a very important step in dcs development and we have it for free, so maybe I have only to address bugs if I find one, and wait. It is true, older modules maybe produce less revenue than newer ones, but it is less than a couple of years that I play DCS (I played lock-on on its days, but then I stopped flight sims, now I'm back thanks to oculus rift) and I have bought my f-5 a week ago, so I'm eager to see it completed; not to talk about a-10c that was - for certain aspects - better developed in 1.5.8. So - since it is one of the oldest modules - I'm a bit frustrated to have to wait the hornet release to see some a-10c 2.5 new issues to be addressed.

Edited April 21, 2018 by nessuno0505