Vol4Ever

On the Settings/Special main tab - - afterburner detent setting is set to Always On. On the Settings/Controls main tab, Throttle Quadrant dropdown - - there aren't any bindings on the finger lift options FYI, I have *not* changed any of the physical hardware on the throttle. I've seen it mentioned in a few places, but is there a piece that needs to be physically flipped or something like that? Never quite understood the stuff I've been able to find, but probably haven't looked in the right place for correct instructions yet.

Similar problem to a post below, but mine is OPPOSITE behavior. Other poster can't do anything without going to full afterburner. My Thrustmaster WH throttle works fine on the increase/decrease, but burner won't light at all. Pretty sure it has something to do with the detent, but I'm not 100% sure where to go to correct it. Tips on which settings to poke around? Thanks!

Did you try the solution from the posters above about setting the overall resolution on the main video settings page to match? You'll probably still have to edit LUA file manually to force what you want to be where on each monitor. A little extra pixel math will be required since all monitors aren't identical size / resolution, but I found it helps to sketch all 3 monitors on a sheet of paper and label the x,y coordinates of the 4 corners on each. I can do that for you, but it would be more helpful if you tried it first yourself to start getting a feel how the pixel math works. For starters you should make your MAIN overall resolution setting as 3880 x 1060 and then 3.6604 should auto-calculate as aspect ratio. That will at least define the complete screen size in the software, although the 2 side monitors will have dead space since they are smaller in height. One other tip I found which was completely by accident. Once the game loads with everything split across a single monitor, take your mouse and randomly click anywhere on one of the other monitors & screen adjusts. No idea why, but it worked for me . . . . . after entering that top level pixel definition for the whole setup. All that gobbledy gook make sense? ~Vol

