F-22A Raptor mod enhancement mod

[BlueAngels]

I know it's been said already, but for anyone who missed it..

The current workaround to make the mod work, is to get in the FC version of the F-15 first, then back out. Doing that seems to "load" the need file to your session and the F-22 mod should work for that instance of DCS.

If you close the game, you need to repeat the steps to "unlock" the F-22 mod again.

[TKhaos]

19 minutes ago, BlueAngels said:

I know it's been said already, but for anyone who missed it..

The current workaround to make the mod work, is to get in the FC version of the F-15 first, then back out. Doing that seems to "load" the need file to your session and the F-22 mod should work for that instance of DCS.

If you close the game, you need to repeat the steps to "unlock" the F-22 mod again.

This is a post I previous did.

Quote

It's been addressed in numerous posts by myself and others that the workaround is flawed and while it gives you access to fly the aircraft there are some major problems.

The landing gear and flaps do not work off HOTAS or keyboard, so you are stuck with the flaps and landing gear jammed down. A majority of the time the trigger doesn't work, sometimes the launch weapon doesn't work and people are now reporting that some of the instruments fail to work.

That is using both the the workaround method and the hot fix by cdpkobra that changes the F-15C cockpit to the SU-25 cockpit. The authors of the mods have confirmed they are not working and will be waiting for the next patch before deciding how to proceed.

One new thing I have had testing both workarounds is I will be flying along in a straight line and it suddently banks left, goes into a steep circular dive and just crashes into the ground, all control of the aircraft is lost. 

As far as I'm aware there have been no further attempts to fix VSN aircraft and several other non VSN. The only one that was affected that I know is now working is the Su-57 Felon by CubanAce as they have a standalone version which doesn't rely on any DCS files. I use the Grinnelli Designs F-22A Raptor and that does exactly the same as the VSN one.

All the other standalones that don't rely on DCS files like the A-4E-C Skyhawk, UH-60L Blackhawk, Hercule by Anubis, OH-6A Littlebird all work fine.  

Edited July 29, 2024 by TKhaos

[F-35 Guy]

On 7/14/2024 at 3:06 AM, mrjay said:

Thanks for information ... I guess i won't be buying FC2024 anytime soon.

Maybe @GrinnelliDesigns or @Nightstorm will find a root cause and update F-22 Mod.

I’ve talked with Grinnelli and the guy he worked with, an update for the F-22 is neither expected or in the works

[plott1964]

So I guess the F-22 and F-15EX are dead?

[TKhaos]

17 hours ago, plott1964 said:

So I guess the F-22 and F-15EX are dead?

Sort of, hoping for a fix but think most are waiting for the next patch as there's no point in fixing something until they know what direction ED are taking. You can still use the workaround and stay in cockpit view, but it handles like a bag of spanners with flaps fully down, gear down and half the time no active guns

I hope they do fix it as the F-15EX is one of my favourite third party mods. If I had more time I would look at it myself but too busy with work at the moment, plus haven't done anything design wise with DCS so would need to find everything, only thing I have done is a multi monitor lua so I can use my second monitor for targeting displays.

[TKhaos]

17 hours ago, F-35 Guy said:

I’ve talked with Grinnelli and the guy he worked with, an update for the F-22 is neither expected or in the works

Technically it's not really solely FC 2024 fault, all the folder structures have changed and ED have apparently made changes to some of the files that third party mods relied on. Some people are running the previous version so they still got the mods working, after the last patch things changed so regardless of FC 2024 it's still affecting people. DCS Stand-alone through ED is good people can still choose not to upgrade to the latest patch, not so easy with Steam unless you have auto update disabled from day one.

If people are upgrading from FC3 to FC 2024 it's worth doing now as the sale ends either today or tomorrow.

If Grinnelli and the other guy aren't planning on updating anything it's a shame, hopefully someone else will come forward and create a fix for the F-22 and F-15EX.

