FoxTwo

I had no issues binding the default master caution reset to a push button, and the hook bypass toggle to one position of a two position switch.

Anything defined in \Mods\aircraft\FA-18C\Cockpit\Scripts\clickabledata.lua can be bound. Not everything has a binding in the input default.lua, but anything that you can click with a mouse can be bound. Axes are a bit trickier than switches. To create a hook bypass binding for off and on, you'd need to edit \Mods\aircraft\FA-18C\Input\FA-18C\joystick\default.lua and add these lines, preferably around line 463 { down = cptlights_commands.HookBypass, cockpit_device_id = devices.CPT_LIGHTS, value_down = 1.0, name = _('HOOK BYPASS Switch - FIELD'), category = {_('Left Vertical Panel')}}, { down = cptlights_commands.HookBypass, cockpit_device_id = devices.CPT_LIGHTS, value_down = -1.0, name = _('HOOK BYPASS Switch - CARRIER'), category = {_('Left Vertical Panel')}},

How about this, I cannot say definitively about YOUR version of 2.7, but for my 2.7 version of DCS that I just ran a repair on to restore the default.lua for the F-18 joystick profile, hook bypass only has an on/off toggle, not specific on and off bindings. Again, COCKPIT_LIGTHS has become COCKPIT_LIGHTS so if you want to fix it, you have all the information you need.

Trust me, you're using the old default.lua. Run a repair to get the 2.7 version. All of these device IDs are part of COCKPIT_LIGHTS, which used to be COCKPIT_LIGTHS. This is what is causing your issue.

Those aren't in the game by default. Are you using a modded joystick default.lua? They fixed a typo in the F/A-18C bindings in 2.7, previously the device was attached to device id devices.COCKPIT_LIGTHS and it's now devices.COCKPIT_LIGHTS. This effectively breaks your edited default.lua file as those devices no longer have valid references. You'll have to edit your default.lua and search and replace "COCKPIT_LIGTHS" with "COCKPIT_LIGHTS". Easily done with Notepad++ or a lua editor of your choice.

I don't have a problem with them but I run a gamma of 2.0 on my reverb, which is slightly darker than 1.6 is on my flat panel.

The ECM edits? Yeah.

Yes hook bypass and launch bar are not in properly. Neither is the fuel dump (on/off) I think. Here's my current default.lua for \Mods\aircraft\FA-18C\Input\FA-18C\joystick\ it should get you what you're looking for. default.lua

Fogging/icing effects wouldn't be awful either. Give me a reason to use the defroster that I can turn on but has no effect.

After a full reload of the game, I want to say it's better but it's still not what I'd call fast to either start up and get into the game or quit out. Did DCS always make a lock file in the savegame folder?

Yeah DCS can't run as admin on my PC I call it through a powershell script. I did verify it anyway. I'm trying a completely fresh install with a new savegame folder to see if that fixes it. Just to reiterate, this is new with 2.7 on my system. Did not happen prior to the update.

No improvement. This only happens if I quit the game from inside a mission. If I quit from the main menu screen, I get to the desktop almost instantly.

