Frostregen

Thanks for the tip^^ Might help the new owner Back then I did not want to dissolve the plastic even more, that's why I stayed away from alcohol / nitro solutions. I did use some sort of "Orange Oil" if I remember correctly, but it was a lot of manual work already to just get to the point that you can see in the pictures

After being my main and trusty setup for many years, I moved on to some new setup. I still think it is a good system, giving the "dead-stick" capability using FFB. Great for helicopter flying. Some notes: G940 Pedals: Rewired to custom Leo Bodnar joystick board, and are connected by USB directly (fixes precision issues from original controller) G940 Stick: Due to its age, the plastic softeners dissolve. This gives a sticky feel to the grip. I removed most of it, so it is not sticky anymore, but it still does not look nice (see pictures). Some work might be necessary to remove all of that stuff. The system itself, the FFB, the LEDs, everything works fine It would be a shame to let it collect more dust in the shelf. If someone wants to continue using it, please let me know. I'm willing to sell it for very little money + shipping. Best, Frostregen PS: Located near Hamburg, Germany

Hi jayzhawk, in October 2022 I decided to finally move away from Windows, and my new PC was set up using Linux. I'm still happy about that switch every single day Of course there are always some issues / changes involved: My G940 pedals (rewired to custom Leo Bodnar joystick board) were not recognised anymore - in DCS through Steam. I assume it is some false positive gyroscope exclusion (it hast just 2 axes - no buttons? Must be gyroscope...). Got MFG Crosswinds instead The FFB on the G940 was simply set to always center. Nothing else worked. I implemented the ability to set the FFB centering strength, as well as disabling it into the driver. This made it usable again, although no "dead stick" anymore I wanted to get a proper heli collective grip. Exchanged the G940 throttle with Virpil Rotor TCS Plus Base and SharKa-50 Grip Last thing was to get a proper "dead-stick" again Exchanged G940 Stick with Virpil CM3 Base, 200mm extension and new FLNKR grip Currently I am not using the G940 anymore. It has been a really nice setup for many years. So I like to sell it cheap in hope someone continues to enjoy it. If you like to be maintainer on my gitlab repo, just let me know. Best, Frostregen

I set up a repository for this here: https://gitlab.com/frostregenprojects/dcs-g940-leds I started to add basic configurations from what I found in other forum threads. Hope this keeps it alive :-) Greetings, Frostregen

I set up a repository for this here: https://gitlab.com/frostregenprojects/dcs-g940-leds I started to add basic configurations from what I found in other forum threads. Hope this keeps it alive :-) Greetings, Frostregen

You could try to skip the first mission by editing the "logbook.lua", if this is an option for you? I assume the real fix will take a while. At least more than the few holiday days remaining. Greetings, Frostregen

Same happens to me. Tried 2 times. Always during hovering while the cable/AQS-13 is deployed. Attached some logs aswell. Probably something dcs-world related, not campaign related: DCSWorld\bin\Flight.dll # C0000005 ACCESS_VIOLATION at 3D5AB1DC 00:00000000 dcs.log-20171223-233053.zip

Thank you :) Yes, this "see how it evolves"-part fails for most of my open source projects too. But at least I know my code (e.g. http://frostregen.de:8085/sme ) helped out some other guys, so it was/is well worth it.

Happy to help :)

I think your problem is case sensitivity: local Mainpanel = GetDevice(0) should be local MainPanel = GetDevice(0) The rest looks fine though :) Greetings, Frostregen PS: I had the same issue with variables always seemingly beeing 1, or conditions always beeing true: I simply did not know, LUA does NOT support "function overloading". So I had 2 methods "SetLed(nr, state) and SetLed(nr, state, condition)", but LUA always called the first one... doh ;) This is why it is now called "SetLedC"... @Flagrun: I would try to stay with numerical values. Much easier to work with. Maybe show your code which did not work out? Else try to log out as much as you can to find the problem. (something like: G940Socket:send("hello=statuslight: "..variablename)

Thanks for the information :)

So how do you manage a heavy load take off then? Max out rotor rpm with 3-way-momentary switch? Or simply accellerate in GE until TL takes over? I "learned" this gov-emergency stuff from UN-Pilot campaign. (And even put this switch on my G940 setup.) Stupid mission ;) UPDATE: Sorry, did not read this: -6400rpm for cruise flight -6600rpm for heavy take off

Nice. Would you share your code again when it is finished? :) (Or are you using some sort of VCS (HG, GIT, SVN?), where I could get a peek at it while you are coding it?) I would love to use this as a starting point for my own FFB coding. (Currently I'm more familiar with C#, due to work)

Thanks for the info! I had the idea to check if it is really a huey at one point, but forgot about it ;) I updated the script to check for the huey, and else do nothing. (Codebase is prepared to simply check and implement logic for other aircraft too) This should even support changing the aircraft ingame. Greetings, Frostregen HueyScript_G940Leds_v2.zip

Ah, nice idea. I will try it out now :) (And thank you for elaborating it this detailed) UPDATE: I tested your suggestion, and it works fine. Thank you for pointing this out, and save me some potential trouble in the future (with Ka-50 and Mi-8 ) Summary: -in simFFB set the dropdown box to 6 (this means button 6 is force trim) -keep pilot trim button assignment in dcs to the same button (6) -keep force feedback enabled in dcs, but change strength to 0 (to easiliy notice if simFFB did not take over control) -when switching from menu to game, in simFFB click on Options->Init DirectInput Greetings, Frostregen