Lineaxe

I am looking away at this as well. So far I can only destroy a unit and not decrease its health. I don't know if a method exists at the moment.

Pretty good for just a few days with the chopper... Was that with someone else in copilot position I wonder?

uh, hmm , well ,I gave it a cold boot and it fixed the software /joystick problem. It now works like it always used to and does not drop the SA342 into the ground. Interestingly , it had never done caused the other 4 types of choppers any problems and I could trim and autopilot with them all. Now, I assume that is what had fixed it since there were no updates of dcs and I used the same version of moose. Well, I was coding and chasing down bugs while playing the mission. Sometimes ,me own bugs cause all the grief!

I believe it is Force Feed back setting is set to OFF position ,found in the dcs main settings . It is recommended for most spring loaded Joysticks.

Here is a picture of my settings in a flight at 150 km/h trying hard to stay up in the air without touching controls. I placed a green circle around settings I have checked & making sure they are set correctly. Maybe I am missing one or something

Hi Jumphigh, Do you use the controls indicator? Yes. I have used it to verify that the trim positions were indeed being changed over (somewhat) to my joysticks postions when I click the Trim button. It seems , I can get them to change the trim. No matter what position it is set into , it dives into the ground. Pretty weird stuff I am finding , since I pitch it up as high as I can get it. I must be doing something else basic very wrong I guess. Now I do use a warm startup from parking when I take off and thus don't need to set most of the stuff required in a normal startup.

Hi Ramsay , Do you depress "Autopilot" Master on the stick and see the SAS indicators center (default attitude hold) ? Yes, SAS shows centered Is your airspeed above 120 km/h (ideally 150km/h or greater) ? My Airspeed has varied at times but is at most times in flight above those minimums Does your joystick show any "jitter" or "sticksion" that might require a dead zone ? No , jitter shows using the SA-342 or by using the Uh-1 , Ka-50, AH-64 , and Mi-8 helicopters. This is what I can not do at all . I can change the pitch and yaw to new Trimmed values, but no matter what they are , the chopper always drops to the ground when I let go of stick.

Ok, file too big. I have found that the inputs are indeed working the trim. I can set the pitch above and below center line and the yaw to the left and right of the center line. Now, no matter how high or low I set the pitch angle and keeping it centered, when I let go of Joystick it still heads to the ground. So , I might have something not set, perhaps? I have Magnetic Brake set to on , Autopilot switch set to on, Trim is turned on, Gyro is on, Sync is set in the GM position . (control dash is English text). Now what would cause the SA-342s nose to constantly want to drop like that , even with a high Pitch angle?

I did turn off the XY axis controls on the Warthog . Heh , that makes so much sense I shoulda thought of it Well anyhow after checking that force feedback is off and flying again, it does not seem to help out. If I let go of the Logitech Extrems 3d pro for a few seconds I will fall into the ground. No pitch control at all for the trim . Well, in my mission , Chop-U , the distances to FARPS and enemy units is not too great at all. Now if I could land on a FARP without breaking something ... that's me next trick!!!

Thanks for the ideas.. I just shot my first moving enemy SA-342 down with the HOTs and then a tank so I am feeling the power of the SA-342 ! Now that SA-342 had killed off my UH-1 at a FARP earlier in the game so it had a price on its head.

Well I have a Warthog Joystick hooked up at the same time & I am wondering if they must be conflicting when I use the Trim settings. The Warthog joystick has no Yaw control , and so I use the Logitech Extrems 3d pro for YAW( & also for flying around in the various helicopters). In the Mi-8 and Huey, as well as the AH-64 Apache , I can fly and manage to get them to Trim out ok . But not when I am flying these Sa-342 s at the moment . Seems I used to be able to fly these SA-342s straight, but can not any more. If I could cut off the Warthog's joystick inputs somehow and leave the buttons on it active then I might be able to get some kind of trim control. ( still have to play around with the Ka-50 to get to know it better)

heh you are lucky if you can leave the handle of your joystick for 3 seconds

Yes and I did try both methods of Trim. As soon as I release the joystick after trying to climb it crashes into the ground every time. I had versions that don't do that and I am thinking the SA-342M variant is too heavy to keep it's nose up. After I dump the 4 hot missiles I do get altitude controls working a lot better. Is anyone else running into this ?