Every time I exit DCS it seems to take its sweet time to close the process and give me my desktop back. It wasn't doing this prior to 2.7. I'm not sure what it's doing but it's kind of annoying. You can see it in the log here, at 20:10:08 GMT I bring up the escape menu and click exit game in a mission and at 20:11:23 (over a minute and fifteen seconds) it finally quits. 2021-04-18 20:10:08.331 INFO Lua: Lua CPU usage: metric: average mission execution: 3.0672 % 2021-04-18 20:10:10.484 INFO Dispatcher: Stop 2021-04-18 20:10:12.328 INFO Config: netview stopped 2021-04-18 20:10:12.519 INFO DCS: wcTanker::onEvent:5 2021-04-18 20:10:12.519 INFO EDCORE: (wcTanker::Channel)enterToState_:6 2021-04-18 20:10:12.519 WARNING LOG: 1 duplicate message(s) skipped. 2021-04-18 20:10:12.519 INFO EDCORE: (wcTanker)enterToState_:3 2021-04-18 20:10:12.519 INFO DCS: wcTanker::onEvent:5 2021-04-18 20:10:12.519 INFO EDCORE: (wcTanker::Channel)enterToState_:6 2021-04-18 20:10:12.519 INFO EDCORE: (wcTanker)enterToState_:3 2021-04-18 20:10:12.841 INFO TERRAIN: lSystem::CleanScenes() 2021-04-18 20:10:12.927 INFO VISUALIZER: StopSimulation 2021-04-18 20:10:12.937 INFO VISUALIZER: Stopped collection of statistic. 2021-04-18 20:10:12.960 INFO EDCORE: (dDispatcher)enterToState_:3 2021-04-18 20:10:13.033 INFO EDCORE: (dDispatcher)enterToState_:5 2021-04-18 20:10:13.686 INFO DCS: application shutdown 2021-04-18 20:10:14.839 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 0 2021-04-18 20:10:14.843 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 1 2021-04-18 20:10:14.844 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 2 2021-04-18 20:10:15.011 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 3 2021-04-18 20:10:15.158 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 4 2021-04-18 20:10:15.167 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 5 2021-04-18 20:10:15.171 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 6 2021-04-18 20:10:15.176 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 7 2021-04-18 20:10:15.177 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 8 2021-04-18 20:10:15.181 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 9 2021-04-18 20:10:15.181 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 10 2021-04-18 20:10:15.182 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 11 2021-04-18 20:10:15.183 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 12 2021-04-18 20:10:15.183 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 13 2021-04-18 20:10:15.791 INFO TERRAIN: lSystem::exit() 2021-04-18 20:10:15.791 INFO VISUALIZER: TerrainRenderer::release 2021-04-18 20:10:15.791 INFO TERRAIN: lSystem::CleanScenes() 2021-04-18 20:11:12.556 INFO VISUALIZER: SceneManager_Implement::~SceneManager_Implement() 2021-04-18 20:11:12.560 INFO VISUALIZER: TerrainRenderer::release 2021-04-18 20:11:13.706 WARNING LOG: 1 duplicate message(s) skipped. 2021-04-18 20:11:13.706 INFO TERRAIN: lSystem::exit() 2021-04-18 20:11:13.706 INFO TERRAIN: lSystem::CleanScenes() 2021-04-18 20:11:15.154 INFO DX11BACKEND: DX11Renderer::shutdown() 2021-04-18 20:11:23.148 INFO DX11BACKEND: NVIDIA API exit OK 2021-04-18 20:11:23.148 INFO DX11BACKEND: textures_count: 0 2021-04-18 20:11:23.148 INFO DX11BACKEND: textures_size: 0 2021-04-18 20:11:23.148 INFO DX11BACKEND: buffers_count: 0 2021-04-18 20:11:23.148 INFO DX11BACKEND: buffers_size: 0 2021-04-18 20:11:23.148 INFO DX11BACKEND: CB_count: 0 2021-04-18 20:11:23.148 INFO DX11BACKEND: CB_size: 0 2021-04-18 20:11:23.148 INFO DX11BACKEND: SB_count: 0 2021-04-18 20:11:23.148 INFO DX11BACKEND: SB_size: 0 2021-04-18 20:11:23.148 INFO DX11BACKEND: IB_count: 0 2021-04-18 20:11:23.148 INFO DX11BACKEND: IB_size: 0 2021-04-18 20:11:23.148 INFO DX11BACKEND: VB_count: 0 2021-04-18 20:11:23.148 INFO DX11BACKEND: VB_size: 0 2021-04-18 20:11:23.148 INFO DX11BACKEND: total_buffers_size: 0 2021-04-18 20:11:23.148 INFO DX11BACKEND: total_size: 0

You don't need to do this anymore since they enabled the ECM in the F-18. Run a repair on your DCS install and try the default bindings. They fixed a typo in the F-18 bindings lua code (COCKPIT_LIGTHS is now COCKPIT_LIGHTS) and that's probably why it's broken but it's completely unnecessary at this point.

How about we finish the hornet we have before we start talking about variants from other countries that may or may not have adequate documentation to replicate accurately. Why is this even a big deal?

