AJ.eightFive

Hi @baltic_dragon I made some notes on M10 a while back but forgot to post them. Not sure how relevant they are not as there have been at least 2 major updates since I played the mission, but I'd thought I'd drop them here just in case: M10 - Not sure if I missed some dialogue, but it wasn't obvious that you're still permitted/expected to drop JDAMS normally (having read the book, I expected to have to drop the JDAMS manually somehow) - Hammers datalink not set up correctly - Sweeps just orbit around the boat - Hammers roll-in right initially before turning back for bombing run which was confusing, not sure if there's a way to tweak the waypoint so they roll straight onto target Thanks for a great campaign! Looking forward to trying Dominant Fury soon!

I'm running DCS at a total resolution of 11904x1800 to accommodate 3x 2560x1440 monitors for the main view, plus 5 other USB displays for exported DDI's, RWR and IFEI. This setup has been stable since January and I have to start by commending ED for building DCS in such a way that this is even possible because it has been awesome flying the Hornet this way. Unfortunately, I've started to have issues with USB stability that I'm having trouble resolving. At seemingly random intervals, all of my USB devices will drop offline for about 10 seconds before reconnecting. This is a big problem when running a multi-monitor setup with USB displays, because it seems like when the game can no longer render to those displays, it falls back to rendering the entire render target to a single monitor. So in my case, 11904x1800 gets squashed onto a single 2560x1440, and there's no way to "maximize" the game after the USB displays reconnect. Here's a snippet from dcs.log when this happens: 2025-08-07 07:33:17.502 INFO APP (Main): Device unplugged: [HID] HID Keyboard Device 2025-08-07 07:33:17.647 WARNING LOG (9680): 1 duplicate message(s) skipped. 2025-08-07 07:33:17.647 INFO APP (Main): Device unplugged: [HID] HID-compliant mouse 2025-08-07 07:33:17.798 WARNING LOG (9680): 1 duplicate message(s) skipped. 2025-08-07 07:33:17.798 INFO APP (Main): Device unplugged: [HID] HID-compliant consumer control device 2025-08-07 07:33:17.864 INFO APP (Main): Device unplugged: [HID] HID-compliant system controller 2025-08-07 07:33:18.011 WARNING LOG (9680): 1 duplicate message(s) skipped. 2025-08-07 07:33:18.011 INFO APP (Main): Device unplugged: [HID] HID-compliant consumer control device 2025-08-07 07:33:18.081 INFO APP (Main): Device unplugged: [HID] HID-compliant vendor-defined device 2025-08-07 07:33:18.211 WARNING WORLD (Main): ModelTimeQuantizer: ANTIFREEZE ENABLED 2025-08-07 07:42:35.428 WARNING WORLD (Main): ModelTimeQuantizer: SAME MODEL TIME 2025-08-07 10:05:40.706 WARNING LOG (9680): 20 duplicate message(s) skipped. 2025-08-07 10:05:40.706 INFO APP (Main): wcTanker::onEvent:5 2025-08-07 10:05:40.706 INFO EDCORE (Main): (wcTanker::Channel)enterToState_:6 2025-08-07 10:05:40.706 INFO EDCORE (Main): (wcTanker)enterToState_:3 2025-08-07 10:34:09.139 WARNING WORLD (Main): ModelTimeQuantizer: SAME MODEL TIME 2025-08-07 14:15:23.819 WARNING LOG (9680): 31 duplicate message(s) skipped. 2025-08-07 14:15:23.819 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [2560, 1440] 2025-08-07 14:15:24.584 INFO APP (Main): Device unplugged: [DISPLAY] @System32\drivers\dxgkrnl.sys,#303;Generic Monitor (%1);(DisplayLink) 2025-08-07 14:15:25.022 WARNING LOG (9680): 2 duplicate message(s) skipped. 2025-08-07 14:15:25.022 INFO APP (Main): Device unplugged: [USB] Racer-Tech USB Display Device 2025-08-07 14:15:25.585 WARNING LOG (9680): 5 duplicate message(s) skipped. 2025-08-07 14:15:25.585 INFO APP (Main): Device unplugged: [HID] HID-compliant touch screen 2025-08-07 14:15:25.695 INFO APP (Main): Device unplugged: [HID] Microsoft Input Configuration Device 2025-08-07 14:15:25.818 INFO APP (Main): Device unplugged: [HID] HID-compliant vendor-defined device 2025-08-07 14:15:26.154 INFO APP (Main): Device unplugged: [HID] HID-compliant mouse 2025-08-07 14:15:26.511 WARNING LOG (9680): 1 duplicate message(s) skipped. 2025-08-07 14:15:26.511 INFO APP (Main): Device unplugged: [USB] USB Composite Device 2025-08-07 14:15:26.618 INFO APP (Main): Device plugged: [USB] USB Composite Device 2025-08-07 14:15:26.761 INFO APP (Main): Device plugged: [USB] USB Serial Device (COM5) 2025-08-07 14:15:27.168 INFO APP (Main): Device unplugged: [USB] USB Serial Device (COM5) 2025-08-07 14:15:27.276 INFO APP (Main): Device unplugged: [USB] USB Composite Device 2025-08-07 14:15:27.383 INFO APP (Main): Device plugged: [USB] Racer-Tech USB Display Device 2025-08-07 14:15:28.154 WARNING LOG (9680): 5 duplicate message(s) skipped. 2025-08-07 14:15:28.154 INFO APP (Main): Device plugged: [DISPLAY] @System32\drivers\dxgkrnl.sys,#303;Generic Monitor (%1);(DisplayLink) 2025-08-07 14:15:28.397 WARNING LOG (9680): 2 duplicate message(s) skipped. 2025-08-07 14:15:28.397 INFO APP (Main): Device plugged: [USB] USB Composite Device 2025-08-07 14:15:28.484 INFO APP (Main): Device plugged: [HID] HID-compliant touch screen 2025-08-07 14:15:28.566 INFO APP (Main): Device plugged: [HID] HID-compliant vendor-defined device 2025-08-07 14:15:28.654 INFO APP (Main): Device plugged: [HID] Microsoft Input Configuration Device 2025-08-07 14:15:28.753 INFO APP (Main): Device plugged: [HID] HID-compliant mouse When DCS detects the disconnected display it resizes the main window: 2025-08-07 14:15:23.819 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [2560, 1440] DCS also detects when the display device reconnects: 2025-08-07 14:15:28.154 INFO APP (Main): Device plugged: [DISPLAY] @System32\drivers\dxgkrnl.sys,#303;Generic Monitor (%1);(DisplayLink) Unfortunately there's no subsequent attempt to resize the main window back to the original resolution when the new display is detected. Obviously I'm going to try and take care of the USB stability issue separately, but I'm wondering if there's a way to make multi-monitor DCS more resilient to display disconnects by making a call to DXGUI_WIN_ADAPTER after a display is connected and attempting to render the main window at the resolution specified in options.lua? Thanks!

