GregP

Probably the 'mini HUD' option somehow got checked by accident?

Do you have something other than '1 monitor' selected within the DCS GUI? (Actually I can't even recall whether that option is still there, but I know it used to be.)

Is the system set up yet to verify that we bought the A-10C module before February 2011? I most definitely bought it right when it first came out, but when I go to the NTTR module product details page, there's no serial there; the only option I have is to purchase the NTTR module.

This isn't my work in any way, but I wanted to share a new ReShade/SweetFX config that I've been using and really like a lot. It was developed by a guy for Fallout4; I liked it so much in that game that I decided to try it in DCS, and I think it looks great. All you have to do is unzip his file into your /bin/ directory, and toggle with ScrollLock. In 1.5, it does drop my FPS by about 10%, but given that I'm generally getting 80-90 FPS anyway, it's tolerable.

Clearly you need to check out the Mods & Apps forum more often! There are high-quality A-7, F-14 and F-18 mods out now, as well as a CVN-77 with working meatball on which to make carrier landings.

Looks excellent! Looking forward to trying it out.

Things have radically changed at 4K with the 1.5 beta: a single 980Ti is enough to get you 100FPS. In 1.2.16, however, even two 980Ti's in SLI won't get you up that high.

My god...seems I should've asked you how hard it would be support earlier versions before sinking an entire day into it!

I just spent the better part of my day rooting my Asus TF700T tablet and updating the OS from 4.2.1 to a 5.1.1 ROM, including many forced pauses when I lost patience with the process. But I kept at it and am now up and running, and just tried out the app--fantastic job, completely worth it! Thank you so much for taking the time to develop this and share with the community.

Whoa, very excited to try this! I've been using an old Android tablet as a sort-of kneeboard for months now, primarily to see Lino's Beacon Map and flight manuals. But having customizable kneeboards for each aircraft now--that's incredible.

Or just follow Zabuza's instructions above. By the way, the L-39 module currently has the same problem in 1.5.

I'm in the same boat -- I get about 33% better FPS on one card compared to choppy performance on two in SLI when forcing AFR2 via Nvidia Inspector. Frustrating!

Just wanted to note that the A-10C lua switch commands you posted below do seem to have been superceded (likely around the time of the 1.2.8 patch, as I noted last year) by a different kind of lua switch logic in later DCS aircraft, where instead of having different names for each switch position, the positions are specified using the 'value_up' and 'value_down' parameters. In practice, I've found working with the latter far easier, as I use lots of custom switch commands in the MiG-21, MiG-15, F-86, etc. What you tried seems to me to have been the right change, but you say it didn't work. Can you clarify exactly what kind of switches you're using -- are they really 3-position toggle switches? If so, have you gotten them to work with any other 3-position commands in DCS? And are they on the 2235 or the LB boards? The fact that adding the 'up' line didn't work makes me think the switch you're using just doesn't support what you're trying to do.

Seat up and down are commands assignable within the controls GUI.

Same issue here, and also noticed that when I click on a command group name, like Flight Controls, it used to automatically open the relevant command list--but now it does nothing and instead you have to click on the arrow on the right. More important for me, though, is: ED, can we please, please finally get a controls GUI that scales with resolution? There's simply no good reason to restrict it to that small size. I've got 8 controllers and constantly scrolling left and right gets old very quickly.

Ah there's the solution: VAC and VoiceAttack are two different program, and I thought your profile was for VAC. Problem solved, thanks.

That looks like a fantastic addition to this mod, however, the VAC profile you included has extension VAP and I can't find any way to get VAC to recognize it. Are you sure that's a VAC file?

As others have said, forget using tracks for this campaign. BUT, Tacview works perfectly fine and is actually more useful than a track could ever be, so I'd strongly recommend you try that instead. It's really a phenomenal tool.

As no one specifically mentioned it, I just wanted to point out that there is a logic to the numbering of the pylons (in the cockpit), even if it's a poor one. :) The numbering is hierarchical, progressing from inner to outer while alternating sides: Thus, start on inner left = 1 Inner right = 2 Outer left = 3 Outer right = 4 It is indeed frustrating how the R&R and ME armament screens use a different logic. I tend to just ignore those numbers, as the only ones you'll actually need when flying are the in-cockpit ones.

Question for those who have more experience with this awesome campaign, as I *just* jumped in for the first time last night: Knowing that I was going to die fairly quickly, I ran the mission MP rather than SP. When I did die, I used 'jump into' to take over another MiG-21, and I then repeated this process when I died 2 or 3 more times. But at least 3 times when I jumped into another MiG, the engine would spool down and I'd get the 'DC GEN' red warning light. Nothing I could do after that point would bring the engine back up. So I'd then have to jump to another MiG until I could finally find one that didn't do that -- which turned out to be maybe 2 of the 6 of 7 I jumped into. Has anybody else experienced this?

Has anyone had any luck recently getting help with activation issues from LNS? Starting over a week ago, I've now contacted LNS three different ways and gotten no response. It seems Cobra847's inbox is too full to accept new messages, so PM'ing him doesn't work either. Any suggestions?

Wow, nice work! Can't wait to give this a try. I too had thought about how to use J2K to select weapons and had given up.

I would guess the mismatched refresh rates is indeed the problem, because in my experience, several recent Nvidia drivers have set refresh to 59 by default and it's THAT that causes problems. I had some SLI flicker that was solved by changing refresh to 60.

Whoa, nice find! That's sure to come in useful to some of our fellow simmers. Thanks for sharing that.

A few more commands I've come up with: --Alternate Anti-Surge {down=device_commands.SurgeDoors,up=device_commands.SurgeDoors,cockpit_device_id=devices.ENGINE,value_down=0.0,value_up=1.0,name='Alternate Anti-Surge Auto',category='Engine'}, --Alternate Air Relight {down=device_commands.AirStart,up=device_commands.AirStart,cockpit_device_id=devices.ENGINE_START_DEVICE,value_down=0.0,value_up=1.0,name='Alternate Air Relight On',category='Engine'}, --Alternate Wing Fuel Pods Cover {down=device_commands.SbrosKrilBakovSafetyCover,up=device_commands.SbrosKrilBakovSafetyCover,cockpit_device_id=devices.WEAPON_CONTROL,value_down=1.0,value_up=0.0,name='Alternate Wing Fuel Pods Cover Open',category='Weapon Control'}, --Alternate Drag Chute Disconnect Cover {down=device_commands.DragChuteSafetyCover,up=device_commands.DragChuteSafetyCover,cockpit_device_id=devices.CHUTE,value_down=1.0,value_up=0.0,name='Alternate Drag Chute Disconnect Cover Open',category='Weapon Control'},