GregP

Fix is here: http://forums.eagle.ru/showthread.php?t=162620

This likely isn't the right place to post this, but I don't see any other L-39-specific bug report area. In the latest 1.5.3 version, for the L-39ZA in the default.lua files, the controls to select and deselect the inboard and outboard stations don't fully work due to a typo in the files: { down = device_commands.Button_48, cockpit_device_id = devices.WEAPON_SYSTEM, value_down = 1, name = _('Outboard Stations Select Button'), category = {_('Left Front Panel'), _('Armament Control Panel'), _('Only Front Cockpit')}}, { down = device_commands.Button_50, cockpit_device_id = devices.WEAPON_SYSTEM, value_down = 1, name = _('Inboard Stations Deselect Button'), category = {_('Left Front Panel'), _('Armament Control Panel'), _('Only Front Cockpit')}}, { down = device_commands.Button_49, up = device_commands.Button_49, cockpit_device_id = devices.WEAPON_SYSTEM, value_down = 1, value_up = 0, name = _('Outboard Stations Select Button'), category = {_('Left Front Panel'), _('Armament Control Panel'), _('Only Front Cockpit')}}, { down = device_commands.Button_51, up = device_commands.Button_51, cockpit_device_id = devices.WEAPON_SYSTEM, value_down = 1, value_up = 0, name = _('Inboard Stations Deselect Button'), category = {_('Left Front Panel'), _('Armament Control Panel'), _('Only Front Cockpit')}}, The middle two lines need to be changed to: { down = device_commands.Button_50, cockpit_device_id = devices.WEAPON_SYSTEM, value_down = 1, name = _('Inboard Stations Select Button'), category = {_('Left Front Panel'), _('Armament Control Panel'), _('Only Front Cockpit')}}, { down = device_commands.Button_49, up = device_commands.Button_49, cockpit_device_id = devices.WEAPON_SYSTEM, value_down = 1, value_up = 0, name = _('Outboard Stations Deselect Button'), category = {_('Left Front Panel'), _('Armament Control Panel'), _('Only Front Cockpit')}},

The problem with the flaps is that the middle flap position on the throttle is not a discrete button. The upper and lower positions are, but the middle one is not. In order for the middle position to register you have to bind it to some function for which the upper and lower flap positions are toggles that will turn back off when you return the flaps to the center position. In my experience I've found that almost none of the DCS modules natively support this function, and instead usually require customizing the controls in the LUA files in order to create a function that toggles on and off to the center position.

Ok so, aside from Sporg, has anyone else been able to get a non-TCP clip to work with the TrackIR software?

I'm really hoping this isn't just a temporary bug and will instead be a permanent change to the forums. I just noticed that the module icons at the top are gone, which is something I've been asking for for YEARS now -- as on mobile devices they used to 'stretch' the page horizontally such that the actual threads would only take up about 3/4 of the screen, and I'd have to manually zoom. FINALLY, the forum by default now takes up the entirety of the screen on my phone and iPad. PLEASE ED, if this was unintended, do not bring the icons back. There are obviously way too many modules now to fit anyway, and it made reading the forum really annoying.

Nice video! Those gunpods sure don't seem to pack much of a punch though, huh?

Yes, excellent work, thanks for so quickly updating for the latest version.

Wow, looks fantastic so far! Nice work.

I had the exact same problem happen to me the other day, which now makes me wonder if maybe this only happens when dropping tanks? Have you also tried after firing weapons? I have not had a chance to try it yet.

Hollywood, several users have reported this error of not finding a file ending in "l ua", which obviously should be 'lua'-- might there be a typo in the code that could easily fix this?

I too am trying to get VAICOM with working, starting with the M2000C module, but I'm having varying success -- possibly due in part to my microphone being suboptimal. But one thing I can't figure out -- when I say 'Start Mission', I don't get any error messages in the log, but it does not unpause DCS, all it does is initialize and then do the equivalent of hitting 'escape': removes the briefing screen but doesn't unpause. Should it be unpausing too?

Great find, YoYo! I just confirmed that for me, in 1.5OB, using 2x SGSA does indeed look better than without, and it didn't cost me much FPS either.

If it's highlighted in red, that usually means that whichever buttons you have them bound to are already bound to something else, and thus neither one may work correctly. Try pressing the button you're binding to and see which command it goes to, or just scan the list and make sure it's only bound once.

The X-Keys line by PI Engineering is the only programmable keyboard I've ever found to be suitable for use in my pit. They're pricey, but well worth it IMO; I now own two, the older 58-key version and a newer 80-key version.

Well, aim your Mirage at the ground, hold down the button, and see what happens.

Definitely looking forward to this!

Thanks for sharing these. For those who don't know how to adjust the default view on your own, it's quite simple: 1. LCtrl-] : set keyboard rate slow 2. RAlt+RCtrl+numpad keys : adjust view 3. RAlt+KP0 : save default view Note that obviously, "allow default snapview saving" in the options menu will have to be selected first.

For those who don't know how to adjust the default view on your own, it's quite simple: 1. LCtrl-] : set keyboard rate slow 2. RAlt+RCtrl+numpad keys : adjust view 3. RAlt+KP0 : save default view Note that obviously, "allow default snapview saving" in the options menu will have to be selected first.

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.