RealDCSpilot

@Mad_ShellYou are not alone. The FM on the Gazelle module only takes wind direction and wind speed as a vector and pushes the game object in that direction. To bring the Gazelle on the level of all the other DCS modules, the FM needs a serious upgrade.

Sorry, didn't cut it myself. I found a company in my city which did the laser cutting. I also considered printing them myself with carbon filament, but i took the "quicker" road

Started to put my project on github: https://github.com/Flashgod-VR/G940-Total-Conversion-Kit

Thanks to fred41 it was possible for me to make a special firmware patch for the G940 to set new axis ranges for my configuration with stick extension, a nice side-effect was a slight increase in motor torque. I also redesigned the air tubes for the cooling fans today, to let the heat get pulled out instead of pushing cool air in. Also installed less noisier noctua fans now and this makes my project feature-complete. Yay! Big Thanks to @propelerand @fred41 !! Without them this would not have been possible.

Those pads are also really useful for helicopter flying, the telemetry output of DCS let start them shake heavily before you enter vortex ring state. Could never fly without it again.

I don't think so. But it does not cost any performance, it's just a mirror of what's rendered in one eye of the HMD (depends how you set it up).

Latest info from BIGNEWY, they are working on native support in DCS at some point in time. The LeapC.dll is already in the bin folder (maybe for XTAL HMD)...

Just my actual settings as an example, better edit this in the options.lua file in your savegame folder. Search for these lines: ["mirror_crop"] = true, ["mirror_use_DCS_resolution"] = true, ["aspect"] = 1, ["fullScreen"] = false, ["height"] = 1024, ["width"] = 1024,

Strangely, my G940 motors are getting very hot with the F-16, something must be very different from other modules. Sure, it is a fly-by-wire system with extremely short inputs, but something in the method how DCS controls the motors seems to be off and drives them with full stress all the time.

I'm currently running forces set to max at 150% in the driver settings. I'm sure i also could do an electronics mod like you, i already have a new power adapter with 24V/5A connected. But i need advice from a pro first. On the other hand i don't use "effects" on the stick (turned it to 0), i only use trim and control surfaces effect force at 100. For all the other airframe effects i have a Forcefeel pad on my seat (Realtus Forcefeel) and use Simshaker for DCS, a much better way to have haptic feedback of the airframe on the whole body.

@TomVR Like finch said, for this mod i'm using just the main PCB of the G940 base, it's motors and the magnetic sensor. fred41 made a special firmware modification for me, to disable the "deadman sensor" functionality that is implemented in the grip of the G940 stick. For the grip i used the PCB of a WarBRD base.

RTX3090 on a native SteamVR HMD (Index) running fine here. I guess switching to OpenXR is the best next option for DCS's engine.

Finished the active cooling design:

My problem is, i can't bind this function to HOTAS (greyed out).

Works on my end with a G940. You have to set trimming to "default" for a FFB stick. "Joystick without springs and FFB" means joystick without springs and without FFB!

To make it simple, cyclic input does not result in roll rate in a helicopter.

@Alan Fistwood Don't forget to include an active cooling solution, especially for your x-axis motor. An open air vent with a 40 mm fan directly underneath the motor should fit your design.

Here is how i solved the implementation of the G940's MLX90333 magnetic position sensor (Melexis): It's basically a "mini joystick-within-a-joystick" to scale the huge movements of the big gimbal to a much smaller one. The magnetic sensor is turned by 180° to mirror the X/Y input from the main stick, the contraption "slides" within the big gimbal's T-connector to compensate moving on the z-axis. The ball joint has a little friction so the magnet's position is always very precise. Due to new motor arrangement their polarity had to be reversed.

Prototype finished. Worked right from the start.

Was vielleicht noch hilft, kurz bevor der vortex ring state wirkung zeigt, fängt die kiste an zu "rappeln" :) Da weiß man sofort das mehr collective zu geben ist. Ich hab auch ein force pad unterm Hintern und Rücken (Gametrix Jetseat/ Realtus Forcefeel etc. über SimShaker app), damit hat man haptisches feedback für alle möglichen Vibrationen am Flugzeug/Helikopter. Man spürt also körperlich das es gleich losgeht. Cool sind auch die rythmischen Vibrationen des Hauptrotors im Rücken.

Yeah, sure. My plan is also to ask @propeler to put it on his github page. Don't forget to rework the thread with a M36x2-6g threading die after printing. GIMBAL_Virpil_Connector.stl

I'm also on a different path, in my case the electronics were already finished a decade ago. I'm basically just using the massive gimbal, because i'm working on a total conversion kit for the G940.

Not exactly, but i usually expect a good flight model for a paid module first before everything else in DCS.

No, i don't think we get Vulkan with 2.7. Only a slightly optimized DX11 render pipeline with raymarching feature for the clouds. They also mentioned "pre-raytraced cockpit lighting" - i'm very curious about this. In general, jumping from 2.5 to 2.7 could mean to be a big step for everything that's working under the hood. They didn't name it 2.6 for a reason.