GPatricks

This is the error I get when trying to Add and Interface - maybe some nice person can create a new DCS profile (think DCS must be in default folder?) and save it? Maybe I can build from there? I tried unplugging a few USB devices, did not help.

Back to Helios in DCS to try and get physical MFDs to show up in VR (MR). I have them working perfectly in 2D on the flatscreen but in VR NG, figured I would try Helios as it works perfectly in BMS. First issue, trying to add an interface causes an error window, so can't create from scratch. I can load profiles like Capt. Zeens but too many errors trying to pare it down to just the two MFDs on my MFD monitors, can't just copy\paste the displays like I can in BMS, any idea a direction to take?

Nope! In my haste to get 6.4.1. installed I downloaded the regular version, sorry!

Not crashing, but with the latest version(s) I no longer have Add-Ons (gives a quick error then I get "Some Add-ons were not loaded because this build of ReShade has limited Add-on functionality") and don't see any way to get rid of the Haze anymore, is that just the way it is now? Never mind, i'm an idiot. Updated to 6.4.1 and did not download the Add-On Support version...

Lol, I wish I knew was just looking for it. Orbmu2K's Github is up to version 2.4.0.18. I ran that and it's laid out differently. Look in Section 5 - Common, DLSS - Forced Preset Letter.. null

Be sure to have a later version of Profile Inspector..

Agree, just set "SR Preset" in "0.2 - DLSS Overrides" to Preset K (v3.10+) and done.. I did it in both the "_GLOBAL_DRIVER_PROFILE (Base Profile)" and in the "Digital Combat Simulator Black Shark" Profile, not sure if that's necessary, but it's done..

I can barely remember what button does what function, let alone have 100 choices for each device!

Unless you have a specific need to have less # of controllers listed there is no reason to use TARGET at all (especially in DCS), just program it normally in-game controls settings. Each of the devices you have: TM MFD frames, TM Warthog Joystick, TM Warthog Throttle, etc. have their own set of 32 DX button presses. As @Lange_666 showed above, you can use the "Off" modifiers to show that a switch is turned off on the throttle (where no DX# is assigned). BMS has a "Release" function modified in it's Alt-Launcher key bindings section that does a similar thing. Now if you have other sims that accept up to DX120 you can use TARGET to program your TM Throttle to send a DX press for ALL switch positions. It still remains a separate "Device", and you don't have to use the "OFF" (or Release in BMS) modifier to use a switch position. In the pic attached you can see my throttle column, and the DX assignments above DX32 assigned. Hope this helps.. null

I am talking about running a Target profile/script that (in all games (not just DCS) that can see above DX32) assigns a DX press to all switch positions on my Warthog Throttle. The stick only has -32 DX presses available, no need to touch it. Without the script running, I do not see a way to increase the actual DX output of the throttle without a TARGET script running. And now this upgrade has broken my existing DX128 script (Line 883 error), so need to try and figure that out.. And it was YOU that actually solved the execution error on "Line 883" a couple years back in this thread!

Really? News to me, thanks, i'll have to take a look at it. The profile I run just effects the throttle as it can use to ~DX45, but not running anything extra would be better (other than what it will mean to my Keybindings in all my games). Running 3.0.23.2003 now.. Edit :Just installed 3.0.24.618.rev1 and I don't see how to get more than 32 DX buttons to work in the Warthog Throttle, please point me to how this is done..

Each Device has it's own range of DX buttons. MFD1 has 1-32, MFD2 has 1-32, ICP has 1-32, HOTAS Stick has 1-32, HOTAS Throttle has 1-32. The HOTAS Throttle has the ability to send a DX press for almost EVERY switch position (DX1-128) if you want it to, if you run a DX128 profile to go beyond the 32 button limit it comes with. In DCS you can use the modifiers to achieve close to the same thing, but I use a DX128 profile that loads automatically on startup.

After all this DLSS stuff I ended up with MSAA 2x and my old 90FPS back....

Getting a 404 error on the link..

The new 2.4.2.3 Profile Inspector (NVPI-Revamped) shows it a bit differently.. null