vonbikia

Correction - the missiles might work fine! The question is the threatening range is a little bit "magnified". When the impact of missiles is estimated 10 seconds for me, it's actually around 30 seconds. That means it travel slower. In this exponential, you have to wait longer for performing your avoidance maneuvering, but in the mean time, the beam way averting will be much easier. And it really works! When you hold it until the missiles close the appropriate range, only suitable maneuverings will be enough for get rid of these missiles, application of countermeasures will be the best. No more shadowing phenomenon exists in this case. This is the situation of flying F-15A against MiG-25 foxbat, which are rather early types. If in much later aircraft, like F/A-18 or Su-27, the missile behaviors will be much more resembling the most nowadays standards. Thank you for your patient tutoring, Arrigo. I believe the game is gonna be one of my favoritest. No more faults exist any more!

Thx! Maybe I should start from locating where are all the enemy aircrafts and try to see. You are far more experienced in modern aero combats than me. My enemy activities is set to Normal. After all, there are often more than 10 of enemy aircrafts in this situation instead of 1 or 2 like in the other simulators.

In WO* series, I enjoyed the designate and shooting, carrier landings very much. They are very satisfactory. But I think the NeverEnough's problem is a real thing what the game is missing. Maybe we cannot blame the creator for this. Since it is clearly noted that it is designed to depict the scenario of the era of cold wars, where missiles just came to the field of warfares. In my collection of modern air combats, I gradually realize that it's TWI(threat warning indicator, an octant look-like display) which is indicating coming missiles in the most early types of crafts. In later fighters, (like F-15), most of them can trace the outgoing and incoming missles on the display( radiation emission sorts, not heat seeking IR sorts). That is what I know. Although the missiles are very fast, they still have a ballistic sense. In the rather severe programs, e.g., Jane's F-15, Red Jets will do as well. The missle avoidance is really going to s**t your paints. When you hear the coming missles alarm, if you don't make drastical maneuverings according to its coming direction, you'll be downed in a few seconds. Both the SAM or AA missles do the same. The most important is, you can have a feel of how you "shake off" of the missiles, and learned from it. The WO* series seems deficient of this reality. Sometimes the missiles seems just "shadowing" you, or it just pop out too fast before you have some clues. Since most of us have the most modern era fihgter aircrafts, we really should have improved it to the most up to date standards - - if it is a possible thing to do. I believe it's an AI sort of stuff, that is, encoded inside the program. I just don't believe we can modify some data file and change it. Maybe somebody who has more available time and talents can do something about it? ...

Thank you MK2! What you support is a most professional and gamers-the-first web site. We all need that! And we'll not hesitate to do our part anytime when it is needed.

At last, I finally work it out! Piece of cake! I'm really very lucky enough. First, I thought of overclocking the video card. There are many Radeon BIOS tuning programs. Some of them are pretty up to date. Like BiosEdit2.7, RadeonBIOSTuner1.4, ATITool_0.26. You'll need ATIWinFlash.v1.14 first to fetch the video BIOS ROM file. But I don't need to go into it. I start from checking the MB BIOS. The ATI has very detailed and overwhelming data on the troubleshooting page. About BIOS, they have mentioned about 5 lines: 1. You should disable FastWrite. 2. Try change 8X to 4X, and 4X to 2X. 3. AGP aperture should be 128M at minimum. 4. You should disabling Shadowing. 5. You should disabling Video BIOS cachable. Since most of these terms are already tuned or cannot be changed on my BIOS, I tried the Aperture size. First I take a shot by enhance it to 256M min from 128M min. The game freezes directly when you are in the air, no need to wait until your second action. Then I thought if I imply conversely, there must have some chance. So I set it to 64M min - Bingo! No more crashes in my Win98 installation! I really don't know what is aperture mean in video mechanism. But this don't harm other games anyway, and instead it had improved many others. Well, the ATI video card ain't that bad! To reward myself, I download the new Snowy Norwegian Terrain for my Wings over Vietnam. I believe my Win98 metropolitan gonna survive for another long while!

