Arch-vile

I posted a video. I don't know how to be more transparent than that. I'd challenge anyone who thinks there are no problems to post a video showing them cruising in level flight at the manual's stated speeds and configurations and sustaining that for 5-10 minutes. Or show WEP being engaged and disengaged successfully with the listed MAP or airspeed changes. I'd love to see that so I know it's an issue that's not affecting everyone. That helps add valuable data to the bug report.

Here's a video I recorded trying to put it through its paces. You can see the inability to accelerate in level flight. I cycled cooling doors to verify. Also tried different super charger settings. I can get it up to higher speeds by diving but once level, or after bleeding speed by maneuvering it doesn't recover well. And WEP seems to have 0 effect. Light eventually comes on but I never notice any increase or decrease in power. I didn't use it at all in this video. I can't say for sure there's something wrong, but the airplane feels really anemic at mill power and the figures in the early-access manual included with the module implies much higher speeds (I understand CAS vs IAS as well, it doesn't account for the difference). /shrug I'm giving up troubleshooting it and will fly around it, but definitely feels underpowered at mil power and WEP seems ineffictive.

We have a growing number of people that are reporting this problem. I can upload screenshots later but mil-power and even WEP configuration does not appear to be generating speeds above 250-270kts in any configuration. Clean, cowl-flaps closed, etc. WEP also doesn't appear to have any impact when the water runs out so i'm not convinced that's working at all. Using the mouse to jam the prop governor past the stop (looks like a bug to me) shouldn't be required to get the posted performance figures. Sounds like some people are fine though? So we're really struggling to figure out why the performance is so bad, especially down low. FWIW at partial power it lines up with the charts pretty well. But Mil-power and WEP are falling far short for many of us.

Dropping back to single-threaded seems to cure it but performance is so bad it's hardly a workaround. This is what it looks like for me. Not sure if it's what others are seeing. https://www.youtube.com/watch?v=-PdPVt3BvxA Sorry the video is so bad. It's hard to record through an eyeport with a phone and get eye-tracking to engage. But you can see it's stable until eye tracking activates and then it freaks out. No other configuration changes.

It appears this update has also broken the existing Scenery Kill events. I relied on these in a dynamic campaign script I maintain. It's event 28 and here's some of the code I used to inspect these events normally. env.info("Kill Event Handled. Type: " .. Object.getCategory(event.target)) if (Object.getCategory(event.target) == Object.Category.SCENERY or Object.getCategory(event.target) == Object.Category.STATIC) then local scenery = event.target local sceneryTypeName = scenery:getTypeName() local sceneryName = scenery:getName() if (sceneryName == nil) then sceneryName = "" end if (sceneryTypeName == nil) then sceneryTypeName = "" env.info("Received a scenery kill event with no type at mission time: " .. timer.getTime()) return end env.info("Scenery Kill Event Handled: " .. sceneryTypeName .. " : " .. sceneryName) These have worked for a long time and as of the latest update no longer fire. I am now getting Lost events (30 in the enum) but with no scenery type information so I can't do much to determine what type of thing was hit. FWIW I believe I do rely on the splash-damage hit-scan code to cause these events to fire, but they did work previously. And I do still get events, they just changed from Kill to Lost and now don't carry a type. TL;DR it definitely seems like something changed.

Happens pretty frequently for me with this module. I'm going to try removing some mods but so far it's been very reproducible. dcs.20240602-135635.log 2024-06-02 13:56:35.486 INFO EDCORE (Main): try to write dump information 2024-06-02 13:56:35.489 INFO EDCORE (Main): # -------------- 20240602-135635 -------------- 2024-06-02 13:56:35.489 INFO EDCORE (Main): DCS/2.9.5.55300 (x86_64; MT; Windows NT 10.0.22621) 2024-06-02 13:56:35.489 INFO EDCORE (Main): C:\Program Files (x86)\Steam\steamapps\common\DCSWorld\Mods\aircraft\F-4E\bin\F-4E-Avionics.dll 2024-06-02 13:56:35.490 INFO EDCORE (Main): # C0000005 ACCESS_VIOLATION at 00007fff82068369 00:00000000 2024-06-02 13:56:35.490 INFO EDCORE (Main): SymInit: Symbol-SearchPath: 'C:\Program Files (x86)\Steam\steamapps\common\DCSWorld\bin-mt;', symOptions: 532, UserName: 'robg' 2024-06-02 13:56:35.490 INFO EDCORE (Main): OS-Version: 10.0.22621 () 0x100-0x1 2024-06-02 13:56:35.490 INFO EDCORE (Main): 0x0000000000188369 (F-4E-Avionics): hb::Dispensers::SetRHPower + 0x50E99 2024-06-02 13:56:35.491 INFO EDCORE (Main): 0x0000000000191ac5 (F-4E-Avionics): hb::Dispensers::SetRHPower + 0x5A5F5 2024-06-02 13:56:35.491 INFO EDCORE (Main): 0x0000000000181752 (F-4E-Avionics): hb::Dispensers::SetRHPower + 0x4A282 2024-06-02 13:56:35.491 INFO EDCORE (Main): 0x0000000000218ede (CockpitBase): cockpit::avDevice_BasicTimer::NextEvent + 0x1E 2024-06-02 13:56:35.491 INFO EDCORE (Main): 0x00000000000045ab (World): wSimTrace::CommandsTraceDiscreteIsOn + 0x3EB 2024-06-02 13:56:35.491 INFO EDCORE (Main): 0x0000000000004bc2 (World): wSimCalendar::DoActionsUntil + 0x262 2024-06-02 13:56:35.491 INFO EDCORE (Main): 0x00000000008c8de9 (DCS): SW + 0x407D49 2024-06-02 13:56:35.491 INFO EDCORE (Main): 0x00000000008c8ac1 (DCS): SW + 0x407A21 2024-06-02 13:56:35.491 INFO EDCORE (Main): 0x00000000008eb962 (DCS): SW + 0x42A8C2 2024-06-02 13:56:35.491 INFO EDCORE (Main): 0x00000000008a8714 (DCS): SW + 0x3E7674 2024-06-02 13:56:35.491 INFO EDCORE (Main): 0x00000000008a9e43 (DCS): SW + 0x3E8DA3 2024-06-02 13:56:35.492 INFO EDCORE (Main): 0x00000000004a1c10 (DCS): (function-name not available) + 0x0 2024-06-02 13:56:35.492 INFO EDCORE (Main): 0x00000000028077ce (DCS): AmdPowerXpressRequestHighPerformance + 0x139D7CA 2024-06-02 13:56:35.492 INFO EDCORE (Main): 0x0000000000cf632e (DCS): SW + 0x83528E 2024-06-02 13:56:35.492 INFO EDCORE (Main): 0x000000000001257d (KERNEL32): BaseThreadInitThunk + 0x1D

Still having the issue described in this thread. Checked easy-comms are off. Using radio-specific comm menu commands. I turn the battery on and the F-10 menu option is not available. The options go through F8. I've tried turning on the backup uhf radio and tuning it manually as well but the frequencies listed in the SPINS don't seem useable for requesting engine startup. <EDITED> Found this thread: which explains the issue. You can't make the radio call on battery power, you have to flip the aircraft's main power to "on" but not start the engine. Looks like this is labeled "not a bug" but it's at least confusing since the instructions specifically reference turning on the battery only. Also, i was able to get this radio call to work using "intercom" and the steps don't involve actually powering on or tuning the backup UHF radio. But at least I can continue.