Nightstorm

You can open up the weapons\stores\a2a_missiles.lua and search for "loft_factor". Right now they're set at the default, same as stock missiles. However, in the past, adjusting that has helped with the issue you're describing. Do some testing and lest us know. I'd suggest trying 3.0 vs 4.5 which is the default.

-------UPDATE 250606 Updated DCS RWR Symbology mod for AIM-74A/B Updated multiple missiles for accuracy and performance boosts Updated enhancement mod for the v2.1.0 release of the EFM F22 Updated Engine page EGT graphics for v2.1.0 and altitude based temperature Updated FCS page graphics for v2.1.0 enhanced control surfaces Deprecated some unused controls in the keyboard and Joystick binding files Simplified the process a bit as the F22 model is included now. You still need the BIN and FM folders and contents from the v2.1.0 release. It will not work without those and you still need the avionics file for the F15C. Both the avionics and RWR files are linked at the bottom of the first post.

I just found out about the new version this morning. There were many changes. I'm updating the enhancement mod to be fully compatible again. I do have a full-time job Mon-Fri. Update should be tonight barring any problems. I'm not going to redistribute an entire mod that other people created. I've made the steps and instructions as simple as they can be.

Yea, the missile testing really became a pain as it got broken right in the middle of the ramp up to release. I hope it gets fixed soon.

Since I replied directly to you previously about the missiles, I'm not going to type it out again but link my reply. The core missile code is somewhere in those compiled DLL files in your BIN directory. We (modders) have no access to that code. So, we cannot fix it, and we cannot break it either. The missiles were working fine on 2.9.14 from back on 3/26. I keep reverting back to that version because a lot about DCS has been broken ever since.

I tested the new .1 release last night and didn't see any improvements. Since there wasn't anything mentioned regarding performance issues, I didn't expect to see any. It sat on a black screen for a minute or so trying to exit a mission back to the ME. All of these delays still seem to be CPU related. I've got a sensor panel with AIDA64 and when this happens, even it stops updating. Core i9 14900k (new) that has always been run on the new microcode and updated BIOS so no degradation. RTX5090, 64GB DDR6000. There shouldn't be ANY issue running this. And not to be a broken record but just switching folders to the 2.9.14 version and all issues go away.

If you're not using too many mods, that makes sense. It can complicated if you're using multiple mods that could potentially overwrite each other. That's when you need a mod manager. If that doesn't apply to you, then do what works.

Thank you. The one I have linked was made in OvGME, so anyone should be able to use it that way if the wanted, but I'm glad you got it figured out. I replace the entire mod file every time and there are often multiple files added or modified. Replacing the entire mod is the way I had intended.

-------UPDATE 250604 Added AGM-131C SRAM-T Tactical nuclear missile 10kt yield ~30nm blast radius in game. ARM guidance. Should make short work of a naval target.

Yes, every update or repair will flag those avionics files as altered, because they are. And it will replace them with the stock versions. Was that with the .1 update from yesterday? No mention was made of anything except campaign fixes. I hadn't tried it. Wouldn't be the first time that things got broken and fixed with no mention of either though.

I fortunately have enough space on my drive that I kept 2.9.14 and just renamed the folder when I updated to the newer versions. So, it's a pretty simple matter to rename folders and swap back and forth. Going back to 2.9.14 and performance is very good. Both in normal and in VR with no other system changes. Unfortunately, I lose access to the Germany map as that was introduced in 2.9.15. There are still many other maps to fly on though until this gets resolved. I can only guess at how complex the code base for this game is. And the strides that were made in multi-thread support are amazing. To the point, I understand, we not only don't need Process Lasso any longer, but should not use it if you're on Windows 11. I'm sure they'll get this sorted out. I just hope it's soon

@bhoop19 has already started work on a standalone version that does not use the F-15C avionics. It will be a long process and not something anyone should expect anytime soon. It takes a lot of work and he, like most of us, is doing this during his free time after working a full-time job and spending time with loved ones. So, yes, something is in the works for a future date, but not anytime soon. In the meantime, be happy that we've got what we've got. It's the best it's ever been in my opinion. Assuming that you can get it working correctly in a regular mission in mission editor, as I stated above, I don't know if the quick start missions work or not. It was said that the cold start quick mission worked. It's not like this jet is hard to start up. Battery - ON, Generators Left/Right - ON, APU start. Once it's up and running, that's it. Taxi, take off. Those quick start missions were written for a version that was introduced in 2020 unless I'm mistaken.

