tiopilotos

I reinstalled SF2 and I think I find out what's the problem. When game is not patched everything is OK but after the February 2010 patch is installed the same think. Screen turns dark and after that pc shuts down. I can see that graphics of SF2 are greater when use February 2010 patch and I think that with some way this has to do the need of power supply for video card. I use two cards ATI HD 4850 and as far as I know two video cards need more power supply than one. Maybe I need a PSU which can provide at least 700 or 800 Watts.

There's also an another thing. In SF2 I use add on aircrafts from 1st gen. I only put them in Saved Games/Thirdwire/Strike Fighters 2 Europe/Objects/Aircraft. Is that OK? Someone in another forum told me that I can't use so simple 1st gen aircrafts in SF2.

Here are some features of my PSU: -Universal input 100V - 240V & active PFC (PF>0.99) -Powerful +12V rail. Combined loading of 60A (750W), 62A (850W), 72A (1000W) -Supports Quad Core CPU and all Multi-Core GPU technologies

The maximum power consumption of the card is rated at 110 watts. Maximum power for PSU is 500 watts. But I think I forgot to mention something important. I use 2 cards ATI HD 4850.

OK, I will try to be as detailed as I can. When game crashes I don't get any error messages, the screen turns black and after 3-4 seconds the computer shuts down! I use the ATI HD 4850 version along with driver Catalyst 9.6 and in the game I use unlimited graphics. When I installed the driver for ATI, I used Windows XP but now I use Windows 7. At the beggining there was no problem but after some time, SF2 Europe started crashing when using some specific terrains like Korea or Desert without doing something. Simply after some time the screen turned black and the pc shut down. Later if the game was paused for more than 10-15 seconds, same thing, screen blacken and pc shut down. I decided to install SF2 Israel to see if there would be any difference. In SF2 Israel things were worse! (Same graphisc selected) I couldn't finish neither one mission! Now I use only SF2 Europe and in every terrain I have this problem. SF2 Europe is updated to June 2010. As described before, most times the game crashes when the explosion effects appear in the screen. In SF2 Europe I use the Hollywood explosions. As said above at the beggining there was no problem. I thought if there is some problem with the performance of the PC so I made a scan in the whole hard disc. No viruses no threats in general. To be honest I can't remember if the unlimited graphics were in use before the problem appear. Because I think that before this problem I used limited graphics but I'm not sure. Anyway as said at the beggining there were no failures or game crashes.

Windows 7 Home Premium Intel ® Core 2 Duo CPU E7500 @ 2.93 GHz 2.93 GHz RAM 4 GB ATI Radeon HD 4800

I have this problem with SARH missiles for both NATO and Warsaw Pact aircrafts. Sparrows, R-530, Super 530, R-23/24R, R-40R can be launched only in the minimum range of the boresight mode. For example F-4Es can fire Sparrows only above 5 nm. How can I extend the target locking range for SARH missiles?

The problem isn't the minimum range of the SARH missiles because I checked it out. In most SARHs minimum range launch was about 1500 and maximum range launch was 30000+. The problem has to do with aircraft's boresight mode. In SF 1 I didn't have this problem but I have it in SF 2. So, is there any way to extend the target locking range of boresight mode?

I agree with SanderK. Mirage 2000 is one of the coolest multirole jet fighter aircrafts.

I have a problem with the early soviet SAMs. I've installed weapons pack 2.52 which includes SA-1, SA-4, SA-5 etc. These SAMs don't appear in the game even If I select early 60s as a mission date. Then I checked the country users of these SAMs by using Weapons Editor. I selected Warsaw Pact but nothing happened. Then I thought that I should check every terrain on its own. In Taiwan terrain the opponents are China and Taiwan. Red side for China and blue side for Taiwan. So I used once again the weapons editor and I added China as country user of these SAMs but even after this nothing happened. Before mid 60s SAMs don't appear in the game. Since mid 60s some early SA-2 versions appear. Any ideas? Thanks.

Same problem here. I have installed Weapons Pack 2.52 and there are some specific cases. For example some Mig-23s like the Hungarian or the DDR Mig-23MF can not carry medium or long range missiles. I mean that in the loadout menu the missiles R-23, K-9, R-40 etc don't exist. Also Tu-128 can not carry the R-4 but the US built aircraft can carry Sparrows, the French built Mirages can carry R-530 or Super 530.

I think there are many parameters that affect SAM's performance. 1. SAM's and aircraft's ability to manuever If a SAM is very manueverable, then it can hit more easily a manueverable aircraft. I believe it is clear to everyone that an aircraft flying straight at the same level is a very easy target. 2. SAM's and aircraft's speed If the target is an aircraft with a maximum speed of 500 kts then, a 2+ mach SAM can easily hit the target even in long distance. I remember once when playing WOI, my F-4E had been locked by a SA-6 but I didn't gave so much importance because the distance was already 10nm and I was heading to the opposite direction with a speed of about 500-550 kts. I thought it would be very difficult for the SA-6 to hit my F-4E but finally the Phantom was shot down! Don't underestimate a SAM even if it is a 1957 SA-2. 3. Aircraft's altitude An aircraft flying at 10.000 ft can be hit much more easily than an aircraft at 600 ft. But I think this can be a method to avoid older SAMs such as MIM-23, SA-2, SA-3, SA-6, SA-7 etc. MIM-104 or SA-8 for example can hit targets flying close to the ground. 4. Aircraft's heading If the aircraft is getting close to the SAM launcher, then a high - G manuever may be enough and the SAM could not be able to follow the target. But an aircraft flying at the opposite direction is in more danger. Remeber the example with the Phantom before. Of course chaffs are very important. If an aircraft can carry many chaffs, it is possible to avoid many SAMs

Suddenly all the control keys were changed! For example landing gear is controlled by "H" and not "G", airbrakes are controlled by "Backspace" instead of "S" etc. I quickly had a look at Options ---> Control ---> Key Control Map, to see if there was any changes in the default selection, but there were no changes! I don't know if this has to do with the problem but I will mention it. I downloaded F-15C and installed it accrding to the readme file. There was an .ini file with the title "AIRCRAFTOBJECT". This .ini file must be put in the objects folder. Can someone help?

STORM you're right. Just before you post I deleted the file and everything went OK. I can't understand why this file was necessary for F-15C.

I can't understand why Chat command doesn't working on my WoE. In the keyboard control map says that you can chat with other aircrafts by pressing Shift / CTRL / Alt + ` (Grave key). I tried many times this combination but nothing happened. I thought that maybe there was a problem with ` (Grave key) and so I changed the combination to Shift / CTRL / Alt + F12 for example instead of the default. Again nothing happened, there was no choise for chat. Can someone help ?

There's something else though. Pressing "tab" gives you the chance to give some commands to wingmen but only this. So far I realized that in WoE/WoI/WoV you can't communicate with the tower. For example, let's suppose that you want to land at a close airport. You have to take permission first and then to land. Or suppose that you aren't in the runway and you need to taxi. In this case you have to communicate with tower to give you instructions. But this is not happening. I ask because in the speech folder I saw many sounds and I heared some of them and in some cases the tower says to pilot to taxi to a specific runway for example.

...Or this is happening just because chat command is used only in multiplayer mode???