|
Fighter Ace II welcomes you to the best in online air combat!
Please read the following notes and information on the Beta release of Fighter Ace II, this information will explain the issues that the FAII team are aware of and will also provide you with information to improve your beta experience.
During the beta time period it is important to note that we may change settings and configurations at any time. We will provide you with as much information as possible during and after any changes that we make.
Please allow FA some moments to start from when you click Fly Now in the game room.
Contents:
- Setup.
- Hardware Requirements.
- D3d and Graphics information.
- Content Issues.
- Flight Model and Physics information.
- In-game help information.
- Scoring support.
- Replay issues.
- Training Mission information.
- Known Crash Reports.
1) Setup.
A) Install screen text misaligned.
Some of the installation screens are known to contain text that is not aligned correctly. This will be fixed with an overhaul of setup art pieces and layout. This will not be fixed until after beta.
2) Hardware Requirements.
A) Fighter Ace II Minimum Requirements for D3d users.
Multimedia PC with Pentium 166MHz or compatible processor
Microsoft Windows 95 or Windows 98 OS.
DirectX 6.1 or higher.
3-D Graphics Accelerator card or chipset compatible with Microsoft Direct3D version 6.1.
16 MB RAM or higher
35 MB of available hard disk space.
VGA monitor supporting 16-bit color and a resolution of 640 X 480.
28.8 Kbps Internet access.
Microsoft Internet Explorer 4.x, AOL 3.0 or higher, MSN 2.0 or higher, or Netscape 4.x.
Mouse or compatible pointing device.
B) Fighter Ace II Minimum Requirements for Software users.
Multimedia PC with Pentium 200MHz or compatible processor
Microsoft Windows 95 or Windows 98 OS.
DirectX 6.1 or higher.
PCI or VESA Video Adapter (VGA 256-color monitor, 640 x 480 display)
16 MB RAM or higher
35 MB of available hard disk space.
Monitor supporting 16-bit color and a resolution of 640 X 480.
28.8 Kbps Internet access.
Microsoft Internet Explorer 4.x, AOL 3.0 or higher, MSN 2.0 or higher, or Netscape 4.x.
Mouse or compatible pointing device.
C) Fighter Ace II recommended configuration.
Multimedia PC with PII 300 MHz or higher, or comparable processor.
Microsoft Windows 98 OS.
DirectX 6.1 or higher.
3-D Graphics Accelerator card or chipset compatible with Microsoft Direct3D version 6.1, with 16mb Video RAM.
64 MB System RAM or higher
35 MB of available hard disk space.
VGA monitor supporting 16-bit color and a resolutions up to 1024 X 768.
28.8 Kbps Internet access.
Microsoft Internet Explorer 4.x, AOL 3.0 or higher, MSN 2.0 or higher, or Netscape 4.x.
Mouse or compatible pointing device.
Force Feedback peripherals compatible to DirectX 6.1
DirectX 6.1 compatible sound card with speakers.
2) D3d and Graphics information.
Where there are known support issues, we have listed them. At this time in beta we have not covered all possible configurations, if the game will not run under D3d or Glide, software is nearly always supported. We will be working to fix these problems as soon they are known and verified.
Fighter Ace II needs the latest video drivers for your system to run correctly. When reporting issues with 3D accelerators and graphics, please be certain to have the latest drivers for your system installed.
For all cards using NVIDIA TNT chip sets, Fighter Ace II will be best supported using the latest drivers from NVIDIA, the NVIDIA Detonator drivers are available from Http://www.Nvidia.Com
A) Under Windows 95 with the desktop resolution running greater than 800 X 600 and the color depth greater than 256 colors, Fighter Ace II Beta 0 will crash to the desktop on first run.
To circumvent this problem run Win 95 using 256 colors. Fighter Ace II will then operate as intended.
B) STB Velocity 4400, Diamond Viper v550 produces missing textures.
Running under the Velocity 4400 or Diamond V550 manufacturer drivers, cockpit textures may not appear correctly, or may appear in flat beige coloring.
Using NVidia Detonator Drivers will correct this problem. NVidia Detonator drivers are not supported by Nvidia. For more information: Http://www.Nvidia.Com
C) Game freezes switching between Glide and D3d on Voodoo 1 and Voodoo 2 cards.
If a user flies with glide, and then exits to the menus and selects D3d running under same card, the game will freeze and the machine will need to be booted.
D) Task switching from flight with Voodoo 1 or 2 causes black desktop.
When alt-tabbing out of fighter ace in Glide on a voodoo 1 or 2, a black screen will be displayed instead of the Windows desktop. The user may alt-tab back into FA and continue to fly normal.
E) Voodoo3 Glide hang.
Running under 3dfx Voodoo3 will not support Glide. Direct 3D mode is available as is software.
F) Revolution IV will not launch in D3D mode.
Selecting D3d from the settings dialog will produce a crash to the desktop while using the Number Nine Visual Technology Revolution IV card.
G) D3d not available from Settings Dialog.
Upon starting the game for the first time, Fighter Ace will attempt to profile your 3D hardware to allow the best experience for the user. There is a known issue with this process that will disable 3D support within Fighter Ace II, when the card is actually known to support FAII. This is known to happen using Creative Labs Riva TNT card, or STB velocity 4400.
This problem is corrected with the NVIDIA Detonator drivers available from Http://www.Nvidia.Com.
H) Explosion effects under Permedia 2 cards
When running under Direct 3d, cards using the Permedia 2 chipset may show explosions over a wide area of terrain, not just on the area where impact occurred.
I) Cockpits under Glide are pixilated.
When running under glide, Cockpits will appear fuzzy and pixilated. This effect will be eliminated prior to release. This effect is not present running under D3d.
J) Profiler continues to run for each new game.
On some machine configurations, the profiler will continue to run each time the user goes into the game. Please report the configuration if this happens to you.
k) User allowed to select 1024x768 on Voodoo II card in D3D
In certain circumstances the profiler will not correctly disable support for 1024*768 resolutions. Running under D3d, the card will not support this resolution.
3) Content Issues.
A) Rear Cockpit views not complete.
Some rear views of cockpits are not complete at this time.
4) Flight Model and Physics information.
A) Certain aspects of the flight model is not yet fully determined and can be changed by us without warning. We do this to get different performance feedback before we settle on a static model for release.
5) Control Issues.
A) Logitech Wingman Force force feedback joystick produces no force feedback.
This stick will work fine as a joystick, but no forces are produced. We are working on this.
C) CH-Products Force-Feedback joysticks may not calibrate or function correctly.
6) In-Game Help issues.
A) No help topic for right click.
In the menu shell, help can be activated using right mouse click on most controls within each screen. Some controls do not have an associated help topic.
B) Right clicking on certain topics brings up the wrong help file or the help window opens and closes very quickly. This will be corrected for Beta 1. Use the Esc key to re-enable help. As an alternate method, any help topic can be reached via the Index Tab.
7) Scoring support.
Scoring is available within the game and shell for Fighter Ace II Beta. It is however only a demonstration of feature. No claim is made at this stage for accurate scoring. Player scores may change randomly within the Beta period, and are not supported as fully accurate. This is Beta, and the FAII team will be making changes on the back end during this time frame that will effect score recording and display.
Scores recorded in Beta will be erased and the database returned to state at the end of beta. In addition, we may wipe the database without warning at any time during the beta.
8) Replay issues.
A) Fighter Ace 1.5 film files will not play in Fighter Ace II.
B) Film files recorded in Fighter Ace II will not play in Fighter Ace 1.5
9) Training.
Training missions are available within Fighter Ace II Beta. These are not fully complete and are shown as a demonstration of feature.
A) Mission 1.
Some planes have only one Flap position, and when starting on the airfield, the flaps will already be lowered when the tutorial asks the user to lower the flaps.
B) Can't turn to face down the runway.
The tutorial may advise 50% thrust to turn onto the runway. Without using brakes, this may result in the plane crossing the airfield.
D) Demonstration Film files are not available in Fighter Ace II Beta. These will be implemented for Beta 1.
E) Re-spawning on the side of the runway, "inside" an AI aircraft, may result in a crash-loop (repeatedly re-spawning to side of runway, you receive a "you have crashed" message, re-spawn again, etc.). To fix this, got to the in-game menu, choose Settings, Arena Settings, and un-check the "Check Collisions On Ground" checkbox.
|