If nothing else ED have alienated and annoyed a large number of there customers, especially by trashing 90% of third party mods and then the Razbam issues. 

Edited July 30, 2024 by TKhaos

[RaptorFighter]

1 hour ago, TKhaos said:

Technically it's not really solely FC 2024 fault, all the folder structures have changed and ED have apparently made changes to some of the files that third party mods relied on. Some people are running the previous version so they still got the mods working, after the last patch things changed so regardless of FC 2024 it's still affecting people. DCS Stand-alone through ED is good people can still choose not to upgrade to the latest patch, not so easy with Steam unless you have auto update disabled from day one.

If people are upgrading from FC3 to FC 2024 it's worth doing now as the sale ends either today or tomorrow.

If Grinnelli and the other guy aren't planning on updating anything it's a shame, hopefully someone else will come forward and create a fix for the F-22 and F-15EX.

If nothing else ED have alienated and annoyed a large number of there customers, especially by trashing 90% of third party mods and then the Razbam issues. 

 

I agree with you. I'm not surprised at all, but in this case, an extreme degree of disrespect was demonstrated to the community using mods and to the modders themselves.

[plott1964]

"If nothing else ED have alienated and annoyed a large number of there customers, especially by trashing 90% of third party mods and then the Razbam issues." Amen Brother!

[SkateZilla]

2 hours ago, plott1964 said:

"If nothing else ED have alienated and annoyed a large number of there customers, especially by trashing 90% of third party mods and then the Razbam issues." Amen Brother!

Well, ED have the right to protect their IP,

However, The mods that relied on a back door to other aircraft's avionics and flight models.

Removing FC3 and the FC3 DLL as well as the "old" reporting and the FC3 Systems loading is what killed mods, it was not intentional, but the community cant expect ED to keep FC3 in the sim just because mods relied on their DLLs.

Removing dependency on FC3 avionics is only way forward for the mods.

Edited July 30, 2024 by SkateZilla

[plott1964]

The dependency is what made them easy and fun to fly. IMHO, ED should most definitely protect their IP while at the same time consider the thousands of users in the community helping to pay their bills. I would say there is only a very, very small number of people who download DCS for free and then fly only free "unofficial" mods. There are plenty of ways to protect your IP while allowing a few talented modders to continue developing and increasing the value of DCS. Microsoft as well as others do it all the time. It's actually beneficial to the company as a whole to do so.

Edited July 30, 2024 by plott1964

[SkateZilla]

It's also less likely to do w/ FC3/FC24 and more likely to do with Program Cleanup and assets not being loaded until needed,
So for example, FM.Old = 6 is not loaded until player loads the F-15C for that session, after which the avionics are loaded and available for mods that call OLD = 6

This behavior is confirmed also by looking at the logs, where the F-15C Fails to load

ie: for DCS 2.9.6
Loading into F-15C:  *(Can clearly see the binaries being loaded at spawn time).

2024-07-30 15:52:56.620 INFO    APP (Main): MissionSpawn:spawnLocalPlayer 5,F-15C
2024-07-30 15:52:58.004 INFO    EDCORE (Main): Loaded E:/Eagle Dynamics/DCS World Open Beta/Mods/aircraft/F-15C/bin/F15CCWS.dll
2024-07-30 15:53:00.058 INFO    EDCORE (Main): Loaded E:/Eagle Dynamics/DCS World Open Beta/Mods/aircraft/F-15C/bin/F15.dll
2024-07-30 15:53:00.245 WARNING WORLD (Main): ModelTimeQuantizer: ANTIFREEZE ENABLED
2024-07-30 15:53:00.248 INFO    VISUALIZER (9816): ILV loaded  for /models/Cockpit_F-15C.edm.ilv
2024-07-30 15:53:00.249 INFO    ENLIGHT (9816): get cockpit shading params from /models/Cockpit_F-15C.edm.lua