Well son of a gun. You just figured it out and didn't realize you did!!! Unticked that one more option, and kaboom. Control functionality jumped over to the sim settings. THANK YOU! I was just short of uninstalling and re-installing the whole blooming thing and probably would've ticked that same Avionics box again. Wasn't 100% sure what it did other than label surrounding aircraft, but evidently also completely screws up the controls. LOL I had already manually re-programmed all my buttons back and that one check box fixed it. For what it's worth, I *tried* going to GAME control settings and loading revised LUA file to use as a starting point, but that was a total disaster. It did some of the stuff from my OP like putting stick button number assignment text into the rudder category (which doesn't even have buttons??). I guess the software can't properly decode and sort the LUA between GAME versus SIM since they have completely different list of settings, but that's OK. Not planning to use game mode anyway. You ARE the man. Have a great night, kind sir! ~Vol

I don't see anywhere in Mission Briefing that it specifies, but you may be onto something. I have Caucasus and Persian Gulf modules, and have been grabbing either Dark Start or Start On Ramp simply to test controls and buttons. *IF* those missions do force the Game settings regardless of checkbox, do they have their own LUA files that I can force to use Sim setup instead? I never really played the game super heavy, but I'm planning to start going through some of the tutorials now that I'm getting deeper into it with the second monitor & rudder pedals! :)

joystick.zip dcs.log WRF-FA18C-Thrustmaster.diff.lua See if those work. Is there a toggle I'm missing to tell software to use "F/A-18C Sim" configuration dropdown instead of "F/A-18C Game"? I'm pretty sure those 2 groups are somehow conflicting. Only related setting I can find is "Game Flight Mode" in the Gameplay settings menu, and it's UNchecked. Just for grins, I'm also uploading a copy of LUA backup made before adding rudder pedals and updating to latest software revs. FYI, the file is dated March 2020 so it hasn't been THAT long ago. Thanks!

EDIT: I just figured at least part of it out. I have every setting I can think of set to "Simulation", including the dropdown on the Adjust Controls menu. However, some of the controls are still responding to the "Game" dropdown settings. Is that a glitch? "Game", for example, doesn't have wheel brakes nor dual throttle on the axis page. I would think these 2 dropdowns are supposed to be a one-or-the-other. Basically, if I have Sim in the dropdown, why would I have to worry about whatever is in the Game menu? Probably missing something obvious where I'll feel dumb . . .

I've browsed boards but haven't found my exact issue discussed. Been away for a while, but got second monitor and also a new rudder set to go with existing HOTAS Warthog. Renewed interest! Took some doing in other threads, but I finally got second monitor setup exactly like I wanted without much effort. It amazes me how programmers had the foresight to allow so much (relatively easy) customization via user editable LUA files. Doesn't take high level IT specialist to do all kinds of cool things. Anyway, then I went to actually fly my trusty F18 and problems started. I don't know if it was the rudder addition or DCS version updates, but my custom controls layouts were completely garbled. When I tried to manually load LUA backup, stuff didn't populate in correct columns (setup screen now has extra pedals column). Kind of a pain, but I just deleted entire user/Saved Games/DCS/ subdirectory & let software rebuild everything from scratch. Not a big deal as I have a hard copy graphical printout of bindings to use as a quick reference & there was really nothing else of interest saved. Still had major problems, so I took it one step further. With F18 loaded, I went to controls adjustment screen and manually cleared every single column for all three devices, including axis settings. Other than keyboard and mouse default bindings, there was *nothing* else assigned. First step was simply re-assigning basic pitch / roll / rudder / left & right thrust / left & right brakes on Axis Settings screen. Programmed those & little "action" bars underneath settings moved exactly in coordination with proper external input, but here's where it gets bizarre. Even though control axis assignments have been double and triple checked, the aircraft DOES NOT respond accordingly. It's not a calibration issue as some controls don't even move the correct surface. For example, wheel brakes operate the elevator/pitch. Left throttle moves rudder. Right throttle does nothing. I haven't the foggiest clue what could be wrong. I even reinstalled all the Thrustmaster drivers & its control panel app correctly "sees" all 3 controllers and their movements operate correctly on test screens. The strangest part is they show to operate correctly in the DCS SOFTWARE screen, but the aircraft doesn't respond accordingly. Sorry for the long note, but short of reinstalling entire software package, which I don't want to do @ 100 plus GB, what else could be gummed up to cause such weird behavior? Feel free to ask questions if I can describe anything more clearly. Can also do screenshots, but there's nothing to see other than a whole bunch of controller blanks with only axis commands defined. ~Vol

That got it. Now if I could just figure out kneeboard code IF it's possible. I really wanted external aircraft camera view included on my second screen, but poster in another thread has me convinced that particular option isn't possible. :( Not sure about kneeboard, but at least I have the 3 primary MFCD's now. Thank you!!!!! ~Vol

I have my (2) MFCD's set up on new second monitor, thanks to this thread and PeterP's tutorial document. Can someone tell me proper code name to add AMPCD to display? I tried replacing "RIGHT_MFCD" with "AMPCD" in lua file, but it didn't work. Hope that question makes sense . . . Thanks!

F-Key Views is a much better way to describe it (thanks). Kinda bummed as I really do like seeing the aircraft itself, but have to stay with the in cockpit view, other than quick toggles, while playing. I guess that's what the replays are for. :) What about kneeboard? This is my first attempt at doing this & PeterP's tutorial was extremely helpful. I fully understand pixel counts and how to define x/y's so everything appears where I want it, but I really wish there was some sort of consolidated list showing EVERY various item that can be put on second screen. Maybe that info can be gleaned from each aircraft's own LUA file somewhere since they all can have different features, but I haven't figured out how to do that yet. For now, I'm using both MFCD's and AMPCD just to get comfortable with editing. ~Vol

Pretty quickly learning LUA file structure & editing via this forum (thank you)! My question deals with external aircraft view camera. Is there applicable code for monitor LUA file so external camera could be shown in a view window on second monitor along with LEFT_MFCD and RIGHT_MFCD? ~Vol

Haven't seen this one covered before. Just got second monitor hooked up today, and of course DCS is one of first things I launched. Poked around in settings just to try one of the built-in configs at random to see what happened. Picked "Camera+LMFCD(on right side)" for grins and almost got in trouble. It split only 1 monitor's view in half, chopping both displayed screens in half while *nothing* appeared on second monitor. Biggest problem was I could no longer see the "apply" button which gave me no way to change it back! Thankfully browsed forums and manually edited proper text files to reset back to default 1 screen. Did I miss a second update setting needed to utilize second monitor, possibly something in one of the pixel resolution fields? I have 2 identical monitors set at 1920 x 1080 with the following final overall goal. May take me a little while (and more browsing!) to get it programmed, but first step is finding out why second monitor is blank. Anyway: Main cockpit display on left monitor Top half of right monitor = external camera view Bottom half of right monitor divided into thirds, with following layout - - LMFCD (which I'm assuming is same thing as DDI on FA-18?) + AMPCD + RMFCD Might even get froggy and calculate in some small black border spaces around each, but that would be later. :) Any tips greatly appreciated! ~Vol

MODS: Please feel free to move thread. I accidentally posted in wrong forum. Sorry about that.

Yeah. That saved games folder is where I had my custom Warthog F18 layout lua file. File is still there, but controls profile doesn't change when I try to import. And I lost all of my graphics customizations. It was really weird. I guess I'll just chalk it up to being unlucky user with one of those random errors somewhere. Like I said, just venting. :( ~Vol