Wrench

Beaufighter force.. (what's funny, is that this pic shows the ENTIRE IDFAF Beau force!!!)

double click the lod viewer exe, navigate to the aircraft's folder in you game install double click the aircraft main ini viola! you can view it. not that hard, is it??

ok...after taking time to d/l the thing and examine the terrain...taking time from what I want to be doing (suffering from a bad cold...) open the Espana_data.ini, "search" for GermanyR-CG, and change the extension (tga) to bmp. That will fix your issue. YOu may also want to change the HasWater=1 to HasWater=0, as it ain't got none.

you haven't prepped the TE properly ..... you'll need to have all the tiles in bmp (convert the tgas) format, and placed within the TE's main folder. You'll need to build the texturelist ini by hand, using the data ini as the start point. You'll need the "espana" terrain folder as a sub-folder, stripped of all but the terrain's inis (mani ini, data,) , and the TFD and HFD. As I said before, the tile go "up on level" into the main TE folder I'd suggest reading Gepard's tutorial's in the 1stGen Knowledge base. What YOU are doing, is basically building a TE install that is JUST for the Spain terrain. I would also contact the "builder" of that terrain, and register your complaint. ALL SF TERRAINS ARE THE SAME-- they are all TFD/HFD based. The only exception is the IcelandNA terrain, with is LOD based. There are 2 3w terrain editors -- one for the "Desert" and the other for WoE,WoV,WoI -- the later is marginally better, as it has a better zoom function on the the TOD building screen. Terrain creation/editing is NOT for the faint of heart or unskilled -- it is the biggest, nastiest beast in the 3rd Wire world. If you screw something up, and don't have a backup -- it won't create it's own -- you can find yourself up the creek without a boat, let alone a paddle. Be VERY certain of what you're trying to accomplish.

like SF1/SF2, FE uses studio max to create the finished file (LOD). Other's have used other programs, like blender, but then THAT file has to be imported into MAX for "finalization" (for lack of a better term), and exportation into the LOD format the game uses.

that message happens ALL the time, even when the textures are present. the only way to see if a texture is present, is go through the terrain folder, and physically confirm it's existence. If one has the texture list ini for that terrain, you can scroll through that as well, to find out where in the data ini it's listed Another, easier way, is use the 3W terrain editor -- you'll have pink squares for missing tiles, that you can "click on" to get it's name.

JRL, you should wait until I get the 2 TF.X versions done!

ah, bummer!! well, one COULD extract them from the 1stGen cats (or pre-locked st2), rename them and drop them into the Tu-104's main folder...

nice to have you back with us!!

AFAIK, not that works with the new versions, and not on Win7. There used to be pilot editors, 15-20 years ago. Most sites are long gone... I have the same problem! Can't get past one Alliance mission (A-W, inspect and destroy freighters), and would like to see them all!

you do know that the Skyraider templates were made years ago, and are readily available, right??

File Name: SF2 WW2 ETO Bristol Beaufighter Mk.VIF (Late), v.9 by Cocas File Submitter: Wrench File Submitted: 01 January 2016 File Category: Other SF2 WW2 ETO Bristol Beaufighter Mk.VIF (Late), v.9 by Cocas 12/28/2015 -- Something for the WW2 ETO players -- = For SF2, Full-5 Merged (Reccomended/Preferred) = *This mod will =NOT= work in SF/Wo* 1stGen game installs, at any patch level. It was built for SF2 ONLY!!.* *Note x2: This mod represents the late production Beau Mk.VIFs for ETO and MTO** usage ONLY! Seperate versions for other theatres, and the later marks, will be released when and as they are finshed. We are calling this "version 0.9", as there exists the possibility of more work being required. But, we wanted to get them out into the hands of our WW2 End Users ™ for their examination, flying pleasures and so forth.* **= will require new squadron code and/or individual aircraft letter decals. But the paint scheme is the same for MTO usage. However, SEAC is completely different, and will require the release of a "theatre specific" version. This is a BRAND NEW aircraft, brought to you by Cocas Aircraft Factory & Co. This package contains 1 aircraft, representing the Beaufighter VIF fighter/intruder variant. This version =HAS= the dihedral horizontial stabs (they point up), the rear swivel MG mount, and the "thimble nose" AI/ASV type radar. The aircraft IS equipped to carry rockets as well as 2 bombs on the wing stations - but, obviously! not all at the same time!! Torpedo capability has been removed for this "Fighter/Intruder" version. This pack contains the following aircraft & skin/decal sets: Beaufighter Mk.V1F (late) Standard Day Scheme (Overall MSG/Dark Green disruptive) No. 604 Squadron "County of Middlesex" The Squadron Crest is used as the paint chip seen on the Loadout Screen. Skins are in jpg format, as are the bump maps. Everything is included (weapons, pilot figures, sounds, etc), excepting the guns (you should have all these already). All markings are decals, and decal randomization is set to TRUE. Other squadrons can easily be reproduced by creating new squadon code letters (either for ETO or MTO usage). As is my habit, a sample bmp is left in the Decals folder so you can match the font and size. All serials, while correct for the variant depicted, should be considered 'generic' in nature, as they represent no specific aircraft with the unit(s) represented. When in-game, you'll see: Beaufighter Mk.VIF (Thimble) (CAF) on the aircraft selection drop-down for this aircraft. The "CAF" (for Cocas Aircraft Factory) will diferentiate these Beaus from any others you may or may not have. It =IS= designed to replace any other Beaus of this type you may or may not have, from "other sources". The "thimble", of course, means this is the thimble-nosed radar equipped version (AI Mk.VIII). As always, fairly easy to follow, yet detailed install instructions are included. So, please =READ= them BEFORE installing this mod!!!. Also, give the "Notes" section a read too. Happy Hunting! Wrench Kevin Stein - for Cocas Aircraft Factory - Click here to download this file

correction to the fuselage cannon. I forgot about the shell casing ejection copy/paste the statements DIRECTLY OVER the existing ones in the data ini.... save the data ini, and that's it! My apologies for forgetting something as simple as this! A post on this subject, shell ejection corrections, for both the cannon and wing MGs (Mk.1 series) has been posted in the WW2 Forum's "Tips & Tweeks" thread

Correction/Fixes for Beaufighters by Cocas This fix adds the positions for the ejected shell casing for the fuselage cannon, on ALL versions (Mk.1, NF, VI, etc). REMINDER-- this is ONLY for those Beaus that Daniel and I have done. Do NOT use these setting for Capun's Beaus. When I was doing them I totallly forgot about the shell ejection.. On subsequent releases, (VIC, TFX) this will be corrected. copy/paste the statements below at the end of each Cannon statement in the data ini: [Cannon01] ---- EjectShells=TRUE EjectPosition=-0.41,0.93,-0.92 EjectVelocity= 0.0,0.0,-2.0 [Cannon02] ---- EjectShells=TRUE EjectPosition=0.50,0.93,-0.92 EjectVelocity= 0.0,0.0,-2.0 [Cannon03] ---- EjectShells=TRUE EjectPosition=-0.40,1.40,-0.96 EjectVelocity= 0.0,0.0,-2.0 [Cannon04] ----- EjectShells=TRUE EjectPosition=0.40,1.40,-0.96 EjectVelocity= 0.0,0.0,-2.0 ------- Below are the ejection position fixes for the wing mounted machine guns (all Mk.1 variants WITH the mgs) [LeftWingMG01] ----- EjectShells=TRUE EjectPosition=-5.09,2.75,-0.21 EjectVelocity= 0.0,0.0,-2.0 [LeftWingMG02] ---- EjectShells=TRUE EjectPosition=-4.80,2.75,-0.26 EjectVelocity= 0.0,0.0,-2.0 [RightWingMG01] ----- EjectShells=TRUE EjectPosition=5.07,2.75,-0.21 EjectVelocity= 0.0,0.0,-2.0 [RightWingMG02] ----------- EjectShells=TRUE EjectPosition=4.78,2.75,-0.26 EjectVelocity= 0.0,0.0,-2.0 [RightWingMG03] ----- EjectShells=TRUE EjectPosition=5.33,2.75,-0.17 EjectVelocity= 0.0,0.0,-2.0 [RightWingMG04] ----- EjectShells=TRUE EjectPosition=5.62,2.75,-0.12 EjectVelocity= 0.0,0.0,-2.0 my apologies for such an error!!

I also have a VIC (Coastal Command, torpedo armed) version, if anyone is interested in that one

converting the skins from jpg/dds to bmp format, and inis from Unicode to ANSI will do you no good, if as I said above, the LOD itself is in Unicode. There's no way to convert that, outside of 3dsMax.

might I suggest for the naval starfigher, keeping the single Vulcan gun, as was planned for it. MUCH easier to deal with, ini and skin wise!!

+1

as 98.6% of the new lods are in Unicode, they are unreadable by 1stGens. maybe it's time to think about evolving up to SF2??

as some folks have mentioned the lack of 'distance lods', I came up with this idea (below). Now, I haven't had a chance to test this, as I'm busy trying to get the next set of Beaufighters done and out...but, here goes... as the Tu-16 is pretty much part of all base SF2 installs (excpeting stock SF2V, but IS availalbe due the merging of cats), one can give this a try backup the main Tu-104.ini, for safety. Then, copy/paste the statements below over the existing lod listings: PLEASE experiment with the varying distances -- these are just 'WAGs' I did from the Badger's main ini. This should help with some of the visual stuff (maybe help with frame rates? ). Anyone that does test it, please report back, either here or in the main Mods/Skinning thread

cat file pointer must be incorrect also, make sure the Desert_Airfield***.ini (all 6) are present WITHIN the ANW terrain folder, if using something other than the Desert.cat pointer

but I do.... pm aces and see if he'll send it to you. if not, I will.

Anzac Strike Wing

ok, let's do this again... in a full-5 merged setup, the mission editor (if/when installed) is available in ALL 'versions' (read: mod folders). to have a naval group(s), the TERRAIN must be set up as "naval map = true", and have the proper zones set on the corresponding *name-of-terrain*_water.bmp. The minimum is 2, one for each side. There also must be enough "sea room" on the terrain to allow for them to spawn or be placed via the mission editor. (GermanyCE ain't got anything close to that) From what I've seen, the "cv zones" must be a minimum of 200km in radius (as the allows spawning of carrier based AWAC aircraft, that orbit at approx. 200km from the boat). So, in essence, if the terrain is NOT set for naval groups, they will not spawn properly* , if at all. * = they could appear anywhere on the terrain, most likely on dry land