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

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

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

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

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 RogueBeats
      Hi! Im pretty new in the community, but i am into sound and the game its actually really eazy to mod in that regard!

      So, im making a big sound mod with high quality samples from other games like BF4 and DCS. I´ve replacing a lot of sounds using a existing mod (Strike Figthers 2 Sounds)
      But maybe some of the sounds are still in the CAT files and i cant find them.

      Can someone help me extract all the stock Sound files from the Cat?
      Thank you.
      PD: also i plan put the Ace Combat Voices in the game but that sounds files are there.
    • By Rayensouissi2002
      I downloaded the mod in campaign ODS but the the mod doesn't show in the screen what should I do ?
    • By yunped
      V-1_JetBike.






    • By VonS
      Hello gents',
      A quick heads up for those running FE2 in WineSkin on a Mac - keep in mind that FE2 is a 32-bit program. MacOS 10.15 and later will not be supporting 32-bit programs anymore (only 64-bit). This of course is a problem considering that WineSkin (and other Wine programs for Macs) are currently 32-bit. While WineSkin may eventually go 64-bit (this is a slim possibility), there is no guarantee that 32-bit programs like FE/FE2 will be able to run in it even if it is 64-bit, considering that MacOS 10.15 and later are stripping out most if not all of the 32-bit code from their OS. This leaves Mac fliers of FE2 in a precarious position. Options are eventually to go over to Windows and drop fiddling with WineSkin, or to keep running your older Intel Macs (like my 2012 quad-core Mini), or grab another Mac and sort of future-proof yourself, with something like a Mac Pro or the newer Mac Mini (2018), providing you don't upgrade past MacOS 10.14 (last one to support 32-bit). SF2 by the way is 64-bit, and so is WOFFue - so those are good to go into the future of 64-bit OSes, on the Windows side. No guarantees that you will be able to fly WOFF/SF2 in future Mac OSes however because WineSkin may remain 32-bit only (no telling what's going to happen with Wine on a Mac at this point). Have been reading some forums that the Wine folks may move over to Linux entirely if the Mac world drops 32-bit...not good news for legacy simming/gaming. Anyway, I'll probably future-proof myself in some way with an extra Mac or two since I like running FE2 in WineSkin and there's no dropping FE2 once you get the modding bug.
      Happy flying,
      Von S
      UPDATE: The CodeWeaver folks working on CrossOver (a fork of Wine) may be developing a way for 32-bit code/libraries to be loaded into a 64-bit version of Wine - something that may eventually be ported to the general branch of Wine too - but again this is work in progress and no telling what will happen until the dust settles down over the next couple of years, in terms of 32-bit gaming on a Mac, in Wine. Linux has a 64-bit version of Wine that can load 32-bit code for older games, and it seems to have had this for several years already - but this is not relevant to gaming on a Mac. Will update this post further if any (good) news emerges.
×

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..