Loading into the F-22A Directly:  *No Binaries are loaded from the SG Folder*, So cockpit and FM are not loaded at all.
 

2024-07-30 15:56:51.320 INFO    APP (Main): MissionSpawn:spawnLocalPlayer 5,F-22A
2024-07-30 15:56:51.335 ERROR   APP (Main): Error: Unit [F-22A]: Corrupt damage model.

But if you load F-15C First, then Load into the F-22A Slot, the systems are loaded:
 

2024-07-30 16:08:41.527 INFO    APP (Main): MissionSpawn:spawnLocalPlayer 4,F-22A
2024-07-30 16:08:41.551 ERROR   APP (Main): Error: Unit [F-22A]: Corrupt damage model.
2024-07-30 16:08:41.555 WARNING EDCORE (Main): Source bazar/textures/avionicscommon is already mounted to the same mount /textures/.
2024-07-30 16:08:41.572 ERROR   VISUALIZER (Main): ILV for cockpit 'Cockpit_F-22A' not found

so F-15C's Old Value is not Defined until it's loaded.

Also without FC3, the F15Cs avionics are now in the F-15C CWS DLL, instead of the FC3.dll.

I literally confirmed, via adding F-15C as client, loaded it, then F-22A,

Exited mission, back to main menu, new mission, drop in F-22A as only client, and it will continue to load until you exit DCS.

 

In Previous DCS World, all the FC3 DLLs were loaded when F-22 is Spawned:
 

2024-07-30 16:20:53.049 ERROR   APP (Main): Error: Unit [F-22A]: Corrupt damage model.
2024-07-30 16:20:53.115 WARNING EDCORE (Main): Source bazar/textures/avionicscommon is already mounted to the same mount /textures/.
2024-07-30 16:20:53.117 ERROR   VISUALIZER (Main): ILV for cockpit 'Cockpit_F-22A' not found
2024-07-30 16:20:54.713 INFO    EDCORE (Main): Loaded E:/Eagle Dynamics/DCS World/Mods/aircraft/Flaming Cliffs/bin/FC3.dll
2024-07-30 16:20:56.703 INFO    EDCORE (Main): Loaded E:/Eagle Dynamics/DCS World/Mods/aircraft/Flaming Cliffs/bin/A10A.dll
2024-07-30 16:20:58.205 INFO    EDCORE (Main): Loaded E:/Eagle Dynamics/DCS World/Mods/aircraft/Flaming Cliffs/bin/F15.dll
2024-07-30 16:20:59.736 INFO    EDCORE (Main): Loaded E:/Eagle Dynamics/DCS World/Mods/aircraft/Flaming Cliffs/bin/Su27.dll
2024-07-30 16:21:01.309 INFO    EDCORE (Main): Loaded E:/Eagle Dynamics/DCS World/Mods/aircraft/Flaming Cliffs/bin/Su33.dll
2024-07-30 16:21:02.833 INFO    EDCORE (Main): Loaded E:/Eagle Dynamics/DCS World/Mods/aircraft/Flaming Cliffs/bin/MiG29.dll

 

Edited July 30, 2024 by SkateZilla

[MAXsenna]

On 7/29/2024 at 5:24 PM, TKhaos said:

All the other standalones that don't rely on DCS files like the A-4E-C Skyhawk, UH-60L Blackhawk, Hercule by Anubis, OH-6A Littlebird all work fine.  

Of course. Own developed flight model. I guess Cuban Ace finally did it himself, like he said he would.

23 hours ago, F-35 Guy said:

I’ve talked with Grinnelli and the guy he worked with, an update for the F-22 is neither expected or in the works

I guess the F-100 is more important. Good on them. Aren't you making an F-35? Why not ask OP if he can fix it. 

 

5 hours ago, TKhaos said:

Technically it's not really solely FC 2024 fault, all the folder structures have changed and ED have apparently made changes to some of the files that third party mods relied on. 