I was given a 2nd hand warthog for my birthday , but it does not have yaw control. I hooked in the Logitech mainly for Yaw control ,but use it to fly the 5 types of Helicopters used in my mission. This repair YAW bug affects them all, as well as the F18 & A10s that I also fly there. I guess I need a 2nd joystick , left handed, as my right hand is on the Warthog while flying Aircraft. Or perhaps a simple device attachment to the warthog so It can address Yaw. Anyhow , I do end up using the buttons on the warthog with the Apache and Mi-8 as they have tons of buttons to push, heheh.

Joystick extension... allows very small movements, hence accuracy? What kind, I am wondering ,as my Logitech is all over the place , no chance of centering it enough to Hover ... Just imagine trying to use your joystick device while balancing yourself on top of a soccer ball. That about sums up the experience I am having getting it to auto hover so I can switch over to Copilot position and shoot at anything.

Thanks for the quick reply. I have done the unplug thing and the yaw still exists . It is somewheres in the code . I do have some past programming experience with Directx and my Spider sense is detecting a ____ , well you know ... Heh anyway I still luv to fly them jets and choppers.

Hmm, I am running the daytime one at the moment and just finished playing through the mission in a few different vehicles. So you can not even download the file from there? I wonder if maybe you need to go directly to the download site inside a separate window and search through the download user files for my name. The files should show up that way. I can't imagine them not properly getting transferred over to DCS World. I checked & I can't attach anything larger than 5 meg here.

Still there is a bug in the dcs engine. I have to let them know about it and this seems to be the place to do that. I did what I could describing it so they can go into the controller code and make the minor modification that will reset the joysticks YAW (twist on the Logitech) and not put it into a very weird position off the the right of center. This is a some kinda bug . I would imagine that they would want to tackle that bit of code somewhere along the way in one of their updates to newer version. So I post this bug here so they can add it into the pile of bugs

heheh can I setup a gofundme for it ?

Where would I find a file called my file is not named that at all , and I would think this filename is created as some kind of file compilation of moose and my files or something else that is created on the fly for a virtual lua interpreter ?

Logitech Extreme 3d PRO controller used with a Thrustmaster HOTAS warthog controller BUG !!!! This bug comes up when I go to repair any vehicle ,Helicopter,Aircraft ,whatever.... After the repair the YAW (rudder left/right) is always reset way off to the right after the repair instead of the center of the joystick where it should be. I could see that action happening in the Mi-8 and looked at the control to find out what went wrong. This is the same action as in an F18 after I repair it . It always yaws to the right and won't center. Getting repaired is the root cause of this joystick problem and I need to report it here so that it might get fixed at some point. I have had the problem for years so far and just don't try to repair anything anymore.

Hi Flappie!! my mission is pretty big to attach I try to just keep it at one spot. So I just updated the the latest copies of the mission, Chop-U ,at DCS World . There is a daytime & a night time version for it. I do my testing and debugging using the daytime one. https://www.digitalcombatsimulator.com/en/files/3311904/ https://www.digitalcombatsimulator.com/en/files/3311903/

Kewl, we will certainly work all that in ! I knew it was a bit of a toughie to fly around but we'll get it one day !! I sure like using the SA-342M as a revenge chopper when one of my UH-1/Mi-8s get shot down by enemy SAMs. However,I do sometimes become another target for them.

