HomeFries

One question: if the relative perspective/distance between nodes is correct in the Blender object, how difficult is it to globally adjust the dimensions (e.g. 95% size) in MAX? I ask because the nature of FakePilot objects means that the Blender object will need to be created without being able to visually QC the object relative to the LOD. Not a huge deal for a blade antenna, but something of an issue for a form-fitting object.

LOL. Me too (though my time is usually 2200-0130). 2200 is about when I get my second wind, and 0200 is typo-time!

Good stuff, SupGen. Definitely gets me thinking that the 3W FM needs to be updated; the RAZBAM models definitely feel heavier. While the A-6 is very nimble, esp. for a bomber, it never really feels like it's carrying 12000lb of Hate and DiscontentTM.

One more catch: [squadron598] Name=VMA331 DisplayName=VMA-331 BumbleBees Nation=RoyalNavy Nation should be USMC.

Here are the unit entries for which I found good tail art: [squadron701] Name=VA203 DisplayName=VA-203 Blue Dolphins Nation=USN [squadron702] Name=VA204 DisplayName=VA-204 River Rattlers Nation=USN [squadron703] Name=VA209 DisplayName=VA-209 Air Barons Nation=USN [squadron704] Name=VA303 DisplayName=VA-303 Golden Hawks Nation=USN [squadron705] Name=VA305 DisplayName=VA-305 Lobos Nation=USN [squadron706] Name=VMA124 DisplayName=VMA-124 Bantam Bombers Nation=USMC [squadron707] Name=VMA131 DisplayName=VMA-131 Diamondbacks Nation=USMC [squadron708] Name=VMA133 DisplayName=VMA-133 Dragons Nation=USMC [squadron709] Name=VMA134 DisplayName=VMA-134 Skyhawks Nation=USMC [squadron710] Name=VMA142 DisplayName=VMA-142 Flying Gators Nation=USMC [squadron711] Name=VMA322 DisplayName=VMA-322 Fighting Gamecocks Nation=USMC [squadron712] Name=VMA543 DisplayName=VMA-543 Knight Hawks Nation=USMC Renumber as necessary.

If you are looking for 850 tops (with Army Air and non-tacair at +1000), then we don't have to worry as much about where certain things should go. I figure I'll add the USNR/USMCR squadrons for which I can find tail art, and leave the rest at +1000 or not at all. The only thing with +1000 is that we won't even get the squadron name unless it is a specifically designed skin. To that end, if we're adding units that currently only have specific skins/decals, we should add them to 1000+ unless we're planning on skinning them for level 1.

I'm very interested. I just downloaded Blender, and I would very much like to create objects that can be added via FakePilot, so at least I'm starting with simple objects.

I was planning on going with the post-1970 USNR structure in which each reserve squadron is assigned to a reserve carrier air wing on the east or west coast. With this model, any reserve unit has an equal opportunity chance of deployment to augment regular forces, with the exception of the tailcodes that have a number/letter combo (which are assigned to naval air stations, not air wings). No need to go crazy on all of the reserve squadrons (I figure do a couple of decals, and pop the rest in 1000+ to possibly bring out at a later date), but we do get a lot of bang for the buck with some of the squadrons that flew multiple A-4 airframes, and a number of the squadrons transitioned to the A-7 and then to the F/A-18. I'm also curious as to if you have anything planned after 700. This would be a good place for the red squadrons, and then leave 800-999 free for the post-1000 listings we take off of ice.

Awesome. If you want, I'll be happy to add those USN/USMC units, but we need to be careful that only one of us is adding at a time, and that we're doing it serially to the same file.

