Nobody Special

This appears to be fixed in 2.8.1.34437. I've played the mission twice with no issue.

Issue is present in 2.8.33006.

Two things I've noticed so far -- haven't tried with today's update yet: Uncommanded rolls upon engaging ground track heading hold autopilot at higher altitudes (~30k feet) in otherwise level flight. Works fine at lower altitudes. Altitude hold seems to work fine. Very large pixellation of something where the canopy joins the fuselage. Look to the side from inside the cockpit at night with the flashlight. Minor / cosmetic issue that I just noticed, probably not new. Freeze issue remains.

Changing the page file to 32000 fixed-size does not solve the problem.

Didn't see the reply until now -- I've attached the mission, it's nothing special. This issue still occurs with 2.8.0.32066. AAR practice.miz I see this behavior in other missions as well.

AMD Ryzen 7 2700X on a Gigabyte X270 AORUS ultra gaming motherboard, Radeon RX5700 XT, 32 GB RAM. System runs stably. OS is Windows 10 (home) 21H1, build 19043.2130. Graphics driver version is 22.5.1. DCS options file is attached. These reflect that I run with Tacview, SRS and the A4 installed, but I found this issue reproducible with a renamed "Saved Games"/DCS.openbeta to run cleanly. I have not found any change to the graphics options that helps. Page file info: I'd be happy to provide additional information, let me know if you need anything more. options.lua Also -- originally I thought this might be related to changing views or head-tracking, but I no longer think so. The freeze happens even if I'm doing nothing in my cockpit.

@IronMike - I'm not sure if this is the same issue or not, but for me this is not fixed in 2.8.0.32066. The game still hangs when approaching WP1 in the mission from my post below.

Issue is still present in 2.8.0.32066, 100% repeatable.

This issue is not fixed in 2.7.17.29493.

Issue remains in 2.7.16.27869.

Here I am running with no mods installed. Note the skill level of the tanker on the right does not match the skill in the table at the bottom. null

There are penguins at these locations: S 52d 25m 40s W 59s 03m 05s (Island south of East Falkland, small group) S 51d 25m 33s W 59d 00m 54s (North of San Carlos FOB, larger group) S 51d 20m 04s W 58d 40m 07s (North-East of San Carlos FOB, several groups) S 51d 40m 31s W 57d 46m 55s (Port Stanley, small group) There was a beach with penguins and orcas offshore, within a short helicopter flight from San Carlos FOB. Either it has changed, I can't find it, or it was the one north of San Carlos and the orcas aren't there now. Edit - location is north of San Carlos FOB (Middle Bay / Paloma Sand Beach on Google Maps), the orcas are still there in the early mission I created (windy weather, 9 June 1988), but I don't see them in a newer mission with calm weather set on 9 June 2022.

Open any mission, add several units. Then open the "unit list," cycle through the units and change their skill setting. The skill shown in the unit list does not update.

Disabling mirrors does not solve the issue for me.

Issue remains in open beta 2.7.15.25026

Issue still remains in open beta 2.7.15.25026. This is my favorite mission.

Disabling the RTB trigger does not solve the problem.

Log file attached - not the same run as the video, but the same mission and slot. dcs.log

I just replaced the player flight with F-18s and tried it, game is again hung at 23 miles from WP1. This is not specific to the F-14.

I see this flickering when certain lights are in the visual field, running current open beta. This issue is not new. I have seen it: At start of the attached mission, in the AH-64 slot In the same mission, due to sunrise a short time after the start while flying the F-14 at night approaching Batumi (so bad I had to exit the game as I could not see where I was going) with lights on the island of carriers I have played with various graphics settings in both DCS and the driver software but I have not found a setting that solves this. Graphics card is a Radeon RX 5700 XT, driver version 22.5.1, performance tuning settings are at default. null Guam target practice no mods.miz

Sorry -- I removed the 2 airliners that I had added for traffic when I saved it to "test.miz" before posting, but I missed a fuel truck. Here is the same mission, with that truck removed. I tested this one and also got the hang. Possibly relevant, there is a trigger when you get to within ~ 20 miles of WP1, that tells the CAP there to RTB. test.miz

Ever since the April patch I have been unable to play this mission without the game hanging and having to be forcibly terminated. Take off from the carrier, heading toward WP1. Climb on mil power at 15 degrees to 36,000 ft., then reduce throttle and cruise at approximately 220-240 kts. At approximately 20 miles from WP 1, the game will hang. The issue seems to occur when changing external views, or moving my head rapidly (using opentrack). This is 100% repeatable on my computer. Logs and mission file are attached; I cannot obtain a track. dcs.log test.miz

It's not a LoS issue. I replayed the track to check - once the artillery barrage starts and I'm getting too close to the column, I do a right turn to re-position back toward the river. At that point I re-engage, with very clear LoS visible in TADS, and hellfires are properly set to LOBL direct. There is still no constraints box, and George will not fire. Here is a screenshot: I've played this mission once or twice on most nights for the past 3+ weeks. I'm very familiar with the LOS difficulties from trees and buildings, and where I can and cannot get LoS and attack. The second pass (after I turn around and re-commit) should be good from an altitude, position and LoS perspective -- the location just beyond WP2 is exactly where I usually position myself for a successful attack. There is a "window" through the trees and along the road there, and you can engage from even lower altitude. I just tried taking control from this point. The hellfire constraints box does appear after I WAS hellfires myself, and I can fire. But I still can not get George to engage, even here; the constraints box never appears, and "MSL NOT READY" never goes away. There is "MSL TYPE?" showing in the bottom-right of the TADS display, I guess there is something wrong with the missile setup, but I can't find a way to fix it.

Happened to me just now, seems to occur when I (unintentionally) tell George to set LOAL. With many attempts I could not get George to fire either hellfires or guns. The squares (dashed or solid, small or large) that I normally see in the HMD with Hellfire selected were not present. dcs.log George not engaging.trk

For comparison, I ran the same test with the F-18, getting as close as I could to 100% RPM without afterburner. The result is similar overall but a bit less in magnitude: At 0C, 25000' maximum HUD indicated speed 580 At 35C, 25000' maximum HUD indicated speed 418 That's essentially the same loss of speed that I see with the F-14B, to within my ability to measure: the ratio (speed at 0C) / (speed at 35C) is 0.72; for the F-14 that ratio is about 0.69. So my tactic of out-running the enemy ought to be okay so long as they obey the same laws of physics that I do. I had no idea that the effect of temperature on turbine performance is so large. Good to know!