Nightstorm

*UPDATED 06/15/25* SEE THE END OF THIS THREAD FOR UPDATES OR CHECK THE README.TXT SCROLL DOWN TO THE BOTTOM OF THIS FIRST POST OR READ THE INSTRUCTIONS INCLUDED IN THE ARCHIVE. *DISCLAIMER* - This is NOT a new version the F-22A Raptor mod by Grinnelli Design's. This an addon to the newly released EFM version of the Grinnelli F-22A Raptor mod by Branden Hooper that overhauls the pilot interface and adds multiple additional weapons and stores. I am NOT by any means taking credit for any of the works of the aforementioned team(s). Without them, there wouldn't have been a mod to mod. I originally started this "project" to modify the F-22A mod to my own liking. Afterwards it was suggested that I make the changes available to anyone else that was interested. It is not a repack of the mod and still requires the flight model and the EFM binary to work. No slight is intended towards the original mod or its creators. I've been very fortunate to have participated in the testing of the new EFM TVC add on for the F-22A mod. That mod is now available for download. I've spent quite a bit of time and testing to update the Enhancement mod for use with this version. See the readme(s) for details and credits and install instructions. See below for links to the updated enhancement mod along with optional liveries and other add-ons. The enhancement mod requires the EFM Raptor v2.1.0 F22 mod. --->EFM Raptor v2.1.0 available at: Releases · grinnellidesigns/f-22a Home - GrinnelliDesigns Thank you to the Grinnelli Designs and EFM team(s) for all of your hard work in bringing this mod back to life better than ever! ***************************************************************************************************************************** --->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. ***************************************************************************************************************************** I'm going to link all of the files and liveries for the F22 "enhancement" mod here. I'll keep the same file names through any updates. More details about the mod found on the link above. Remember that the main mod is REQUIRED (linked above). F-22A Raptor Enhancement Mod available here: ATTENTION: CHECK THE CONTROL BINDINGS. MANY NEW CONTROLS WERE ADDED. --->https://www.dropbox.com/scl/fi/wv1jjbz9998m9rngmp6iw/F-22A-Raptor-Enhancement-Mod.zip?rlkey=h6ut6o9kaeoxctbq8iwuavy6o&dl=0 F-22A Squadron liveries. These are consolidated into four large zip files that contain liveries for all 195 Raptors. Some have different versions of some aircraft at different points in their life cycle. A good example of this would be the Raptors of the currently deactivated 7th FS from Holloman AFB. Those aircraft were later dispersed to various squadrons. Some corrections have also been made to other aircraft. A special thank you to @Texac for allowing the use of his livery template for these! Set A is the FF (Langley AFB Squadrons) https://www.dropbox.com/s/tlt22v884c3q37r/F-22A Liveries Set A.7z?dl=0 Set B is the TY (Tyndall AFB Squadrons) https://www.dropbox.com/s/3d3e201qdmz63lt/F-22A Liveries Set B.7z?dl=0 Set C is the AK (Elmendorf AFB Squadrons) https://www.dropbox.com/s/nm6g4raiinvuy90/F-22A Liveries Set C.7z?dl=0 Set D is all of the other squadrons HO, ED, OT, WA and HH (Holloman AFB, Edwards AFB, Nellis AFB, Hickam AFB) https://www.dropbox.com/s/k4mq5gws34t1sfp/F-22A Liveries Set D.7z?dl=0 *NEW* - Additional F22 liveries by @Texac F-22A Raptor Weathered Textures (digitalcombatsimulator.com) F-22A Raptor 422nd Test and Evaluation Squadron "Mirror/Chrome" (digitalcombatsimulator.com) F-22A Raptor 31st Test and Evaluation Squadron Edwards "Clean" (digitalcombatsimulator.com) INSTALLATION INSTRUCTIONS: To install the F-22A Raptor Enhancement Mod you will need three files and with several optional files for liveries and RWR updates. REQUIRED: DCS Aircraft Avionics from: https://www.dropbox.com/scl/fi/mswde779igbwj04ktrjah/DCS-Aircraft-Avionics.zip?rlkey=dqjub4qer7y4s3kbwhc7mn1iy&dl=0 F-22A Github EFM v2.1.0 f-22a.zip from: Releases · grinnellidesigns/f-22a F-22A Raptor Enhancement Mod from: https://www.dropbox.com/scl/fi/wv1jjbz9998m9rngmp6iw/F-22A-Raptor-Enhancement-Mod.zip?rlkey=h6ut6o9kaeoxctbq8iwuavy6o&dl=0 OPTIONAL: F-22A Liveries Set A from: https://www.dropbox.com/scl/fi/6wjy997bfcssikyid5xly/F-22A-Liveries-Set-A.7z?rlkey=7g24x378ru6qyka6daiougrmh&dl=0 F-22A Liveries Set B from: https://www.dropbox.com/scl/fi/n4a1ijlb2bg3jy54zi4ci/F-22A-Liveries-Set-B.7z?rlkey=og2z4xup1xxpvn9cbbqla58to&dl=0 F-22A Liveries Set C from: https://www.dropbox.com/scl/fi/3yf45wdiib9yb1tnx4ow4/F-22A-Liveries-Set-C.7z?rlkey=aicwt4xq9wktu0f2avb8mml8t&dl=0 F-22A Liveries Set D from: https://www.dropbox.com/scl/fi/n7gmfbbvr7pglyxzq1h37/F-22A-Liveries-Set-D.7z?rlkey=ef1hivxs8lewtk532kfe1syci&dl=0 DCS RWR Symbology from: https://www.dropbox.com/scl/fi/3wtdmx7v04yhcj96qbh4g/DCS-RWR-Symbology.zip?rlkey=7jgwti2c1erspf8iq7xwxs156&dl=0 AIM-120D-3, AIM-120C-8 AMRAAM Combined v1.2 from https://www.digitalcombatsimulator.com/en/files/3343056/ 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.1.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.1.0 F-22A folder, copy the BIN and FM folders and paste them into the F-22A folder under your .\Saved Games\DCS\Mods\aircraft\F-22A The mod is now installed. 5. Optional: From that SHAPES folder you can delete any file that DOES NOT START WITH F-22A OR R-73U. These files are not needed. The F-22A files are the model for the Raptor, you DO need those. 6. Optional: Download the DCS RWR Symbology mod and extract it into your DCS MAIN Game folder, not your DCS SAVED GAMES folder. These files will add many custom aircraft (like the F22), and missiles to the RWR display. Without this, unknown aircraft show up as <U>. 7. Optional: Download the Liveries sets and extract them to whatever location you wish to keep your livery files. Example: .\Mods\aircraft\F-22A\Liveries\F-22A under your DCS SAVED GAMES folder. 8. Optional: Install the AIM-120D-3, AIM-120C-8 AMRAAM Combined v1.2 mod to your DCS MAIN Game folder, not your DCS SAVED GAMES folder. This will replace the AIM-120B with a 120D and improve the 120C's performance. The F22 isn't supposed to use the 120B but it's in the loadout options. DCS RWR Symbology.zip DCS Aircraft Avionics.zip