I saw it in the changelog. Great work as always, and thanks a lot!

Was this ever confirmed as a bug? I'm still not able to dim the flashlight or change colours in flight.

Hey baltic_dragon. Really enjoying the campaign so far and have had a pretty smooth experience as far as bugs go. M06 is consistently generating a script error after turning onto BRC at WP3 for the Missing Man formation though. The first time, I didn't realize I could continue and closed the game. I also forgot to take a screenshot of the error. I realized I also had all of my squadron's mod's turned on so I disabled those and ran the mission again and got the same error at the same place, right after the dialogue to "bring it right". Took a screenshot and continued the mission this time and had no further issues. Hope that helps. Thanks for the great campaign!

This definitely needs to be an option that can be disabled.

Hopefully 2025 and not Beyond…

To add to C180’s comment, the HeadTracker.dll needs to be replaced after every update as well in my experience. The file is found in the tobiiGameHub Program Files folder if I recall correctly.

Fingers crossed this topic isn't dead. Just picked up a Cubesim display for the RWR and discovered this IC issue while searching the forums for help setting it up. It's working great now with the .lua tweaks, but such a bummer to be locked out of MP because of it.

This is still an issue. As another user pointed out, it helps to set the DDIs to DAY and maximum brightness. For the AMPCD, the flickering still occurs with the brightness all the way up if the moving map is displayed. If the moving map is disabled, the flickering stops.

How are things going jrsteensen? Any sexy new renders you can tease us with?

Looking at picking up some acrylic sheet so I can start experimenting with back-lit panel fabrication. I'd rather just order one big sheet cut down into a more manageable size so I have enough to experiment with and plenty remaining to pack the actual panels when the plans are available. If I recall correctly, you are designing the OpenHornet back-lit panels around the assumption they will be made of stacked layers of 3mm/0.125" acrylic, milled (necessitating cast, not extruded acrylic), painted and engraved, is that correct? I'm thinking to get the sheet cut down into 5.750" wide blanks to minimize material wastage when milling the light plate and panel to their final dimensions while being wide enough to make the backing plate to the mil-spec dimension if I stick with an acrylic back plate instead of aluminum. Are the OpenHornet panels being designed around those same dimensions from the mil-spec or should I look at getting the sheets cut to a different size? Thanks and Happy New Year!

Amazing work as always! Just got my Shapeoko XXL fired up before Christmas and can't wait to start making some OpenHornet related chips and sawdust!

Been a while since I've stopped by. That latest render looks amazing, keep up the good work!

Great update, thank you!