rob10

And in answer to the OP's original question from a F-18 perspective: what I find works best with TIR is to lean back as far as you can when you re-centre TIR (TIR will typically max out in how far you can go). Then when you are in your natural sitting position the HUD should be fully visible to you.

Pretty sure that's a default section in the "file structure" for the F-18 and there are no official Supercarrier F-18 training missions to be had, so nothing to re-download because it doesn't exist.

And just to point you that you posted in the F-18 section. You might have more people with A-10 specific knowledge in the A-10 subforum. Or when you say Warthog do you mean the Thrustmaster Warthog joystick/throttle? If so disregard my comment. I assumed you meant the plane based on the previous comment, but I see you have other questions re: F-18, so now I'm thinking you meant Warthog controller.

A few more details? And try removing any mods you might have. I just tried "carrier t/o" on Persian Gulf and had no problem with external views.

I can't help you with your question, but I can say it's not an issue for all 3 DDI screen users (and I'd bet a pretty high percentage of DDI users are 3 screen). I had 3 on my old system with Win 10 and now on a new system with Win 11 Pro and I haven't had issues with the settings not sticking. I also have my screens alternating with the button frames (in the same hub) so I don't think having them all side by side is necessarily a requirement either. So, sorry no useful info for you, but just wanted to clarify that it's not an all user problem either .

I have a Brother one that does similar.

I get your bitterness towards DCS currently, but yes, of course you will be asked those questions. In your case they aren't likely going to help, but in at least 50% (or more) of the cases they get it's probably the cause, so rather than chasing a phantom issue that doesn't exist because they didn't ask those questions they check for basic issues. I've seen too many threads on here that go on for pages before they're solved because no one asked the simple question ("do you have the supercarrier module installed?") and are assuming it's a mod conflict or something that's causing the carrier not to show up.

I enjoy SP, but in fairness your MP experience sounds like you needed to find a different group. If you get a good one people show up on time, are mature, and no-one abandons the mission mid-course barring hardware issues, or there is very rarely not enough for a proper RTB. Not having time for RTB is poor planning -- either late takeoffs or mission isn't designed well to allow for enough time.

It's not a "bug" perse, they just never implemented voiced callouts for the new callsigns. It's a lot of work to do that correctly. I believe they're waiting until they do the complete ATC overhaul before they mess with it (so they aren't coming "soon").

Ya, active LED version is probably less affected, but there is about a week a year for about an hour a day where I get some sort of weird reflection (sun is on other side of the house and nothing obviously reflecting but angles apparently line up right) that causes me issues. Otherwise with reasonable blocking of direct sun it's not a problem.

All kinds of reports on that if you look around here. It should be fixed in the next actual core update (today was campaign update only).

Glad it got you sorted! You might be able to play with the position of the MIP monitors from the way I showed (i.e. move the right one down a bit) you to get yourself a bigger area to catch the corner. There is no specific layout required (just try to minimize the total area).

Wouldn't hurt to bump your pagefile to 32 GB from the 20 GB you have it set at for MP. It doesn't appear you have mods installed but errors like this: 2025-02-05 02:29:07.078 ERROR_ONCE DX11BACKEND (11120): texture 'KevinWakePattern812x1024.dds' not found. Asked from '' suggest you maybe have some mods installed in the main DCS folder rather than the Saved Games folder (or remnants of mods)? Definitely run a repair because you've got a crap load of missing file type errors. Maybe someone else can identify what they suggest (and actually this one that I randomly landed on suggests you're short pagefile memory or else your pagefile is running out of space -- how much space do you have available on your pagefile drive): 2025-02-05 02:32:44.435 ERROR EDCORE (12148): More out of memory in ed_malloc for 20971535 bytes. 2025-02-05 02:32:44.435 ERROR EDCORE (12148): More out of memory in ZoneAlloc for 20971520 bytes. 2025-02-05 02:32:44.435 ERROR DX11BACKEND (11120): failed to create vertex buffer. Reason: DXGI_ERROR_DEVICE_REMOVED 2025-02-05 02:32:44.435 ERROR DX11BACKEND (11120): Failed assert `false && "failed to create vertex buffer"`

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.

Guess I'm not "most players" either. I own a bunch of modules, but I fly the F-18 almost exclusively these days. Just from the forums it's pretty obvious there is no generalizable "most players" when it comes to anything DCS.

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.