citizen67

Hi everybody, I found a strange issue with A-6A and A-7C_71 in SF2 Vietnam, modded with Air & Ground War Expansion Pack. The bombs are merged in fuel tanks and the A-7's Sidewinders are not attached to their pylons (as you can see in the pictures). Anyone knows how to solve? Thank you very much. Citizen67

Me too I got this problem: every time I install the "FA-18 Series Update by The Hornet Team 2.0" in a game (I tried in SF2 with Afghanistan and Libya terrain, in SF2-NA with Eastern Mediterranean terrain) the sounds go weird. The windloop.wav and the jetengine.wav sound like they were old LPs playing at 45 rpm... I noticed this happens ONLY when I install this pack.

I've installed F-16C Blk 50 only in SF2E with the Rend's upgraded terrain. I'll do some try in different terrains.

Germany Terrain reworked, by Rends. But happens only with F-16C Block 50/52 by Viper Team...

Hi Happy308, what do you mean saying "rename the loadout.ini file"?

Changed software, now unpacking with winrar works. Thanks

Hi everybody, I'm asking you about this strange issue happened using the F-16C Block 50/52 by Viper Team, on strike missions in SF2 Europe: immediately, when the mission begins, the aircraft starts to tilt on the right side until it explodes, as if sinking in liquified tarmac... The loadout is balanced, no different weapons, no different weight under the wings and it seems this happen only on strike missions. I haven't found nothing about similar issues on the forums, so I'm asking your help. Thanks in advance. -- Citizen67

Strange indeed. unzipping I got the message that the .wav files were corrupted... I will retry.

downloaded twice, from both download and mirror link, but the file seems corrupted.

Hi Fubar, thanks for the answer. I forgot to set my gallery to "public"... now the video should be viewable. I don't think is a "texture popping" issue. As you can see in the video (I hope, now) the flickering lines are in the cockpit, not in the environment. Looks like an anti-alias or a V-sync failure... I don't remember if my card is 512 or 1024, i'll check this evening back from work and I'll post it tomorrow. bye

Hi everybody, I tried to solve this problem by myself without success, so I'm here to ask your help... I've noticed that in some cockpit (F-16, F/A-18, Tornado and few others), the horizontal lines are constantly flickering, as highlighted in the following image and as you can see in the video: I tried several times to set my graphic card settings but I could not fix it. Anyone knows hot to manage it? My PC has an old Nvidia GeForce 9800GT... Thanks in advance -- Citizen67

me too 4.12.2 and VP Modpack. But no way to set any kay...

Yes, I found it, in the far bottom of the Control Menu, under the last section "HOTAS CONTROL" (or something like that...). But I can't input any key, it remains blank. I don't know why, so I figured out it's because I haven't a HOTAS...

Hi Yubba, looks like the Head Movement key, in the IL-2 Settings Menu, is available only using an HOTAS, isn't it?

Hi 1977Frenchie, I agree, it could be the menu screen set I installed upon the game that cause the CTDs... I'll try to reinstall the SF2NA Expansion Pack without the menu and I'll check. Thanks

Yes, the stock SF2 NA works fine...

Hi everybody, I've got a SF2 full merged install, I've modded SF2 NA with the Expansion Pack (http://combatace.com/files/file/13980-sf2na-expansion-pack-part-1-of-3/) and I've also installed a new menu screen set (http://combatace.com/files/file/12866-strike-fighters-north-atlantic-replacement-menu-1680x1050/). The problem is that when I create a single mission and hit the "edit" button, the game freeze and CTD... I can only set the few option in the main single mission screen (map, weather, enemy activity...), but I can't go further to modify flights, waypoint, etc. I can only hit "fly" button. Does anyone has encountered the same issue? Is there someone who can help me? Thanks -- Citizen67

Hi eburger68, I will try installing your version, thanks.

No, I haven't altered anything. I've opened a few skins in Photoshop to look if there were difference between the ones working and the ones don't (things like 8bit vs. 16bit, RGB vs CMYK), and I closed without saving. The skins are in JPG format, not BMP. Maybe, as Geezer said, there is a disconnection in the file path. In which file I can take a look to check the file names/file path?