mrjay

Nope, stock version is not better. By "this version" i meant whole mod since Grinelli v3 release. Sorry for the confusion.

I flew a few hours today in f-22a(Grinelli + Nightstorm mod) In my opinion, the f-22a in this version is more sluggish, accelerates slower. It is hard to win a 1v1 mission. Like it has not enough power. Do you guys feel this way too? Or is it just me?

@SSP1 Try this ^ and in the last step you should copy contents of the folder "F-22A Single Player" without that folder. So folders you should copy are: "MissionEditor", "Mods", "Sounds" to "Saved Games/DCS.openbeta". Also note that "DCS.openbeta" might be in your case "DCS" folder. It depends how old your DCS installation is.

That's a shame. Well I guess I can copy the message here (hope Grinnelli doesn't mind): That's all i found in the discord logs. There isn't much of it.

@Nightstorm try https://discord.gg/FrK2NAB5wS and channel community mods // #f-22. Conversation starts at 27.01.2025, 23:46.

Hi @Nightstorm Good to hear that you are back on modding F-22A. I just wanted to add that Grinelli on discord wrote that GD are preparing OPEN SOURCE release of the F-22A mod. This is another good news. Link to discord https://discord.com/channels/778817642860904468/1010337321620623410/1333568732278296708 Cheers!

Could you post your dcs.log when it happens?

Ok ... I've deleted dcs saved games folder. I did a fresh install of the Grinelli F-22A mod without the Nightstorm overlay. I did a repair of the dcs. And the throttle only opens to 96%. What else should i do to get this thing working as it should?

Thanks i will do fresh installation and check what I have done wrong the first time.

A lot of things doesn't work in mod v3.0. Does gear up/down, air brake and flaps works for you guys?

Thanks Grinelli! We appreciate you finding time for the F-22A despite having a bigger project on your plate. The revised flight model explains the incompatibility with the previous F-22A code base. I hope the fix does not prove difficult and does not take up much of your time. Regards.

I'm observing that too. Maybe @Grinnelli could look on that issues? Seems like they changed min and max values for throttle, pitch and maybe others too.

@Grinnelli The issues with landing gear, flaps speedbrake are gone now for me with @SkateZilla fix. They were only observable with a workaround to load f-15c before f-22a. I see the issue with landing gear handle going up and down few times before gears comes down. @SkateZilla what tools did you use to debug that? This simple fix looks like a lot of work. I'm asking because I want to learn new things ;-).

@Thunder Chicken22 For me it was enough to comment out or delete: and add inplace:

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.

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

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.

Ok. I've updated to FC 2024 and got it working with a workaround: 1. Start DCS. 2. Start F-15C mission. 3. Exit F-15C mission. 4. Start F-22A mission and it should work. There is a word on Mods discord that ED is currently working on a fix. Use the above steps, until fix will be released.

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.

Downloads are on the first page and first post of this thread. You need to buy Flaming Cliffs module

On the first page and first post. You need to download grinelli mod than Nightstorm variant.

Start with empty "Saved Games/DCS.openbeta" folder. Create "Saved Games/DCS.openbeta/Mods/aircraft/" directory structure. Then you need to install f-22 grinelli mod to "Saved Games/DCS.openbeta/Mods/aircraft/" folder. Then you need to extract Nightstorm mod to "Saved Games/DCS.openbeta/" and replace existing files. Cheers!

Did you first install grinelli f-22 mod?

Well, maybe something else interfere in saved games folder ... so you could also try "fresh" install of mods(after ranaming DCS folder in saved games directory). Sorry for not being more specific, but i had some issue with a game after an update few months ago(around october or november). I'm not sure now what helped, but I remember "repairing" installation and cleaning saved games dcs folder.

I'm not seeing radar issue. Maybe delete fxo and metashaders folders from DCS.openbeta directory after update? And Happy New Year to DCS community!!!