Sprool

Another vote here or the fabulous 109 - great immersive experience and great performance

Joystick gremlin and vjoy are the answer. Sorted.

That sounds just what I'm after. I've been using vjoy and FreePie to use a load of knobs and sliders on a midi controller (korg nano) but if I can get all the controls needed onto my X52 axes that would be really cool. Edit: great advice, works exactly as I needed, thanks for the heads-up. A bit scary looking through the website at first but when you download it and play with it, its really straightforward. Perfect for my needs - thanks!

Is it possible to set up both real joystick and other virtual identical joysticks via vJoy to control different things off the same real joystick axes? I'm trying to get one rotary axis on the joystick (JOY_RY or JOY_RX) to control 3 or 4 different light panels at same time but it wont allow sharing of axes to more than 1 function. If I got a second & a third identical vjoy running where I could map different functions to the same axis, say console light to real JOY_RY and floodlight to virtual JOY_RY and instrument light to next virtual JOY_RY then would the real axis control both things?

I tried editing the joystick lua file in the Huey to set all 6 cockpit lights to JOY_RY, but although it shows up in the settings as all assigned to JOY_RY only one of them works (and animates)

I would be very interested to hear if there's a way of doing this, multiple assignments for one rotary axis, especially for the rotary knobs on my X52 - to be able to assign one knob to control level of console, instrument + flood lighting together frees up the other rotaries for more important tasks.

Is it possible to assign multiple commands to a single rotary axis? I want the option to assign all cockpit lighting to a single rotary knob rather than having separate light systems, even the Bf109 has separate left and right lighting which is a waste of an axis for me. The F-18 I'd want all mfd's on one rotary, and the instrument lights, console, flood, etc together on their own bound axis. Huey has about 8 separate cockpit lights, they could all go onto one if I knew how. Edit: I edited the joystick lua file for the Huey so console, sec, engine, ped, copilot & pilot lights were all using JOY_RY but only one of them works in game. edit 2: sorted via joystick gremlin and vJoy.

I started using the TDC slew profile linked to above and it works fine as long as I load the profile s/ware and the game controller properties window in Windows 10 first. I struggled with poor pot quality on the "precision" (joke) slider and the rotaries for zoom function so ended up using the scroll wheel thingy n the back of the throttle stick, once I discovered I had to press it in quite hard to click it like a button dcs then sees it as a scroll wheel and it works. Documentation on the X52 seems very sketchy.

The other thing I'm confused about is the controls only seem to work fully when the Game Controller settings / properties window is open in the background?

Is there any way you can get the X52 to retain a profile loaded into it, or use as default? Can it only have 1 profile loaded in at a time? I sort of thought the 3 'modes' option was for loading 3 different profiles? (ok 6 modes with a modifier button..) Anyone else struggling to get the scroll wheel and mini mouse thumbstick working in a useful way?

Got the X52 yesterday and zoom function, so important for operation in DCS, was nasty on the joystick, tried the "precision" slider and one of the throttle rotary controls, the view jittered around all the time. I finally managed to get the scroll wheel working by downloading latest Logitech s/ware and an F-18 'tdc slew' profile from DCS so I can also now make use of the little thumbstick. Seems documentation & support on the X52 is pretty shoddy tbh, but I now have a much more stable and usable zoom by mapping the scroll wheel down to the zoom in slow key and scroll wheel up to the zoom out key - ignoring the zoom on the axis controls. It only takes 4 or 5 clicks - about 1/4 of a rotation, to go from neutral to full in or out, which is fine for me. Trouble is, the X52 doesnt seem to hang on to the loaded profiles.

This is amazing stuff. Are the 2gb of texture files also needed for this mod or are they replicated from the main download?

Doesnt the TDC Depress button toggle lock/unlock for radar targets?

+1 from me, I spent 5 yrs stationed out by Dhahran AFB, would be great to have them in game. (the original Dhahran AFB and the newer King Fahd international airport at Dammam just to the north.

shaderLineParamsUpdatable = true shaderLineDefaultThickness = 0.1 --was 0.8, balance between export blur and readable cockpit shaderLineDefaultFuzziness = 0.08 --was 0.4, balance between export blur and readable cockpit shaderLineDrawAsWire = false shaderLineUseSpecularPass = true This is not ideal, in-cockpit display still very faint but nice and clear on the export.

Sorted now, new panel created in photoshop, gauges just dragged around to new locations in the helios editor, even got my controls position indicator back.

I downloaded & reinstalled the script files from the FA-18c profile and its all working again now. Just juggling with the rwr lines to get something readable.

Its a nice layout. Im scratching my head at the moment as the Helios profile I was using earlier for the F-18 no longer exports the UFD, rwr or fuel stuff, only the 3 DDI's, and I have no clue why. What I'd really like as a stripped down version just showing the AMPCD and R_DDI on the secondary monitor, but with working buttons, but Im not clever enough to delve into all the scripting to get working buttons on a profile.

@Cowboy10UK : have you tried setting ShaderLineDrawAsWire to True? Then thickening up the lines a bit?

Yep all my minotorsetup lua's have a line under each unit to set aspect ratio. RIGHT_MFCD = { x = 1010; y = 530; width = 810; height = 810; aspect = 1920/1080; } CENTER_MFCD = { x = 100; y = 530; width = 810; height = 810; aspect = 1920/1080; } Sorry to ask but you're not running windowed mode are you?

Usual advice is to put them in saved games folder, Users / YourName / DCS.OpenBeta / Liveries / then they remain intact when ED rolls out updates to DCS. F14 is not an ED module though so they may have gone for different file structure for the skins, models & textures. Having said that, I dont have the F14, but the coremods path you listed is same as on my pc, and theres about 20 liveries in there. I just have no way of testing them :(

what are the resolutions of your two monitors?

Are there any resources to show how to create a working custom panel in Helios or edit the Capt Zen ones? I want to create a stripped-down version of the Huey gauges to just show 4 or 5 of the most important gauges in a strip down the side of my secondary monitor. I've worked through the youtube videos on creating the MFD's for the F-18 and it works fine, but theres nothing about the gauges?

Download here: https://www.digitalcombatsimulator.com/en/files/3302014/

I'm using a Korg Nanokontrol2 for additional buttons & knob control in DCS. It runs fine via 2 free plugins - FreePIE and vJoy, then shows up as 2 additional control sets in DCS when you assign controls in settings. I now have 8 sliders, 8 rotary knobs, 35 additional buttons to assign as I wish, far more than I could get with an expensive joystick upgrade. Biggest problem is remembering what control I mapped where, I tend to map non-critical functions like console/instrument light levels, F2, F5, F10 views, then flaps and gear, which leaves my joystick buttons to focus on weapons control. I also use one of the sliders for zoom since my joystick rocker switch for zoom is really cranky. The midi controllers are a really cheap option for people who dont mind a bit of scripting, and when Im not flying, it controls a load of VCV Rack virtual synth settings for me.