This was wished for numerous times by FC3 owners that wanted all the different modules to be displayed independently from FC3 in quickstart, training etc. Only fix was to purchase the modules separately, which I did, install and disable FC3. Money well spent. 

 

5 hours ago, TKhaos said:

If nothing else ED have alienated and annoyed a large number of there customers, especially by trashing 90% of third party mods and then the Razbam issues. 

Now, I do feel for you guys. While this is a little rich.  

 

1 hour ago, plott1964 said:

There are plenty of ways to protect your IP while allowing a few talented modders to continue developing and increasing the value of DCS.

Now, why didn't they make it check for both FC3 and the Standalone F-15C. Maybe not possible of course.  

[plott1964]

Thanks for the details @SkateZilla. So with all that being said, is there a possible solution? Even with the loading the F-15C first, we still have the avionic issues (i.e. landing gear, flaps, etc.). Plus we are still seeing the "Corrupt damage model" error. Not really sure what that means.

[mrjay]

Problems with keybindings (gear, airbrake and others) occur because they changed iCommand* ("strings bin-mt/Input.dll | grep iCommand ") definitions in previous patch.

In F-22 these values were hardcoded (without iCommand* definitions). For example plane gear was the value of 68.

As if that weren't enough, files where comunication between keyboard/joystick and mod happens are compiled to lua bytecode(encrypted). These files are in "Mods/aircraft/F-22A/Cockpit/Scripts/Systems/" folder (Avionics.lua, Electrical_System.lua, Engine_System.lua, ICP_System.lua, MFD_System.lua, PMFD_System.lua, Weapon_System.lua).

 

So to fix the mod we need:

1. Source of Avionics.lua, Electrical_System.lua, Engine_System.lua, ICP_System.lua, MFD_System.lua, PMFD_System.lua, Weapon_System.lua which only @GrinnelliDesigns can provide. But i woudn't count on that.

2. Find new values for iCommand* definitions. I think it would be easy with script, but time consuming

3. Replace iCommand definitions in these files.

 

Alternatively we could write these files from scratch. It would take much more time.

Edited July 30, 2024 by mrjay

[plott1964]

What about using a previous version of the Input.dll saved in the mod's own directory structure and called from there? Could cause conflicts I would guess.

[mrjay]

26 minutes ago, plott1964 said:

What about using a previous version of the Input.dll saved in the mod's own directory structure and called from there? Could cause conflicts I would guess.

I don't think it is possible. Only loadable executables are dlls with flight model and avionics. Sorry ...

[SkateZilla]

OK Guys I believe I got it,
I looked into some stack chains and memory dumps :

for the F-22A, try this, I cannot fix the systems and controls missing, that's up to the person that compiled the LUA.:
But I was able to load into the cockpit, Set the axes and switches, control the aircraft switch modes, fire the cannon, IR and RDR Missiles, etc, use the MFDs, toggle FCS Modes, deploy the gear and land without issue.

Backup your F-22's Entry.lua, 
and Select all and paste the code below.
 

