Hello, Do you know how change the color of the HUD? im looking for a mod to change the color of the hud . Necesito un mod que cambie el color del HUD o lo haga más fuerte porque entre las nubes se ve todo blanco desde una aeronave

Will this mod allows firewill's aircraft to spawn inside antistasi ultimate factions in the open world? Or would they have to be spawned in to play them? Hoping its something like if the plane is flagged NATO then all Nato nations have a chance for it to spawn, but maybe thats wishful thinking.

Anyone know of a mod that gets rid of all the skins being actual planes just moves the skins to the garage editor? would be nice to clean up the blufor tab tbh

ohh ok thanks mate

If you copy paste the object after selecting the kit and pylon items, each new copy will have the correct look to it. But, if you move the object after placing it it will leave the wing pylons visually where they were, but that doesn't affect the object when you go to play as it will be armed and usable and have the ghosthawk kit visual. (And when you come back to the editor it will update to the new position visually). Here is a short video screen grab of me placing the UH80R in the editor and demoing the kit install. see: https://files.catbox.moe/uha7h5.mp4

@Bonger So the UH80R was never released by Firewill past an early alpha build, but it is playable via the editor and making a mission with it. The main issue is that if you try to spawn it via zeus or the garage it will appear as a normal Ghosthawk. you MUST place it in the editor, and select then right click, attributes, check the option to "install ghosthawk kit" and then choose what ya want on the pylons. Then click "OK". You will not see a visual change in the model. (But if you were to play you would and have the weapons on the pylons and sensors.)

pls fix the UH-80R ghost hawk, its just a normal ghost hawk

Is there an easy way to disable AMS system from MQ-12Falcon uav drone?

@Projekt It is in this pack. (originally part of Firewill's ROK Armed Forces 2035) I think you have to access it via the editor only though, sort of like the ghosthawk DAPL heli thing.

Me hoping that one day he will make a AH-64D mod.

@ DragonZord2030 it says, "+Helis". That little symbol means "plus" as in addition to. Also 17,002 other people are subscribed to this mod which has been around for almost 5 years. You are the waste. Never post here again. Please have a bad day, thanks!

SMH love how it says Helis but has nothing but damn jets! Wow what a waste!!!!!

Mod updated to include C-130

I updated the Mod, everything ok, I solved it by finding IDD that I was missing "5283" thanks for your time

@Rios I have updated the mods to be current. Try updating this modpack and seeing if it fixes your problem.

-Updated AWS and mods to be current

hello guys, i have the mod FIREWILL Aviation Pack (Complete) + Helis and for some days now the window to customize the jets closes immediately. I already have IDD codes for infistar, help thanks

Ah, sorry I missed that disclaimer. And I did look! Haha

Ah, sorry I missed that disclaimer. And I did look! Haha

@Hudson242 No, I manually update the mod. Please read the description final section area marked with triple ***

Asking again: So with all these packaged together, does that mean if the original author updates one mod, it automatically will update this package?

@THORGUY Steam reports the mod size independently from the author who has no control over it. Sadly it'll continue to report improper sizes until they fix that little issue on their end.

This pack is actually about ~10 GB boys.

@RotarRooter
Yo this MOD ISN'T 2.2 Gbytes but 9.8
Could you please modify that ,-, It's really annoying when trying to make space on the drive without the right informations
Thank you ! ;)=)

@OksmanTV Yea, it is like right at 14 GB. Thus the disclaimer. You'd think Steam would be able to accurately report how large a file size is.

Haha damnit steam I thought this was too good to be true, 2GB nah more like 10Gb :D

So with all these packaged together, does that mean if the original author updates one mod, it automatically will update this package?

how do you get to use any of this stuff?

Updated again - F-15 and AWS are current to what Firewill has put out.

Add this to your Allowed IDD list:

5168,5225,5280,5581,9920,9918, //Firewill - Incomplete ...


I found these by finding the "closed IDD" listing in your Infistar Surveillance logs.
If you get any of these blocked in the future, note the time and watch the log.

