Nealius

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.

What about the method that ED implemented on the Viper and Hornet, where the pilot body head pops into existence when the camera is moved sufficiently far away from it, with player head movements preserved? It works well in those modules while staying inside F1 view.

No plans to make it functioning in replay tracks?

What conditions trigger that bug? I can't say that I've ever come across it in hundreds of plugs. At any rate, any way to turn it off? The checkbox in special settings for it is now gone.

Now that the auto-pre-contact is working, it seems to be trigger happy. After hailing the tanker from observation positon, auto-pre-contact fires. When sliding into actual pre-contact position, it does not fire since it already fired while in observation. When falling off the boom and setting up for another plug, it fires again when it's not needed.

Same. It's impossible to use trim while tanking. 3-4 taps of trim and the nose refuses to move. 1 tap of trim the opposite direction and it's like those 3-4 taps are immediately applied opposite the direction they were supposed to go.

CAS/JTAC. What targets to prioritize? Do you need to hit multiple in one pass, or just one? Do you need to do a show of force first? Is the fight so close you have to skip the JDAMs and strafe the treeline? What's your attack heading so a short/long bomb doesn't hit friendlies? Employing smart munitions is more than simply handing off coords and mashing the pickle button. There's an entire tactical decision-making process that occurs before releasing the weapon.

Ah yeah, that and "game mode" are both off. The only two bits of clues I've been able to find so far are: 1. At some point, all 6 of my cores go to 100% (but haven't matched the timing to see if it's related to the stutter) 2. When there's a stutter my GPU dedicated memory dips slightly and "Copy" increases

What are hags?

Power management to max performance disables core parking. However, I have DCS set to not use cores 0 and 1 because Oculus seems to like using those, and DCS gets absolutely horrid framerates if I don't set affinity to cores 2~6.

Using MT, not using OTT.

Power management is all set to max performance, All USB ports as well.

Slow repair hasn't fixed it. There's a spot a few hundred feet back where the big change/stutter happens, then there's another small change/stutter around 100ft or less.

Would you happen to know the name of that public document for our tape?

Henry Cavill cameo.

Free program called Paint.net. You might need a DDS plugin, I'm not sure exactly. Basically just open the texture files in that program. Most of them are 4096x4096px. Resize those to 2048x2048 (half), save as the same DDS (DXT5 with mipmaps I believe), and you're good. Well, probably not good if you fly online with IC-on servers. For me, adjusting external textures improved performance. I didn't need to touch the cockpit textures.