--[[ DEFINE MODULE ID	   ]] self_ID = "F-22A by GrinnelliDesigns"
--[[ DEFINE MODULE START   ]] declare_plugin(self_ID, {
--[[ DEFINE MODULE IMAGE   ]] image     	 = "FC3.bmp",
--[[ DEFINE INSTALL STATUS ]] installed 	 = true, -- if false that will be place holder , or advertising
--[[ DEFINE BASE DIRECTORY ]] dirName	  	 = current_mod_path,
--[[ DEFINE DEVELOPER NAME ]] developerName	 = _("GrinnelliDesigns"),
--[[ DEFINE DEVELOPER LINK ]] developerLink      = _("https://grinnellidesigns.com/"),
--[[ DEFINE MENU NAME	   ]] fileMenuName       = _("F-22A"),
--[[ DEFINE DISPLAY NAME   ]] displayName        = _("F-22A"),
--[[ DEFINE SHORT NAME	   ]] shortName   	 = _("F-22A"),
--[[ DEFINE VERSION 	   ]] version	 	 = "MK II",
--[[ DEFINE INSTALL STATE  ]] state		 = "installed",
--[[ DEFINE UPDATE ID 	   ]] update_id       	 = "F-22A",
--[[ DEFINE MODULE INFO    ]] info		 = _("F-22A Raptor Mod by GrinnelliDesigns"),
--[[ DEFINE ENCYCLOPEDIA   ]] encyclopedia_path  = current_mod_path..'/Encyclopedia',
--[[ DEFINE MODULE RULES   ]] rules 		 = { ["F-15C"] = {required = true},},
--[[ DEFINE BINARIES	   ]] --binaries 	    = --{'F22_EFM'},
--[[ DEFINE THEME FOLDER   ]] Skins		 = {{name = _("F-22A"),dir	= "Theme"},},
--[[ DEFINE MISSIONS FOLDER]] Missions 		 =	{{name = _("F-22A"),dir = "Missions",},},
--[[ DEFINE LOGBOOK 	   ]] LogBook 		 = {{name = _("F-22A"),type= "F-22A",},},			
--[[ DEFINE INPUT PROFILES ]] InputProfiles      =	{["F-22A"] = current_mod_path .. '/Input/F-22A',},
--[[ DEFINE INFO CLOSE     ]] })
--[[ DEFINE MODEL PATH     ]] mount_vfs_model_path(current_mod_path.."/Shapes")
--[[ DEFINE MODEL PATH     ]] mount_vfs_model_path(current_mod_path.."/Cockpit/Shape") 
--[[ DEFINE LIVERIES PATH  ]] mount_vfs_liveries_path(current_mod_path.."/Liveries")
--[[ DEFINE TEXTURES PATH  ]] mount_vfs_texture_path(current_mod_path.."/Textures")
--[[ DEFINE TEXTURES PATH  ]] mount_vfs_texture_path(current_mod_path.."/Textures/F-22A.zip")
--[[ DEFINE TEXTURES PATH  ]] mount_vfs_texture_path(current_mod_path.."/Textures/F-22A_Cockpit.zip")
--[[ DEFINE TEXTURES PATH  ]] mount_vfs_texture_path(current_mod_path.."/Textures/Clipboards")
--[[ DEFINE TEXTURES PATH  ]] mount_vfs_texture_path(current_mod_path.."/Textures/Cockpit Photo")
--[[ DEFINE TEXTURES PATH  ]] --mount_vfs_sound_path(current_mod_path.."/Sounds") --caused an error

--[[ DEFINE EFM CFG PATH   ]] --local cfg_path = current_mod_path ..  "/FM/F22A/config.lua"
--[[ DEFINE EFM DO FILE    ]] --dofile(cfg_path)
--[[ DEFINE EFM SELF ID    ]] --F22A[1] = self_ID
--[[ DEFINE EDM BINARY 	   ]] --F22A[2] = 'F22_EFM'
--[[ DEFINE EFM CFG PATH   ]] --F22A.config_path = cfg_path
--[[ DEFINE EFM OLD VALUE  ]] --F22A.old = 6 -- SU27-3, SU33-4, F-15-6, SU25-54
 
--[[ DEFINE F15C EFM CFG   ]] --local cfg_path = DCS_ROOT_PATH ..  "/FM/F15/config.lua"
--[[ DEFINE F15C EFM DO    ]] --dofile(cfg_path)
--[[ DEFINE F15C EFM ID    ]] --F15FM[1] 				= self_ID
--[[ DEFINE F15C EFM BIN   ]] --F15FM[2] 				= 'F15'
--[[ DEFINE F15C EFM CFG   ]] --F15FM.config_path 		= cfg_path
--[[ DEFINE F15C EFM OLD   ]] --F15FM.old 				= true

