Bullant

I'm surprised nobody has chipped Wags for dropping the gear well in excess (by over 100 kts) of the 250 kt limit ;)

Yep knobs and buttons not switches. Thanks for the info, might have to pass on this form of lighting for now unless I can magically find a supply of authentic knobs and buttons!

No, not another question about panel backlighting. This is in regards to the lighting on the actual switches. This video shows exactly what I mean from about 13 seconds in when the NVGs are disabled. Now, my question is: All of the lighting that is visible on the DDI buttons, UFC buttons etc ... is that active lighting or something like fluorescent paint? I was thinking of getting some glow in the dark paint and painting the markings on the switches unless someone has a better idea?

In for a penny ... if I am going to do my F18 cockpit, I am going to do it right. I've set dad the task of learning French and building me some prototypes based on the previous post. Now the question is ... does anyone know how many MHS are in the F/A-18C, and their mode of operation? The seven I have identified so far are: APU: Two position, with a signal to return it to the "OFF" position. Switch can be manually moved to OFF. ENG CRANK: Three position, with a signal to return it to centre the "OFF" position. Switch can be manually moved to OFF. LTD/R: Two position, can only be moved to the ARM position if a host of conditions are met, otherwise springs back to SAFE. GND PWR 1, 2, 3, 4: 3 position, can be manually moved from centre position to the A ON or B ON positions. Will snap back to centre position when ground power is removed or engine power is applied. These will work fine with the solution above, the only issue I'd see is if there is a switch like the A-10 EAC where the magnet stops you from manually moving the switch out of the held position.

I am building up an excel spreadsheet right now to work out how many of each type of switch/pot/encoder etc I will need. For your UFC/HUD control as posted on the previous page, by my calculations you will need: 26 momentary push buttons which can use a 6 x 5 keyboard matrix and therefore only use 11 pins. 10 two position switches (10 more pins, with the other leg of each switch connected to ground). 4 of these are for the comms volume, HUD brightness and AOA brightness pots that will need to have an integrated switch for the OFF position. 2 three positions switches (4 more pins) 2 rotary encoders (4 more pins) That gives a total of 29 digital I/O pins. You will also need 7 analog inputs for the 7 pots. A uno isn't going to cut it, will need to move up to a Mega or use two unos and split the functions across the two boards.

When using the Arduino to implement a matrix, you are using the row as the supply and the column as the ground (or vice versa). Pressing a button completes the circuit. The logic implemented in the matrix handling class is: for each row { set the output high for each column { if the input is now high (because a switch has closed the circuit) { set a flag to indicate that the appropriate key has been pressed based on the row and column } } } This explains it really well: https://www.baldengineer.com/arduino-keyboard-matrix-tutorial.html Here is a very simple example, hooking up the 4 N, S, E, W buttons from the UFC. You would connect on pin from the N key to D0 and the other to D2 You would connect on pin from the S key to D1 and the other to D2 You would connect on pin from the E key to D0 and the other to D3 You would connect on pin from the W key to D1 and the other to D3 The logic is exactly the same as you make the matrix larger. Note also that for the UFC you would only use the matrix for the (momentary) push button switches. For the 2 position and 3 position switches you are going to need to use 1 and 2 extra digital input pins respectively for each switch.

That's perfect, thanks heaps!

Excellent :) Starting work on a pit for the upcoming DCS:F18C release. Looking at the NATOPS manual and the DCS screenshots, it doesn't seem to match either of your option. Back in a minute with a screenshot. Here we go: Note that this looks almost exactly like your first image, but without to AUTO option on the top rotary.

At 400% I get these measurements for the ECS panel. Can someone please confirm exactly what the internal screen width of the DDI should be? My plan is try and get DDI and MPCD built as a starting point but don't want my measurements to be off. fwiw, it is 4 3/4" left to right and 4 5/8" top to bottom for the screen area of the DDI when I print at 400%.

Use chrome and let it translate the page for you, that worked for me.

You must be using some sort of magic. I follow exactly what you do and end up going for a swim. Not even close enough to the ship to burst into flames lol. Bravo, this is going to take some practice.

Found the answer myself, posting here in case anyone else was not aware that there is a kneeboard that can be toggled on/off with rshift-K. For some reason this is enabled for display in the HUD view by default.

I can't help with your question but that looks great and I'd love to get a copy once you are happy to share :)

as per the title, when I switch to F2 HUD view, there is a moving map/GPS displayed. How can I turn this off? I have a projector for my main display and a second monitor running helios, all I want in the HUD view is the HUD and the terrain :)

Have a read here: https://forums.eagle.ru/showthread.php?t=196646

Did you bind the keystrokes for enabling the MFDs? And then actually press the bound keys?

Anyone have a link to this that isn't behind a paywall?

This is an amazing document, great find!

Haha love it, that looks oddly familiar, although I am yet to try a ship landing!

OK so I have bound the keys as suggested, and hitting them makes the MFCDs appear in the top right hand corner of the screen. Now, I have: * Added the following to my monitorsetup.lua (I have a 1920x1080 projector stacked "on top" of a 1920x1080 monitor that I want to display the MFCDs on). These are the same settings as I use for the A-10C MFCDs, I have just changed the names LEFT_MFCD = { x = 67; y = 120+1080; width = 445; height = 445; } RIGHT_MFCD = { x = 1406; y = 120+1080; width = 445; height = 445; } * Enabled the commented out lines as indicated by mkiii above * Made sure I have the updated ViewportHandling.lua in C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Scripts\Aircrafts\_Common\Cockpit that defines the try_find_assigned_viewport macro Ignore me, it works :) The move to the Beta screwed me up, I forgot to choose the extended 1920x2160 resolution

Just updated to the latest version, noticed that the tooltip for the AV-8B has been copied and pasted from the Viggen. Thought you might want to know ;) Also, when you select the first menu option under Application Information to get to this thread, the URL is incorrect, it is %20//forums.eagle.ru/showthread.php?t=160053 rather than http://forums.eagle.ru/showthread.php?t=160053

Today is the first time I've read it, and I saw quite a few people asking which version it would be released for without an answer. Look it is not the end of the world, but it is disappointing to not have been able to be prepared by having Beta installed.

Great news on the new copy protection system. Bugger on needing Beta, its the only version I don't have. Big download incoming :(

Is it time yet? ;)

Paul Hogan has a lot to answer for lol