HomeFries

There's a limit to how deeply you can nest your decals. Try removing the D folder and just going with F4Black\Euro1

DA, Got to thinking earlier: given the push for tactical squadrons and the desire not to double dip, I propose we change entry 554 from VA-128 to VAQ-128. While VA-128 better fits the default timeframe, it is a RAG squadron that is already represented by skin-specific decals. The VA-128 Golden Intruders became the VAQ-128 Fighting Phoenix in the mid 1990s, becoming a Prowler expeditionary squadron when there was no longer any need for an A-6 RAG. Besides, we already have VA-42 represented for the East Coast A-6 RAG for people who want to take the A-6 Superpack to the training range. No need to make the change now (it would screw up my A-6 Superpack, which still uses VA-128), but we should get it in when we release the RP. My Superpack 2.0 will use VAQ-128 as a Prowler squadron. If you prefer, I'll take care of the entry myself prior to release.

Thanks, DA. Interesting issue w/ the tail. No promises, but why don't you send the files my way; I'll see if there's something from the forest view since I'm sure you're all about the trees.

DA, I'm planning on releasing my RAAF Intruders tomorrow (today?). Please upload the version of squadronlist you are uploading with your F-4s and I'll include that in the package. I figure that our mods should at least cover down in the interim until this is released.

Here are the entries I'm using for my RAAF A-6Es: [Decal001] MeshName=fuselage_rear DecalLevel=0 DecalFacing=RIGHT FilenameFormat=InsigniaFuseR Position=-6.20,0.50 Scale=1.0 DecalMaxLOD=3 [Decal002] MeshName=fuselage_rear DecalLevel=0 DecalFacing=LEFT FilenameFormat=InsigniaFuseL Position=-6.20,0.50 Scale=1.0 DecalMaxLOD=3 [Decal003] MeshName=wing_left_outer DecalLevel=0 DecalFacing=TOP FilenameFormat=InsigniaWingL Position=-5.64,-3.42 Rotation=20.0 Scale=1.0 DecalMaxLOD=3 [Decal004] MeshName=wing_right_outer DecalLevel=0 DecalFacing=BOTTOM FilenameFormat=InsigniaWingL Position=5.64,-3.42 Rotation=20.0 Scale=1.0 DecalMaxLOD=3 [Decal005] MeshName=wing_left_outer DecalLevel=0 DecalFacing=BOTTOM FilenameFormat=InsigniaWingR Position=-5.64,-3.42 Rotation=-20.0 Scale=1.0 DecalMaxLOD=3 [Decal006] MeshName=wing_right_outer DecalLevel=0 DecalFacing=TOP FilenameFormat=InsigniaWingR Position=5.64,-3.42 Rotation=-20.0 Scale=1.0 DecalMaxLOD=3 I also have entries for InsigniaLVWingR, InsigniaLVBWingR, etc. All work just fine. Hope this helps.

While putting final tweaks on my RAAF Intruders, I noticed that when I tweaked the Textureset.ini, I would lose the Aussie flag from the tail. Before: After: You'll note that there are actually six separate decals on the tail node (no reverses, but L/R versions of each decal): the squadron logo, the fin flash, and the flag at the top of the tail. Though not complaining, I couldn't figure out why it was even working in the first place, much less what I was doing to break it. Long story short, when I was adjusting the specular/glossiness/reflection values, non-zero values for all three would cause the last decal (the flag) to disappear. Resetting reflection to 0.0 would cause the flag to reappear. I haven't yet tested this with the other values; I can release this just fine with a 0 reflection value by keeping the specular and glossiness values up. I just thought that people might be interested in a way to stretch the decal-mesh limit.

I've actually decreased the cloud effect from my USN/USMC A-6s since the RAAF birds aren't constantly exposed to salt air. However, I'm looking at going back to my default USN values for lighting and reflection, as the default RAAF values (taken from DLC17) make everything too glossy.

The way I could think of doing it is to copy the Hawk as Hawk_IR (and rename the Hawk.ini file to Hawk_IR.ini), then change the weapon to Air to Air missile (not sure off the top of my head what entries are required). Set Nation to Iran, no Export, and SpecificStationCode=AIM54. You should be able to then mount the Hawk wherever you could mount a Phoenix.

Sheriff, I had no problems at all doing this with RAAF roundels. Are you calling the default roundels, or are you copying files to your specific decals folder, then trying to call them as InsigniaWingR, et al? Also, if you do call InsigniaWingR, et a, make sure they are listed as DecalLevel=0.

