Jump to content

Recommended Posts

I have done an experiment to get "First Eagles 2" objects into "Strike Fighters 2" and would like to ask if anyone would be willing to try it and corroborate my findings?

 

 

To do this experiment you first need to own legal copies of both FE2 and SF2 5 full/merged.

 

 

Next you need to do the following procedure.

 

 

Copy “AvionicsWWI.dll” and “wwiComm.dll” from “C:\Program Files (x86)\ThirdWire\First Eagles 2\Flight” to “C:\Program Files (x86)\ThirdWire\Strike Fighters 2\Flight” then do the same for “wwiCambrai.CAT” and “wwiVerdun.CAT” from “C:\Program Files (x86)\ThirdWire\First Eagles 2\Terrains” to “C:\Program Files (x86)\ThirdWire\Strike Fighters 2\Terrains”.

 

 

Now for the complicated part, extract everything from your SF2 ObjectData004.CAT, ObjectData005.CAT, ObjectData006.CAT, and ObjectData015.CAT. You will need to place these extracted .TGA files into your MODS directory Decal folder as these CAT files will not be available when you are done.

 

 

Then take the four ObjectData CAT files that you just extracted everything from, and move them from the “C:\Program Files (x86)\ThirdWire\Strike Fighters 2\Objects” folder to a safe backup folder elsewhere on your hard drive.  

 

 

Next copy all four ObjectData CAT files from “C:\Program Files (x86)\ThirdWire\First Eagles 2\Objects” to a separate safe folder. Once copied, rename the copied FE2 CAT files to match the four CAT files that you removed from the “Strike Fighters 2\Objects” folder, like so…

 

 

ObjectData001.CAT ----> ObjectData004.CAT

 

ObjectData002.CAT ----> ObjectData005.CAT

 

ObjectData003.CAT ----> ObjectData006.CAT

 

ObjectData004.CAT ----> ObjectData015.CAT

 

 

Be careful about the renaming due to both the old and new file names having one file named "ObjectData004".   

 

Now cut and past the renamed copies into “C:\Program Files (x86)\ThirdWire\Strike Fighters 2\Objects”. We are now done with the Install directory.

 

At this point I recommend that you copy the stock Aircraft, GroundObjects, Guns, and Weapons from your FE2 mod directory and paste them into the SF2 mod directory that you intend to use for the experiment. I have attached the FE2 stock Aircraft, GroundObjects, Guns, and Weapons INI files if you don’t want to go through the trouble of generating them yourself.

 

 

If all the above worked out, you should have the “First Eagles 2” stock Aircraft, GroundObjects, Guns, Weapons, and Terrain available for use in SF2.

 

Please let me know how this works for you.

 

 

Note1: You may need to extract everything from the terrain CAT’s “wwiCambrai.CAT” and “wwiVerdun.CAT” into your SF2 mod Terrain folder to fix some terrain issues.

 

 

Note2: In order to get a fully working FE2 install, not just having the objects, weapons, and terrain available requires a lot more extracting and editing of FE2 INI files for SF2.

 

FE2 Objects Folder.7z

 

post-56847-0-64738400-1418080355_thumb.jpg

 

post-56847-0-22433900-1418080378_thumb.jpg

  

 

  • Like 1

Share this post


Link to post
Share on other sites

ive got some terrains into sf2 but they need some items from fe effects etc  and work to a degree.wwicambrai wwiverdun and galicia..also some gliches like runways appear oddly i forget what else went askew

Edited by russouk2004

Share this post


Link to post
Share on other sites

Sound a bit difficult...  Do we need everything from the CAT files?  Because there is a lot of files in the CAT which cannot be extracted, and are hidden to the official  extractor...

Share this post


Link to post
Share on other sites

Yes, you'd need EVERYTHING from all the cat files. LODS especially. This goes for the terrains as well, but that can be "adjusted" by simply creating a terrain subfolder, and dropping the terrain's cat file INTO the named terrain folder. Just like how 1stGen SF/FE did.

 

I would think that a better way, albeit not easier, would be after extraction, the put the various objects into the actual folders where they'd be needed.

Aircraft lod (D7.lod) into the /DVII folder), the cockpit lod and all the various bits into the /cockpit folder and so on.  Same thing for all the decals. Be more work, but would be simplier in the long run to folderize them, and simply rewrite the decals inis

Share this post


Link to post
Share on other sites

