Flying the Huey in any 229th 1.5 server I get a joystick issue that nobody else is experiencing. Hot start, cold start, I get the same issue. Cold starting, my controls all seize up and stop responding after the throttle rpm gets to 38% except the throttle. The throttle works, but the engine rpm wont increase, the rudder pedals look like they are jittery back and forth. This doesnt happen in single player or any other online server in 1.5, just the 229th servers. The 229th 2.0 server works just fine.

I have the 476th Range Targets mod installed, and the 229th Objects Mod 1.2 installed in the saved game folder.
I have nothing installed in GSJME.
I have the same exact mods in NTTR Alpha.
Both are fresh installs on a brand new install of Windows 10.
I have the HOTAS Warthog, Crosswinds Pedals, Cougar MFD pack, and the Rift.

No device is conflicting with each other. If they did, I would see it in SP and other servers too. Its local only to 229th 1.5.1 servers.

Nobody else has these problems, but my problems only exist in the Huey in the 229th 1.5.1 servers only. If its not a hardware or a mod issue on my end, but everyone elses works but mine, but mine works everywhere else, then what could be the problem?

The first thing I would do is rename my config folder and try again. Its an easy thing to get the original back if this fails to clear up the issue. Its the first thing I do if I have screwy shit happening. Also I think we covered this on TS but make sure there is no extra controller (X bOX) or suchlike conflicting. Powered USB hub, I know it does not cover the fact other servers work fine

Something else to add that I just noticed a few minutes ago. It never occurred to me to try to do the full startup after the fact, and found out that the hydraulic control toggle switch is the problem. I turn it on, my hydraulics go wonky - my stick freezes, my rudder jitters, my collective doesnt move...I turn it off, I have a moving stick, my rudder works, my collective works, but my hydraulics warning light is lit.

(B/229) Cib wrote:The first thing I would do is rename my config folder and try again. Its an easy thing to get the original back if this fails to clear up the issue. Its the first thing I do if I have screwy shit happening. Also I think we covered this on TS but make sure there is no extra controller (X bOX) or suchlike conflicting. Powered USB hub, I know it does not cover the fact other servers work fine

Ive tried this a few times already and determined its not a controller issue. It works everywhere but on our servers in 1.5.5. And almost everything inside the Huey I toggle with the mouse button inside the cockpit.

Did you run a repair?

Its a fresh install.

Can still be borked, doesnt hurt to try.

How do you roll your throttle up and down?

Left throttle quadrant on the warthog

But that axis won't move the throttle from idle. It takes the keyboard Pg up/pg down to get past the idle "cutoff" then the throttle can be used as advertised.

Its the Hyd Cont switch that is borked for some reason or other. Thats what Ive narrowed it all down to. Strange thing is that it only happens in our 1.5 server and nowhere else...

Ever since I have used DCS I have always had to waggle the KB pageup/page down keys to inicialise the Warthog left throttle... so, thanks for explaining that Cib. Hope you get it sorted soon Utley.

Oh, my new PC is up and running... not installed any of my modules yet as I have to sus this 'activication' crap out and am moving my Huey out of my race car cockpit. But flying round in the SU25 and P51T... I am getting 100 - 200+ FPS with everything maxed out... wow, it looks gorgeous Thanks to Cib and Utley for all the hardware advice ^

Opp's, better not hi-jack Utleys thread, sorry dude.

Its the autopilot. For some reason, the autopilot is activated at mission start (yet I have autopilot availability disabled), and the controls are disabled while in autopilot.

This Post Moved to https://1stcavdiv.forumotion.net/t2423-new-issues-with-certain-mods-dcs-versions-9-december-2016#20828

It looks like the recently updated 229th Combined Mi8 Cockpit mod Black 2.2 borks ALL my inputs.  Could that be Utley's problem?

(A/229) Chic wrote:It looks like the recently updated 229th Combined Mi8 Cockpit mod Black 2.2 borks ALL my inputs.  Could that be Utley's problem?

I have not tested That mod  (Mi8 Black 2.2) but it's worth  trying the Mi8 Black 2.1 and then removing that mod to see if that is indeed a cause for your Input problem.
I'll have a look this morning

ANY mod that has an "input" Folder  could be a culprit....for any reason.... ---> example:  The slightest syntax error......

Again, sorry for hijacking the thread

My input problem is an autopilot function somehow loading up at mission start while in the right seat.