Clown me hard!

[+Spectre_USA 7]

OK,

 

So I have a thing for the USAF, having done the deal for 14 fun-filled years, and wanted a new, exotic airframe flying the

USAF colors.

 

The J-20 is a neat beast, so I tried to do what I did when I converted the J-10 into an IAF Lavi.

 

It all works good, and shows up as the F-40 Warhawk II as I intended, except for 1 thing. The black skin is, well, black.

 

Well, the name is black, but it is a fine mottled grey when adorning the Chinese one. I changed everything in all INI's from

J-20 to F-40. I changed the names of all INI's to F-40. I even changed the lines in the OUT file, referring to the J-20.bmp,

and saved it in Unicode format.

 

Still a black, as opposed to a grey like the SF1 series, tone to the jet.

 

Where have I erred, kind sirs?

 

Once I get that sussed, I plan on pressing on with changing the loadout, loding scren, etc.

[FastCargo 412]

If it's black, it's because the skins aren't showing up at all...make sure the texture directory exists.

 

Also, the OUT file does nothing for you...its information only.

 

FC

[+Spectre_USA 7]

Oh, Vey!

 

Clown be hard?

 

I meant to say Clown me hard, as a take-off of readme's given occasionally.

 

`Be' just doesn't sound Cricket.

 

A thousand pardons...

[+Spectre_USA 7]

If it's black, it's because the skins aren't showing up at all...make sure the texture directory exists.

 

Also, the OUT file does nothing for you...its information only.

 

FC

 

I did not know that, as they are a rarity.

 

Anyway, there is a directory, with F-40.bmp called "black," case sensitive, in the F-40 directory.

 

I did change it to USAF, was Israel, in the INI, and the squadron to the 431TFS. The LOD hasn't changed.

[+Brain32 265]

Hmm first of all - J-20?

 

Now second is if you change the name of the texture(from J-20.bmp to F-40.bmp) then you need to change the name in the *.lod file too with the hex editor, the *.out file has no effect on the game...

[+Spectre_USA 7]

Hmm first of all - J-20?

 

Now second is if you change the name of the texture(from J-20.bmp to F-40.bmp) then you need to change the name in the *.lod file too with the hex editor, the *.out file has no effect on the game...

 

Yessir, the very finely crafted Lurking Dragon.

 

I was afraid it would take an edit in the LOD file. I haven't monkeyed with a HexEditor in a

lot of years.

 

I'll probably just name it back to J-20, or learn myself hex editting again, after making

back-ups of back-ups!

 

Cheers for the insight...

 

PS-Thanks for the hand, whoever changed the subject line!

Edited January 6, 2011 by Spectre_USA

[Wrench 9,559]

why f*** around with hex editing lods??? All you need to do, is reanme the inis, change the nation for whom ever is using it (service-wise). Leave the lods and skin bmp names alone. Let everything point to how is stock. Everything can be done with ini edits, via the data, main, and textureset ini. Don't forget to re-wite the decals ini to get the correct 'new' nation's markings.

 

didn't I write a tutorial on creating "nationalized" aircraft for the 1stGen KB???

 

wrench

kevin stein

 

EDIT: took some digging, but here's the link:

 

http://combatace.com/topic/19469-how-to-create-a-country-specific-aircraft/

Edited January 6, 2011 by Wrench

[+Spectre_USA 7]

Cheers Kevin,

 

I just wanted a clean and pristine folder called "F-40" with no reference to any Chinese aircraft.

 

I'll just name the skin back, as all else works OK.

 

As to the decals, there are none, at least there is no decals.ini.

 

I may have to hand map them, which as you know, is a tedious and time-consuming endeavor from scratch, but it would be a

worthy stablemate for the F-22 and F-35, IMHO.

 

Maybe I'll even gin up a goofy little story to how it came to be, or summat...

 

[Wrench 9,559]

I just wanted a clean and pristine folder called "F-40" with no reference to any Chinese aircraft

 

which is exactly what that tut will accomplish. Trust me, brother!!! I've done it dozens of times!! The game dosen't care what the skin or lod is called -- it's all in the ini (as opposed to the wrist). All the names stay the same!!

 

Here's a screenie of the best example I can think of... from my WW2 MTO install. A Spitfir Mk.VB (Trop), for the USAAF.

 

in the main ini:

[AircraftData]

AircraftFullName=Spitfire Mk.VB Trop (USAAF)

AircraftDataFile=Spitfire5BT_DATA.ini

CockpitDataFile=Spitfire5Bt_cockpit.ini

LoadoutFile=Spitfire5BT_LOADOUT.INI

LoadoutImage=Spitfire5BT_LOADOUT.bmp

HangarScreen=AAF_Spit5_Hangar.bmp

LoadingScreen=

 

[LOD001]

Filename=SpitfireVBt-R14.lod

Distance=250

 

[LOD002]

Filename=SpitBt-MR8.lod

Distance=500

 

[LOD003]

Filename=SpitBt-MR6.lod

Distance=1000

 

[LOD004]

Filename=SpitBt-MR4.lod

Distance=2000

 

[LOD005]

Filename=SpitBt-MR2.lod

Distance=8000

 

and the data ini:

 

[MissionData]

NationName=USAF

ServiceStartYear=1942

ServiceEndYear=1945

AircraftRole=FIGHTER

AircraftCapability=DAY_ONLY

Availability=COMMON

Exported=FALSE this bit IS important!! no exportation!!

ExportStartYear=

ExportAvailability=

PrimaryRoles=SWEEP,CAP,INTERCEPT,ESCORT

SecondaryRoles=ARMED_RECON,RECON,SEAD

NormalMissionRadius=318.00

MaxMissionRadius=462.50

Ceiling=11275.00

MinBaseSize=SMALL

 

It's so simple, once you do it, you'll kick yourself as to how easy it is.

 

wrench

kevin stein

Edited January 6, 2011 by Wrench