i did whit SFP1 and FE1 all but the dlls after some edits to the nations ini and all decals inis very thing work but the FPS whit the Terrain but i was whit a 128mb ati 9200 and p4 2.8g whit 512 ram but aircraft work just need a shitload of edits

Share this post


Link to post
Share on other sites

Yes, you'd need EVERYTHING from all the cat files. LODS especially. This goes for the terrains as well, but that can be "adjusted" by simply creating a terrain subfolder, and dropping the terrain's cat file INTO the named terrain folder. Just like how 1stGen SF/FE did.

 

I would think that a better way, albeit not easier, would be after extraction, the put the various objects into the actual folders where they'd be needed.

Aircraft lod (D7.lod) into the /DVII folder), the cockpit lod and all the various bits into the /cockpit folder and so on.  Same thing for all the decals. Be more work, but would be simplier in the long run to folderize them, and simply rewrite the decals inis

 

Interesting.  I fooled around with FE1 and SF1 some years ago when there was less of a difference in file organization.  Since returning to TW sims, I have not done the same with the newer editions - I did not realize there was THAT much difference between FE2 and SF2.

Share this post


Link to post
Share on other sites

Yes, you'd need EVERYTHING from all the cat files. LODS especially. This goes for the terrains as well, but that can be "adjusted" by simply creating a terrain subfolder, and dropping the terrain's cat file INTO the named terrain folder. Just like how 1stGen SF/FE did.

 

I would think that a better way, albeit not easier, would be after extraction, the put the various objects into the actual folders where they'd be needed.

Aircraft lod (D7.lod) into the /DVII folder), the cockpit lod and all the various bits into the /cockpit folder and so on.  Same thing for all the decals. Be more work, but would be simplier in the long run to folderize them, and simply rewrite the decals inis

arent FE2s lods locked liked SF2s are?

Share this post


Link to post
Share on other sites

arent FE2s lods locked liked SF2s are?

No. That title was released before the fhit hit the san.

Share this post


Link to post
Share on other sites

Ahh. Ok I though I need to extract SF2 ... but if FE2 is extractable, then no prob.

 

