miguelaco

Any word on this? I provided a track and I think there's enough evidence to determine if this is a bug or working as intended. My view is that this is bugged and it makes no sense to change mode to BOL on undesignate while it is possible to select R/BL with no target selected. Any comments?

I noticed it is possible to select R/BL mode with no target selected. This seems to contradict what's stated in the manual and Chuck's Guide. Additionally, if R/BL is selected before having a TGT, when undesignate, the mode is changed back to BOL, but only for the selected station. Even more puzzling if you observe that when R/BL is selected for the first time, the indication INV TGT is displayed, possibly indicating that you need a designation first. However, later on, if you undesignate and select R/BL again, the last TGT seems to be remembered, IN RNG is displayed and the target is displayed in the HSI. If this is a feature and the target is persisted to the missile's memory after undesignate, why changing mode back to BOL? Is this correct behavior? Doesn't seem very consistent as it is right now. agm84d_mode.trk

The obvious workaround is to edit program 6 to your liking. And I somewhat feel the same about these issues. First patch introducing the DTC and it was broken both for radio presets and ALR-67 programs, but at least you could ignore them since everything worked as it did when ignoring DTC. Second iteration and DTC ALR-67 programs are still not fixed and the dispense function is broken in the process. I can't help but think that these problems should have been seen in the most basic tests, they don't look like corner cases at all.

I think there are three issues that might be related: DTC programs are loaded in the wrong/shifted by +1 slots (i.e. DTC program 1 is loaded in ALR-67 program 2 and so on). This is what the OP reported in this thread. Dispense Switch Aft releases the wrong/shifted by +1 program. Dispense Switch Fwd releases program no 6 (it was 5 before this patch). Bear in mind that cycling through all the programs back to the one you want selected seems to reset the counter and then Dispense Switch Aft executes the selected program as it should. This is the workaround I'm using at the moment for issue 2.

I did my own tests with latest patch (2.9.16.10523) and I'll try to showcase the results here as briefly and simple as possible. I focused on testing the AIM-9X boresight mode with no radar, since I think any issues when slaving to L&S target are related to cage/uncage behavior as well. Please, feel free to comment below if I missed something: HUD only (HMD off): Seeker placed over the target: Press and release CAGE/UNCAGE button: a lock cannot be achieved Press and hold CAGE/UNCAGE button: a lock is achieved whenever the button is pressed. As soon as it is released the lock breaks. After a lock is achieved it is no longer possible to achieve a lock again as described in point 2. HUD + HMD: Seeker in HUD placed over the target: Press and release CAGE/UNCAGE button: a lock cannot be achieved Press and hold CAGE/UNCAGE button: a lock is achieved whenever the button is pressed. As soon as it is released the lock breaks. After a lock is achieved it is possible to lock again by holding the button as described in point 2. Seeker in HMD and placed over the target: Press and release CAGE/UNCAGE button: when pressed, a lock is achieved and upon release the lock briefly breaks and locks again as described previously in the thread. Press and hold CAGE/UNCAGE button: a lock is achieved and when released, there are three possible outcomes depending where you're looking when that happens: If released over a target, the first lock is broken and it will lock again on the new (or same) target If released while looking at the HUD (the HMD is masked as a result), the lock breaks and if placed again over the target it will not reacquire again automatically. If released while HMD is not masked, the lock breaks and if placed again over the target it will reacquire the lock automatically Find attached two tracks showing the described behavior. Do not reset view while playing them and feel free to take control and experiment by yourselves. Looking at my findings and assuming I didn't do something wrong, I think the boresight mode is broken and not reliable at all, as pointed out by other users in this thread. aim9x_hud_only.trk aim9x_hud_hmd.trk

Reported here and seems related to this:

What really puzzles me more about this subject is realizing that some people prefer to run the headset at 90Hz,which means it's more likely to have drops below the native rate. Having quite a hefty system myself (i9 14900K + 64Gb + RTX 4090) I find it simply it's not possible to run the sim at 72 fps in all situations. There are instances, for example, while flying low over highly populated areas in some maps, I struggle to reach the required rate for smooth flying. Maybe lowering details or reducing the headset's pixel density would alleviate things a bit, but I'm quite skeptical it's worth it at all. What do you think, is 72Hz the way to go or 90 Hz with less detail is worth it?

