Jump to content

SkateZilla

ED Beta Testers
  • Posts

    21634
  • Joined

  • Last visited

  • Days Won

    20

Everything posted by SkateZilla

  1. 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).
  2. Seems like a bug in FM Linking, Pitch authority is decreased, and is next to nothing below 350 knots.
  3. 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.
  4. anyone having issues with pitch authority?
  5. 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.
  6. 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.
  7. 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.
  8. this is the correct way to load, I would recommend using this line, it was changed w/ 2.9.6 My work around simply adds the Old info to force a binary load, this properly loads the DLLs and systems.
  9. These values are residual and haven't been used in a long time if ever in the recent DCS Engine, ["heading_units"] ["Datum"] [""canopyReflections""], Controls the reflection strength of the active rendered reflection on the glass, it should be in the options.lua I cannot comment on these, as they not part of the public builds: ["aircraftMode"] ["compassTape"] ["easyRadar"] ["tacticalMap"]
  10. Today's update, Finally finished unwrapping and painting the surfaces, approaching the finish line, just tweaking and color corrections left. Then cleaning up and getting everything packed.
  11. 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
  12. 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()
  13. SuperHornet and Sufa dont replace, they augment themselves into the core files because they need the System and Flight Model DLLs. FCS Aircraft previously were handled different.
  14. 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
  15. 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.
  16. Debating if I should change the name to F-5E Expansion.. lol
  17. The antenna is only cosmetic anyway.
  18. Today's update, Started building the shape for the Skoshi Tiger AAR Probe attachment, It was a bit tricky, as the reference schematic was not properly scaled, and in individual sections. However, I was getting creative I built the base fuel transfer pipes first, then built the Skoshi specific items on top of the pipes, Once all the pcs were shaped, I only had to assemble them and place them, From there I have to do some tweaking passes to get the shape position and size correct, then unwrap and texture them. I also decided to not have the AAR probe light enabled, as it would not be controllable by player or AI, unlike the 50 Gallon Tank lights, it would be pretty intrusive to have it on all the time. I have both general shape in DCS as Skoshi and Export, Skoshi will be on the left, and the Export will be on the right once I finish tweaking and texturing it. This would pretty much complete the Package, I decided to not do the dual VHF antennas, as I only found 1 reference image of that setup.
  19. Textures were moved to the new map for the antenna this morning, I spent some time tweaking the ADF shape to better line up with the existing panels, also re-mapped it for the 5th or 6th time to fix some alignment issues and edited the normals again to resolve some shadow issues on the sides. Aside from minor color correction and adjustments to panel lines and weathering, they are pretty much done. Dual VHF Antennae is planned, but I have to get started on the AARs.
  20. 1. which hardpoint? the fuel tanks can't be moved as the pylon is part of the external model, I've tried removing the pylon and using a element configuration, but it did not work. *I may look into trying again after everything else is done using some alternate methods.* 2. not that I can see, there's no connector on the pilot head, so the item would not move with the pilot's head movement.
  21. Apologies I forgot to update last night, I have ILS/VOR, VHF, and ADF Antennae done, I still haven't gotten enough reference images for the sky spot antenna. *ILS/VHF Maps were moved to the new Antenna texture, so I just have to transition them on the models themselves and re-export. I also have to do some fine tuning passes to the antenna maps, and check some normals *(I saw some weird shadowing while flying around in some instances) I am going to try and get the AAR Probes started and integrated in the next few days, along with the Dual VHF E/M Antenna.
  22. Right now i have the ILS/VOR and VHF squeezed into the PTB-50 Texture file. I may separate them to their own texture map, as that texture has no room for anything else, Which would allow me to add ADF Dorsal attachment, Skyspot Spinal Attachment etc. *(still gathering reference material for those) I also want to do AAR Probes, But quality reference images are in short supply, As I know there's multiple variants of the probe as well. *(Std Export on Right, and F-5C Skoshi Tiger on the left w/ different connectors, Blank off Paneled probes, glass panel probes etc etc) I have *Usable* reference images of the Skoshi tiger probe, but these images are High resolution staged poses of High LoD/Scale Models. their accuracy to schematics cannot be 100% verified. and they also lack in close Sub 6 Inch details *(Panel lines, rivets, internal details behind the glass panel etc). I also scoped the static displays I could, which do not have the items to capture reference data.
  23. As in you used my LUAs and structure as a template for your own?
  24. Still working on some small issues, but I have added some more attachments:
×
×
  • Create New...