Becasue all my games are bundled by that Win98 HD. I just don't like to separate from my main working system. Well, maybe just for recreation. I have determined to work it out. I still don't dare to update my system to WinXP version. Becasue I am afraid I'll sacrefice many of my old games.

That's correct!

I have surfed internet for this video card. The Radeon 9250 seems have a reputation for "not the card for games". Somebody said it can adjusted by BIOS RAM settings. It seems helps a little bit. There is always a line before Win98 booting "initializing MBA xxxxx ...". Can anybody teach me how to turn off this organism? Maybe this can help. Thanks!

Trimming the texture size still won't work. So I use the drastical move: to setup win98 again. I thought maybe the achronicle Win98 update had spoiled my OS. But still didn't work. I found the SFP1E extract utility and revised the flightengine.ini. And I tested if it's the SFP1 original desert terrain compatibility problem, using the Hymalaya terrain and test. It crashes all the way. When you try to fly your second action, sometimes it freezes, sometimes the screen freezes into a kaleidoscope, sometimes it simply shut down to your BIOS. I have a feel that this bug is a very hostile one. It should have been resolved when you managing your CAT file. It will be an endless abyss going into it. So, just stand by! The WoV in my PC works well until I installed Falcon 4.0. Then this symptom becomes completely intolerable. It looks like my PC is play around with me. No, Stwa, what I mean is Win98 drivers. Besides, my version is newer than 5.9: it's 6-2_wme_dd_cp_30314. If in WinXP, I used the factory sealed CD drivers. I though ATI will be no longer developing Win98 drivers for Radeon 9250. But in my present serving MB, I have to choose this card. Because my MB video voltage rating is 3.3V or something. You'll find most of the present day video card which support other than 1.5V is almost extincted. Only this card still left. I have found some more modern aircraft really will "stutter". I have now set the graphic options to default medium, i.e., no mirrors any more. This will really make the game what we called "smooth". I have tested the game this morning. The WinXP installation is anyway still in very good shape.

Good News, something comes out! But still a little regretful. Somebody post a firm conclusion it's the line MinBaseSize=(should set to "small"). But this is only probable. I have tuned them all fine anyway. Try the keyword "wings over vietnam" "freezes" in combatace forum searches. After step by step approximation, I have come very close to conclude it's the video driver problem. Because when I use the sealed driver of Radeon 9250 in my WinXP system, the game runs all fine! I have tested the graphic setting, my present options are with mirror, shades... all turned on, it seemed will not hazard the performance, and my hardware is actually lusty enough for it. In my XP, it seems WoV go to its finals. But in Win98, it's still crashing all the same. In this case, I have to turn to WinXP only for WoV. May be I have to adapt for it, because my working HD are Win98 system. And maybe my Win98 are already rotten enough. To resize the texture is a whole new concept for my resolution. If I want to save my Win98 installation, I have to start from here... Do any body knows there is a more modern driver for Radeon 9250 in Win98? Thanks! and welcoming anybody can offer more information!

Pentium 1.6G. 512M memory. OS: Windows 98, and also WinXP one. Albatron KX400 8XV Pro MB. ATI Radeon 9250 128M Vid. But my motherboard might not be well configured. The CPU should be 2G, originally. Others things went right anyway.

My version is Wings over Vietnam. I am attracted by its easy access to carrier operations. But one nasty bug have been accompanying this simulator since my first installation. In some aircraft, it will freeze the computer when you entering the scenes. It's an "always" symptom no matter what time you install the game or what operating system it is in. May be the only way to play it is everytime you boot your Windows, with only once action. Next time you want play the game, you have to wait the reboot of your computer. Any body knows what's going on in the game? I have patched up all the updates, from WOV_sp051506a to WOV_p083006, even the wov_p071006, which alleged will make the game more stable. And also newest 9.0c, and display drivers. I even checked the sound data identities. But I think what I met is a kernal problem. This is a dead dilemma, since the game's high visual qualities and smoothness, and it's expandability. It's the second game since Jane's USAF that can make such enormous expansion at will. But it's really suffering playing it. I just feel I am helping the programmer debugging the program instead of using the game.