rob10

They have said recently it is planned for Q1/Q2 of 2025. So it's still coming, just not here yet.

ED has made it clear that it's added to F4, F16 and F18 to start and will come to other modules over time. Is that perfect? Maybe not, but it's not unreasonable. It also gives them a chance to see how it's working in the wild and fix or tweak it. I'd rather have it show up on those 3 planes than have to wait until they added to every plane in the game at once. And I say that as someone who basically only flies the F18 so should be "disadvantaged" by this.

Wow. I'm not sure I've ever seen that many file errors in a log. Have you ran a slow repair and allowed it to remove extra files? It sure looks like you have a bunch of leftover mod files or something. Eventually you get to the C0000005 access error, which might be a different issue, but I'd start with trying to reduce the number of outright errors that are showing up before you go any further.

I don't think Stennis was ever meant as a training ship in any way. It was simply an option for modern carrier ops for those who didn't want to purchase the supercarrier module. Supercarrier has always had additional functionality and more variation so it is a paid add-on.

Yes that will work. Just note that you'll have to redo that after every update as it will get wrote over.

Have you actually bound any of the OSB buttons in the DCS bindings? And done so under the "F-18" tab? They are not automatically assigned. If you're using the provided download option from WW I have no idea because I have never used them.

Do you have the "speed limit" setting turned on? It could be that you're trying to move out of the landing area (at what I would consider to be a reasonable speed for doing that) at slightly over speed and it's slamming the chocks in. You need to drop throttle back to idle to remove them in that case IIRC.

0.5 nm from the tanker to be exact.

I like the idea for it showing up in the kneeboard, but realize that doing ESC in MP doesn't actually freeze anything. You can very successfully crash or get shot down while you're busy looking at that stuff . In SP it does pause the game.

Try temporarily setting your TDC DEPRESS to something that's independent of your TDC controller (i.e. a different button rather than an actual depress of your TDC controller) and keep your finger off your controller when you depress the other button (you might be causing movement as you press which will make it not work). If it still isn't working set your deadzone to something like 25 or 30 and see if it works just to confirm you're getting tiny input from it even if it's not obvious. Almost always this issue tracks back to tiny movements of your TDC controller. Also check that you don't have any extra bindings for the controller.

You would be surprised. I forget which mod aircraft it was that caused the carrier to completely disappear on mission launch (even if it wasn't in the mission). And we still have zero clue what you're trying to do when you see or exactly what you are doing, so it's pretty hard to offer any suggestions.

How much memory/pagefile? And is pagefile on your fastest drive? And what anti-virus/do you have DCS excluded? For that it sounds like something is slowing texture loading. An easy thing to try (may not help, but easy to do and can't hurt) is delete your fxo and metashader2 folders in your saved games folder.

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"`