GregP

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'},

Single-card results: MiG-15: 50 MiG-21: 46 Mi-8: 44 F-86: 53 So SLI is giving me the following improvement: MiG-15: 42% MiG-21: 26% Mi-8: 41% F-86: 28%

Wow, I look away for a few days and Chuck bangs out another awesome guide. Excellent work as usual--thank you!

Good question -- I have checked, yes, and CPU usage never goes above about 70%, whereas GPU usage varies between 60 and 100%. So I'm thinking at this point I'm still being limited primarily by GPU power. In revisiting my F-86 results above, I realized that I was using a different takeoff airport in that case compared to the others -- with that fixed, my 980 Ti result is 68 FPS, not 45. Of course it's now too late for me to compare against the 970 results, but at least now all four tests are in the same general range.

EDIT: SOLD I bought this card in November but recently upgraded to a 980 Ti. This is the short 8" ZT-90101-10P model. Never been overclocked and it's in perfect condition. I've got the original box and all accessories. Heatware is here. $275 shipped within the U.S., and I'd prefer Google Wallet payment.

Today I upgraded from two GTX 970s to two GTX 980Ti's. This decision was driven almost entirely by The Witcher 3, as at 4K gameplay wasn't quite smooth enough with the 970s. My framerate in W3 went from 43 to 56 FPS, a nice nearly 33% increase, but my somewhat disappointing DCS results were as follows, all examples being simple sitting-on-the-runway takeoff missions that I typically use. SLI GTX 970 4GB, 352.86 drivers: MiG-15: 59 FPS / 3133 MB VRAM MiG-21: 55 FPS / 3294 MB Mi-8: 50 FPS / 3227 MB F-86: 44 FPS / 3622 MB SLI 980Ti 6GB, 353.06 drivers: MiG-15: 71 FPS / 3152 MB MiG-21: 58 FPS / 3277 MB Mi-8: 62 FPS / 3261 MB F-86: 45 FPS / 3674 MB Those increases percentage-wise were thus: MiG-15: 20% MiG-21: 5% Mi-8: 24% F-86: 2% With the VRAM usage being nearly identical. So, I had hoped that this upgrade would sort of future-proof me for DCS2, but now I'm not so sure -- the current results obviously very much depend on which module you're talking about.

Ah ok, thanks for the clarification, guys. So has anyone had any success using just a single audio card, but plugging the Buttkicker into one of the card's unused ports? I'll test this weekend to verify.

Andre, I just tried the sound mode expansion module and I first want to make sure I understand what this is testing: Am I correct that you have added simple sounds for landing gear and bumps, that should work for all aircraft, and that will get played over our normal output devices, such as 5.1 speaker systems as well as a Buttkicker? If that's correct, then yes, the module seems to be working for me. However, since there were already bass tones from DCS itself corresponding to these effects, my Buttkicker is not acting any differently than without the sound mode module; I can hear the effects playing over my speakers, but there's no difference in what I actually feel. Is this the way it's supposed to work? I presumed you'd be adding additional deep bass tones, so that either the subwoofer or Buttkicker alone would play those sounds.