Majik

Another log attached. dcs.log

The missions I've been getting most crashes on do have F-14 slots, but none spawned. Does that make a difference? Also, I've flown around in the Tomcat on busy Supercarrier decks with no issue. My squadron's server does have a few static jets (Warthogs, Hornets, Vipers) placed around Nellis, and loading textures on one of these seem to causes crashes as I click to spawn into a jet. When I do manage to get in, I get crashes as I apporach one of the ranges and objects/units there try to load in. As you said, I have enough memory and pagefile, so it's a little baffling unless there is a memory leak or something. As for rebuilding saved games, I've done so twice already. Got a nice performance boost, but no help on the crashes unfortunatly.

Windows is current, no pending updates. I've attached dxdiag below DxDiag.txt

For the past month, I'm getting constant CTD, usually on heavy MP missions, and seemingly for various reasons. Limited memory/VRAM seems to come up regularly when it seelingly shouldn't. I've attached 4 logs below. Often the log won't even show why the crash happened, and I've even had a blue screen happen once. Based on advice I've seen, the steps I've taken to alleviate issues, all to no avail: - Tried without mods - Lowered in-game settings (textures, clouds, preload radius) - Multiple slow repair and clean - Clear fxo and Metashader2 constantly - Reinstalled Nvida drivers (w/ DDU clean) - Removed GPU overclock - Run Nvidia debug mode - Rebuilt saved games folder twice - Moved pagefile from SSD to NVME I'm at a loss of what to do here dcs1.log dcs2.log dcs3.log dcs4.log

From the mission linked description: I haven't played Nightly Silence, but as Sinclair_76 says above, and judging by the name, if NVGs are installed, then HMCS will not be (it's an either-or case, and can be switched by talking to crew chief on the ground)

I've had this happen a few times in the last couple months, both with airstart and cold. Only ever with Sidewinders, and I've checked my hotas isn't the issue. This is a bug for sure. I don't have a track, but I do a have a tacview of one such incident attached below Tacview-Multiple-AIM9.acmi

Thanks for confirming, after cycling through a bunch of different DNS providers, Cloudflare ended up working. I had stayed on Google DNS since the last time, and incorrectly ruled that out as being the issue. Thanks again

Hey Home Fries, I'm getting the server not available error when trying to update. Being from Europe, I remember a similar issue last or earlier this year that was solved for me by changing DNS to Google's servers. I have been trying a few times a week at all sorts of hours, for the past couple months with no luck, as I've seen in this thread that the server may be down when you've been away. (I'm still on 2.570) Any thoughts on how I might solve this?

https://www.digitalcombatsimulator.com/en/files/3309795/

If you're talking about the Left and Right Hardpoint switches at the front of the right side panel (SNSR PWR), those are used to power the cheek stations, which only hold sensors (TGP, HTS), not stores.

Once the HSD features are more fleshed out, you should be able to cursor over, and delete the ring.

Sounds like you're talking about the auto and semi modes, which release countermeasures with consent (enabled and disabled via CMS switch), based on current detected threat. Not currently implemented, but are on the roadmap. In semi mode, when a threat is detected, the VMU will promt you with "counter", and you can CMS aft to dispense the program once. In auto, you press CMS aft to enable, and the system will dispense the program as many times as needed, when needed, until the threat is gone. CMS right disables auto dispense, but you'll still get the "counter" VMU warning. To my knowledge, steerpoints don't play into this (unless somehow planned into the DTC I guess?)

Unless playing a mission with preset frequencies programmed, it's usual to just punch in the freqency required on the COM 1 or 2 pages and they'll show up on the CNI page. Personally, when using presets, I also change them using the COM 1/2 pages as well instead of faffing with the dobber on the CNI page. e.g: COM 1 > 4 > Enter done.

Best place is here: https://www.f-16.net/f-16_versions.html

You've posted the instructions on how to do exactly what you're looking to do... That CNI page on the DED is the "default page", and all you have to do is press Return on the dobber, no matter what other page you're on, to get back to it.

I imagine it's for added strength in case of a bird strike. I know Japanese F-2s replaced the F-16's bubble canopy with a two-piece as they're used in a naval role, where I think bird strikes are more of a concern. If it is the case with the 35, then it'll be another reason the B and C model commonality hold back the A

It can seem daunting to setup initially, but it's extremely well thought out, and works for all modules

Look like it could be a binding issue? In your video, you've got two seperate sets of buttons bound to Main Power (22/23 and 27/28), which look like they might be interfering with each other. I'm not sure how you've set it up though, and I'm no bindings expert, so could be wrong. Try each of the following and see if it helps: - Remove one set of bindings (22/33 OR 27/28) - Remove all Main Pwr bindings - Run a DCS repair I've had a few odd issues like this clear up with a repair

Tried a few hot start instant action missions just now, and everything works fine here. Do you perhaps have the Elec Power switch mapped somewhere on your hotas, and it's left in the off postion? Might be worth running a repair if not. Also, to get rid of the ELEC SYS caution on the panel, hit the Caution Reset button on the ELEC panel in your first picture.

Denmark received Block 1s, as well as 5s, 10s and 15s later. US F-16s were entered into, and won, the Tactical Bombing Competition, Lossiemouth, in 1981. The production F-16 Block 1 was not the YF-16, and was always A/G capable (to the lament of those who came up with the original design). Block 15 added the intake hardpoints (5L/R), not underwing. Back on topic, SDBs would have been great. But understandable why we won't be getting them. Edit: Also, the Israelis proved the A/G capabilties in combat, also in 1981, with Operation Opera/Babylon

There are two seperate issues at play here. First is the LOD issue discussed here: Turning on the parser pre 2.7 solved the horrible LOD differences with clouds (most egregious), shadows, and smoke/fire, with the primary downside being floodlights only appearing in one eye, and occassionally seeing ghost coastlines. Despite being WIP and the stated issues, having it on was the better option for me. The second is that 2.7 introduced new issues with smoke and contrails appearing in different eyes with the parser on. Now that I've turned it back off, the shadow LOD issue is back, but doesn't seem as bad, and the new clouds are working fine as well as smoke and contrails. Coastlines and floodlights appear just fine again also. Overall, despite losing the performance benefit, having it off now is the better option for me.

Yeah, we don't have EGI our jets. I haven't tested in DCS, but in the real jet, you're supposed to be able to do an in flight align on the ground in lieu of cocking and stored heading align, and have it sort it all out for you. Not sure if that's for the EGI models only though.

Mirrors my experience and thoughts. Upping Steam SS to 130% from the default 100% produced a similar picture to what I normally see, with similar performance going by feel (frametime monitoring may prove otherwise)

+1 And IFA actually is implemented as you state. If you need to re-align in the air, you set the switch to IFA, set/confirm your heading in the DED, and fly straight until aligned, then back to NAV.