rob10

They are telling you that the unit is beyond limits side to side (6 degrees rather than max 5 degrees) but within limits front to back (1 degree vs max 5 degrees). So you need to place it on leveller ground for it to be able to be functional.

No apparent reason for it, but NordVPN seems to be coming up as a problem with number of people in the last week or so. Likely something that would need to be tweaked or fixed on their end.

It's your anti-virus. There are lots of threads about this issue and how to fix it if you search around even a little bit.

From your other post, you're flying the F-18 as a RED COALITION member. Unless you have Unrestricted SATNAV selected you're going to have a degraded GPS so no wonder it's not hitting accurately. This is a prime example of why we ask for a track file when trying to help people. It's usually the little details that they don't think to mention because it doesn't seem important to them that are the root of the problem.

See this reply from further up the page: And add a track if you want to get actual answers about your specific case.

Do you have them plugged into a USB hub? Is it powered? My 1st thought would be not enough power. Try swapping the bezel that not showing for one of the ones that is and see if it's working. That should rule out hardware (cable or physical device).

Yes, DLSS isn't a good option if you have a higher end system. You can't get something for nothing so the tradeoff is some ghosting or less clarity in return for higher FPS and potentially higher resolution settings. For people flying in VR a lot of them are happy with the tradeoffs. DLAA can be turned on independently of DLSS. DLSS does not need to be activated to have DLAA turned on.

Completely guessing what your problem is, but you need to turn the external lights either off or on (can't remember which) for the Tomcat if I'm not mistaken (rather than saluting like you would in the Hornet).

You have unlimited ammo/weapons checked on in your settings.

Just add a tiny (like 1 or 2) deadzone in the axis tuning. You shouldn't notice it and it should allow you to arm the A/P.

At 300 kts you very probably broke the gear doors (250 kts is max deployment speed) which will inhibit weapon release. As I said before, maybe not enough to damage the gear itself, but if you damage the doors you can't fire weapons. This used to be a common issue when people weren't retracting gear fast enough coming off the boat.

If they told you it worked but it didn't, then maybe I could see the point of your post. But them telling you it won't work but it does? Pretty hard to get upset about that. Saying it DOESN'T work I imagine would be the default position if for some reason someone wasn't sure of an answer but was answering it anyway because there's a lot less chance of blowback if they say it doesn't work but it actually does. In fairness, it's arguably in their own interest to "officially" claim it doesn't work since maybe that'll drive more people to buy their stick and base rather than just a base. I can't really fault them for that either because any indication of support and you'll be back screaming that they won't help you with their competitors hardware. I agree with previous posts, either there's a language issue or else you're making a mountain out of a mole hill.

If you made it up to FL18 with gear still down you likely went fast enough to rip the gear doors off, so even though you could technically retract the gear, the F-18 systems would have considered that serious damage that would prevent weapon employment.

You may not realize it, but you are on the current version of DCS so you ARE using the MT version (from your log: DCS/2.9.13.6818 (x86_64; MT; Windows NT 10.0.19045) since there is no ST version anymore. That's not really important to your question though. Taking a quick look at your log you should set your pagefile to 32GB set max and min value, set it on your fastest drive, and make sure that drive has at least 10% free space (after taking the 32 GB for the pagefile into account). You've only got 32GB RAM and your pagefile is showing about 4GB so you're almost for sure running out of memory with full fidelity planes.

If you have PRIORITY (i.e. the little diamond in the top right of the MFD) on SA page, it will perform the EXP (expand) function the SA page. It will blank the HMD if you have priority on the HUD or any MFD that DOES NOT have the SA page on it. Not a bug. And if it's not that, remove any mods and do a repair and if it's still happening post a track because it's working fine for me.

Thanks. That's helpful for figuring out what works. We at times have a range of different planes and helos in our missions so finding freqs that work across our spectrum gets challenging.

The reason it's not better than it is is because it's not "an inexpensive add on". Look at the challenge the carrier deck crew has been and that has ONE layout (generally speaking) for all carriers, vs how many different variants at all the different airports. Hopefully they decide at some point it's worth adding as a base function, because I doubt it will be less than a full module cost if they specifically make an ATC module.

Thanks @Flappie. Doesn't appear that it has any ability to change modulation, just frequency. AutoHotKey option in the mission editor itself has been handy, but no easy way to select or change the modulation so might have to look at doing something like you linked or changing up our freqs to avoid default F-18 FM ones.

That is "normal" as ai aircraft would be despawned after they land and shut down. I realize it's not a great option since that's happened at the end of a mission so likely bigger trackfile, but you're not likely to get a lot of traction on the report without a track.

This change was made quite a while ago now, but unfortunately the manual hasn't been updated to reflect the current situation. I'd recommend scrolling back through the changelogs for updates because there are likely other things that have changed that aren't reflected yet. Any videos more than 6 months old you'll need to take with a few grains of salt as things have been added or changed over time.

I know it changed back at some point because in our virtual squadron we use an AutoHotKey macro to insert all of our radio presets (we use a standard set of frequencies and presets). If it hadn't changed back since the original change we'd have had the issue in missions because the other planes (i.e. F-16) are on AM by default so the F-18 guys wouldn't have been able to communicate with them. So I suspect the "bug" was that it regressed from the 2023 change at some point and just got fixed. Anyway, thanks for looking into it and the explanation of why it is the way it is (back to) now!

Did you set the laser code on the bomb in the REARM MENU on the ground before takeoff to whatever the JTAC is using? You can't change the code on the bomb in the air (it's a mechanical settings on the bomb). Changing it in the stores page is strictly for reference for guided bombs. The MAV is different and you CAN change it in the air that's why it worked.

My guess is you're using the Stennis carrier. ALL deck crew (not just the new one) is currently disabled on it (even if you own the supercarrier module) while ED figures out how to have the new one only show if you have the paid carrier module and aren't just using the free Stennis (which has no crew at any time). Could be a mod conflict, but that has typically caused the whole carrier to not appear.

This gets way out of my "have much knowledge" zone, so take it with a few grains of salt. But from what I've seen the newer/higher end Intel CPU's don't seem to play well with DCS (can't really speak to other games). I recently upgraded to an AMD x3d based on recommendation from squad mates and it works very well for me.

No you don't. Just turn the new deck crew off in options menu. And there would be a much greater chance of this getting fixed if either of you had included a track file (with NO MODS) to make it easy to reproduce and figure out the exact case that causes the issue.