Jump to content
  • Announcements

    • Erik

      2022 Support Drive   09/01/2022

      Our support drive for 2022 has kicked off. You can find out more about it here: Please Donate or Subscribe
VonBeerhofen

Fly EAWPRO at the EAW Launchpad

Recommended Posts

Visit the EAW Launchpad for online games with EAWPRO, have a chat with like minded or for help and guidance relating to v1.2 derivatives!

Teamspeak server details can be obtained via our (admission free) chatroom as it may change:

http://www.chatzy.com/251310437564

Just leave a message or e-mail adress in our chatroom and we'll get back to you ASAP.


Open all day ,no membership required, professional help or just a chat. And you can also have a look at my latest creations or just visit our screenshot gallery to get an impression of our games!

https://rabartel.home.xs4all.nl/test/Gallery/image/ 

[Linked Image]

VonBeerhofen

http://www.europeanairwar.net

Share this post


Link to post
Share on other sites

I'm coming, albeit at a slower pace than I'd like.  Soon.

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 VonS
      Hello Gents',
       
      I have been investigating the core string and ini files that make up FE2 - primarily to see if multiplayer can be reintroduced. The relevant files can be found in the MenuData.cat and MenuText.cat files of the "Menu" folder of the actual game (not in the user folder for the game).
       
      I managed to restore the "multiplayer" button to the main screen of the game, but it leads nowhere. Also possible to restore was the "network" button under the options settings - but again this led nowhere when you click on it.
       
      It seems that each STR (string?) file requires a corresponding INI (initialization) file to work at all. Most of the files have both components, such as is the case with OPTIONSSCREEN.INI and OPTIONSSCREEN.STR - the ini file contains the relevant buttons, lists, codes, placements, lots of other things too, and the str component file contains the relevant data calls that correspond with what is called for in the ini file.
       
      I was however stumped to find that most of the network sub-option files have the STR component files in place - but ini files for those are all missing, perhaps having been removed by the game designer - or perhaps there is a more obscure way of calling up those string files that I am not aware of with my very limited knowledge of program/app coding.
       
      As an example, the NETWORKCONNECTIONSCREEN.STR file and the NETWORK.STR file - obviously important ones (and it's obvious what they are for) - cannot be called up in game, likely because corresponding ini files for those are missing. Looking through some of those network option str files shows, in some cases, more than 30 or 40 different data calls. I can only imagine then how much time it would take to create corresponding ini files for all of those different data calls in the str files, with all of the relevant buttons, menus, submenus, toggles created in the corresponding ini files - to get mutliplayer up and fully functional in FE2 - a daunting task that while theoretically possible would probably take a good month at least of full-time work on it (and then there is the risk of how stable the setup would be when done).
       
      Those who are inclined to tinker further with multiplayer possibilities in FE2 are advised to look at the main Options.ini file first that's in the user folder for FE2. The multiplayer settings should read as follows to be enabled:
       
      [MultiplayerOptions]
      LobbyLaunched=TRUE
       
      The following should also be toggled but I didn't experiment with correct values:
       
      [Multiplayer]
      Connection=0
      PlayerColor=0
      SessionType=0
      GameType=0
      Password=MyPassword
      MaxPlayers=8
      IPAddress=127.0.0.1
       
      In the OPTIONSCREEN.INI file that should be extracted to your "Menu" folder, the following should be toggled:
       
      [NetworkOptionsButton]
      StickySelection=TRUE
      Active=TRUE
       
      In MAINSCREEN.INI, also to be placed in the "Menu" folder, the following should be toggled:
       
      [MultiplayerHotspot]
      Active=TRUE
      Enabled=TRUE
       
      Also, the following should be modified to look as you see here, from the same file indicated above:
       
      [MissionControl]
      SingleMission=SingleMission
      InstantAction=InstantAction
      Campaign=Campaign
      Multiplayer=Multiplayer
       
      And finally, the relevant STR files that are missing corresponding INI files - or maybe requiring some other kind of call that I'm not aware of, are:
       
      NETWORK.STR
      NETWORKCONNECTIONSCREEN.STR
      MPDOGFIGHTSCREEN.STR
      MPHANGARSCREEN.STR
      MPMISSIONSCREEN.STR
      MULTIPLAYERSTATUS.STR
      PILOTRECORDSCREEN.STR (this one is to enable flight recording in multiplayer)
       
      As far as I can see, it's more feasible to continue improving the single-player side of the game, such as improvements in AI, scenery, also the great plane and skin mods that often come out for FE2. And thanks to all who contribute to this game and make it great. Those interested in pursuing the multiplayer aspect further will hopefully find my post useful. I will not be pursuing this topic further since I don't consider the project to be worthwhile.
       
      Happy flying,
      Von S
       
    • By VonBeerhofen
      Thx to Erik and Stratos a special EAWPRO club was erected where further devellopment of my work can take place without unnecessary interruptions. Anyone is welcome to read it's contents which remains uncensored, but discussions are limited to members only and admittance to the club is exclusively under my control. Ofcourse crticism about EAWPRO can still be posted in the General EAW forum and when possible will be taken to heart. I'm sorry that there is no other way to present my work but it will not hamper further devellopment in any way.
      You can find the club through the forum's main page or by selecting CLUBS in the top from any page in the CA forum or by clicking the picture below:
       
    • By VonBeerhofen
      8 hours to unravel it's R/S secrets and 8 more to tweak the model into a light fleet/escort cariier. From here the model can be turned into any carrier class or split up into a multipart model. As a single 3DZ it can be a moving interdiction target (not landable) as well as a static target in harbours or alongside the coast. This is just a start as the model will be turned into a 100% model and It's texture will be upgraded soon.
      VonBeerhofen

      This picture shows the R/S check of a beached carrier with a few additions already :) The model will be added to PTIV as the new EAWPRO exe has freed a slot for an extra ship.

    • By VonBeerhofen
      The Reichenberg was the first and last plane I created in 2010, but with some recently acquired knowledge I felt the model should benefit from it, hence II. The initial model had it's cockpit more integrated into the fuselage but pictures show it was more of a small cubicle on top of the body. The old version also only used 6 sides and now 10. It may be further improved someday but for now this is where it stands. Weapons wil be added later too.
      As usual a rock solid R/S, new skin, semi 3D pilot (as in the Ohka) and dashboard (not visible yet in this picture but it's already there).
      VBH

    • By VonBeerhofen
      Derived from my Reichenberg and still carrying some of it's details but with a fully working Rendering Sequence. There is a pilot inside too but I couldn't use the Reichenberg's tranparency file but he's in there. The skin is largely from the Reichenberg with a white overlay and all colors removed from the plane and a quick Nippon dot replacing the German insignia. Later a proper skin with proper shading will be added but first the model needs to be tweaked so all V1 details are properly adapted to get the model as it should be. Notice that the model has 8 sides, like my Reichenberg, giving it a rounder shape then the stock V1. Couldn't squeeze more out of it due to the model's small size which limits the circumference of a circle polygon. However large planes can use this technique too and may be able to use 10 or 12 sides.
      VonBeerhofen



×

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