Very nice.

Hey all, Looking through the keyboard and joystick LUA files I don't see any command to arm or disarm the Vipers seat. I've got my simpit set up to where I don't have to use a mouse for anything.....except to arm and disarm the seat. Why? The Hornet has bound commands for this. Why doesn't the viper? Does anyone know how to code that? Thanks!

I'm using two installs. The current open beta as one, and a second install of the current stable. The current stable version is 2.5.6.49798 and it supports the F22 and other mods that were dependent on Flaming Cliffs 3 dll files. You can download and install it as the stand alone version and then simply not update it after that. That would be an option if the Open Beta updater won't install the old version for some reason. You could also try to revert Open Beta: "X:\DCS World OpenBeta\bin\DCS_updater.exe" update 2.5.6.49798@openbeta If that doesn't work for you, then Stable should.

I'm a nobody when it comes to reviews etc and I don't have time for an in depth review. However, I've had my set since mid-December and I love them. Granted I primarily use the throttle b/c I have a Realsimulator Lighting base, but I have used the stick too and I have it mounted so that I can swap it in and out. The set is in a work awesome. I have had zero issues. In my opinion this is the best throttle I've every owned. The panel is great, I use it for everything. Now that they sell them separately, you could always buy the Throttle only if that's your desire. I think its safe to say you wouldn't regret it.

I imagine that it's highly unlikely an extractor for the EDC files will be created, and even if one were, it's purpose would be to decrypt what ED intentionally encrypted. As such, it wouldn't be sanctioned or condoned by ED. In order to gain access to the unencrypted versions of the sounds and sdef files for aircraft including the F5 I would suggest installing a copy of the 2.5.5 OB which would require a roll back or separate install. The last version I know of that was not encrypted was 2.5.5.41962. I kept a copy of that install prior to moving to 2.5.6 but I doubt ED would appreciate me uploading any files from it. You should be able to tell the "Revert DCS World OpenBeta" to go to that version. "X:\DCS World OpenBeta\bin\DCS_updater.exe" update 2.5.5.41962@openbeta Good luck.

Typically, you don't have to remove mods from your saved games folder, as anything there will override what's in the main folder. Now that doesn't guarantee that they'll work or won't cause additional problems with a new release. So as with anything, test. Skins/Liveries in the main folder, I always remove mine and everything for that matter from the main before an update, so I don't know. I use OvGME for that. Worst case, after the update they'll get moved to a new location in your install folder and you could move them back I guess. Reverting should take less time than doing a full install, but another option to consider is having two installs. This is what I've done. I installed the stable release which is the build 2.5.6.49798 and I installed Open Beta. You don't have update the Stable and can leave it where it is and run anything that used FC3 DLL files just as before. Of course it will never have any new content past that point. But, that's what the second install of OB would be for. Keep the stable copy for the old stuff and OB for the new stuff. If space is an issue, then you'll have to make a choice until it isn't.

