mx22

Sorry, just got around to flying your mission again. Boxes are indeed there, but in VR I had to zoom and really look for them; practically invisible...

Not sure why, but in your night fog case 3 recovery mission there is something wrong with HSI page. When turning on TACAN and trying to select it on DDI with button, it won't put a box around TACAN. It still works as distance to TACAN starts to display on HUD, but then when plotting course - bearing line would not display on HUD heading tape. Also, a somewhat similar problem with ICLS - pressing on the DDI button does not put a box around it, so you are stuck flying and hoping that it worked (which it did).

Some people say the announced change did not make it into this week's patch, but to me flaps down/gear down handling did change - I don't know if it's wheels drag reduced or throttle input, but it does feel smoother and easier to control now.

For those who can't find goggles mappings - they are listed under Sensors drop down menu.

Matt - thanks a lot!

Somehow I thought ED would add Case III quick mission after Matt's video, but alas... Has anyone created their version yet and would be willing to share?

Yes, it saves... Also, just as someone already mentioned - I would not backup controls settings and then load them up on a new version. While it may work, it may also mean that something in controls changed and there is a need for a total reset - this is alpha, not even beta, version of the module so everything is subject to change... It took me 5 minutes tops to reconfigure Warthog throttle and joystick; if you have problem remembering where you mapped your buttons, maybe it is time to rethink your mapping or what is being mapped.

I figured out the problem - I must have assigned MFD2 buttons to act as mouse buttons some time ago and forgot about it. This is why, when trying to reassign buttons, pressing on them showed on action on the button assignment screen. I'm not sure why manually forcing the button assignment would neither overwrite, nor show a DCS message showing that button was already assigned to something else...

Nope, manually assigning button from a drop down did not help. I've played a bit and realized that my MFD2 Button 10 (on the right side, bottom) acts as right mouse button and if I however mouse cursor over any button, pressing the button will activate whatever right click on that particular button does. Likewise, MFD Button 11 (on the bottom row, on the right) acts as left mouse click. MFD Button 15 (on the bottom row, on the left) does not appear to have any action at all. Any clues?

Hi guys, Has anyone encountered a problem where not all of the MFD buttons are working in DCS? All of the buttons work just fine in Windows joystick interface, but some of the buttons do not work in DCS. By not working I mean that DCS does not register a button press at all (ie can't even assign them to anything). Thanks!

Thanks for clearing this up! Hopefully these get released soon then, I'd like to try them out.

Looks like leg movements are independent from each other? Not sure I like that.

Here are my commands for gear and hook. Gear, 2 way switch, down - gear down, up - gear up: { down = gear_commands.GearHandle, up = gear_commands.GearHandle, cockpit_device_id = devices.GEAR_INTERFACE, value_down = 1.0, value_up = 0.0, name = _('Landing Gear Control Handle - 2 POS'), category = {_('Special For Joystick'), _('Left Vertical Panel')}}, Arresting Hook, 2 way switch, down - hook down, up - hook up: { down = gear_commands.HookHandle, up = gear_commands.HookHandle, cockpit_device_id = devices.GEAR_INTERFACE, value_down = 1.0, value_up = 0.0, name = _('Arresting Hook Handle - 2 POS'), category = {_('Special For Joystick'), _('Right Vertical Panel')}}, Just keep in mind that unless you have 'Synchronize cockpit controls with HOTAS...' option checked, I don't think first click on the switch will work. So, for example, to get gear down, the first time around you would need to cycle it once up and down before it starts working.

Warthog AB detend is not push through like it is on F-18.

What is your altitude after the 180 (final turn) as you start lining up. Jabbers is around 300ft mark as he starts to complete the turn and 210ft as he's lined up. If you hit these numbers, you will see the ball. As you approach the ship and try to land, at some point you come close to the correct glideslope and that's where you are start seeing high/low ball - most likely by that point it's too late to do anything, but try to slam the deck. What would really help is LSO who can say high/low as you are in the groove.

Are you guys approaching the carrier at the right altitude? If you are too low or too high, you will only see horizontal green lights. I'm still trying to get a hang of proper carrier landings, but I never had a problem seeing horizontal green lights and as long as I'm somewhere near the right altitude, I will also see meatball.

Just to follow up on my post above. When I launch F-18C Carrier landing quick mission, using settings from the first post of this thread, I'm at around 32fps. This is with EVGA 1080ti... What kind of frame rates are you guys getting?

The difficult part of carrier approach is that you need to be hitting all kinds of specific numbers in a very short time window during the last/second 180 turn (degrees of bank, AoA and vertical velocity). I feel you will get more from just trying all kinds of turns during which you maintain proper AoA and some predefined vertical speed.

Raven One spoilers below

Nope, it needs to be 'FA-18C_hornet'. See my comment a couple of posts above with a possible solution.

How did you upgrade to 2.5? If you've done it from 1.5, more then likely you will need to put files under C:\USER NAME\Saved Games\DCS\Kneedboard\FA-18C_hornet DCS folder should already exist under Saved Games

I think poster above meant to point to this: http://www.dcskneeboardbuilder.com/

In all honestly, I don't think this particular page will work very well in VR. Given the resolution and size of kneepad, I don't think it will be readable at a glance. And if I have to zoom on it, I might as well bring the keyboard up...

Any updates now that Hornet and Persian Golf are out? Just wonder if settings in the first post are still relevant...

Does anyone else have this problem with a kneeboard on pilot's body? Kneeboard itself works fine if I bring it up via shortcut...