Jump to content
  • Announcements

    • Erik

      2019 Drive   05/31/2019

      Can you lend a hand?  GET STARTED TODAY
  • Similar Content

    • By VonBeerhofen
      This screen's horizon has always been a problem and was showing black areas on the left and right. The screen became pretty important to me to quickly check objects from all sides to identify any R/S issues and fix them, without having to fly the game, altough that would work as well but you'd have to concentrate on not getting shot down. The introduction of EAWPRO's HiRes skysets and UHR horizon posed yet another problem in this screen, but have already been partially fixed a long time ago. However the horizon problem stayed and always kind of atracted attention away from the object or plane I was watching.
      I finally found a solution which fixes this problem in D3D mode (Glide is still incapable of using my UHR Horizons) and the fix was tested with various resolutions on two different machines using different monitors and was verified to work with both traditional monitors as well as HDMI. I couldn't check any other monitor types but my HDMI monitor accepts nearly all possible resolutions up to 1920 x 1280 and they all worked fine, with standard skysets as well as EAWPRO's HiRes sets. I can't test XVGA mode, just don't have the dosh to buy one, and besides that I'm very happy with what I have already and have no room for anything more anyway.
      These screens were taken in my most commonly used resolutions on either machine, not very important but educational.
      HDMI in 1280 x 768

      SVGA in 1024 x 768

    • By VonBeerhofen
      It's come to my attention that some people do not understand how to select the previously none flyable planes which are not directly accessible through the plane selection screen. They can be selected and edited from from within any hangar by selecting the MISSION PARAMETER editor that sits on each desk in any hangar. When in the Parameter Selection Screen you then select the LOAD option at the bottom of the screen and a list of MISSION (.MSN) files will be displayed. You can select any of them, no matter which hangar you're in. The Default** ones contain your last flown mission for each plane, sadly they don't give much information about which number corresponds to which plane but they're sequentially American, British, German.
      The ones which display their name were SAVED from within the parameterscreen, very usefull to setup planecombinations and targets that you like but can still edit after it's loaded. I could give you a list of the default numbers but I think you can also write each number down after selecting each and note the plane you've selected. If you want to fly Mosquitos you select Mosquito vs ******. You can also save the Default missions with a name yourself. To do this you start with loading Default00 and you save it under the name P38J vs WHATEVER. Having all planes there you can quickly navigate between planes and load any on the fly without having to go back to the plane selection screens.
      When a mission is SAVED it'll store all your selections and you can store up to 256 mission files yourself, either before or after the mission is flown. It's more convenient to do things this way and has become a real timesafer when testing all possible combinations. The saved missions remain unchanged untill they're overwritten with a new one but every time you load one it will randomise the target location as part of a new airfield and target check to prevent CTD's when .MSN files are corrupt, don't work, or aren't at all present (which is the case in nearly all old addons). When a certain plane's selection has become corrupt you can still get to it's Mission file via any other Hangar and set it right again by editing the corrupt plane's mission parameters, provided you understand which one to select. Flying the mission will overwrite the old Default**.MSN file and things will work normal from there on.
      Note that when you reselect the same target and/or airfield already present in a corrupt .MSN file, the selection can't be set since either of the two is an illegal choice. Just select another one which displays the target number on mouse over and the file should be fine from then on as the editor only allows legal targets to be selected. Illegal target locations are greyed out in the editor, an indication of a corrupt .MSN file. Sometimes they can still be flown and will allow take off from enemy bases or attacks on friendly ones, but being corrupt you may not be able to enter these plane's hangars on startup directly, except with this method.
    • By VonBeerhofen
      the original Microprose NoCD version from the Source Code is now implemented, making the the old NoCD hack redundant. It allows the game to run on newer operating systems, even when a CD drive isn't present. This change will be in the next release.
    • By VonBeerhofen
      intended for higher operating systems then XP. I managed to fix the lightning speed selection without compromising how it works on older systems, the only downside to it is that you need repeated mouseclicks to change the selections, holding down the mouse button will no longer incite the next successive selection. It applies to all keyboard input which uses this routine, possibly keyboard throttle and such too, but who's still using that option anyway? (retoric question)
      A big thx to Mark EAW who was so kind to test it's functionality!
    • By VonBeerhofen
      A new filter was programmed which allows more diverse maneuvering for the lower AI skill levels. Expert planes remain unaltered by the new filter. The lower skills now have a 10% chance to do expert moves when the enemy is within 2000 feet. Expert planes are programmed to enter this phase when the enemy is closer then 1000 feet, simply because they react faster then lower skills. Additionally, the lower skills can still optionally follow the original game's maneuvering phases when not selected by the random routine. This essentially seperates rookie pilots from the more skilled and asigns them to their own maneuvering phases with a newly added phase for the greenest, which wasn't there previously.
      In short, the lowest skill, which in v1.2 was set the same as medium, now has it's own maneuvering phases and criteria for carrying them out and with the medium skilled they have an additional random option to do expert moves if the enemy is closer then 2000 feet. An additional benefit of this is that planes are less likely to get stuck in a repetitive or endless loop, like endlessly flying circles around each other because the game only allows that one option for a particular skill level under certain circumstances. The random expert moves will make em do something entirely different.
      Another benefit is that these lower skill levels are more likely to react sooner when an enemy gets close, i.e. within 2000 feet. This behaviour changes real time and makes it much less predictable as to when the none expert planes will start using expert maneuvering or when they stop doing that. The routine doesn't influence the preprogrammed reaction times for each skill level, so inspite of being able to detect the enemy sooner their moves will remain as sluggish as in v1.2. You can't become an ace pilot in a single battle but you can occasionally do the right thing either by accident or by learning from mistakes.
      Furthermore the criteria calculation now also allows higher skill levels to be introduced (Advanced Criterium Emulation or ACE for short, :D), EAWPRO already has many provisions for this but it's only partially active due to a limitation in the cofiguartion screen to select only 3 skill levels. I hope full implementation will follow.
      How this will play out in the end is beyond my prediction but anyone with advanced knowledge on AI behaviour is welcome to write an essay about it, :)

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