The following reserve squadrons flew the A-4 (though not all flew the L). USNR Squadrons to add (with tailcode): VA-203 Blue Dolphins (AF) VA-204 River Rattlers (AF) VA-209 Air Barons (AF) VA-210 Black Hawks (AF) VA-303 Golden Hawks (ND) VA-305 Lobos (ND) VA-831 Mohicans (AB when activated) Additionally, VA-205 also flew the A-4L, though the Green Falcons are already in the updated SquadronList.ini with A-6 decals. The following USMCR squadrons flew the A-4: VMA-124 Bantam Bombers (QP) VMA-131 Diamondbacks (QG) VMA-133 Dragons (ME) VMA-134 Skyhawks (MF) VMA-142 Flying Gators (MB) VMA-143 (7X) VMA-144 (5F) VMA-217 (7Z) VMA-233 Blazing Aces VMA-322 Fighting Gamecocks (QR) VMA-543 (MD) EDIT: We could put all of these post-1000, except for VMA-543 (which I can easily do a tail for) so we will at least have 1 USN and 1 USMC Reserve squadron available with tail art. Then as we add tail art for the aircraft, we can pull them below 1000. We should also give some love to the Royal Navy No. 892 Naval Air Squadron (Name=892NAS). This is the F-4K squadron used in the DLC, so adding it to the squadronlist.ini is a natural.

Just thinking: we should probably do the A-4 reserve squadrons (USN/USMC) now that we have the A-4L as DLC.

I also thought it was hilarious, and should be interpreted strictly as parody.

We have (at least) 3 Ace Combat skinners here. I still think you guys should join forces and create a campaign or two.

:yes:

I think I pulled that from Wrench's tips in the KB, but I can't recall for sure.

Wow, I remember playing TV on my Pentium 100.

Thanks, SupGen. Another general question: is there any way to get the ILS needles working? Or was that functionality never implemented in the LOD?

Of course you can...and don't call me Shirley.

The XY slew works with any cockpit (AFAIK), and the VDI trick works with the EA-6A as well. The EA-6B cockpit doesn't have a VDI, so no-go on the first trick there.

Thanks for the reminder, SupGen. That thread was when I started modding, and I had completely forgotten about it. I've since revived the thread.

Gents, I'd like to revive this thread to see if there has been any headway made with releasing the updated RAZBAM cockpit. I would also like to add the following tweaks I made to the cockpit (and have included in the readme for the A-6 Superpack). This changes the steering symbol on the VDI from a CDI to a waypoint correction symbol: [steeringSymbol] Type=WP_CMD_YAW NodeName=SteeringSymbol MovementType=POSITION_X ValueUnit=DEG Set[01].Position=-0.090 Set[01].Value=-90.0 Set[02].Position=-0.080 Set[02].Value=-45.0 Set[03].Position=0.000 Set[03].Value=0.0 Set[04].Position=0.080 Set[04].Value=45.0 Set[05].Position=0.085 Set[05].Value=90.0 Adding the following lines to the [CockpitSeat001] section will allow XY slewing for TrackIR users: MinMovementX=-0.16 MaxMovementX=0.18 MinMovementZ=-0.08 MaxMovementZ=0.10

I had assumed the issues with the RAZBAM pit were LOD related, and the CRS/DME has always been my pet peeve. This is the first I have heard of the updated pit, though I would be happy to include the mods in future releases. Perhaps it would drum up sales for RAZBAM as well.

I think the idea now is to keep everything to a minimum, with a focus on datafile tweaks. The idea is to make edits to files that aren't likely to change on a regular basis, so skins and 3rd party LODs are deemphasized. I believe that the stock aircraft are the ones receiving the most attention, though I doubt anybody has ruled out using stock LODs for different/additional variants. I think the plan for installable variants at this time is to have separate components that can be added based on what SF versions are currently installed (e.g. install this for SF2, install this for SF2V, etc.). Of course, we're not far enough along to set this approach in stone.

SupGen, I ran into that myself, and based on the information in EA-6B Prowler in Detail & Scale it appears that the EA-6A didn't have a visible RWR. I haven't been able to confirm this for the EA-6B Standard and EXCAP, but it looks as if there is no RWR display on the pilot side for either variant. Since I couldn't verify the non-existence of a visual RWR, I left the Standard and EXCAP variants as Vector type RWR in case people do have displays. Unfortunately, the "clock trick" from the 3W A-6 cockpit doesn't work with the RAZBAM cockpits since they display the entire panel, with the only components being the H/M/S needles and not the clock face itself.

Brennus, Rather than focusing on a single aircraft, why not touch on multiple aircraft across multiple theaters? The main loadscreen could have aircraft in use by both USAF and USN/USMC (e.g. F-4 and A-7). Throw on the Tomcat for another screen, the F-15A for another, the F-105 in SEA for another, etc.