rob10

Why are people SOOOOO resistant to posting a track? It's the easiest thing you can do and often shows some simple step that's not mentioned in the written description that is causing the issue and saves so much time guessing what's actually going on for people trying to help. In your original post you mentioned both the button and the keybind not working which suggested a procedural error (in fact you even said "Am I missing something stupid?"). A track would help diagnose what you missed or help ruling out a procedural error. Now mentioned if you plug (presumably the old hardware) back in it works fine. Which suggests a possible hardware issue. Good luck figuring it out.

As I said in the other subforum where you posted this, ADD A TRACKFILE. That will narrow down what you could be doing wrong. Currently it's a complete guessing game.

Which carrier (Essex carrier has a problem with all users currently and is acknowledged) and are you using Tobi eyetracking (which currently is causing an issue with all carriers, which is reported, but not sure if it's acknowledged)

It's not a "problem with the external drive" per se, it's the fact that it IS an external drive which is almost always going to mean it is (much) slow transferring data to your motherboard.

Can I ask how many other 8 year old maps (or similar DLC) related to other programs are still getting updates (beyond what may be needed to keep them backward compatible)? Lots of programs have had updates or new "maps" introduced in that kind of timeline that look and perform better and rarely have they gone back and updated the old one.

I was just playing with this and I can say that SA-15 TOR's aggressively defended against AGM-88's that I fired at them . Set to Engage Air Weapons and Alarm State RED.

This is probably better in the F-16 part of the forum rather than Game Performance, but you really should post a trackfile of this happening because there's likely something you're doing wrong that's causing the issue.

Not sure why, because mine also gave me Windows restart prompt and everyone else I know had WIndows restart prompt as well.

What mods do you have installed? Try removing them, and if that doesn't work try running a repair with remove extra files. And if all that fails post a track of the issue, because I just tried in both P51 and Spit and all trims are working correctly for me.

My guess would be that if you get the refund from Steam under that exception ED will have to pay for the WHOLE refund (including Steams cut of the original purchase price, so ED is shelling out more than they actually received from your original purchase), which is likely why they want to wait until it's confirmed dead. If they refund it on Steam now, even if the F-15 comes back and you rebuy it, ED is still out whatever Steam's cut of the original purchase was. Purely speculation on my part, but seems logical.

I can't actually give you a true answer on that (not sure what that answer is), but it would be plausible to me that it might time out the USB and put it to sleep at which point it would freeze in game (and it doesn't recover well from such things), but wake the USB port up when you started looking at it in the TIR software. Regardless, it'll take you less than 30 seconds to check and doesn't involve changing any fundamental settings or anything, so what do you have to lose? One other thought - what's it plugged into? Direct into you computer or a powered USB hub? It's also possible (esp. if direct) that it's experiencing a momentary power drop if too much pull on all the USB's which could cause the same as above.

Yes it's a "simple thing to recreate" in theory, but without a TRACK FILE you're not likely going to get any traction from ED on this (if only because with a track file they can instantly tell if there are any mods installed and stop there instead of wasting time trying to recreate it and discovering it was mod related so they can't -- not saying mods are the issue here, just an example of why the need for a trackfile).

And check that the "shut off to save power" setting is turned off on your USB ports. You may have done it before, but Windows likes to change settings during updates etc.

You can do it. You still need to load it in the plane (i.e. for the F-18 in the MUMI page you need to press the ALR-67 OSB), but you won't have to browse and load the file everytime. However, I can't remember exactly how I set that up now, and I need to go hunting for directions and make a note of it in case I need to redo it EDIT 3: OK, change to what you desire for your "default" loadout in this file (adjust path for whichever aircraft you're after): World/coremods/aircraft/FA-18C/DTC/ALR67/CMDS_defs.lua You'll still need to load it in plane, but you won't need to browse for the file in the DTC manager. You can do the same under ..../COMM/COMM1_defs.lua and COMM2_defs.lua for Comm Presets. Can't say whether this breaks IC or not, I haven't checked.

TA radar should be in next patch (fingers crossed for this week), MSI has always been "planned" for August patch.

If you do a search around the forums there is a current bug with Viper and multiple HARM launches causing a crash, so likely a DCS issue rather than an issue with your mission.

Question: are you running DCS as Administrator? That could be why TIR wants to be run as admin. It is preferred NOT to run DCS as admin because it can sometimes cause issues. If you're running DCS as admin, try making both it and TIR run NOT as admin.

I don't doubt the graphics engine is showing it's limits, but reality today is 32 GB isn't enough (esp. in VR and MP) if you're less than 64 GB without pagefile. Having said that, MSFS is a very different game to DCS (I think people under-estimate the overhead of destructable units and proper simulation of weapons behaviour) so I'm not really sure you can directly compare.

Because it's not about your GPU RAM (more important in VR, but not always the issue), it's your actual RAM that's being influenced by your lack of SYSTEM RAM. Yes, lack of SYSTEM RAM can cause crashes, but also stuttering. Pagefile can help with that. As a basic rule of thumb having a minimum of 64 GB physical RAM + pagefile is a good recommendation to avoid issues.

As a starting point since you only have 32GB RAM, I would adjust your pagefile to a fixed 32,768 MB on your fastest drive (it's currently only using 2,048 MB

Sorry, but not likely or this would be more widely reported. As Muchocracker said, post a trackfile. There are a lot of little things you may be missing (i.e. single steps somewhere) that can prevent it from firing and a trackfile can narrow it down very quickly.

I can't recall what all WASN'T included, but some of the assets were not included in the "official included" version for various compatibility reasons I believe. IIRC moving vehicles + lights might have been included in that. Do a search on Massun and you'll likely come up with threads on what is/isn't included.

You need to be 1/2 flaps (full also probably prevents this, but 1/2 is proper way to do it) for land or carrier takeoff. If you forget and it starts doing a rocket to the moon imitation just flip flaps to 1/2 and back to AUTO and it will give you control back.

Alternative that I discovered today is to change the default DTC loadout to save you the step of going into the DTC manager to load that file everytime. You still have to load it in the MUMI page, but that's less of a headache than loading the cartridge profile if you use the same settings all the time. You can change it here: DCS World/coremods/aircraft/FA-18C/DTC/defs.lua No idea if it impact IC as I haven't tested that.