jrdani

Can anyone tell me what file governs the "takeoff time" shown at the beginning of each campaign mission and subsequently shown on the Hangar screen? For example, in WOV the time is "teletyped" out right after the date on the Opening screen and then shown again on the Hangar screen. I used to think it was randomly generated, but I've now experienced a string of more than a dozen consecutive missions where it's exactly the same: 07:27:11. I've looked in what I thought were the most likely files for the "trigger", but so far I've struck out. If someone could point me in the right direction I'd appreciate it very much.

B Bandy, if you're still shopping for a 22" widescreen, try looking at the 22" LCDs on TigerDirect.com. I've dealt with them numerous times during ths last several years and have always found them to be excellent to deal with, before and after the sale. I forgot to mention previously that I'm running my Optiquest Q22wb on a DVI cable that I purchased separately with good results achieved. You might also use Znet to compare prices around the web. Hope you have better luck with your next one.

You asked for input from anyone who installed a 22" widescreen monitor. I recently switched from a 17" CRT to a ViewSonic Optiquest 22" LCD with no problems whatsoever and the graphics are fantastic on the widescreen. You mentioned attempting to lower your PC's display resolution, but I didn't see any mention of whether or not you've changed the game(s)' graphics options to match your new monitor. I have my game's "Display Resolution" set to: 1680x1050x32 and the "Display Aspect Ratio" set to: Widescreen (16x10). You also mentioned changing all of the game's graphics settings to "Low" with no success. I think those settings are more dependent on the capabilities of your display adapter (video card) than your monitor. I have all of mine set to "High" with no problems. Make sure that your video card supports the resolution potential of your new monitor. It looks like yours should. Bottomline, your problem might be resolved by something as simple as making sure your game(s) display options (both resolution and aspect ratio) match your monitor and video card settings. I hope this information is helpful to you.

Thanks guys for the replies. As you said, Kevin, it is a pity. I guess we will have to wait for "avionics80.dll". Fubar, thanks much for the RWR tip, I'll try it right away. Again, thanks to all of you for your replies.

I've searched the archives for hours now, both here and at SimHQ, for ini editing info to enable the Ground Radar mode of Avionics70.dll to show a carrier's blip or an "updated/modified" Avionics70.dll file that would accomplish the same thing. I've been away from SFP1/WOV/WOE for over a year and I'm sure this problem was probably resolved at some time in the past. I just can't seem to find the record of it. I found a lot of info regarding Avionics70.dll in relation to CCIP display, etc., but nothing with respect to "blips" As you all know, it's very difficult to find the carrier, especially at night, without that blip. I also found statements indicating that A/G radar was not functional at that time in Avionics70.dll. I've recently installed the F/A18 Blue Angel model that was part of the C6 Megapack and everything works fine (A/A radar/TV Screen/CCIP, etc.) except the blip function of the A/G radar. If anyone could point me in the right direction I would be very grateful.

I agree wholeheartedly with your point of view, Stephen (Streakeagle).

My apologies, Kout, I've got it straightened out now. Another fantastic job as you always do. You are truly the best. Thank you for all your creations that have brought me, and continue to bring me, so much enjoyment!

Kout, I've been looking forward to these since I viewed the post where you related you made the icon for WOE and TK didn't use it. However, the downloaded files don't appear as icons, they're basically hexadecimal files. Thought you'd want to know.

Congratulations to all of you and thank you for bringing back one of my favorite websites. I know you are all are proud of this site you've created and you have every right to be. Long live CombatAce. I'm sure you've made it such that the idiot that's been doing this can never do it again. I hope that he and others like him wind up behind bars which is where they deserve to be.

Thanks for your replies, Lexx and Capun. Lexx, I did get your comments and ideas at Thirdwire and I appreciate them. I'm trying some of your ideas at present. Thanks again for posting them. Capun, I did mod the [GraphicsSettings] in the FlightEngine.ini some time before having this problem. Also, I've checked and I do have the very latest DirectX 9.0c. I have an ATI 7500 All-In-Wonder graphics card. I'll try rolling back to the previous driver as you suggested to see if maybe that will solve it. I'll also check the Sound, Effects, etc. files as well. Thanks for taking the time to reply, guys. These things will give me several ways to try and resolve the issue.