I did some experiments with a FE2 biplane FM to use with helicopters,   which have serious problems with landing when controlled by the AI.  Not much luck to figure out what is causing the problem(

Share this post


Link to post
Share on other sites

iirc you can add path in the ini toi point to new location of the cats

Share this post


Link to post
Share on other sites

I don't want to hijack this thread, but you guys are discussing stuff that I have some questions about - maybe you can answer them?  I am thinking about a 1940 desert mod for FE2 that features biplanes as the main actors, but also has a few monoplanes.  Years ago, I tested biplanes in the old FE1 and SF1, and FE1 had better handling characteristics for biplanes.  Since returning to modding FE2, I have not had time to make the same comparisons.  Is FE2 still better at simulating the handling characteristics of biplanes or has this difference gone away because TK improved the SF2 code?

 

Also, I may have something to contribute.  When I asked about retractable landing gear in FE, I found out that TK did not strip the code out of FE.  Its still there, as the flaps and gear still work in autopilot, and another guy says you can restore manual control by adding command lines:

 

I am not 100% sure but I think you can have landing gears in FE/FE2 but just adding a couple of command lines in the Control\Default.ini file

I know there are other commands that are not enabled in FE/FE2 that I turned on in the past by just adding those command lines.

I think these commands (and others) are not in the Default.ini

FLAPS_DOWN=JOYSTICK02_BUTTON10
FLAPS_UP=JOYSTICK02_BUTTON09
AIRBRAKES_TOGGLE=JOYSTICK02_BUTTON21
WHEELBRAKES_TOGGLE=JOYSTICK02_BUTTON20
LANDING_GEARS_TOGGLE=JOYSTICK02_BUTTON22

 

If this information is correct, perhaps other functionality can be restored to FE2 by adding appropriate command lines?  If so, then FE2 would seem to have some real advantages.  Many files have not been locked, as in SF2, and - if using the same size terrain artwork - FE2's smaller terrain tiles display more detail than SF2's larger terrain tiles.

Share this post


Link to post
Share on other sites

 

arent FE2s lods locked liked SF2s are?

 

Don't say that too loud ... cause it'll get patched and locked.

 

You need to use Gerwin's extractor, and it pulls EVERYTHING

Actually I think it would work better the other way around, as SF2 has some FE2 coding in it.

 

But it's definitely worth experimentating with in BOTH directions

Share this post


Link to post
Share on other sites

Don't say that too loud ... cause it'll get patched and locked.

 

You need to use Gerwin's extractor, and it pulls EVERYTHING

Actually I think it would work better the other way around, as SF2 has some FE2 coding in it.

 

But it's definitely worth experimentating with in BOTH directions

 

What FE code does SF contain?

Share this post


Link to post
Share on other sites

Gun unjam and reload, though the statements for them need to added to the objects/aircraftobject.ini and control/default.ini files.

Share this post


Link to post
Share on other sites

Gun unjam and reload, though the statements for them need to added to the objects/aircraftobject.ini and control/default.ini files.

 

Thanks.  Are you the guy that got landing gear to work in FE?

Share this post


Link to post
Share on other sites

Thanks.  Are you the guy that got landing gear to work in FE?

Not that I can recall.

Share this post


Link to post
Share on other sites

Guess I was misinformed. :blink:

Share this post


Link to post
Share on other sites

In FE the landing gears, airbrakes, flaps of planes worked perfect. I had a FW-190 there and some MiG's worked very well. Even guided missiles for an AH-64 or a Mi-24 worked perfect in FE.

Screenshot of two Mi-24 in First Eagles

 

post-3395-0-32697900-1418237897_thumb.jpg

 

 

Dont know wheter it is in FE2 the same. But give it a try.

 

That are the entries of my modern days FE controls

 

[ControlSet001]
EXIT_FLIGHT=ESCAPE
QUIT_GAME=ALT+Q
PAUSE_FLIGHT=ALT+P
TIME_COMPRESSION=ALT+T
NORMAL_TIME=ALT+R
CHANGE_TIME=ALT+C
SKIP_TO_NEXT=ALT+N
RADIO_COMM=TAB
CHAT_ALL=GRAVE
CHAT_ENEMY=SHIFT+GRAVE
CHAT_FRIENDLY=CTRL+GRAVE
CHAT_TARGET=ALT+GRAVE
AUTO_PILOT=A
WING_LEVELER=SHIFT+A
NEXT_WAYPOINT=W
PREV_WAYPOINT=SHIFT+W
MAP=M
SCREEN_SHOT=PRINTSCREEN
DEBUG_TOGGLE=CTRL+H
GOTO_COCKPIT_FRONT_VIEW=F1
GOTO_COCKPIT_LEFT_VIEW=F2
GOTO_COCKPIT_RIGHT_VIEW=F3
GOTO_COCKPIT_UP_VIEW=SHIFT+F1
GOTO_VIEW_PADLOCK=F4
TOGGLE_COCKPIT=NUMPADPERIOD
SNAP_VIEW_FRONT=NUMPAD8
SNAP_VIEW_FRONT_RIGHT=NUMPAD9
SNAP_VIEW_RIGHT=NUMPAD6
SNAP_VIEW_REAR_RIGHT=NUMPAD3
SNAP_VIEW_REAR_LEFT=NUMPAD1
SNAP_VIEW_LEFT=NUMPAD4
SNAP_VIEW_FRONT_LEFT=NUMPAD7
SNAP_VIEW_UP=NUMPAD5
SNAP_VIEW_DOWN=NUMPAD0
GOTO_VIEW_SHOULDER=F5
GOTO_VIEW_OBJECT_NEXT=F6
GOTO_VIEW_OBJECT_PREV=SHIFT+F6
GOTO_VIEW_GROUND_OBJECT_NEXT=F7
GOTO_VIEW_GROUND_OBJECT_PREV=SHIFT+F7
GOTO_VIEW_TARGET=F8
GOTO_VIEW_PLAYER_TO_TARGET=SHIFT+F8
GOTO_VIEW_TARGET_TO_PLAYER=CTRL+F8
GOTO_VIEW_WEAPON=F9
GOTO_VIEW_PLAYER_TO_WEAPON=SHIFT+F9
GOTO_VIEW_WEAPON_TO_PLAYER=CTRL+F9
GOTO_VIEW_FLYBY=F10
GOTO_VIEW_FLYBY_PREV=SHIFT+F10
GOTO_VIEW_TOWER=F11
GOTO_VIEW_TOWER_PREV=SHIFT+F11
GOTO_VIEW_ACTION_CAM=F12
GOTO_FREE_VIEW=CTRL+F12
CAMERA_PITCH_UP=JOYSTICK01_POV01_UP
CAMERA_PITCH_DOWN=JOYSTICK01_POV01_DOWN
CAMERA_YAW_RIGHT=JOYSTICK01_POV01_RIGHT
CAMERA_YAW_LEFT=JOYSTICK01_POV01_LEFT
CAMERA_ZOOM_IN=MOUSE_BUTTON01
CAMERA_ZOOM_OUT=MOUSE_BUTTON02
CAMERA_PITCH_AXIS=MOUSE_Y-AXIS
CAMERA_YAW_AXIS=MOUSE_X-AXIS
CAMERA_ZOOM_CONTROL=
PITCH_UP=DOWNARROW
PITCH_DOWN=UPARROW
ROLL_RIGHT=RIGHTARROW
ROLL_LEFT=LEFTARROW
YAW_RIGHT=PERIOD
YAW_LEFT=COMMA
THROTTLE_UP=EQUALS
THROTTLE_DOWN=MINUS
THRUST_VECTOR_UP=CTRL+EQUALS
THRUST_VECTOR_DOWN=CTRL+MINUS
FLAPS_DOWN=F
FLAPS_UP=V
AIRBRAKES_TOGGLE=S
WHEELBRAKES_TOGGLE=B
LANDING_GEARS_TOGGLE=G
ARRESTER_HOOK_TOGGLE=H
CYCLE_NAV_LIGHT=CTRL+L
DRAG_CHUTE=CTRL+B
EJECT=ALT+B
PITCH_CONTROL=JOYSTICK01_Y-AXIS
YAW_CONTROL=
ROLL_CONTROL=JOYSTICK01_X-AXIS
THROTTLE_CONTROL=JOYSTICK01_U-AXIS
THRUST_VECTOR_CONTROL=
NEXT_AA_WEAPONS=JOYSTICK01_BUTTON03
PREV_AA_WEAPONS=SHIFT+BACKSPACE
NEXT_AG_WEAPONS=JOYSTICK01_BUTTON04
PREV_AG_WEAPONS=SHIFT+BACKSLASH
FIRE_PRIMARY_GUN=JOYSTICK01_BUTTON01
FIRE_SECONDARY_GUN=
FIRE_WEAPON=JOYSTICK01_BUTTON02
UNJAM_GUN=SHIFT+JOYSTICK01_BUTTON03
OPEN_BOMBBAY_DOOR=CTRL+O
DROP_TANKS=CTRL+D
JETTISON_STORES=CTRL+J
NEXT_RIPPLE_QUANTITY=RBRACKET
PREV_RIPPLE_QUANTITY=SHIFT+RBRACKET
NEXT_RIPPLE_INTERVAL=LBRACKET
PREV_RIPPLE_INTERVAL=SHIFT+LBRACKET
NEXT_HUD_MODE=APOSTROPHE
PREV_HUD_MODE=SHIFT+APOSTROPHE
NEXT_GUNGROUP=SEMICOLON
PREV_GUNGROUP=SHIFT+SEMICOLON
CHAFF=C
FLARE=X
ECM_TOGGLE=Z
TOGGLE_RADAR=CTRL+PGUP
NEXT_RADAR_MODE=PGUP
PREV_RADAR_MODE=SHIFT+PGUP
NEXT_RADAR_RANGE=PGDN
PREV_RADAR_RANGE=SHIFT+PGDN
SELECT_NEXT_RADAR_TARGET=HOME
SELECT_PREV_RADAR_TARGET=SHIFT+HOME
ACQUIRE_RADAR_TARGET=INSERT
ACQUIRE_VISUAL_TARGET_ON_RADAR=SHIFT+INSERT
REJECT_RADAR_TARGET=DELETE
SELECT_CLOSEST_CENTER=NUMPADSTAR
SELECT_TARGET=T
SELECT_PREV_TARGET=SHIFT+T
SELECT_CLOSEST_TARGET=CTRL+T
SELECT_FRIENDLY=Y
SELECT_PREV_FRIENDLY=SHIFT+Y
SELECT_CLOSEST_FRIENDLY=CTRL+Y
SELECT_GROUND=E
SELECT_PREV_GROUND=SHIFT+E
SELECT_CLOSEST_GROUND=CTRL+E
SELECT_LAST_RADIO=R
SELECT_LAST_RADIO_CALLER=SHIFT+R
SELECT_RADAR_TARGET=CTRL+R
SELECT_WAYPOINT=CTRL+W
DESELECT_TARGET=
ANIMATION_1=
ANIMATION_2=
ANIMATION_3=
ANIMATION_4=
ANIMATION_5=
ANIMATION_6=
ANIMATION_7=
ANIMATION_8=
ANIMATION_9=
ANIMATION_10=

[ControlSet002]
FIRE_PRIMARY_GUN=SPACE
FIRE_WEAPON=RETURN

[RangedControl001]
AxisControl=PITCH_CONTROL
MaxValue=1000.000000
MinValue=-1000.000000
DeadZone=10.000000
Saturation=100.000000
ReverseJoystick=TRUE
MouseScale=1.000000
UseMouseRate=FALSE
ReverseMouse=FALSE
LimitValue=TRUE
SelfCenterRate=2.000000
KeyControlRate=1.000000
AllowKeyControl=TRUE
IncreaseControl=PITCH_DOWN
DecreaseControl=PITCH_UP
CenterControl=

[RangedControl002]
AxisControl=YAW_CONTROL
MaxValue=1000.000000
MinValue=-1000.000000
DeadZone=10.000000
Saturation=100.000000
ReverseJoystick=FALSE
MouseScale=1.000000
UseMouseRate=FALSE
ReverseMouse=FALSE
LimitValue=TRUE
SelfCenterRate=2.000000
KeyControlRate=1.000000
AllowKeyControl=TRUE
IncreaseControl=YAW_RIGHT
DecreaseControl=YAW_LEFT
CenterControl=

[RangedControl003]
AxisControl=ROLL_CONTROL
MaxValue=1000.000000
MinValue=-1000.000000
DeadZone=10.000000
Saturation=100.000000
ReverseJoystick=FALSE
MouseScale=1.000000
UseMouseRate=FALSE
ReverseMouse=FALSE
LimitValue=TRUE
SelfCenterRate=2.000000
KeyControlRate=1.000000
AllowKeyControl=TRUE
IncreaseControl=ROLL_RIGHT
DecreaseControl=ROLL_LEFT
CenterControl=

[RangedControl004]
AxisControl=THROTTLE_CONTROL
MaxValue=1000.000000
MinValue=0.000000
DeadZone=10.000000
Saturation=100.000000
ReverseJoystick=TRUE
MouseScale=1.000000
UseMouseRate=FALSE
ReverseMouse=FALSE
LimitValue=TRUE
SelfCenterRate=0.000000
KeyControlRate=1.000000
AllowKeyControl=TRUE
IncreaseControl=THROTTLE_UP
DecreaseControl=THROTTLE_DOWN
CenterControl=

[RangedControl005]
AxisControl=CAMERA_PITCH_AXIS
MaxValue=1000.000000
MinValue=-1000.000000
DeadZone=10.000000
Saturation=100.000000
ReverseJoystick=FALSE
MouseScale=0.200000
UseMouseRate=TRUE
ReverseMouse=FALSE
LimitValue=FALSE
SelfCenterRate=50.000000
KeyControlRate=2.000000
AllowKeyControl=TRUE
IncreaseControl=CAMERA_PITCH_DOWN
DecreaseControl=CAMERA_PITCH_UP
CenterControl=

[RangedControl006]
AxisControl=CAMERA_YAW_AXIS
MaxValue=1000.000000
MinValue=-1000.000000
DeadZone=10.000000
Saturation=100.000000
ReverseJoystick=FALSE
MouseScale=0.250000
UseMouseRate=TRUE
ReverseMouse=FALSE
LimitValue=FALSE
SelfCenterRate=50.000000
KeyControlRate=2.500000
AllowKeyControl=TRUE
IncreaseControl=CAMERA_YAW_RIGHT
DecreaseControl=CAMERA_YAW_LEFT
CenterControl=

[RangedControl007]
AxisControl=CAMERA_ZOOM_CONTROL
MaxValue=1000.000000
MinValue=-1000.000000
DeadZone=0.000000
Saturation=100.000000
ReverseJoystick=FALSE
MouseScale=1.000000
UseMouseRate=FALSE
ReverseMouse=FALSE
LimitValue=FALSE
SelfCenterRate=100.000000
KeyControlRate=5.000000
AllowKeyControl=TRUE
IncreaseControl=CAMERA_ZOOM_IN
DecreaseControl=CAMERA_ZOOM_OUT
CenterControl=

[RangedControl008]
AxisControl=THRUST_VECTOR_CONTROL
MaxValue=1000.000000
MinValue=0.000000
DeadZone=10.000000
Saturation=100.000000
ReverseJoystick=TRUE
MouseScale=1.000000
UseMouseRate=FALSE
ReverseMouse=FALSE
LimitValue=TRUE
SelfCenterRate=0.000000
KeyControlRate=1.000000
AllowKeyControl=TRUE
IncreaseControl=THRUST_VECTOR_UP
DecreaseControl=THRUST_VECTOR_DOWN
CenterControl=
 

Edited by Gepard

Share this post


Link to post
Share on other sites

Wow!  Great information. Thanks.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Similar Content

    • By JamesWilson
      Hi,
      after seeing the TMF F-14 has wrong and inaccurate speed and fuel indicators, i found out the default Third Wire F-14 has working and accurate ones, but i dont wanna use it cause the TMF Tomcat is better and the cockpit too more realistic too, so can you switch the speed and fuel indicators on the TMF F-14 with the default Third Wire F-14? And for fuel too? Do you need to 3D model and/or do something else other than edit some text files?
       And is it or it's not possible to do?
      Down here are 2 pictures from the correct cockpit in the default Third Wire F-14:


      And 2 from the TMF F-14 (the inaccurate one):


       
      Thanks for helping.
    • By JamesWilson
      Hi everyone,
      I just noticed that the speed indicator in the F-14 Tomcat by TMF (TheMirageFactory) only shows up to 800 kts, and the Mach indicator does not move, not letting you know the speed of the aircraft if you have your HUD turned off.
      As you can see down here, i'm at Mach 2.23, but the indicator only shows 800 kts and doesn't go above. Obviously it adapts to my altitude, so if i'm higher, then the IAS is lower, but still should move, making it impossible flying at high speed without HUD turned on as i have it down here:

      Another issue, maybe even worse than the previous one, is that the fuel indicator shows wrong numbers, or as i may think, it shows "a number less". For example: if i have 20000 pounds of fuel left, it should show 20000, but it shows 02000. This is a theory on how it works, not confirmed, and i'm gonna explain you why i think it is like that:
      I hardly think i truly have 2000 pounds of fuel left, cause i choose Fuel 100% and tried climbing and flying for a long time with full afterburner, and the numbers slowly started going down, even reached the point of burning the engine at Mach 2.30and the fuel wasn't gone yet, it showed i had like 00700 left, so i presume it's 20000 in reality, otherwise i would have been out of fuel in no time, since it's a quantity even under the bingo quantity, but i flew for minutes and minutes in full afterburner, and at 8x speed, so. Speaking of Bingo, there's no bingo indicator.
      Here's a picture of the fuel indicator:

      I tried the default F-14 cockpit, and even if that one shows correctly both speed and fuel indicators and even if it's a great cockpit, i personally like more and find more realistic and immersive the TMF one.
      In the end, since these two indicators are crucial, especially for flying without HUD, and the fuel indicator especially, since there's no way to know how much fuel you have left even with HUD turned on other than the cockpit indicator.
      So, what i'm asking is:
      Is there a way to fix these? A mod that remakes the indicators? Or another cockpit that is not the default one that i can use to swap this one?
      Thanks in advance for helping me.
    • By JamesWilson
      Hi everyone,
      I was wondering how to customize the numbers after your callsigns, since it always gives me the same ones.
      I think i managed somehow once, a bit of time ago, but now i forgot and have no idea how to.
      I'm not talking about how to customize the callsign name, but the unit number after it.
      As you can see in the Roster and in the picture under, i get "Fast Eagle 1-1" and "Fast Eagle 1-2"
      Here are some examples:


      The numbers on the tail, wing and nose numbers are customized, cause i managed how to change them, choosing them individually for each unit in the mission file by changing "AircraftNumber=" and typing the number, like "2" (as for 202). It doesn't change by typing the whole number tho, like 202 by typing 202, but it goes by typing the number that corresponds to the list of numbers you have. For example, In a list that goes from 200 to 400, you will have to type 10 to get 300. Here i just typed "2" and "7" since the list starts from 200


      IIRC, in the past i just used to type the Aircaft number just like that, and in-game i had the proper number after the callsign, like "Fast Eagle 102", not just the number displayed on the plane livery.
      How do i do? I'm pretty sure that it's possible to have "Fast Eagle 102" on my screen HUD and in the Roster
      Thanks in advance for helping me.
       
×

Important Information

By using this site, you agree to our Terms of Use, Privacy Policy, and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..