Strike Fighters 2 problem - no aircraft markings

[+allenjb42 4,234]

Purchase, download and directx update went fine. Installed with no problem and then went to fly a single mission.

 

My plane (a USAF F-4E) didn't have any tailcodes, nor did my flight. The MiGs and IL-28s had only Soviet nose numbers, and no insignia. The ai flight of friendly Hunters had no markings or insignia at all, and neither did the B-57s parked at my airbase.

 

I tried again with a USN F-4B with identical results.

 

Then tried a campagin and again no one had markings or insignia as above.

 

I've uninstalled and reinstalled, and even downloaded the game again but keep getting the same results.

 

My graphics settings have either been unlimited or high.

 

I've had no such problems on any fully patched versions of SFG, WOV, WOE or WOI.

 

Any help would be appreciated.

 

Thanks

Allen

[Coupe 0]

Hey allenjb42, I'm having almost the same problem. I'm running "The Dragon" in WOE. In WOE single mission and campaign, the tail numbers come up no problem. But when I run "The Dragon" campaign, no tail codes.

In the load out screen the paint scheme will show in the box, but no numbers in the number box.

It's a fun campaign but having the tail codes show up would make it better.

I have even down loaded other campaigns and compared the files to see if something was missing or needed to be tweeked.

I feel your pain.

 

Coupe

[+allenjb42 4,234]

Thanks mate.

 

OK, I've been troubleshooting this a bit.

 

I downloaded and installed onto my wife's computer and it plays fine, with all of the planes having appropriate markings. So now I'm thinking rather than a bad download, that it's my system that's the problem. Here's what I've got:

 

Packard Bell I-Xtreme 2600

P4 2.66ghz

512mb RAM

120gb hard drive

Geforce4

Win XP Pro

Saitek Cyborg Evo

 

Now my wife's computer is newer but has only a 1.73ghz processor. However, she's got 1gb RAM as opposed to my 512mb. Could that be the problem?

[Gr.Viper 131]

1 GB RAM is in game's system requirements. Maybe it cuts features when hasn't enough?