I initially posted this in the General Discussion portion of this forum, but maybe I should have posted it here instead, so here goes: Is there anything different that must be done in order to install older add-on aircraft in WOV, Patch 4a (5/25/06)? I've added the respective aircraft's folders of the E-2C, F-14A, FA-18A and F-16 to the ..........\Objects\Aircraft directory and modified the Options.ini file in the main Wings Over Vietnam folder to show an EndYear=2010 as suggested by USAFMTL. I've tested each one in the Single Mission scenario and the E-2C and F-16 work fine. However, I have one small problem with the FA-18A (not the latest one with the corrupted file) and the F-14A. If I simply load them and don't fly, I can hit the escape key to terminate the mission and they exit to the De-briefing Screen as they should. However, if I load them, fly around and then land, hitting the escape key won't exit to the De-briefing Screen. The screen stays black and I initially had to do a "hard" shutdown of the computer and then re-boot. I've waited as long as a hour to see if eventually the black screen would disappear. The computer is not "hung-up" because each time I can see and move my mouse pointer. I've recently found that if I hit the escape key a second time, it will return to the desktop but not to the Debriefing Screen where its supposed to be. The reason I'm asking if anything has to be different for WOV Patch 4a (5/25/06) is because I've copied the exact folders (FA-18a and F-14A) from WOV Patch 4a's Aircraft folder to WOV Patch 3's (7/5/05) Aircraft folder, tested them several times in Patch 3 and after flying and landing, hitting the escape key exits properly to the De-Brief Screen every time. As mentioned above, I have this problem only with the F-14A and the original FA-18A (not Blackbird's with the corrupted file) and only in WOV Patch 4a (5/25/06). Works fine in Patch 3. I've tried everything I can think of to fix it with no success. I've removed and re-installed both the F-14A and the FA-18A several times. I've defragged the hard drive. I've compared all of the ini's between the F-16 that works with the F-14A that doesn't, and nothing different jumps out at me. I've even copied the entire WOV Patch 4a folder to a 160 gig backup hard drive and tested it there with the exact same results. I've searched the forums of CombatAce, SimHQ and Column5, and if the answer's there, I must have missed it, but I've sure searched hard. Just today downloaded, installed and tested the F-15A Eagle in WOV Patch 4a. It exits to the Debriefing Screen just as it should. BTW, the F-15 is beautiful.........kudos to the Mirage Factory. I hope some of you modders out there have some ideas? Any help would be much appreciated.

Bump I have this problem (see original post) only with the F-14A and the FA-18A (not Blackbird's with the corrupted file) and only in WOV Patch 4a (5/25/06). Works fine in Patch 3. I've tried everything I can think of to fix it with no success. Doesn't anyone have any ideas? Any help would be much appreciated. Just downloaded, installed and tested the F-15A Eagle in WOV Patch 4a. It exits to the Debriefing Screen just as it should. BTW, the F-15 is beautiful.........kudos to the Mirage Factory.

Is there anything different that must be done in order to install add-on aircraft in WOV, Patch 4a (5/25/06)? I've added the respective aircraft's folder; ie. E-2C, F-14A, FA-18A, F-16 to the ..........\Objects\Aircraft directory and modified the Options.ini file in the main Wings Over Vietnam folder to show an EndYear=2010. I've tested each one in the Single Mission scenario and the E-2C and F-16 work fine. However, I have one small problem with the FA-18A (not the latest one with the corrupted file) and the F-14A. If I simply load them and don't fly, I can hit the escape key to terminate the mission and they exit to the De-briefing Screen as they should. However, if I load them, fly around and then land, hitting the escape key won't exit to the De-briefing Screen. The screen stays black and I have to do a "hard" shutdown of the computer and then re-boot. I've waited as long as a hour to see if eventually the black screen would disappear. The computer is not "hung-up" because each time I can see and move my mouse pointer. The reason I'm asking if anything has to be different for WOV Patch 4a (5/25/06) is because I've copied the exact folders (FA-18a and F-14A) from WOV Patch 4a's Aircraft folder to WOV Patch 3's (7/5/05) Aircraft folder, tested them several times in Patch 3 and after flying and landing, hitting the escape key exits properly to the De-Brief Screen every time. Thanks in advance for any guidance anyone can give me because at this point I'm clueless.

I had a problem also as follows: Recently added the FA-18A Hornet to my fully patched WOV (5/25/06). Thus far, I've only tried single missions. After landing and completing the mission, I hit the escape key as usual to go to the de-briefing screen. However, the screen just remains totally black, and after waiting about 5 minutes, I have to shutdown the computer and reboot. While the screen is black, I can see the mouse pointer and even move it, but the game won't go to the de-briefing screen or return to the desktop. This has happened every time (3). I've done an exhaustive forum search and have found other black screen probs, but nothing similar to this one. Any ideas?

Could someone whose added other moving ships in formation (cruisers, DE's, tanker, etc.)to a WOV/SFP1 campaign carrier, therefore creating a carrier group, steer me in the right direction as to the "how to"? I've searched and searched the posting archives and the above quoted post from Hengist with Gramps' reply is the closest thing to info I've found, however I'm not able to find Gramps' Aussie carrier mod to compare ini entries. Any help and/or information would be greatly appreciated.