-- ADD LINE BELOW FOR DCS 2.9.6
--[[ DEFINE F15C OLD INDEX ]] F15FM.old = 6

--[[ DEFINE WEAPONS DATA   ]] dofile(current_mod_path.."/Weapons.lua")
--[[ DEFINE VIEWS DATA     ]] dofile(current_mod_path.."/Views.lua")
--[[ DEFINE VIEWS SETTINGS ]] make_view_settings('F-22A', ViewSettings, SnapViews)

-- ADD NEW DEFINITION FOR DCS 2.9.6
--[[ DEFINE FLYABLE AC     ]] MAC_flyable('F-22A', current_mod_path..'/Cockpit/Scripts/', F15FM, current_mod_path..'/comm.lua')

-- OLD MAKE FLYABLE STRINGS
--make_flyable('F-22A',current_mod_path..'/Cockpit/Scripts/',F22A, current_mod_path..'/Comm.lua')--THIS IS THE EFM BULL<profanity>
--make_flyable('F-22A',current_mod_path..'/Cockpit/Scripts/',{nil, old = 6}, current_mod_path..'/Comm.lua')--F-15 = 6  ------this is the F-15 SFM VERSION
--make_flyable('F-22B',current_mod_path..'/Cockpit/Scripts/',{nil, old = 54}, current_mod_path..'/Comm.lua')--SU-25T
--make_flyable('F-22C',current_mod_path..'/Cockpit/Scripts/',{nil, old = 4}, current_mod_path..'/Comm.lua')--SU-33 = 4 SU-27 =3
--make_flyable('F-22A',current_mod_path..'/Cockpit/KneeboardRight/',{nil, old = 6}, current_mod_path..'/Comm.lua')

--[[ DEFINE AIRCRAFT DATA  ]] dofile(current_mod_path..'/F-22A.lua')
--[[ DEFINE AIRCRAFT DATA  ]] --dofile(current_mod_path..'/F-22B.lua')

--[[ DEFINE MODULE FINISH  ]]plugin_done()

 

Edited July 30, 2024 by SkateZilla

[TKhaos]

3 hours ago, MAXsenna said:

Now, I do feel for you guys. While this is a little rich.

I'm referring to aircraft, not every third party mod.

As for the Razbam thing I don't own any of there products at present. I was however just about to purchase the AV-8B @ £55 and the F-15E @ £51 but until it's clearer on updates or if it's a dead product I'm not spending out on stagnant products. It's like buying a bicycle and the front wheel is missing and the store telling you they may or may not supply one later

3 hours ago, MAXsenna said:

Now, why didn't they make it check for both FC3 and the Standalone F-15C. Maybe not possible of course.

It's a shame they can't do similar to other game developers and do something like create a legacy folder with the few files that are needed.

Edited July 30, 2024 by TKhaos

[mrjay]

1 hour ago, SkateZilla said:

OK Guys I believe I got it,
I looked into some stack chains and memory dumps :

for the F-22A, try this, I cannot fix the systems and controls missing, that's up to the person that compiled the LUA.:
But I was able to load into the cockpit, Set the axes and switches, control the aircraft switch modes, fire the cannon, IR and RDR Missiles, etc, use the MFDs, toggle FCS Modes, deploy the gear and land without issue.

Backup your F-22's Entry.lua, 
and Select all and paste the code below.
 

