rob10

Watch your speed as that circle contracts and expands. As your speed is going down (while you're turning) it's contracting because the SLAM is starting at a slower speed so can't travel as far (using more energy to go the same distance because you're giving it less of a boost off the start). Also (although I don't think it's the thing in this case) if you point your nose off the target, the circle is going to contract because the SLAM is going to have to travel farther/expend extra energy in a turn than if you're heading directly toward the target (that's what I was expecting to see TBH). And sorry, didn't pay attention to the X'ed out, but that likely means you're within MIN range or due to speed/off boresight you're beyond MAX range.

For starters I would recommend STACKING your MFD's rather than having all three beside each other (at least stack two and have the third beside). That will reduce the total amount of screen you're rendering and should help reduce load on your system (even all that black area at the top right still causes load). A side effect of that would be that the top left corner should be in one of your MFD's and allow you to move it. Example of how I have mine stacked below. Which one is where doesn't really matter as long as you have it set properly in SimAppPro. And it doesn't directly solve your problem, but a possible 2nd option (at least in the F-18, not sure the F-16 has it) is to enable the pilot body and use the kneeboard on the leg of the virtual pilot. I overlooked that option for a long time since I didn't normally fly with the pilot body before they added the kneeboard to it's leg.

You can actually put the solider INSIDE most or all of the buildings so it's basically invisible. Not sure if that's what you're meaning by clutter.

Can't be just Win 11, 24H2. I'm on Win 11 PRO 24H2 on a new setup I just got and not seeing any issues. In your case you only have 32GB RAM and you've only got 5 GB pagefile. Bumping your pagefile to 32GB max/min should help you out.

I just tried this on our squadron server, JF at about 20K so I went up to 30+K. No problem locking and holding him (actually 2 of them) at 50+ nm. Double check your radar altitude and that you're in an appropriate PRF. Really sounds like either he's notching you (MED PRF can help) or you're not on ideal PRF for distance (HI for longer range, MED for <20 nm)

Go to MISSIONS AND CAMPAIGNS subforum just above here and search BANKLER and you'll find it.

They're perfectly visible (esp. if you use Reshade). If you don't use reshade then you may find the main screen versions too bright at night or else the WW MFD versions too dim if you turn the screens down. Daytime it really isn't an issue either way.

If you actually only had 64MB as you said, then yes your RAM would be holding you back. Fortunately you have 64 GB which is very comfortable . Since you mentioned you are using SimAppPro, have you tried changing this (change inteveral to 0.3 from 0.03): In the file \SimAppPro\resources\app.asar.unpacked\Events\wwt\wwtExport.lua Line 19 -- winwing.interval=0.3 - default is 0.03 NOTE to prevent this from being overwrote back to default every time you restart SimAppPro you need to set the file to READ ONLY. This change reduces how often SimAppPro polls the devices from every 0.03 secs (so almost continuously) to every 0.3 secs (which is still a lot) and often reduces to overhead of SimAppPro.

This seems to be the common error in your logs. Can't say I've seen it before (at least not enough times in a log that it stood out): 2025-02-02 03:33:21.981 ERROR EDCORE (Main): Failed to set thread's affinity mask (id:18884 priority:13). Error:87 That's way beyond my knowledge level, so I can't really suggest anything in relation to it. The other thing seems to be this: WARNING BACKENDCOMMON (7840): Need to reprocess [DDS] image '/textures/Deck_Normal.dds'. Reason: Conversion requires - expanded pixel size, setting alpha to known value. Source is an 8:8:8 (24bpp) format ... which is more common but I can't remember what it suggests right at the moment. I'd agree with @Flappie that renaming your "Saved games" would be a good starting point. Definitely seems to be some questionable files hiding somewhere

Is it actually tracking it or is the "new" proximity fusing distance change just causing it to explode beside the missile? From the pic above it looks like it changed course well before the missile went very far and about the same time the F-14 pitched up. Not saying you're wrong, but not sure those pictures make a convincing argument for what you're claiming.

If the DATE is set before Mar 29, 1994 GPS didn't exist so you won't get any GPS data.

I just got a new system and was really disappointed at how slow it was loading DCS. Then I remembered to exclude it and WOW does it make a huge difference.

I just got a new system and was really disappointed at how slow it was loading DCS. Then I remembered to exclude it and WOW does it make a huge difference.

Pretty sure he means in the real world, not in DCS. He's explaining why left turns are the normal.

Assuming the AI actually understood that, yes. Problem is that currently most of them literally just make stuff up if they aren't sure and it ends up being gibberish. At least that's what I've seen reported so far.

I think it may work well for creating a storyline, but as for actually creating the mission good luck. Current AI are still too prone to making stuff up if it doesn't know the answer so most of the code it comes up with is pretty questionable.

I have no proof, but I'd think not. That's maybe a different (or maybe related?) issue to when they changed the structure of the .lua for that stuff. I get limited resources so they can't do everything instantly, but it would be nice if ED could update stuff like this on the included aircraft eventually. Drove me nuts on the F-18's in our squadron's custom liveries until I finally got it to work right. And really don't even see it that much

Definitely an issue and ED are working on it, but also seems to be server specific. I haven't ran into it on our private squadron server at all. I think 4YA is one of the more common ones seeing it.

It's very handy function (barring the current blinking issue). A side benefit is because they are actual "units" they show up in Tacview. The pretzels I contorted myself in to make this work with triggers before I learned about this function ..... . Glad to help!

UNCONTROLLED OPTION – using this the aircraft will be visible at mission start - it will not do anything (won’t start or move) until it is given a PUSH command with trigger - these aircraft can be destroyed on the ground at any time from mission start - in AIRCRAFT TRIGGERS (third tab), ADD – PERFORM COMMAND / START - in your triggers, set ACTION as AI TASK PUSH, in dropdown select desired UNIT NAME / 1.START NOTE: UNCONTROLLED AIRCRAFT will NOT perform any Advanced Waypoint Actions until they become controlled (even if these are set on WP 0). For example, an uncontrolled aircraft with an Advanced Waypoint Action of “invisible” on WP 0 WILL NOT become invisible UNTIL they are controlled.

It was fixed, the thread you're posting in is over 3 years old. The current version of this problem is being discussed here:

Set it as UNCONTROLLED and use a trigger to start it when you want. NOTE: currently there is a MP bug where if you have any uncontrolled aircraft clients may get some blinking of objects in game. ED is working on it and I think are hoping that it will be fixed next patch.

Being discussed already here. Which is actually the more appropriate place since this is a supercarrier issue, not a F-18 issue.

1st check that you have DCS excluded from your anti-virus (anit-virus may have caused the issue in the first place), then run a REPAIR on your DCS (can't remember what it's called in STEAM but something like "verify" if you're using Steam).

And they've indicated recently that they aren't likely to mess around with never versions of DLSS until they Vulkan finished up. I think that timing is about resources.