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

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.

Read the entire first post, the answer is in there.

Debating if I should change the name to F-5E Expansion.. lol

The antenna is only cosmetic anyway.

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.

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.

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.

We don't know the 3rd Party's contract terms, halting payments for contract violations until violation is resolved/corrected may or may not be directly stipulated in their contract. This is where "Heresy" comes in, 2 of the 3 camps are just assuming based on the heresy, one camp assumes another is making stuff up. there's no public disclosure of evidence either way. One party was said to have violated the IP, the other is saying they didn't, due to the legal standing of the dispute, ED has not made their evidence public, the only thing consumers can do is hope for a full resolution and all vital members of the RB team returning to work.

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.

That's not how IP works, just making a legal agreement w/ another party using something that don't belong to you to secure or support that agreement is all you gotta do. There was plenty of "Talk" regarding the alleged breach on other social groups/sites, I'm not getting into it here, because it's not going to be confirmed nor denied by anyone, so it's all just hanger talk.

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.

As in you used my LUAs and structure as a template for your own?

Still working on some small issues, but I have added some more attachments:

Update my Mod how? I'm already adding VOR/ILS and VHF Antennae.

Slight delay in first revision, I made some adjustments to lighting that has some unwanted side effects, So I need to revert those changes and try again. and I want to add a few more things, so I'm not adding Aux pylons for one item, lol.

I need to get a clean and recent build for the F-22 cause my build is old and been tinkered with too much.

I'm putting final touches on the VOR/ILS Antenna. I've also added it via 8th "AUX" Pylon, Which will allow me to include the lines for the Refuel Probe mod items, user would just have to enable them. Also made custom loadout graphics for the wingtips and VOR/ILS

it doesn't, I just tried, it seems the FC3 Mods now fall under the same as DCS Modules, Binaries are not loaded from \Saved Games\ Folder.

Try: MAC_flyable('F-22A', current_mod_path..'/Cockpit/Scripts/',{nil, old =6}, current_mod_path..'/Comm.lua')

Thanks for the report, I've Identified the issue, Should be fixed in next build.

Templates / Textures are 4096x4096, the PTB 50 tanks are incredibly detailed vs prior mapping, The Templates also include groups for albeda (diffuse), Roughness, Metallic, Heightmaps, A.O. etc, I can remove those groups and it would drop template to about 275 Mb from 596 mb. But Users would be on the hook for generating their own PBR Maps. They are all BC3 nVidia DDS *( I'll likely re-export as Intel BC7 DDS for the patch to help w/ compression).

This is because you're running the ST ModelViewer Need to use MT ModelViewer in \Bin-mt\ ST is going away soon, any new features, are likely not coded for ST regardless, it's been this way for over a year, any new features require MT..

I was working on some things, but didnt want to delay the tanks while building stuff. As for the template... I'll look into maybe a 2048x Version, but it would lose a lot of detail.

check the app logs, controls are only disabled if the parser returns a null value for the string.