Nealius

Can this be applied selectively, e.g. to certain modules only, by selecting specific folders in the popup, or can it only be run on the entire DCS root folder?

Replays using external scripts used to work fine up until the August update(s).

Still happening quite a lot with both SP and MP tracks. Others seem to be having the same issue. On occasion after a few days (PC reboots maybe?) they sometimes sort themselves out for others, but I haven't experienced that yet. Here's a whacky log from one today: That converts to 16,384 pebibytes. I didn't even know anything above a terabyte existed until today.

Hoping the Japanese liveries for the Hook are the correct color. The ones they made for the Apache are totally wrong.

CBU-99 (or -100?) was commonly seen on Tomcats during Southern Watch, the Hornet module has had them since day one, and a carrier-based aircraft missing the thermally protected Mk20 equivalent (while having access to the Mk20) seems a bit odd, but it appears we still don't have the CBU-99. Was it never planned for HB Tomcat? Double yellow stripes indicates thermal protection on the casing, therefore CBU-99 or -100. FMU-140 (perhaps?) also visible; which is not available on the Mk20 (at least in DCS).

Even with medium textures the Phantom makes online flying a pain when players aren't even flying the Phantom. With one F-4 holding short, the texture pop-in as I'm coming in for landing chokes my system so hard right where I need the most finesse for flaring, and I plow into the runway thanks to the Phantom-induced freezing. With textures medium. On a 4070Ti Super.

Bonus strafing episode:

"Without having to use" does not mean "will replace." This is basic English.

I don't think mine goes above 70, but next time I fly I plan on using MSI Afterburner to run my fans at 100% during the session to see if that makes a difference.

Definitive SUU-23/A pics I can find only show the right side for some reason. The one shot I found of the left side shows a link ejection port, but I can't find any pics of the bottom. Do closed systems typically eject links? I always thought they kept both the casings and links.

Rather famous footage of a SUU-23 affixed to a Phantom that's cut into nearly every aviation-related Vietnam documentary I've seen. Casings are clearly seen being expelled from slightly left of center.

With the lack of aileron trim in the Anton, you will always have some stick/rudder pressure to keep ball centered and wings level.

Bumping this, mainly for the SUU-25 pod. It appears to have been a standard load in Afghanistan, but the model and textures for ours is Windows 95 level of pixelation.

Would be nice to have these vital details in the manual. Or even a detailed guide pinned in the forums. There's zero documentation on MC-LOAD errors, the matching fuze requirement, or the JPF page. And yet the customer is somehow expected to understand all these changes.

Ah looks like I did have two different fuses. Is it not possible for the system to work with mixed fuzes for all bombs, or is this only a thing for the BLU-109? It would be useful to be able to carry mixed DSU-33 and plugged GBU-38s, for example. Manual does not mention MC-LOAD fault at all. Lost me here. When boxing the weapon the fuse settings normally appear on the left. With the BLU-109 weapons, is it moved to this JPF entry you're talking about? The manual makes no mention of JPF at all, and I've never needed to use the JDAM DSPLY page for TOO drops of BLU-109s in the past (box weapon, select TOO, set EFUZ, TDC depress on target, drop).

For the GBU-31(v)4B, how do you access the fuse settings in the Hornet's stores page? Yesterday I tried them in MP via the rearm window, set the FMU-152 to 60ms as per chart, but when I selected the weapon in the Hornet's stores page there was no MFUZ or EFUZ submenu at all. The bombs dropped, however they were X-ed out and were consequently duds.

This is where the Phantom is an outlier, and outliers make people question things. Having put significant hours on the F-5, F-86, F-14, A-10, AV-8B, F-15E, MiG-19, MiG-21, P-51, P-47, Mosquito (all analog modules that require constant trimming), the Phantom is the only one where you cannot trim to zero pressure for at least long enough to do admin work. Your statement is so far from the reality in DCS I question if you've actually flown all the other analog modules at all. Are you simply not being contrarian? Because you lack any supporting evidence at all. At least the devs are teaching us about the bellows and bobweights that make this such an unusual system. Taking the Tomcat for example, I can trim for hands-off CASE I marshal stack orbits. One click NU trim results in one click NU trim. One click ND trim results in one click ND trim. It's predictable and consistent because one click of trim = one click of trim. In the Phantom, one click NU trim does nothing. One click ND trim results in effectively 5 clicks ND trim. Then the next time I use trim, one click NU trim results in effectively 3 clicks NU trim, and one click ND trim results in effectively 2 clicks ND trim. This is what I mean by unpredictable and inconsistent. One click of trim could be anything from 0 to god-knows-what.

It would be. I have a hard time understanding how the Blue Angels ever flew this thing with any precision at all. I understand they have a history of making modifications, but with the description of how the trim/bellows/wizardry works, it sounds like any modifications would be rather limited.

Coming from primarily US aircraft where compasses are always magnetic by default and there's no need to faff with magnetic declination, I'm still confused. 1. KURSKORR to magnetic declination sets all compasses in the aircraft to true? 2. KURSKORR to 0 sets all compasses in the aircraft to magnetic? 3. KURSKORR to 0 does not cause a nav error as it used to in previous updates?

No, the size in the log is wrong. Both track files are essentially the same 30-40 minute flight with very few units. Actual size of the broken .trk file is 23,583kb. Size of the working track file is 30,154kb.

Since the latest update I've had a couple issues with replay tracks (single-player missions, but with client slots) failing to load, getting hung up on "Terrain Init: 1, vti." I've had it happen on Syria with the Hornet, and Kola with the Phantom. The missions work fine, it only freezes when loading a replay track. I've tried removing mods and updating graphics drivers, no change. Spotted this interesting line in the log: What doesn't make sense is that I can fly the mission one day, save the track, the track works fine. Then the next day fly the same mission, do the same task, save the replay track, and that one is broken. I'm attaching two tracks. "F4-Vidsel" is the one that hangs, "M82-Vidsel" is the one that doesn't. The only difference between the two is the addition of an AI MiG-19. M82-Vidsel F4-Vidsel

In VR I usually get frames varying between 60s and 72 (locked refresh rate) in other modules. Same settings, same mission, same location in the Phantom and I'm at 36 (half refresh rate).

Since release I've had this weird, random issue where the gear lever will move but the gear itself will fail to actuate, all below 250kts indicated on the dial. It's been really hard to capture because it's so random; sometimes on takeoff, sometimes in the pattern, sometimes on the third circuit of touch-and-go's, etc. But I finally captured it on takeoff and saved the short ~10min track file. Unfortunately on Kola map. Immediately once airborne I press the gear up/down command (G) mapped to my throttle base. Gear lever comes up, but does not illuminate, and the gear doesn't move. After confirming the status of the gear I press the gear up/down command again. The gear lever does NOT move, but illuminates, and the gear actuates as normal. After exiting this mission I flew two more and had no problem, so it was a 1 in 5 failure this time around. Note: I was in selfie mode to get vids/screenshots, but this issue crops up regardless of using selfie mode or not, so it shouldn't be a factor. I suspect the sim might be receiving the input twice even though I only pressed it once, as I often have a similar issue with right mouse click throwing switches twice when I click it only once. gear-fail.trk

The Phantom may be an exception here, but constant trimming in formation/tanking is standard practice IRL. The difference with other aircraft is that the trim input results in a consistent and predictable output. In the Phantom it's inconsistent and unpredictable.