rob10

Something that could cause that is if you're dropping the points too close together. Zoom out a bit and it should be farther apart and that may solve your problem. Mods are always a good culprit to check too since they can cause weird and unexpected issues at times.

It isn't really obvious, but if you click on the FILE button in the top left it will allow you to IMPORT a DTC if you've made one and exported it already.

@NineLine Here is a track and the associated DTC. 1 x F-18C runway start in Caucasus. Imported the DTC on the "fly" page, then loaded it via the MUMI page. Frequency #'s are correct but they all default to FM. Only Comm 2 presets 10-12 should have been FM (only available modulation for those frequencies). Double checked that Easy Comms is off on my computer and in the mission file. Also, and at least as big of problem, it won't let you change it from FM to AM in the UFC. Haven't checked which it's actually using in game yet (AM or FM). (Sorry Bignewy, meant to ping Nineline, not you 1st time ) F18 DTC forced FM only.trk FA-18C JTF-111 BASE.dtc

A short trackfile of the problem will be much more helpful to figuring out the problem than that picture. It's likely something simple, but without the trackfile it's purely guesses.

If you're seeing flares on landing you need to update. That was removed shortly after it got added.

In the Hornet, as long as the mission builder places a bullseye in the mission, WP59 will default to it (even if it's also at say WP 4). So it's generally safe to assume that WP59 is always (not quite true but close enough) your bullseye.

Not sure what your actual issue is . Yes, it changes it to 4096 x 1440 because it now includes wherever the MFD's are displayed. They are displayed as part of the "main" screen and then exported onto the external MFD's, so it's completely normal for it to be 4096x1440 and shouldn't cause you any issues in game. Are your MFD's actually working if you change it back? As a sidenote, if it's going to 4096 you likely have the 3 MFD's side by side in your windows setting. You can stack them in whatever configuration results in the smallest total area displayed. At 4096 x 1440 you're pushing 5,898,240 pixels. This likely includes a bunch of black space which is still has to draw. If you can get it to for example 3340 x 1440 you're only drawing 4,809,600 pixels so less load on your computer.

If you include a track file of this happening you're much more likely to get a meaningful response. Without it there are so many possible variables that it's nearly impossible to recreate it exactly. My other question would be what MODS of ANY type to you have installed? They can cause issues with things that seem completely unrelated.

It was legit to bring it up. We don't have good details on the fuses to suggest whether it's correct the way it is or whether the option to select DLY1 is bugged. I might not have noticed except that I never even thought to change it to DLY1 when I dropped it Saturday, so I noticed you did (was watching to make sure you had armed the fuses and that wasn't the issue).

Well there's your problem: you used the AF variant and it didn't like being dropped off a Navy plane . I did use the USN variant but they should in theory be identical. Yes, that was the C+C bunker I dropped on (good to check). So in quick testing it's related to the fact that you set the fusing in the stores page to DLY1. If you set it as INST (with the 0.06 sec set in the re-arm menu or mission editor) it will take them down with a single GBU-31 (naval or AF). I suspect this is it looking for something functionally when you have DLY1 set that doesn't work with that particular fuse (I assume you were using the default FMU-139?) when you have it to DLY1 and isn't triggering at the appropriate timing. I don't have in depth enough knowledge to speak intelligently any deeper than that on it though.

If you a track you might get some useful answers. Trying to diagnose from pictures is very difficult to do reliably.

As the OP discovered, if you run into this specific error check the time on your computer is correct.

100% agree with what MAXsenna said. That's a LOT of IC errors which suggest that the mod was installed into core rather than saved games. It also was showing IC error on Aim-120.lua and Aim-9X.lua near the top of the log so a slow repair to clean it all out and reset things back to base is your 1st step.

Used a single GBU-31 on a command and control bunker on Saturday from the F-18 and took it out no problem. Are you changing the fuzing delay on it in the Hornet? I set it to the maximum (can't remember what it is). Not sure if the F-15 has options for that yet so that may be the difference. And yes, a track file is pretty much a need to do to get a real answer.

It works differently to other datalink stuff. You can't change the frequencies for it and you don't need to have anything in your plane tuned to a specific frequency to use it.

The enemy likely was firing an IR missile at you which will give you no warning. They have some very effective longer range IR missiles that you need to be careful of.

Did you previously have a target designated? You may need to undesignate it and VVSLV your pod to get it to slew to the new target. You need to do that with the A-G radar for example.

The "random" retractions are likely due to time out of your clearance. If you take too long to catch the basket it will retract it and you need to get cleared again. Normal behaviour and has always happened. Of course as Flappie said, a track would be very helpful.

There are a bunch of errors related to the A-4 mod. I'd start looking there.

Just to check, do you have ANY mods installed? They are known to cause issues like this. Would also likely be helpful to have a trackfile of the issue so they can follow the exact same steps to recreate it.

Sorry, can't help with old version of the app, but from your log you definitely seem to be experiencing what the OP does. Your crash was an out of memory error.

The nVidia splash screen was strictly as a result of the licensing agreement related to use of DLSS if I'm not mistaken. So it probably doesn't indicate anything else.

And one watchout to WEAPON IN ZONE is that you can't make them too small or you'll get very inconsistent results. The game only checks roughly once per second so if timing works out that it enters the zone just after a check and manages to exit it (or blow up and no longer exists) BEFORE the next check it will never fire.

How about they'll fix it when they get to the bottom of what's causing it? It seems to be an issue on specific servers and isn't widespread beyond that which likely isn't helping them find the cause.

If your probe is going through the drogue that usually means you done proper comm's to get cleared for contact. You still need to do that even if the drogue is out already. If you don't get cleared it won't allow you to connect.