This is a great example of the "fight fire with fire" philosophy. Though it's definitely not easy to fly this thing with expert controls, once you get the hang of it, you'll never be outmaneuvered by another drone again. 10/10 purely for leveling the playing field against annoying enemies.
i wonder what you then think about UAV-45R mod then as still think this one is more easy to control but 45 is little buzzard that is like controlling a QAAM missile
On the Add-on Compatibility Patch for the F-15D, the name on the Menu has it listed as AircraftShort_Name_f15d, along with the names of the skins after the Strider Skin. Is there something that can be edited in the Data Table?
That would be the Localization files. However, I have tested my patches and there's no issue with all new addon aircraft's descriptions and names. Maybe you have another mod that also changes aircraft descriptions? Whatever it is, remove those kind of mods, and try adding more tildes (~) in front of my patch's name. Be sure to place it alongside Addon Compatibility Mod's localization .pak file.
If the issue still there, show me the contents of your ~mods folder.
I did alter the Aircraft Data Table like with Sincerity's Mod, and the F-15D is only one is acting like this. The Other Mods I kept in work just fine which is odd.
Data Table shouldn't be the issue. Again, the cause is likely other mods that changes Localization.
From what I remember, there are a couple of newer addon mods that have their own patches that only add those mods to the current version of Addon Compatibility Mod. Said optional files has their own localization files inside. There's also one mod that exclusively changes one weapon's name and that also has its own localization files. Check if there's any of those and remove them.
I can't seem to get the patch working oddly. All other aircraft show up but can't seem to get the SU-35SX to show up. Kind of stumped at the issue. Updated from the last version for the Comanche and had no issues getting that mod working. Can someone steer me in the right direction?
Oh, you're right. You are trying to use the Non-ASS version, yes? There's a discrepancy with the Su-35SX's file pathing in that patch's plane registry. The ASS version doesn't have the issue.
I'll put an update immediately, please give it a try once it is up.
Do you have any other mod that changes things like ammo or weapon names? If you do, remove them first. Those kinds of mods are modifying the aircraft data table that prevents the drone -or any other addon mods for that matter- from being registered into the plane list.
If so, as I've said in the description, use my temporary patch in the "Files" tab here as it has yet to be updated to support this drone and the other two newer addons. Choose either the ASS (Additional Skin Slots) or the Non-ASS versions.
And if the WUAV-R's entry's still not showing up, add more tildes (~) in front of my temporary patch's name.
can you add iml to these drones and add them to adf 11fs and cfa 44s so that the main plane's control system will be more powerful and it will fly with you throughout the mission and its only job will be to destroy missiles
You don't need to do it now, I just said it because I thought you could do it. Just think, if this mod is created, it will be the most downloaded and clicked mod. I recommend you to examine the codes of the ravens in Mission 20. I saw some things but I'm not good enough to modify them, only a professional like you can do it.
30 comments
The su-34k and the su-35sx, but now only uav seems to be on the list
And share me the screenshot of your ~mods folder.
If the issue still there, show me the contents of your ~mods folder.
From what I remember, there are a couple of newer addon mods that have their own patches that only add those mods to the current version of Addon Compatibility Mod. Said optional files has their own localization files inside. There's also one mod that exclusively changes one weapon's name and that also has its own localization files. Check if there's any of those and remove them.
Once more, if the issue still around, share me the screenshot of your ~mods folder.
I'll put an update immediately, please give it a try once it is up.
If so, as I've said in the description, use my temporary patch in the "Files" tab here as it has yet to be updated to support this drone and the other two newer addons. Choose either the ASS (Additional Skin Slots) or the Non-ASS versions.
And if the WUAV-R's entry's still not showing up, add more tildes (~) in front of my temporary patch's name.
Also, again, I'm not interested in taking requests.