--[[ DEFINE MODULE ID	   ]] self_ID = "F-22A by GrinnelliDesigns"
--[[ DEFINE MODULE START   ]] declare_plugin(self_ID, {
--[[ DEFINE MODULE IMAGE   ]] image     	 = "FC3.bmp",
--[[ DEFINE INSTALL STATUS ]] installed 	 = true, -- if false that will be place holder , or advertising
--[[ DEFINE BASE DIRECTORY ]] dirName	  	 = current_mod_path,
--[[ DEFINE DEVELOPER NAME ]] developerName	 = _("GrinnelliDesigns"),
--[[ DEFINE DEVELOPER LINK ]] developerLink      = _("https://grinnellidesigns.com/"),
--[[ DEFINE MENU NAME	   ]] fileMenuName       = _("F-22A"),
--[[ DEFINE DISPLAY NAME   ]] displayName        = _("F-22A"),
--[[ DEFINE SHORT NAME	   ]] shortName   	 = _("F-22A"),
--[[ DEFINE VERSION 	   ]] version	 	 = "MK II",
--[[ DEFINE INSTALL STATE  ]] state		 = "installed",
--[[ DEFINE UPDATE ID 	   ]] update_id       	 = "F-22A",
--[[ DEFINE MODULE INFO    ]] info		 = _("F-22A Raptor Mod by GrinnelliDesigns"),
--[[ DEFINE ENCYCLOPEDIA   ]] encyclopedia_path  = current_mod_path..'/Encyclopedia',
--[[ DEFINE MODULE RULES   ]] rules 		 = { ["F-15C"] = {required = true},},
--[[ DEFINE BINARIES	   ]] --binaries 	    = --{'F22_EFM'},
--[[ DEFINE THEME FOLDER   ]] Skins		 = {{name = _("F-22A"),dir	= "Theme"},},
--[[ DEFINE MISSIONS FOLDER]] Missions 		 =	{{name = _("F-22A"),dir = "Missions",},},
--[[ DEFINE LOGBOOK 	   ]] LogBook 		 = {{name = _("F-22A"),type= "F-22A",},},			
--[[ DEFINE INPUT PROFILES ]] InputProfiles      =	{["F-22A"] = current_mod_path .. '/Input/F-22A',},
--[[ DEFINE INFO CLOSE     ]] })
--[[ DEFINE MODEL PATH     ]] mount_vfs_model_path(current_mod_path.."/Shapes")
--[[ DEFINE MODEL PATH     ]] mount_vfs_model_path(current_mod_path.."/Cockpit/Shape") 
--[[ DEFINE LIVERIES PATH  ]] mount_vfs_liveries_path(current_mod_path.."/Liveries")
--[[ DEFINE TEXTURES PATH  ]] mount_vfs_texture_path(current_mod_path.."/Textures")
--[[ DEFINE TEXTURES PATH  ]] mount_vfs_texture_path(current_mod_path.."/Textures/F-22A.zip")
--[[ DEFINE TEXTURES PATH  ]] mount_vfs_texture_path(current_mod_path.."/Textures/F-22A_Cockpit.zip")
--[[ DEFINE TEXTURES PATH  ]] mount_vfs_texture_path(current_mod_path.."/Textures/Clipboards")
--[[ DEFINE TEXTURES PATH  ]] mount_vfs_texture_path(current_mod_path.."/Textures/Cockpit Photo")
--[[ DEFINE TEXTURES PATH  ]] --mount_vfs_sound_path(current_mod_path.."/Sounds") --caused an error

--[[ DEFINE EFM CFG PATH   ]] --local cfg_path = current_mod_path ..  "/FM/F22A/config.lua"
--[[ DEFINE EFM DO FILE    ]] --dofile(cfg_path)
--[[ DEFINE EFM SELF ID    ]] --F22A[1] = self_ID
--[[ DEFINE EDM BINARY 	   ]] --F22A[2] = 'F22_EFM'
--[[ DEFINE EFM CFG PATH   ]] --F22A.config_path = cfg_path
--[[ DEFINE EFM OLD VALUE  ]] --F22A.old = 6 -- SU27-3, SU33-4, F-15-6, SU25-54
 
--[[ DEFINE F15C EFM CFG   ]] --local cfg_path = DCS_ROOT_PATH ..  "/FM/F15/config.lua"
--[[ DEFINE F15C EFM DO    ]] --dofile(cfg_path)
--[[ DEFINE F15C EFM ID    ]] --F15FM[1] 				= self_ID
--[[ DEFINE F15C EFM BIN   ]] --F15FM[2] 				= 'F15'
--[[ DEFINE F15C EFM CFG   ]] --F15FM.config_path 		= cfg_path
--[[ DEFINE F15C EFM OLD   ]] --F15FM.old 				= true

