SkateZilla Posted August 1, 2024 Posted August 1, 2024 (edited) Seems like a bug in FM Linking, Pitch authority is decreased, and is next to nothing below 350 knots. Edited August 1, 2024 by SkateZilla Windows 10 Pro, Ryzen 2700X @ 4.6Ghz, 32GB DDR4-3200 GSkill (F4-3200C16D-16GTZR x2), ASRock X470 Taichi Ultimate, XFX RX6800XT Merc 310 (RX-68XTALFD9) 3x ASUS VS248HP + Oculus HMD, Thrustmaster Warthog HOTAS + MFDs
scommander2 Posted August 1, 2024 Posted August 1, 2024 36 minutes ago, VR Flight Guy in PJ Pants said: BTW, as a lazy noob, is there any combined fix available? Not that the @SkateZilla one was not good enough. Just wondering, is it a package (zip file) for all fixes and adjustments whatever? Thanks. Spoiler Dell XPS 9730, i9-13900H, DDR5 64GB, Discrete GPU: NVIDIA GeForce RTX 4080, 1+2TB M.2 SSD | Thrustmaster Warthog HOTAS + TPR | TKIR5/TrackClipPro | Total Controls Multi-Function Button Box | Win 11 Pro
plott1964 Posted August 1, 2024 Posted August 1, 2024 1 hour ago, SkateZilla said: anyone having issues with pitch authority? Yes! 39 minutes ago, scommander2 said: Just wondering, is it a package (zip file) for all fixes and adjustments whatever? Thanks. ...not yet. 1 PC specs: Intel Core i7-13700K [Raptor Lake 3.4GHz Sixteen-Core LGA 1700] (stock clock)/64.0 GB RAM/RTX 3080 GPU (stock clock)/Windows 10 Home/Multiple M.2 SSD Drives/T.Flight HOTAS X/HP Reverb G2
SkateZilla Posted August 3, 2024 Posted August 3, 2024 (edited) Ok guys, Myself and few other testers debugged this all morning, so here goes: First, you can only load one set of binaries per make flyable definition, there's no way around this, and the FC3 DLLs aren't pre/auto loaded anymore, but that's OK. To Force Load Binaries at Launch: Open the \Mods\Aircraft\<F-15C, A-10A>\ Entry.lua (whichever Avionics you want to use.) Scroll all the way to the binaries block, And add: load_immediately = true, Below it, ie: binaries = { 'F15CCWS', 'F15' }, load_immediately = true, This will force the binaries to load at launch, and give you access without having to jump pits. But will fail IC. Backup the Entry.lua Entry.Lua, Paste the code *Just use it all, because there's several values that need to be specific now* There's instructions for if you want to use the F22A.DLL EFM w/ F15C Systems As well, However the mod as delivered seemed to always use the F-15C w/ systems on top to modify it. --[[ 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 --[[ USE F22A EFM W/O SYSTEMS, OR LOAD F-15C FIRST THEN LOAD F-22A ]] --[[ DEFINE EFM CFG PATH ]] --local cfg_path = current_mod_path .. "/FM/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 PFM SRC OPTIONS]] --F22A.user_options = 'F_22A' --[[ USE F15C PFM W/ MODIFIED SYSTEMS]] --[[ DEFINE F15C EFM CFG ]] local cfg_path = current_mod_path .. "/FM/config.lua" --[[ DEFINE F15C EFM DO ]] dofile(cfg_path) --[[ DEFINE F15C EFM ID ]] F22FM[1] = 'F-15C' --[[ DEFINE F15C EFM BIN ]] F22FM[2] = 'F15' --[[ DEFINE F15C EFM CFG ]] F22FM.config_path = cfg_path --[[ DEFINE F15C EFM OLD ]] F22FM.old = 6 --[[ DEFINE PFM SRC OPTIONS]] F22FM.user_options = 'F_22A' --[[ 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 LOCAL ]] --make_flyable(OBJ NNAME, optional_cockpit path, optional_fm = {mod_of_fm_origin,dll_with_fm}, Path to Comm) --[[ DEFINE FLYABLE EXT. FM]] --make_flyable(OBJ NNAME, optional_cockpit path, FMNAME , Path to Comm) (FM MUST BE CONFIGURED IN CONFIG) --[[ DEFINE FLYABLE EXT FM ]] --make_flyable('F-22A', current_mod_path..'/Cockpit/Scripts/', {'F-15C', 'F15'}, current_mod_path..'/comm.lua') --[[ DEFINE FLYABLE F22 FM ]] --make_flyable('F-22A', current_mod_path..'/Cockpit/Scripts/', F22A , current_mod_path..'/comm.lua') --[[ DEFINE FLYABLE F15 FM ]] make_flyable('F-22A', current_mod_path..'/Cockpit/Scripts/', F22FM , 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() Now use this code, and past into \F-22A\FM\Config.lua *( For Use w/ F-15C PFM ) -- BEGIN -- this part of the file is not intended for an end-user editing --[[ --------------------------------------------------------------- ]]-- F22FM = { center_of_mass = {-0.172 , -0.6, 0},--x,y,z moment_of_inertia = {38912 ,254758,223845,-705},--Ix,Iy,Iz,Ixy suspension = { { -- NOSE WHEEL wheel_axle_offset = 0.07, damper_coeff = 120.0, self_attitude = true, --amortizer_min_length = 0.0, amortizer_max_length = 0.43, amortizer_basic_length = 0.43, amortizer_spring_force_factor = 990000.0, -- force = spring_force_factor * pow(reduce_length, amortizer_spring_force_factor_rate amortizer_spring_force_factor_rate = 2, amortizer_static_force = 47500.0, amortizer_reduce_length = 0.43, amortizer_direct_damper_force_factor = 50000, amortizer_back_damper_force_factor = 60000, anti_skid_installed = false, wheel_radius = 0.377, wheel_static_friction_factor = 0.75 , wheel_side_friction_factor = 0.85 , wheel_roll_friction_factor = 0.08 , wheel_glide_friction_factor = 0.65 , wheel_damage_force_factor = 450.0, arg_post = 0, arg_amortizer = 1, arg_wheel_rotation = 101, arg_wheel_damage = 134 }, { -- LEFT WHEEL --amortizer_min_length = 0.0, amortizer_max_length = 0.228, amortizer_basic_length = 0.228, amortizer_spring_force_factor = 29370398.0, -- force = spring_force_factor * pow(reduce_length, amortizer_spring_force_factor_rate amortizer_spring_force_factor_rate = 3, amortizer_static_force = 202394.0, amortizer_reduce_length = 0.221, amortizer_direct_damper_force_factor = 50000.0, amortizer_back_damper_force_factor = 25000.0, anti_skid_installed = true, wheel_radius = 0.486, wheel_static_friction_factor = 0.75 , wheel_side_friction_factor = 0.85 , wheel_roll_friction_factor = 0.08 , wheel_glide_friction_factor = 0.65 , wheel_damage_force_factor = 450.0, wheel_brake_moment_max = 15000.0, arg_post = 5, arg_amortizer = 6, arg_wheel_rotation = 102, arg_wheel_damage = 136 }, { -- RIGHT WHEEL --amortizer_min_length = 0.0, amortizer_max_length = 0.228, amortizer_basic_length = 0.228, amortizer_spring_force_factor = 29370398.0, -- 10000 -- force = spring_force_factor * pow(reduce_length, amortizer_spring_force_factor_rate amortizer_spring_force_factor_rate = 3, amortizer_static_force = 202394.0, amortizer_reduce_length = 0.221, amortizer_direct_damper_force_factor = 50000.0, amortizer_back_damper_force_factor = 25000.0, anti_skid_installed = true, wheel_radius = 0.486, wheel_static_friction_factor = 0.75 , wheel_side_friction_factor = 0.85 , wheel_roll_friction_factor = 0.08 , wheel_glide_friction_factor = 0.65 , wheel_damage_force_factor = 450.0, wheel_brake_moment_max = 15000.0, arg_post = 3, arg_amortizer = 4, arg_wheel_rotation = 103, arg_wheel_damage = 135 } }, -- gears disable_built_in_oxygen_system = true, --[[ ------------------------------------------------------------- ]]-- -- END -- this part of the file is not intended for an end-user editing -- view shake amplitude minor_shake_ampl = 0.21, major_shake_ampl = 0.5, -- debug debugLine = "{M}:%1.3f {KCAS}:%4.1f {KEAS}:%4.1f {KTAS}:%4.1f {IAS}:%4.1f {AoA}:%2.1f {ny}:%2.1f {nx}:%1.2f {AoS}:%2.1f {mass}:%2.1f {Fy}:%2.1f {Fx}:%2.1f {wx}:%.1f {wy}:%.1f {wz}:%.1f {Vy}:%2.1f {dPsi}:%2.1f", } Edited August 4, 2024 by SkateZilla 5 2 Windows 10 Pro, Ryzen 2700X @ 4.6Ghz, 32GB DDR4-3200 GSkill (F4-3200C16D-16GTZR x2), ASRock X470 Taichi Ultimate, XFX RX6800XT Merc 310 (RX-68XTALFD9) 3x ASUS VS248HP + Oculus HMD, Thrustmaster Warthog HOTAS + MFDs
Spino Posted August 4, 2024 Posted August 4, 2024 8 hours ago, SkateZilla said: Ok guys, Myself and few other testers debugged this all morning, so here goes: First, you can only load one set of binaries per make flyable definition, there's no way around this, and the FC3 DLLs aren't pre/auto loaded anymore, but that's OK. To Force Load Binaries at Launch: Open the \Mods\Aircraft\<F-15C, A-10A>\ Entry.lua (whichever Avionics you want to use.) Scroll all the way to the binaries block, And add: load_immediately = true, Below it, ie: binaries = { 'F15CCWS', 'F15' }, load_immediately = true, This will force the binaries to load at launch, and give you access without having to jump pits. But will fail IC. I don't suppose it's possible to add the binaries block to the entry file of the mod itself and have this work? Nevermind, I checked and it doesn't work. Couldn't possibly be that easy. Thanks ED Website (DCS Content): https://sites.google.com/view/spinossimulationsite/home?authuser=0 Discord: discord.gg/V6W8gJSx83 YouTube: https://www.youtube.com/@SpinosSimulations?sub_confirmation=1 System Specs: Ryzen 7 5800X, RX 7800 XT, 32GB DDR4-3200 RAM DCS Wishlist: F-8E/J Crusader, UH-1Y/AH-1Z, F-14B(U), F-14D/ST-21 Super Tomcat
Gorn557 Posted August 4, 2024 Posted August 4, 2024 Hmm, when I drop the code above into entry.lua and config.lua I get the message "The following module is required to install: F-22A" and then it drops me in an A-10. Any ideas? I did have it working with the "normal" entry.lua and config.lua, albeit with the pitch authority issue. And I've added the load immediately = true to all the FC luas.
VR Flight Guy in PJ Pants Posted August 4, 2024 Posted August 4, 2024 (edited) 16 hours ago, SkateZilla said: \F-22A\FM\Config.lua should be F-22A/FM/F-22A/config.lua (?) and the 16 hours ago, SkateZilla said: F22FM = { and this line should be F22A (?) If I follow the changes, it did not work at all as I cannot jump into the aircraft. Update: change the config.lua and retain the entry.lua with F-22A, it works and the pitch seems more responsive as if it were normal. However, the trim was still a bit rough. Edited August 4, 2024 by VR Flight Guy in PJ Pants I Fly, Therefore I Am. One cannot go around not saying "Thank you" every time these days, can't you? YouTube: https://www.youtube.com/channel/UCc9BDi-STaqgWsjNiHbW0fA
daskjdhjah Posted August 4, 2024 Posted August 4, 2024 我刚刚尝试了最新的解决方法,它有一个很大的优势,可以在飞行 MOD 之前无需登录 F-15C/SU-27 等 DLC 模型一次即可强制驾驶舱授权,但它似乎没有解决起落架无法降低和减速板不可用的问题,我还需要做些什么吗? 17小时前,SkateZilla说: 好的伙计们, 我和其他几个测试人员整个上午都在调试这个,所以这里是这样的: 首先,每个 make flyable 定义只能加载一组二进制文件,没有办法解决这个问题,而且 FC3 DLL 不再是预/自动加载的,但没关系。 要在启动时强制加载二进制文件: 打开 \Mods\Aircraft\<F-15C, A-10A>\ Entry.lua(您想要使用的任何航空电子设备。 一直滚动到二进制文件块, 并添加: load_immediately = true, 在它下面,即: binaries = { 'F15CCWS', 'F15' }, load_immediately = true, 这将强制二进制文件在启动时加载,并让您无需跳过坑即可访问。 但会使IC失败。 备份 Entry.lua Entry.Lua,粘贴代码 *只需全部使用,因为现在需要具体几个值* 如果您想使用带有 F15C 系统的 F22A.DLL EFM 也有说明,但是,交付的模块似乎总是使用顶部的 F-15C 带系统来修改它。 --[[ 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 --[[ USE F22A EFM w/ F-15C FORCE LOADING, OR LOAD F-15C FIRST THEN LOAD F-22A ]] --[[ DEFINE EFM CFG PATH ]] --local cfg_path = current_mod_path .. "/FM/config.lua" --[[ DEFINE EFM DO FILE ]] --dofile(cfg_path) --[[ DEFINE EFM SELF ID ]] --F22A[1] = 'F-15C' --[[ DEFINE EDM BINARY ]] --F22A[2] = 'F15' --[[ 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 PFM SRC OPTIONS]] --F22A.user_options = 'F_22A' --[[ USE F15C PFM W/ MODIFIED SYSTEMS]] --[[ DEFINE F15C EFM CFG ]] local cfg_path = current_mod_path .. "/FM/config.lua" --[[ DEFINE F15C EFM DO ]] dofile(cfg_path) --[[ DEFINE F15C EFM ID ]] F22FM[1] = 'F-15C' --[[ DEFINE F15C EFM BIN ]] F22FM[2] = 'F15' --[[ DEFINE F15C EFM CFG ]] F22FM.config_path = cfg_path --[[ DEFINE F15C EFM OLD ]] F22FM.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 LOCAL ]] --make_flyable(OBJ NNAME, optional_cockpit path, optional_fm = {mod_of_fm_origin,dll_with_fm}, Path to Comm) --[[ DEFINE FLYABLE EXT. FM]] --make_flyable(OBJ NNAME, optional_cockpit path, FMNAME , Path to Comm) (FM MUST BE CONFIGURED IN CONFIG) --[[ DEFINE FLYABLE EXT. FM]] make_flyable('F-22A', current_mod_path..'/Cockpit/Scripts/', F22FM , 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() 现在使用此代码,并过去到 \F-22A\FM\Config.lua -- BEGIN -- this part of the file is not intended for an end-user editing --[[ --------------------------------------------------------------- ]]-- F22FM = { center_of_mass = {-0.172 , -0.6, 0},--x,y,z moment_of_inertia = {38912 ,254758,223845,-705},--Ix,Iy,Iz,Ixy suspension = { { -- NOSE WHEEL wheel_axle_offset = 0.07, damper_coeff = 120.0, self_attitude = true, --amortizer_min_length = 0.0, amortizer_max_length = 0.43, amortizer_basic_length = 0.43, amortizer_spring_force_factor = 990000.0, -- force = spring_force_factor * pow(reduce_length, amortizer_spring_force_factor_rate amortizer_spring_force_factor_rate = 2, amortizer_static_force = 47500.0, amortizer_reduce_length = 0.43, amortizer_direct_damper_force_factor = 50000, amortizer_back_damper_force_factor = 60000, anti_skid_installed = false, wheel_radius = 0.377, wheel_static_friction_factor = 0.75 , wheel_side_friction_factor = 0.85 , wheel_roll_friction_factor = 0.08 , wheel_glide_friction_factor = 0.65 , wheel_damage_force_factor = 450.0, arg_post = 0, arg_amortizer = 1, arg_wheel_rotation = 101, arg_wheel_damage = 134 }, { -- LEFT WHEEL --amortizer_min_length = 0.0, amortizer_max_length = 0.228, amortizer_basic_length = 0.228, amortizer_spring_force_factor = 29370398.0, -- force = spring_force_factor * pow(reduce_length, amortizer_spring_force_factor_rate amortizer_spring_force_factor_rate = 3, amortizer_static_force = 202394.0, amortizer_reduce_length = 0.221, amortizer_direct_damper_force_factor = 50000.0, amortizer_back_damper_force_factor = 25000.0, anti_skid_installed = true, wheel_radius = 0.486, wheel_static_friction_factor = 0.75 , wheel_side_friction_factor = 0.85 , wheel_roll_friction_factor = 0.08 , wheel_glide_friction_factor = 0.65 , wheel_damage_force_factor = 450.0, wheel_brake_moment_max = 15000.0, arg_post = 5, arg_amortizer = 6, arg_wheel_rotation = 102, arg_wheel_damage = 136 }, { -- RIGHT WHEEL --amortizer_min_length = 0.0, amortizer_max_length = 0.228, amortizer_basic_length = 0.228, amortizer_spring_force_factor = 29370398.0, -- 10000 -- force = spring_force_factor * pow(reduce_length, amortizer_spring_force_factor_rate amortizer_spring_force_factor_rate = 3, amortizer_static_force = 202394.0, amortizer_reduce_length = 0.221, amortizer_direct_damper_force_factor = 50000.0, amortizer_back_damper_force_factor = 25000.0, anti_skid_installed = true, wheel_radius = 0.486, wheel_static_friction_factor = 0.75 , wheel_side_friction_factor = 0.85 , wheel_roll_friction_factor = 0.08 , wheel_glide_friction_factor = 0.65 , wheel_damage_force_factor = 450.0, wheel_brake_moment_max = 15000.0, arg_post = 3, arg_amortizer = 4, arg_wheel_rotation = 103, arg_wheel_damage = 135 } }, -- gears disable_built_in_oxygen_system = true, --[[ ------------------------------------------------------------- ]]-- -- END -- this part of the file is not intended for an end-user editing -- view shake amplitude minor_shake_ampl = 0.21, major_shake_ampl = 0.5, -- debug debugLine = "{M}:%1.3f {KCAS}:%4.1f {KEAS}:%4.1f {KTAS}:%4.1f {IAS}:%4.1f {AoA}:%2.1f {ny}:%2.1f {nx}:%1.2f {AoS}:%2.1f {mass}:%2.1f {Fy}:%2.1f {Fx}:%2.1f {wx}:%.1f {wy}:%.1f {wz}:%.1f {Vy}:%2.1f {dPsi}:%2.1f", } 我刚刚尝试了最新的解决方法,它有一个很大的优势,可以在飞行 MOD 之前无需登录 F-15C/SU-27 等 DLC 模型一次即可强制驾驶舱授权,但它似乎没有解决起落架无法降低和减速板不可用的问题,我还需要做些什么吗?
SkateZilla Posted August 4, 2024 Posted August 4, 2024 (edited) 9 hours ago, Spino said: I don't suppose it's possible to add the binaries block to the entry file of the mod itself and have this work? Nevermind, I checked and it doesn't work. Couldn't possibly be that easy. Thanks ED Binaries will only load from their original location. 1 hour ago, VR Flight Guy in PJ Pants said: should be F-22A/FM/F-22A/config.lua (?) and the and this line should be F22A (?) If I follow the changes, it did not work at all as I cannot jump into the aircraft. Update: change the config.lua and retain the entry.lua with F-22A, it works and the pitch seems more responsive as if it were normal. However, the trim was still a bit rough. Are you using the F-22 EFM or the F-15 PFM? I had modified the config to work with the F-15 PFM which is why I had instructions to save in \FM\ and not \FM\F22A\, I also forgot to put the lines back for the EFM and Binaries. To load the F-22 Binaries you only have to remove the -- right before "binaries" and change the EFM from "F-15C"to "self_ID' and the 2nd line from "F15" to "F22_EFM", you should still have the default \FM\F22A\config.lua, it should point to that one, correct, I will update my post. I will get with Grinnelli team on a more perm. fix. Edited August 4, 2024 by SkateZilla 1 Windows 10 Pro, Ryzen 2700X @ 4.6Ghz, 32GB DDR4-3200 GSkill (F4-3200C16D-16GTZR x2), ASRock X470 Taichi Ultimate, XFX RX6800XT Merc 310 (RX-68XTALFD9) 3x ASUS VS248HP + Oculus HMD, Thrustmaster Warthog HOTAS + MFDs
VR Flight Guy in PJ Pants Posted August 4, 2024 Posted August 4, 2024 Noted with thanks. I Fly, Therefore I Am. One cannot go around not saying "Thank you" every time these days, can't you? YouTube: https://www.youtube.com/channel/UCc9BDi-STaqgWsjNiHbW0fA
SkateZilla Posted August 4, 2024 Posted August 4, 2024 My build also doesnt have a F-22 EFM Bin Folder with the binary in it, so AFAIK it was meant to use F15's EFM with additional properties attached on top via cockpit systems. Windows 10 Pro, Ryzen 2700X @ 4.6Ghz, 32GB DDR4-3200 GSkill (F4-3200C16D-16GTZR x2), ASRock X470 Taichi Ultimate, XFX RX6800XT Merc 310 (RX-68XTALFD9) 3x ASUS VS248HP + Oculus HMD, Thrustmaster Warthog HOTAS + MFDs
Spino Posted August 4, 2024 Posted August 4, 2024 2 hours ago, SkateZilla said: Binaries will only load from their original location. Are you using the F-22 EFM or the F-15 PFM? I had modified the config to work with the F-15 PFM which is why I had instructions to save in \FM\ and not \FM\F22A\, I also forgot to put the lines back for the EFM and Binaries. To load the F-22 Binaries you only have to remove the -- right before "binaries" and change the EFM from "F-15C"to "self_ID' and the 2nd line from "F15" to "F22_EFM", you should still have the default \FM\F22A\config.lua, it should point to that one, correct, I will update my post. I will get with Grinnelli team on a more perm. fix. Actually tried it using the old SFM line, was experimenting on my F-15EX mod instead of the F-22. Didn't work anyway. Website (DCS Content): https://sites.google.com/view/spinossimulationsite/home?authuser=0 Discord: discord.gg/V6W8gJSx83 YouTube: https://www.youtube.com/@SpinosSimulations?sub_confirmation=1 System Specs: Ryzen 7 5800X, RX 7800 XT, 32GB DDR4-3200 RAM DCS Wishlist: F-8E/J Crusader, UH-1Y/AH-1Z, F-14B(U), F-14D/ST-21 Super Tomcat
mrjay Posted August 7, 2024 Posted August 7, 2024 On 8/1/2024 at 5:23 AM, hoff1218 said: It's a bit sluggish for me as well in the air and easily stalls on turns when before I could keep a steady 8-9 Gs. Also noticed that the max throttle does not go over 96% for me, before it would go as high as 110%. it's a lot closer than before though and we are back on the F-22's cockpit! 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 Posted August 7, 2024 Posted August 7, 2024 So the current situation is as follows, the fix Skate found is working however, it will no longer pull from the F-22 SFM lua, it is calling the F-15 avionics dll as well as the FM dll that means the SFM table is not being used. You also might notice that the plane doesn't pinwheel on the ground anymore due to the use of the F-15 FM dll. Our intention was to not use the F-15 FM and just deal with the SFM table as it let us get different results. You will also notice the plane will stall a lot smoother and doesn't chunk at all anymore again due to SFM no longer being in use. I am working on a fix to the mod to get it back up and running as best we can for now. We will have to evaluate the situation and make a decision on what we can/are going to do moving forward. 9 8
scommander2 Posted August 7, 2024 Posted August 7, 2024 6 minutes ago, Grinnelli said: I am working on a fix to the mod to get it back up and running as best we can for now. We will have to evaluate the situation and make a decision on what we can/are going to do moving forward. Thank you so much for keeping the project moving forward... 1 Spoiler Dell XPS 9730, i9-13900H, DDR5 64GB, Discrete GPU: NVIDIA GeForce RTX 4080, 1+2TB M.2 SSD | Thrustmaster Warthog HOTAS + TPR | TKIR5/TrackClipPro | Total Controls Multi-Function Button Box | Win 11 Pro
mrjay Posted August 7, 2024 Posted August 7, 2024 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.
hoff1218 Posted August 13, 2024 Posted August 13, 2024 On 8/7/2024 at 12:26 PM, Grinnelli said: So the current situation is as follows, the fix Skate found is working however, it will no longer pull from the F-22 SFM lua, it is calling the F-15 avionics dll as well as the FM dll that means the SFM table is not being used. You also might notice that the plane doesn't pinwheel on the ground anymore due to the use of the F-15 FM dll. Our intention was to not use the F-15 FM and just deal with the SFM table as it let us get different results. You will also notice the plane will stall a lot smoother and doesn't chunk at all anymore again due to SFM no longer being in use. I am working on a fix to the mod to get it back up and running as best we can for now. We will have to evaluate the situation and make a decision on what we can/are going to do moving forward. Thank you @Grinnelli!!! Downloading now!
dmatt76 Posted August 13, 2024 Posted August 13, 2024 I had FC3, didn't buy FC24, so I only have F-15C now Downloaded the latest 3.0 version and still I can only fly the F-22A if I jump to F-15C first, if not - there is only AI F-22, F10 map if set as player Is this the only way to fly the F-22A now or it works nornally with FC24?
TKhaos Posted August 13, 2024 Posted August 13, 2024 1 hour ago, dmatt76 said: I had FC3, didn't buy FC24, so I only have F-15C now Downloaded the latest 3.0 version and still I can only fly the F-22A if I jump to F-15C first, if not - there is only AI F-22, F10 map if set as player Is this the only way to fly the F-22A now or it works nornally with FC24? Odd, I've had FC3 and upgraded to FC 2024 and downloaded F-22A v3.0 today and worked fine, had to reassign the pitch and roll axis to normal as the F-22 settings aren't there for it anymore, was a couple of others I changed as well. You should have more than just the F-15C as well, FC3 included the A-10A, F-15C, MiG-29, Su-25A Su-27, Su-33 and the J-11. The FC3 folders don't exist anymore it's all individual aircraft so no reason why the F-22A shouldn't work for you, unless your running an old version.
dmatt76 Posted August 13, 2024 Posted August 13, 2024 So, you have FC24, I don't and that's what I am trying to confirm... Does the F-22 work as intedned only with FC24...? It doesnt matter if I have A-10 or MiG-29... I HAD Fc3, I have F-15C installed and cant make the F-22 to fly until I jump in F-15C mission first
TKhaos Posted August 13, 2024 Posted August 13, 2024 (edited) 11 minutes ago, dmatt76 said: So, you have FC24, I don't and that's what I am trying to confirm... Does the F-22 work as intedned only with FC24...? It doesnt matter if I have A-10 or MiG-29... I HAD Fc3, I have F-15C installed and cant make the F-22 to fly until I jump in F-15C mission first That's what I meant, it should work as the F-15C is part of the FC3 pack, it's exactly the same aircraft in FC2024 nothings changed, unless they changed a file name on one of the DLL's. When I upgraded to 2024 it just added 3 new aircraft to the existing FC3 ones. When you downloaded and installed did you just overwrite the previous one or delete it. Edited August 13, 2024 by TKhaos
hoff1218 Posted August 13, 2024 Posted August 13, 2024 (edited) It worked fine for me on the first try, it's still not functioning exactly as before, but it's a lot better. I have the F-15C on it's own, I never got FC3 or the new update... Are you using the entry lua from v3 or did you replace it with Nightstorms? if you're using the lua from Nightstorm, that may be the reason you need to jump in the F-15 first. I tested using the following in the entry lua which is what was being used in Nightstorm's version "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" and it still loaded directly to the cockpit view. it appears it's actually what SakateZilla suggested by adding the "load immediately" to true on the binaries for the F-15's entry lua... When I removed that line (load_immediately = true,) it loaded unto the map view. example: binaries = { 'F15CCWS', 'F15' }, load_immediately = true, }) Edited August 14, 2024 by hoff1218
ke51 Posted August 14, 2024 Posted August 14, 2024 (edited) The F-22 is now playable again in Ver. 3.0! (Unfortunately, you cannot fly again after installing the Nightstorm flight model mod. Excessive bending of the wheel has been eliminated Additionally, the F-22 now feels the same center of Weights and gravity as other aircraft. The way I play to make sure the F-22 is all functioning on replay is to start the mission with engine standby start, stop the engines on the fly then restart the engines finally stop the APU by itself. After takeoff use G on the keyboard to control the gear and the replay works perfectly. Thank you GD. Edited August 16, 2024 by ke51 1
Tusk.V Posted August 15, 2024 Posted August 15, 2024 Has anybody else noticed that the AIM-9X's go bananas now when you launch them? They fire off like a bottle rocket with no stick. Main Pit: i7 13700KF, RTX 4090, Pimax Crystal Super Co-Pilot Pit: i7 11700K, RTX 3090, Pimax Crystal OG
LHP Posted August 21, 2024 Posted August 21, 2024 Found a bug, i had posted this in the 2d video forums but on further testing, I found out it's the f22 with the problem... no other aircraft have the issue the sun is a huge big blinding blur and it comes through walls and everything, first-person only, 3rd is fine, pictures below 1
Recommended Posts