SkateZilla

IIRC The First teaser was modelled after an Export Configuration. (Italian to be precise). Since then ED has likely gotten more data from the US Army and shifted versions.

I already explained this multiple times and multiple places, this is the author's responsibility to update, I do not have the time allotment for fixing every FC3 Based mod.

Advanced Launch Options, Top Row, Click External Apps Launch Order, make Launch External Apps is checked, then set the order in each slot below that. if the settings file is compatible, it updates itself on App launch and brings over the settings. If you jumping from v1 to v2, settings are not compatible.

Technically VHS was telecined 29.976 Hz w/ 3 Interlaced frames for every 2 progressive frames typically PIPII or PIPIP depending on recording hardware., So 3:2 Pulldown would apply. 30 Hz moving every 2 frames would mean 20 Hz.

I know what they are and what they do, Like I said, I cannot comment on them because they are not public.

Early testing, I was adding some things to check clearances quickly, Once I get around to fully going through the loadout they will be corrected. The other Issue is Maverick A and B on the F-4E belongs to HB and is declared locally, so not "available" for other aircraft w/o modding their core files.

when I get around to re-mastering mine, they will.

The AI Doesn't have those limitations, so the AI can have them, along with AGM-65, AIM-9s on the outboards, etc. At present, my plan is to have: - F-5C Skoshi Tiger (AI ONLY) *Adds the Bullpups, restricts the AIM-9s to earlier models, adds tank and AAR Skoshi Left Side Probe. - F-5E Export Tiger (AI ONLY) *Adds AGM-65E Singles to IN/OUT Board Stations, a few other items, and AAR Export Right Side Probe - F-5E Modded Tiger (PLYER AIRCRAFT) * Adds the Wingtip FuelTanks, Antennae and AAR Probes etc. *(All Cosmetic)*, - F-5E FC Modded Tiger (PLAYER AIRCRAFT) * Adds the Wingtip FuelTanks, Antennae and AAR Probes etc to the FC. *(All Cosmetic)* That way there's no modding of the core F-5E Files. There's also the issue where I have to integrate new new Aircraft Property, to switch the AAR Coordinates between left/right. Right now I have F-5E Export and F-5C Skoshi flyable to test things, but will change before I release, as the F-5C external model has clipping issues w/ the cockpit, and until I fully script the addon systems, the extra weapons will not work, *(AGMs, AIMs on Outboard, AAR Fuel Transfer, WingTip Fuel Transfer, etc).

The make flyable line and the CFG needs to be updated, along with the \FM\Config.lua

do they have 150 gallon tanks on those wingtips? lol.

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.

Both variants are flyable yes, and requires the DCS: F-5E Binaries -C Skoshi Tiger uses F-5E(-1?) shape with the pointed nose, but there is cockpit clipping because that model doesn't have the removal of the side walls and panel hood like the -3. -E Export Tiger uses F-5E-3 shape and works flawlessly, Both versions have the ability to add the AAR, Antennae, and Wingtip tanks etc. As for the AGMs, I haven't tested the bullpups, the AI uses them, But for Mavs, I started coding a addon system that puts the display over the radar, however it has an issue where it never goes away after being activated even once you've depleted your MAV stores, so I'm working on that, and the system wont be publicly added until I can finish it properly. Along with addon Fueltank systems. (Allowing use of the Wingtip tanks, as well as full AAR capability), these systems will take a while to properly code and integrate, as the FM/F-5E systems don't have the wetlines to the pylons, nor the AAR Transfer switch in the systems or cockpit. The point of including new versions was to help with mission building, as well as make it so the mod is 100% in SG and does not require modifying core files. User can use the Export Tiger and have all the capabilities of the -E-3 Plus addons, without having to modify their DCS Core files to add things. I plan to develop more addon systems for the cockpit as soon as I can get the core package done and clean. I'm also looking into FCS Versions.

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.

Apologies, it goes in the Entry.lua for the modules, not the A-10A.lua etc, was typing fast and lost my train of thought.

Good Day Everyone, In order to restore FC3 Dependent mods that utilize the Old = x System, You have to force load them on startup, In the \Mods\Aircraft\ Folders for: A-10A F-15C MIG-29 Su-25A Su-27 Su-33 There are entry.lua files You will need to open these files, and add a line below the binaries block Add: load_immediately = true, And save the LUA File, This will tell DCS to load the Binaries at DCS Startup, Allowing mods that used Old = x to run as they did before 2.9.6.

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", }

I built my own fuel probes that will be in the next update.

Update for today is pretty much all under the hood things, I have a few goodies being added that I want to cook a little bit *(more under the hood stuff).

Seems like a bug in FM Linking, Pitch authority is decreased, and is next to nothing below 350 knots.

I'm pulling the stick, and I see the elevators deflect, but the aircraft is barely moving, if I revert the lines back from the {'F-15C''F15'} fm lines to what I had before it seems to work.

anyone having issues with pitch authority?

right now the only issues I'm working on fixing, is the Pitch input is gimped and it won't allow me to change the input files so I can change seats, it assumes I'm still in the F-16C, despite F-16I having it's own settings. The external model animations also need updated, tires don't spin etc etc.

I have to clean up a bunch of cross linked file issues and some bugs from removing the core files from the \Saved Games\, but I will send the info to the team, if they want to share it, they can.

For the record, I was able to modify and have the Sufa 100% self contained in the \Saved Games\ Folder instead of breaking IC and merging with the F-16C Folder.