-- ADD LINE BELOW FOR DCS 2.9.6
--[[ DEFINE F15C OLD INDEX ]] F15FM.old = 6

--[[ DEFINE WEAPONS DATA   ]] dofile(current_mod_path.."/Weapons.lua")
--[[ DEFINE VIEWS DATA     ]] dofile(current_mod_path.."/Views.lua")
--[[ DEFINE VIEWS SETTINGS ]] make_view_settings('F-22A', ViewSettings, SnapViews)

-- ADD NEW DEFINITION FOR DCS 2.9.6
--[[ DEFINE FLYABLE AC     ]] MAC_flyable('F-22A', current_mod_path..'/Cockpit/Scripts/', F15FM, current_mod_path..'/comm.lua')

-- OLD MAKE FLYABLE STRINGS
--make_flyable('F-22A',current_mod_path..'/Cockpit/Scripts/',F22A, current_mod_path..'/Comm.lua')--THIS IS THE EFM BULL<profanity>
--make_flyable('F-22A',current_mod_path..'/Cockpit/Scripts/',{nil, old = 6}, current_mod_path..'/Comm.lua')--F-15 = 6  ------this is the F-15 SFM VERSION
--make_flyable('F-22B',current_mod_path..'/Cockpit/Scripts/',{nil, old = 54}, current_mod_path..'/Comm.lua')--SU-25T
--make_flyable('F-22C',current_mod_path..'/Cockpit/Scripts/',{nil, old = 4}, current_mod_path..'/Comm.lua')--SU-33 = 4 SU-27 =3
--make_flyable('F-22A',current_mod_path..'/Cockpit/KneeboardRight/',{nil, old = 6}, current_mod_path..'/Comm.lua')

--[[ DEFINE AIRCRAFT DATA  ]] dofile(current_mod_path..'/F-22A.lua')
--[[ DEFINE AIRCRAFT DATA  ]] --dofile(current_mod_path..'/F-22B.lua')

--[[ DEFINE MODULE FINISH  ]]plugin_done()

 

Ok. It's working. I can confirm that

adding:

 

F15FM.old = 6
make_flyable('F-22A',current_mod_path..'/Cockpit/Scripts/',F15FM, current_mod_path..'/Comm.lua')--F-15 = 6  ------this is the F-15 SFM VERSION

 

did it. Good Job!!! And gear also works.

Edited July 30, 2024 by mrjay

[Grinnelli]

I will look into this and report back soon. Nice work @SkateZilla!

[plott1964]

I can confirm we are almost there. Good job SkateZilla

[Grinnelli]

8 hours ago, SkateZilla said:

for the F-22A, try this, I cannot fix the systems and controls missing, that's up to the person that compiled the LUA.:
But I was able to load into the cockpit, Set the axes and switches, control the aircraft switch modes, fire the cannon, IR and RDR Missiles, etc, use the MFDs, toggle FCS Modes, deploy the gear and land without issue.

Do you happen to recall what systems and controls were not working for you?

[SkateZilla]

1 hour ago, Grinnelli said:

Do you happen to recall what systems and controls were not working for you?

I personally did not have any issues,

It was noted because a few other users were having issues:
https://forum.dcs.world/topic/252855-f-22a-raptor-mod-enhancement-mod/?do=findComment&comment=5493409

[PeeJott17]

Ohhh, a round of applause for @SkateZilla

Will try to confirm that works this evening

Edited July 31, 2024 by PeeJott17

[VR Flight Guy in PJ Pants]

The changes work! Thanks @SkateZilla. Video in works processing at the time of typing.

 

Edited July 31, 2024 by VR Flight Guy in PJ Pants