Well a firmware that old may not be compatible with the latest version of the software. So either downgrade or load the new firmware.

I'm not sure what firmware you're on but there's a version that only shows up as one device in windows. That said, even before I loaded this firmware mine never showed up as more than two devices.

https://www.f-16.net/forum/viewtopic.php?f=36&t=53335 The swiss never had a need to run the F/A-18C as a multi-role aircraft, and would never need to mount bombs on that station, hence the custom A2A missile only pylon. Again, it makes sense based on all available information. If you want to run a single missile on that station, run some AIM-7Ms, the LAU-115 can mount them directly. It's not really a big deal.

Well like it or not, it's the developer's prerogative to target simulating a specific block and model aircraft that has certain features and avionics, not some fictional frankenplane that couldn't have possibly existed.

We fly US Navy F/A-18s, not swiss. We don't have those mounts as we don't fly that plane. US F-18s could only mount the AIM-7 on a single pylon.

They know. This is the first iteration. They will improve in time as the weather system is updated.

Based on the effect in VR. It seems to look fine in 2d/flat panel.

I'm fine with anything that pushes more frames and doesn't impact the view through the headset. If streamers want an option to disable it, they should have it but don't throw the baby out with the bathwater please.

The day/night, cont, gain and sym bindings are still wrong. For the second time, I don't know why you're using the icommand script bindings when you can call the direct button bindings (which work just fine, and better) but whatever. Either way, up works fine, down doesn't work at all (for gain, sym, cont, and day/night). In the meantime I'll go back to using my own binding lua code for these buttons. {down = mpcd_r_commands.Switch_DAY_MODE, up = mpcd_r_commands.Switch_DAY_MODE, cockpit_device_id = devices.MPCD_RIGHT, value_down = -1.0, value_up = 0.0, name = _('Right MPCD DAY/NIGHT Switch - DAY'), category = _('Right MPCD')}, {down = mpcd_r_commands.Switch_NGT_MODE, up = mpcd_r_commands.Switch_NGT_MODE, cockpit_device_id = devices.MPCD_RIGHT, value_down = 1.0, value_up = 0.0, name = _('Right MPCD DAY/NIGHT Switch - NIGHT'), category = _('Right MPCD')}, {down = mpcd_r_commands.Switch_GAIN_UP, up = mpcd_r_commands.Switch_GAIN_UP, cockpit_device_id = devices.MPCD_RIGHT, value_down = 1.0, value_up = 0.0, name = _('Right MPCD GAIN Switch - UP'), category = _('Right MPCD')}, {down = mpcd_r_commands.Switch_GAIN_DN, up = mpcd_r_commands.Switch_GAIN_DN, cockpit_device_id = devices.MPCD_RIGHT, value_down = -1.0, value_up = 0.0, name = _('Right MPCD GAIN Switch - DOWN'), category = _('Right MPCD')}, {down = mpcd_r_commands.Switch_CONT_UP, up = mpcd_r_commands.Switch_CONT_UP, cockpit_device_id = devices.MPCD_RIGHT, value_down = 1.0, value_up = 0.0, name = _('Right MPCD CONT Switch - UP'), category = _('Right MPCD')}, {down = mpcd_r_commands.Switch_CONT_DN, up = mpcd_r_commands.Switch_CONT_DN, cockpit_device_id = devices.MPCD_RIGHT, value_down = -1.0, value_up = 0.0, name = _('Right MPCD CONT Switch - DOWN'), category = _('Right MPCD')}, {down = mpcd_r_commands.Switch_SYM_UP, up = mpcd_r_commands.Switch_SYM_UP, cockpit_device_id = devices.MPCD_RIGHT, value_down = 1.0, value_up = 0.0, name = _('Right MPCD SYM Switch - UP'), category = _('Right MPCD')}, {down = mpcd_r_commands.Switch_SYM_DN, up = mpcd_r_commands.Switch_SYM_DN, cockpit_device_id = devices.MPCD_RIGHT, value_down = -1.0, value_up = 0.0, name = _('Right MPCD SYM Switch - DOWN'), category = _('Right MPCD')},

The gloss/reflective index of the inside of the canopy seems way way too high.