I want to troubleshoot the error messages in dcs.log coming from the lua code I have written. A lot of the dcs.log messages have given me a line number in my lua code. I can look at the line and I fix the error in the code . These following errors give out lots of information, but none of it points the way to where the errors in my code might be. Now, I want to dig deeper into the dcs.log so I can find out what I did to cause these errors to be added into dcs.log file. So, Here are the two latest errors I am chasing down. I have managed to fix (most of?) the errors which have pointed to a line number in my code & had triggered an error in the log. Where can I find more information on the dcs.log and the meaning of all these numbers and such ? I want to dig deeper into the dcs.log 2022-04-18 20:12:53.143 INFO SCRIPTING: Error in SCHEDULER function:[string "C:\Users\username\AppData\Local\Temp\DCS.openbeta\/~mis00002050.lua"]:52476: attempt to call method 'GetVec2' (a nil value) 2022-04-18 20:12:53.143 INFO SCRIPTING: stack traceback: [string "C:\Users\username\AppData\Local\Temp\DCS.openbeta\/~mis00002050.lua"]:10081: in function 'GetVec2' [string "C:\Users\username\AppData\Local\Temp\DCS.openbeta\/~mis00002050.lua"]:52476: in function <[string "C:\Users\username\AppData\Local\Temp\DCS.openbeta\/~mis00002050.lua"]:52472> (tail call): ? [C]: in function 'xpcall' [string "C:\Users\username\AppData\Local\Temp\DCS.openbeta\/~mis00002050.lua"]:10429: in function 'onEvent' [string "Scripts/World/EventHandlers.lua"]:13: in function <[string "Scripts/World/EventHandlers.lua"]:11> [C]: in function 'addStaticObject' [string "C:\Users\username\AppData\Local\Temp\DCS.openbeta\/~mis00002050.lua"]:32947: in function <[string "C:\Users\username\AppData\Local\Temp\DCS.openbeta\/~mis00002050.lua"]:32853> (tail call): ? [string "C:\Users\username\AppData\Local\Temp\DCS.openbeta\/~mis00002050.lua"]:44625: in function <[string "C:\Users\username\AppData\Local\Temp\DCS.openbeta\/~mis00002050.lua"]:44615> (tail call): ? [C]: in function 'xpcall' [string "C:\Users\username\AppData\Local\Temp\DCS.openbeta\/~mis00002050.lua"]:8958: in function <[string "C:\Users\username\AppData\Local\Temp\DCS.openbeta\/~mis00002050.lua"]:8895> 2022-04-18 20:12:53.147 INFO SCRIPTING: Error in SCHEDULER function:[string "C:\Users\username\AppData\Local\Temp\DCS.openbeta\/~mis00002050.lua"]:52476: attempt to call method 'GetVec2' (a nil value) 2022-04-18 20:12:53.148 INFO SCRIPTING: stack traceback: [string "C:\Users\username\AppData\Local\Temp\DCS.openbeta\/~mis00002050.lua"]:10081: in function 'GetVec2' [string "C:\Users\username\AppData\Local\Temp\DCS.openbeta\/~mis00002050.lua"]:52476: in function <[string "C:\Users\username\AppData\Local\Temp\DCS.openbeta\/~mis00002050.lua"]:52472> (tail call): ? [C]: in function 'xpcall' [string "C:\Users\username\AppData\Local\Temp\DCS.openbeta\/~mis00002050.lua"]:10429: in function 'onEvent' [string "Scripts/World/EventHandlers.lua"]:13: in function <[string "Scripts/World/EventHandlers.lua"]:11> [C]: in function 'addStaticObject' [string "C:\Users\username\AppData\Local\Temp\DCS.openbeta\/~mis00002050.lua"]:32947: in function <[string "C:\Users\username\AppData\Local\Temp\DCS.openbeta\/~mis00002050.lua"]:32853> (tail call): ? [string "C:\Users\username\AppData\Local\Temp\DCS.openbeta\/~mis00002050.lua"]:44625: in function <[string "C:\Users\username\AppData\Local\Temp\DCS.openbeta\/~mis00002050.lua"]:44615> (tail call): ? [C]: in function 'xpcall' [string "C:\Users\username\AppData\Local\Temp\DCS.openbeta\/~mis00002050.lua"]:8958: in function <[string "C:\Users\username\AppData\Local\Temp\DCS.openbeta\/~mis00002050.lua"]:8895> 2022-04-18 19:48:58.116 INFO SCRIPTING: Error in timer function: [string "C:\Users\jimru\AppData\Local\Temp\DCS.openbeta\/~mis00002050.lua"]:32430: attempt to perform arithmetic on field 'Time' (a nil value) 2022-04-18 19:48:58.116 INFO SCRIPTING: stack traceback: [string "C:\Users\jimru\AppData\Local\Temp\DCS.openbeta\/~mis00002050.lua"]:8906: in function <[string "C:\Users\jimru\AppData\Local\Temp\DCS.openbeta\/~mis00002050.lua"]:8903> [string "C:\Users\jimru\AppData\Local\Temp\DCS.openbeta\/~mis00002050.lua"]:32430: in function <[string "C:\Users\jimru\AppData\Local\Temp\DCS.openbeta\/~mis00002050.lua"]:32406> (tail call): ? [C]: in function 'xpcall' [string "C:\Users\jimru\AppData\Local\Temp\DCS.openbeta\/~mis00002050.lua"]:8950: in function <[string "C:\Users\jimru\AppData\Local\Temp\DCS.openbeta\/~mis00002050.lua"]:8895>