Bullant

And I will say again that you are wrong. They are miles apart, as my screenshots show. Have a look just up above and you will see a shot of mine with the brightness turned down. It is still terrible. Thankfully for myself and the others affected by this, the devs agree with me.

So close. I have the F18 talking to DCSBios and vice versa. I've made up a simple switchbox with: Landing gear, launch bar, hook, ldg/taxi light, anti skid and hook bypass switches. I have created and f18 lua with entries as below: defineToggleSwitch("GEAR_LEVER", 5, 3001, 226, "Gear Panel", "Gear Lever") defineToggleSwitch("LAUNCH_BAR", 5, 3002, 233, "Gear Panel", "Launch Bar") defineToggleSwitch("ANTI_SKID", 5, 3003, 238, "Gear Panel", "Anti Skid") defineToggleSwitch("HOOK_LEVER", 5, 3004, 293, "Gear Panel", "Hook Lever") defineToggleSwitch("LDG_TAXI_LIGHTS", 8, 3001, 237, "Gear Panel", "Landing/Taxi Lights") defineToggleSwitch("HOOK_BYPASS", 9, 3001, 239, "Gear Panel", "Hook Bypass") This was based on the following entries from clickabledata.lua elements["pnt_226"] = LDG_Gear_Control_Handle(_("Landing Gear Control Handle, (RMB)UP/(LMB)DOWN/(MW)EMERGENCY DOWN"), devices.GEAR_INTERFACE, gear_commands.GearHandle, 226, gear_commands.EmergDown, 228, 4.5) elements["pnt_233"] = default_button2(_("Launch Bar Control Switch, EXTEND/RETRACT"), devices.GEAR_INTERFACE, gear_commands.LaunchBarSw, 233, anim_speed_default) elements["pnt_238"] = default_2_position_tumb(_("Anti Skid Switch, ON/OFF"), devices.GEAR_INTERFACE, gear_commands.AntiSkidSw, 238) elements["pnt_293"] = default_2_position_tumb(_("Arresting Hook Handle, UP/DOWN"), devices.GEAR_INTERFACE, gear_commands.HookHandle, 293) elements["pnt_237"] = default_2_position_tumb(_("LDG/TAXI LIGHT Switch, ON/OFF"), devices.EXT_LIGHTS, extlights_commands.LdgTaxi, 237) elements["pnt_239"] = springloaded_2_pos_tumb2(_("HOOK BYPASS Switch, FIELD/CARRIER"), devices.CPT_LIGTHS, cptlights_commands.HookBypass, 239) and devices.lua devices["GEAR_INTERFACE"] = counter()--5 devices["EXT_LIGHTS"] = counter()--8 -- External Lighting devices["CPT_LIGTHS"] = counter()--9 -- Cockpit Lighting This is the relevant part of my sketch DcsBios::Switch2Pos gearLever("GEAR_LEVER", 2); DcsBios::Switch2Pos launchBar("LAUNCH_BAR", 3); DcsBios::Switch2Pos hookLever("HOOK_LEVER", 4); DcsBios::Switch2Pos ldgTaxiLights("LDG_TAXI_LIGHTS", 5); DcsBios::Switch2Pos antiSkid("ANTI_SKID", 6); DcsBios::Switch2Pos hookBypass("HOOK_BYPASS", 7); This is where it gets weird ... The landing gear lever does nothing The Launch bar switch enables the emergency landing gear (rotates the handle) The hook lever toggles the anti skid switch LDG/TAXI light switch appears to do nothing Anti Skid switch appears to do nothing Hook bypass switch toggles the panel lighting between off and full on I can see in the dcsbios window that the correct commands are being toggled as I hit each switch, so I know I have my sketch setup correctly to match the commands in the aircraft lua, so the problem must be in the definitions in there. Any help greatly appreciated (Ian??). I looked at the A10C lua a LOT before starting on this and it looks as though I've followed the correct process, but obviously not. I plan on releasing this for other people to use once it is working ... edit: some more info. using the dcsbios live data view, I can see each of my configured entries properly changing when I click on the appropriate switch/lever in the cockpit. Weird. Unfortunately I can't test in the opposite direction as the controls to force a state change from the live viewer appears broken (for all modules).