Here's my latest progression on the project. Please note that in each of the screenshots, I have included 1st and 6th Squadron custom logos, which will be added to Squadronlist.ini. I've reduced the roundel size to 1.0 on the A-6E and TRAM models. I may keep the A-6A at 1.4 to suit the early similarity with the USA schemes. Here's the updated Sky/Sea blue scheme with grey underside markings instead of black. I've also substituted the standard roundels and fin flashes with the low visibility color versions on the nightfighter schemes. I've also added a 1990s Sea Grey low visibility scheme. And moved the low visibility squadron markings to the European camo as well. Finally, I added the ARDU scheme for Sheriff. I hope I did it justice. Please add any critiques or suggestions. I have thick skin, and I just want to get it right. This pack is pretty close to release, so please get your suggestions in ASAP.

IIRC, the 601 is part of the E-2 skinpack, so this is a squadron that already has skin-specific decals. Definitely fits the 1000+ criteria. The Kokutais appear to be limited to helos and maritime patrol aircraft, so not anything flyable in SF right now. My take: they can be represented by UnitName in campaigns, or added to 1000+ if there is enough demand.

Dang! I looked it up, and the Wilhelm scream isn't the one I was thinking of. I was thinking of the other scream, also known as the Howie Long scream. http://www.freewebs.com/notthewilhelmscream/history.html This would also be funny as hell in SF2.

Since you've made decals associated with squadrons in squadronlist.ini, you need to assign them as level 1. The program will then take care of the numbering. Here's an example, assuming you're dropping your decals in the Objects\Decals\CF-110 folder. DecalLevel=1 FilenameFormat=CF-110\SQN Now if you're using the default F-4 LOD for the CF-110, you may be better served covering down on the existing naming convention for the F-4 level 1 decals, then just drop the files directly into your main decals folder (since you're supplementing existing default decals). Note that if you do this, you will likely need to cover down on the default decal placement within the canvas itself, though you are not limited in file size. Example: DecalLevel=1 FilenameFormat=F4_SqTailL (and another entry for F4_SqTailR)

:rofl:

Awesome! Now all we need is the Red Leader scream (extended version). [media] [/media]

Well, you got the 67 right, and the ALR-45 is 2-18, but I haven't found a good comprehensive RWR site like that. I would also be interested in finding out what kind of displays each model did or didn't have.

W00t on the Dhimari squadrons. Just so you know, all I need right now is the squadronlist that has the USNR/USMCR A-4 squadrons and the RAAF 1st and 6th. I know you gave me the entries, but for purposes of configuration control I would rather just get the list from you and not make any changes to the one I have.

DA, Sorry for the jerk-around, but I think we can leave ARDU off squadronlist.ini, or at least put it at post-1000. Any skins will be specific to ARDU, so there's no need for level 1 decals and a sub-1000 number. Also, can you please post your latest squadronlist.ini. I'd like to some decal integration on my end.

I know that in SF2 the Canberra uses 2nd Sqn, and the Mirages use the circa-400 entries in Squadronlist.ini. From there, 1st sqn flew the F-111 operationally (and I think the F-4 as well), and 6th Sqn is a RAG-type squadron that trains pilots on their specific airframe. ARDU is like the T&E units at Edwards and Pax River. I haven't looked at the rest. I'm still surprised that the Danish entries are temperamental; I would think it would be easier to just code an engine that reads the UnitName entry without preconception. But I'm also discovering weird things about decals that make no sense and that I can't figure out, but can only make work.

DA, I just got a request to do an ARDU skin for the A-6, and while I could easily make this a squadron-specific set of decals, ARDU might be a fun RAAF unit because it is a test unit for the RAAF that has multiple airframes and unique skins. I'd like to drop this into the SEA section if possible.

http://en.wikipedia.org/wiki/General_Dynamics_F-111C Second picture down shows the scheme in 1981. Just wondering the date range on that. Was thinking about that myself. Adding ARDU to the SQUADRONLIST.INI should be interesting as it can be applied to multiple airframes (like VAQ-33).

Due to reasons of intellectual property, the A-6 Superpack doesn't include cockpits. These have to be purchased, extracted from WoV, or downloaded from any number of mods in the SF1 section here. Once you add the cockpits, you will need to enable them in the a-6a.ini file (as well as a-6e.ini, et al). Instructions are in the readme.

Thanks, guys. I'm planning to keep the roundel near the intake on the A models because of the speedbrake on the rear fuselage (I don't know the mesh name, and it would look weird to have the roundel partially cover the brake anyway). However, I just figured out how to get the roundel on the rear fuselage and keep the national flag on the tail (I was having decal issues before). I'll do that for the E variants, which don't have fuselage speedbrakes on the LOD. For the tropical grey, I am planning on doing that as well. I assume it's Sea Grey overall; do you have any information on when it was in use. As far as the tropical green camo, I know it was in use in 1981, but I was wondering how much time on either side of that year the scheme was in use.

Yes. RAAF. I may play with RAN as well; I'll see if the A-6 can be launched from the Melbourne. Should be fun.

I still need to look at the F-4 stuff you sent me. I'm trying to get to a good stopping point with my What-If RAAF A-6 before I look at that.