And you did follow the directions, right? Because the enhancement mod doesn't include the F22 3d model, flight model or EFM file, all of which are required for it to work. Procedure: 1. Download DCS Aircraft Avionics file and extract into your DCS MAIN Game folder, not your DCS SAVED GAMES folder. These files are required to use any third party mods that use the F-15C or other Flaming Cliffs avionics. Without this, the F-22 will not load properly. Example: .\DCS World OpenBeta or \DCS World 2. Download F-22A Github EFM v2.0.0 and extract it to a TEMPORARY LOCATION. You will copy three folders out of it in a later step but you do not need this installed. Example: Downloads folder 3. Download F-22A Raptor Enhancement Mod and extract it to your DCS SAVED GAMES folder, NOT the MAIN Game folder. Example: .\Saved Games\DCS 4. Required: From the F-22A Github EFM v2.0.0 F-22A folder, copy the BIN, FM, and SHAPES folders and paste them into the F-22A folder under your .\Saved Games\DCS\Mods\aircraft\F-22A The mod is now installed.

The anti-radiation version of them can be. The only issue is that because they had to be flagged as Air 2 Air missiles, defenses will not engage them. So, they'll just sail on into a ship. They go after Radar of course, and they just lock onto the closest strongest signal. You cannot designate a target. I do not know if the AI can employ them in that capacity because they are flagged as A2A. @Spino actually did a video of that.

-------UPDATE 250603 Modified the AIM-174B GUI name to "Gunslinger" as that is the official name. Adjusted sound WorldID that resulted in a smoother in cockpit sound loop. Added AIM-74A/B MUTANT missiles for use in the side bay or wing pylons. Adjusted all wing pylon missile rotations to align with the launch rails. MUTANT – Air Force Research Laboratory

At the bottom of the first post, you'll see this file DCS Aircraft Avionics.zip. That needs to be extracted to your main DCS folder. It should overwrite the entry.lua for a few of the Flaming cliffs aircraft including the F-15C. It will be replaced by a repair or an update and it would need to be extracted again. With that entry.lua there, you do not have to start in an F15C. If you still do, then the file isn't in the correct location. Look at the folder structure of the zip and compare it to your DCS main game folder.

Is that because you want it that way? You quoted my reply that said "See the first post for more information on this" From the first post: (You have to scroll past it to download the mod.) ***************************************************************************************************************************** --->F-22 WON'T LOAD, I CAN'T FLY IT.<--- IMPORTANT THERE IS A DOWNLOAD LINKED BELOW TO RESOLVE THIS ISSUE. THIS WILL HAVE TO BE REINSTALLLED EVERY TIME DCS IS UPDATED OR REPAIRED BECAUSE THE MODIFIED FILES WILL BE REPLACED. THIS WILL ALSO FAIL INTEGRITY CHECK ON MULTI-PLAYER SERVERS. READ THE GLOBAL FIX LINKED IMMEIDATELY BELOW THIS TEXT FOR MORE INFORMATION. *****************************************************************************************************************************

Good catch. I never use that so didn't think of it.

Well, I just flew it for an hour earlier and it shows up every time for myself and many other people. All I can suggest is that you follow the instructions. The mod isn't the problem. The instructions are both on the first post of this thread and included in the archive.

Yes, all available flyable aircraft, mod or not will show up in the mission editor. Yellow aircraft are flyable ones.

I was meaning the Quick Mission Generator doesn't support mods. Instant action missions? Don't know.

Any update or repair of DCS is going to remove the avionics stuff since those are modified files. That will need to be reinstalled every time a repair or update is done. See the first post for more information on this.

The new instant action didn't support mods in the previous 2.9.16 release. I didn't check since Friday. I don't know if it does it or not. I use the mission editor, and it supports all mods.

While the new version does still "work" and so does the F22 mod, I've had many issues with it. And it appears others have as well. The now locked 2.9.15 thread is still there to read through. The ONLY solution I've found is to roll back to 2.9.14. You lose the Germany map, as it was released with .15. I really hope the issues get resolved.

There are issues with the core missile code, not the mod. These are recent and apparent even with a clean unmodded install. There are a lot of bugs in DCS too. No one is forcing you to use the EFM. Good luck. The recent DCS update didn't affect the mod. Still works fine for me and many other people. The GD release of v3 and older I believe had that issue. I do not maintain or curate those versions. It was fixed in a release of the enhancement mod that's available on the first page of this thread. I've made many changes and fixes to the F22 mod over the last several years. I tried to notate changes in the readme but I can't remember every one that I did. It was brought up that it was an issue, and the current release of the enhancement mod has that normal file in the cockpit textures file. I don't think that the v2.02 EFM has it yet, but it will in the next release I think.