I concur with your observations. Anything below headset's native refresh rate seems jittery and definitely not a good experience. I also wonder how people cope with these situations and even say they're happy to have such a "high" refresh rate. I also thought if there is some magic or trick I am not aware of to get good results when fps go down below native's.

I can confirm this issue, all programs are shifted when loaded from the dtc. Moreover, there is also an issue with the selected program for dispense being shifted at mission start, as described here: I'm also attaching my own track in case it helps. fa18c_cmds_dtc_bug.trk

I can confirm this issue and also add that cycling through all the programs back to man 1, makes the dispense switch aft to release program 1 as it should. Dispense switch fwd seems to always release program 6 as @Nazgûl pointed out in the previous post. I made a short track showing the behavior. fa18c_cmds_step_bug.trk

It's not my intent to start a discussion here, but with all due respect, I don’t understand the reasoning behind closing the previous thread. The proposed solution aligns with my findings, and I don’t believe it’s my specific issue. I’ve shared two different sets of logs, which show delays that are inconsistent, ranging from less than a second to 7 seconds. While this isn’t a critical issue, I believe it might be indicative of something else. Furthermore, the last post from the OP in that thread reflects the same findings. Additionally, I don’t find this approach efficient. Opening a new thread closely related to an already closed one and losing all the comment history doesn’t seem ideal. That said, as I mentioned earlier, it’s not a major issue, and I’ll continue investigating. If I uncover anything new, I’ll create a new thread.