Thanks, and that was exactly why I compared it to another screenshot rather than a photo of a real HUD. It appears the devs have acknowledged that this is a bug, so hopefully there will be a fix soon-ish because it is horrible flying with it as it is now.

So happy to see this, good work mate!

A bit more info. My graphics settings: Tried turning down the brightness. The fonts are still too large and blurry and even harder to read:

Every single module has this same issue.

So I have noticed that my fonts on the HUD and DDI are larger and blurrier than everyone else. Attached is a screenshot of what I have and what I expected (first image is mine, second is stolen from someone else). Any ideas?

Definitely not. If you have a look at the detent piece with the cover off you can see the front edge where the throttles stop requiring lifting. Simply slowly file down that edge, testing constantly until you get to the point where you can push forward over the detent with the required amount of resistance.

$8 for the shapeways item plus $30 delivery. Much prefer 5 minutes with a file and a bit of patience.

For what it is worth, these are my settings for with throttles set to slider and custom curve 0 - 6 - 16 - 24 - 33 - 43 - 57 - 67 - 80 - 90 - 100 I also modded the detent by filing down the leading edge slowly so I can push through into the A/B range without having to use the lifts.

For what it is worth, these are my settings for the F/A-18C: 0 - 6 - 16 - 24 - 33 - 43 - 57 - 67 - 80 - 90 - 100 I also modded the detent by filing down the leading edge slowly so I can push through into the A/B range without having to use the lifts.

Agreed. Something is borked with the Hornet.

Meh I'm out. 11pm here, it would have been nice to start the updater so it was ready in the morning. Will just have to wait that bit longer tomorrow.

LOL, that has to be some sort of record!

As as software developer, I'd say no chance. They would have had a build a day or two ago that they have smashed the hell out of before declaring it ready for release. Developing right up to the moment of release is a recipe for disaster ... I second the thought that they are just sitting back having a bit of a laugh ;)

Yeah, no. It's not.

Y? 9pm here, willing to pull an all nighter, but some indication of release time would be great ;)

It depends on how the F18 configuration files are laid out. I tried doing it for the AV8B but could not get it to work. Hopefully the hornet is setup like the other modules in which case I plan to have a basic version up and running for my own testing fairly quickly. edit: Details of my AV8B issues here

There is no concept of early access for steam DLC.

And that's an incredibly good point. Here in standalone world we know we are buy a pre-release 'Beta'. I wonder how that will go down in the Steam world ...

For PG, it actually worked out cheaper to NOT pre-order, buy on release day and use your store credit! But that's completely beside the point. How hard is it to understand that the discount was being offered because of the large delay in getting the Hornet to steam? Now they are being nice and bringing the release forward, therefore no discount. If I were ED, I'd dump steam altogether and go back to standalone only.

In anticipation of the Hornet module release on Wednesday, I threw together this prototype so I could test out the dcsbios logic. Should give me the controls I need for my planned endless case I carrier recovery attempts without having to go head down with the mouse clicking switches. I just need to add (out of place) hook and wing fold switches to complete the setup.

Not sure if anyone has pointed it out, and it is a super nit-pick. But on the Aussie models, the tail number is shown as 'A - 21 - 10' and it should be 'A21-10', i.e. no dash between the A and 21 and less space either side of the dash between 21 and 10. But thanks heaps for including the Aussie skins on release :)

It is used as a backup if the HUD goes U/S. It is possible to designate a target location based on the point on the ground visible behind the cross. It is not an iron sight, it designates a point on the ground that can then be engaged in CCRP (AUTO) bombing mode. It is also not used for JHCMS alignment. This seems to cause a lot of confusion, see here for a definitive answer form Wags: https://forums.eagle.ru/showpost.php?p=3241993&postcount=28

Straight into missions 10 and 11 for me :)