Hmm ok. Thank you for the feedback. I'll update the one in User Files. I'm glad it's working. *Updated Mod* and i used your screen shot of what it looks like.

Sure no problem: I've attached just the current materials.lua file last updated 3/7/20 and the current version of the mod I'm using. materials.lua F-16C Display Readability.zip

I've not been able to reproduce the problem. I see black on green for the highlighted/active MFD button. As you can see in the LUA code you posted the changes are not significant. I have the original values in the materials.lua file commented for the white. If you want to put that back to normal for testing just replace those values in that file. It's difficult for me to trouble shoot an issue that I don't see. I have no idea why it's happening to some people.

I started a new thread about the FC3 avionics here: https://forums.eagle.ru/showthread.php?t=277907 Doesn't hurt to ask.

Hello, It would appear that with the recent open beta releases after 2.5.6.49798 the Flaming Cliffs 3 avaionics that are used by many 3rd party mods are no longer accessible for some reason. If you attempt to fly an aircraft that was using say the F15C.dll avionics you will not be able to enter the sim properly or at best you won't have the correct avionics. I would imagine that this impacts all FC3 type avionics. We don't know if this was intentional or if this was accidental but it does render a lot of work done by the modding community useless for anything other than AI aircraft. A lot of people enjoy using these mods and now our only option is to revert back to the 2.5.6.49798 release of OB or Stable. We would greatly appreciate having this functionality restored. Thank you,

"X:\DCS World OpenBeta\bin\DCS_updater.exe" update 2.5.6.49798@openbeta This is the same version that was pushed to Stable and is the exact same code. So your choices are install Stable or use the DCS_updater.exe to "update" back to that version indicated. You can run that from the command line or a shortcut.

How did you get it work? I still haven't found a way to get it work at all, even with Su-25.

If someone has a working example they could post? That might help the rest of us. Thanks!

I commented out what looked to be everything related to the FM code but it didn't change the outcome. Still just goes to the ME screen instead of into the sim. Attached current entry.lua. entry.lua

I've tried to follow what you said here but it doesn't appear to be working for me. I commented out the sections about binaries and replaced the make_flyable line as you indicated. I still don't get the cockpit of the aircraft and the sim doesn't load. Just the mission editor screen. I've attached the entry.lua file I edited. entry.lua

It seems that with every recent update, we get to go find out what doesn't work any more. I'm finding these recent events to be very frustrating. They said they do support mods but every time we update DCS now, mods are getting disabled or quit working. Mods that have worked for a very long time. Heck, these mods are even IN the saved games path that we're supposed to use and now they don't work either. So does every non official flyable mod no longer work?

When/if you do install the OB it will likely install that latest version, which currently is 2.5.6.50321. That version introduced the P47 and the Channel map but also multiple issues on the Viper. If you want to run the same version as Stable for now, you'll need to change the shortcut for "Revert DCS World OpenBeta to this: "X:\DCS World OpenBeta\bin\DCS_updater.exe" update 2.5.6.49798@openbeta X of course being whatever drive/location you have DCS installed to. Good luck.

Well the stable version is 2.5.6.49798 and that's the same version of the Open Beta that I'm using. I decided not to use the last OB due to the problems introduced on the Viper. I can tell you that mods are indeed working with 2.5.6.49798 Open Beta. The stable was released on 5/28. The patch was released on 5/26 that reenabled modding of lua files in the coremods folder. Maybe that hotfix didn't make it to the stable code branch despite the same version number? I can't say, I don't run stable as I found there was little point. You don't have to update to every OB that comes out if you don't want to, and if Stable and Open Beta have the same version numbers and are released within a week of each other, is there really much of a difference? In this case, my advice would be to switch to Open Beta 2.5.6.49798. It works. Beyond that, hopefully the devs will see this post and consider fixing it for the next stable release, whenever that may be.

This issue only affected the CoreMods folder of the main install. However, I'm using the Logbooks mod for US Navy and that works just fine. I'm also using extended callsigns and that works just fine. At least on the OB.

There was a hotfix on 5/26 to OB that allowed it to work again. As far as I know, that code should be in the stable 2.5.6 as well as the OB and modding should work normally.

The OB version released on 5/20 is the version that locked down the lua files in Coremods. The OB hotfix on 5/26 relaxed the restriction and allowed modified lua files again. Yes the dcs_manifest.x86_64 still appears in root folder.

There was a hotfix on Tuesday of this week that restored the ability to mod files in the CoreMods folder of the main installation.

Yes thank you very much for the fix!