For the most part, and I also said I was going to further investigate to determine, if possible, the BIOS setting (even though I'm not convinced it is the cause). Anyway, it's fine by me, but as you can see in my previous post, there's still a noticeable difference in load times.

Looks like the original thread where I was posting was closed. May I ask why? I think the issue is far from solved and it is not clear to me we're even talking about the same problem.

I haven’t been able to pinpoint the exact setting that might have caused this, but I’m not entirely convinced it’s the root cause, it could still be a false positive. In the meantime, I asked my friend @dariocs to run the same test and send me his log file for review. I noticed that his load time was significantly lower than mine, even though we have similar hardware, if anything, mine should have a slight advantage My load times now: 2025-03-25 10:56:59.276 INFO WorldPlugIns (Main): loading "South_Atlantic_Assets": 0.013 2025-03-25 10:56:59.288 INFO WorldPlugIns (Main): loading "AV-8B N/A AI by RAZBAM Sims": 0.011 2025-03-25 10:56:59.299 INFO WorldPlugIns (Main): loading "C-101 Aviojet by AvioDev": 0.011 2025-03-25 10:56:59.325 INFO WorldPlugIns (Main): loading "China Asset Pack by Deka Ironwork Simulations and Eagle Dynamics": 0.025 2025-03-25 10:56:59.338 INFO WorldPlugIns (Main): loading "Christen Eagle II AI by Magnitude 3 LLC": 0.013 2025-03-25 10:56:59.349 INFO WorldPlugIns (Main): loading "F-15E AI by RAZBAM": 0.011 2025-03-25 10:56:59.397 INFO WorldPlugIns (Main): loading "F-4E AI by Heatblur Simulations": 0.047 2025-03-25 10:56:59.405 INFO WorldPlugIns (Main): loading "F-14B AI by Heatblur Simulations": 0.008 2025-03-25 10:56:59.417 INFO WorldPlugIns (Main): loading "M-2000C AI by RAZBAM Sims": 0.011 2025-03-25 10:56:59.429 INFO WorldPlugIns (Main): loading "MiG-21Bis AI by Magnitude 3 LLC": 0.011 2025-03-25 10:56:59.441 INFO WorldPlugIns (Main): loading "Mirage F1 Assets by Aerges": 0.011 2025-03-25 10:56:59.452 INFO WorldPlugIns (Main): loading "OH58D AI by Polychop-Simulations": 0.011 2025-03-25 10:56:59.463 INFO WorldPlugIns (Main): loading "SA342 AI by Polychop-Simulations": 0.011 2025-03-25 10:56:59.477 INFO WorldPlugIns (Main): loading "CaptoGloveSupport": 0.012 2025-03-25 10:56:59.497 INFO WorldPlugIns (Main): loading "LeapMotionSupport": 0.020 2025-03-25 10:56:59.513 INFO WorldPlugIns (Main): loading "SensoryxVRFreeSupport": 0.015 2025-03-25 10:56:59.531 INFO WorldPlugIns (Main): loading "VoiceChat": 0.017 2025-03-25 10:56:59.585 INFO WorldPlugIns (Main): loading "jsAvionics": 0.017 2025-03-25 10:57:01.186 INFO WorldPlugIns (Main): loading "Combined Arms by Eagle Dynamics": 1.600 2025-03-25 10:57:01.737 INFO WorldPlugIns (Main): loading "Supercarrier": 0.551 2025-03-25 10:57:01.741 INFO WorldPlugIns (Main): loading "DCS-SRS": 0.004 2025-03-25 10:57:58.965 INFO WorldPlugIns (Main): loading "F/A-18C": 7.703 @dariocs load times: 2025-03-24 18:58:33.061 INFO WorldPlugIns (Main): loading "South_Atlantic_Assets": 0.017 2025-03-24 18:58:33.076 INFO WorldPlugIns (Main): loading "AV-8B N/A AI by RAZBAM Sims": 0.014 2025-03-24 18:58:33.090 INFO WorldPlugIns (Main): loading "C-101 Aviojet by AvioDev": 0.014 2025-03-24 18:58:33.123 INFO WorldPlugIns (Main): loading "China Asset Pack by Deka Ironwork Simulations and Eagle Dynamics": 0.032 2025-03-24 18:58:33.139 INFO WorldPlugIns (Main): loading "Christen Eagle II AI by Magnitude 3 LLC": 0.016 2025-03-24 18:58:33.154 INFO WorldPlugIns (Main): loading "F-15E AI by RAZBAM": 0.014 2025-03-24 18:58:33.215 INFO WorldPlugIns (Main): loading "F-4E AI by Heatblur Simulations": 0.061 2025-03-24 18:58:33.227 INFO WorldPlugIns (Main): loading "F-14B AI by Heatblur Simulations": 0.011 2025-03-24 18:58:33.241 INFO WorldPlugIns (Main): loading "M-2000C AI by RAZBAM Sims": 0.015 2025-03-24 18:58:33.257 INFO WorldPlugIns (Main): loading "MiG-21Bis AI by Magnitude 3 LLC": 0.015 2025-03-24 18:58:33.272 INFO WorldPlugIns (Main): loading "Mirage F1 Assets by Aerges": 0.015 2025-03-24 18:58:33.287 INFO WorldPlugIns (Main): loading "OH58D AI by Polychop-Simulations": 0.014 2025-03-24 18:58:33.301 INFO WorldPlugIns (Main): loading "SA342 AI by Polychop-Simulations": 0.014 2025-03-24 18:58:33.318 INFO WorldPlugIns (Main): loading "CaptoGloveSupport": 0.016 2025-03-24 18:58:33.347 INFO WorldPlugIns (Main): loading "LeapMotionSupport": 0.029 2025-03-24 18:58:33.367 INFO WorldPlugIns (Main): loading "SensoryxVRFreeSupport": 0.020 2025-03-24 18:58:33.389 INFO WorldPlugIns (Main): loading "VoiceChat": 0.021 2025-03-24 18:58:33.469 INFO WorldPlugIns (Main): loading "jsAvionics": 0.021 2025-03-24 18:58:34.477 INFO WorldPlugIns (Main): loading "Supercarrier": 1.008 2025-03-24 18:58:35.038 INFO WorldPlugIns (Main): loading "NS430": 0.561 2025-03-24 18:58:35.046 INFO WorldPlugIns (Main): loading "DCS-SRS": 0.008 2025-03-24 19:01:08.237 INFO WorldPlugIns (Main): loading "F/A-18C": 0.995 As you can see, the times are quite similar, except for the player's aircraft module (F/A-18C), where I'm getting more than 7 seconds compared to less than a second. I’ll continue my tests when I have more time to see if I can replicate those minute-long times by reverting to the previous BIOS settings, just to confirm whether they are indeed the cause. dcs-dariocs.log dcs.miguelaco.log

I managed to solve it somehow. I remebered I made some changes to the BIOS settings a few weeks ago, rolled them back and now I'm getting less than 20 seconds in the first mission load. I'll try to narrow down the exact setting when I have some time to test since I changed more than one.