Also not sure if this works now as I haven't tested it recently, if the IDD's have changed this will be blocked. Also my Infistar logs have stopped working for some reason and working with them on it. So as soon as I have logs I can post any new ones I find.

players cant open ams but admins can do u have infistar dialog whitelist idd's

@rgoncapo12 I am unsure what the issue might be. You might have more luck with this new update I just did. I really have no clue about server setup. I am a one trick pony that can update the mod. My knowledge unfortunately ends there.

Mod updated! Should be current with the F-15 mod update that Firewill made a few days ago. Thank you @Fluff the Sergal for the reminders.

@RotarRooster im new installing the mod for an Exile server, and I got an issue with this pack. every time I log into a server it says Verifying PBO failed: @FIREWILL AviationPack/addons/fir_airweaponssystem_us.pbo, any specific fix for that ?

Mod is updated! Thank you @Fluff the Sergal for the reminders.... I truly need them!

@Nobody contact your host or research SteamCMD and how it works with Workshop.

@Nobody I have no idea.

how write this mod inside decade server

To #1, yes it would be fine if you didn't use any other mod you publish with the same BIKEY.

#2, yes it causes what you are describing because people can side load his other mods using same key as "Optional Mods" So in effect you can double load up the mods when it's not needed.

And #3 is exactly that. Each of your packs, even if you make some XYZ widget mod, use a different key than a single one and done approach. :)

Bikey's shouldn't modify content, only if there's verification from Battleye and the resources were not signed properly.

I know there are other mods out there that work with the firewill mods and add enhancements / changes. For example the many "optics packs". Would changing the other modpacks .bikey not interfere with those mods being able to be run in tandem with the no helis all in one pack? I only created this alternate heli pack so as to be able to include Firewill's helicopters as they have the same FIR.bikey name but it is clearly different as they will not work together with the jets.

Thanks for breaking it down for me. I am all ears for suggestions.

@speedrcr So let me explain what I am understanding:

1) This mod pack with helis is fine as it is all signed by me with its own unique .bikey file name and there are no other mods signed by me.

2) The other modpack (without helis) causes issues because it has the original firewill .bikey that his mods all standalone share... and thus this causes problems because someone can have both the no helis modpack on and also have some of the standalone mods which would double up any of the jets. And, since mods I do not include in these all in one packs like his "Hunter GPK" vehicle share the same original Firewill .bikey that also makes filtering difficult.

3) The solution being to come up with a separate .bikey file for the all in one pack without helis, that is not the firewill original FIR.bikey that does not share a .bikey name with any other mod / modpack.

Is that all correct?

This pack has a different key now, that's correct. But your other pack without the helis, shares same bikey name. When you use or have the same naming it can cause an issue when you're hosting your mod on a server. The firewill key allows players if they have all his other mods to connect with them.

Suggestion like others (CUP, RHS, etc), have a distinguished name for the pack than a "general name" (i.e. your Steam name). One example would be to have "FIRwH082122.bikey". This way if you update it, and when hosted on a server, it will force the client to have the proper version. People that use a general key name or key for all their mods don't know the hassle that creates for servers as others can try to join with mods that use same key.

Does this make sense to you?

This is coming form an advanced hosting perspective where we want to filter out certain mods or people incorrectly connecting with additional mods and causing issues.

@ speedrcr Hello and thanks! This pack is already signed by me with my own .bikey file. The other pack is signed/keyed by Firewill. I am not sure what else you might mean?

Thanks for your work on collecting all of Firewill's favorites! Makes this a ton easier for server admins!

if you can at some point, produce your own keys so we can filter out loading your other mod optionally :)

Thanks again for the update!

Mod is updated! Added the new EA-6B Prowler as well.

Yes, but it will be like a week or so. :) I will get it done though!

Will you be adding the new EA-6B Prowler?

Mod is updated!

@joshuamezzapelle To confirm, were they all there before? I know that other users have said before that the way Firewill made the mods that they only show up in the virtual garage and not the zeus list. (Or something like that... it has been a long time.) I have no clue how any of that coding works, but that would be an issue for Firewill to fix / update.

Does anyone know how to fix the multiplayer speed brake? It's always up on other players' aircraft.