rockyalexander

I have a single ATI 5770 and am also getting some bad flickering in the TGP display when zoomed in. I have the resolution set at 512. I just can't spare the FPS to run the rez at every frame.

Yeah, Nate. I actually already posted the track in the "Object Errors" section. http://forums.eagle.ru/showpost.php?p=1120180&postcount=3 Again though, the errors occur when visibility is set to LOW.

Okay, was running visibility distance on LOW. Raising it to MED solved a whole plethora of problems for me, including the ground flickering (although the TGP flickers are now an issue), the guns not appearing in the Russian paratroopers hands while moving, and even stutters have been reduced (albeit slightly).

Notice the 4-second stutter as well. Pretty typical.

http://www.youtube.com/watch?v=dgQtdVE9xIo

Uploading the clip now. Thanks, Nate.

I don't use HDR. Have never had any flickering with the MFDS. How do I record a video with FRAPS? I've never done it before.

Predominately it's the flickering triangles on buildings when you fly over urban areas. The same issue from the early betas.

The flickering was bad in the early betas, but wasn't really an issue in Beta4. Now it seems to have returned in the release version. The flickering of buildings is insane for me. Is it just me???? I'm running a Q9300 Quad with a ATI HD5770 1GB. 4 GB RAM. Vista 64 home Premium.

I spent days trying to figure out how to get 52's to bomb. One thing I learned is that they won't release if there's any AA threat at all in the bombing area. Makes no sense to me, but that seems to be the way it is.

After installing Lockon Gold my drive didn't work for months, well, it wouldn't read any disc other than Lockon, that is. Then a few weeks ago I popped in a driver disc for my printer, and the drive managed to read it. It also allowed me to install the Control Manager software for my Fighterstick last week, so it seems to be working randomly now.

I had this problem after attempting to activate the Harrier. I removed my edits from the lua files, then the problem ceased. I must have made a mistake during my first attempt at the edits because the second time I tried, it worked like a charm.

I downloaded and installed this pack for the first time this evening, and I noticed that nearly all the skins still end up being the gray one once selected. What is the fix?

"Once" did the trick. Thanks, guys.

How do I deactivate a group 30 seconds after the start of a mission? I've tried (Triggers) Mission Start/Time More(30)/Deactivate Group... ...doesn't seem to work.

Again, it's the line abreast formation. In this case, 1WP Frontline. For some reason line abreast formations spawn facing opposite their programmed direction of travel. When they try to respawn facing the right way...lockup. Change 1WP Frontline's formation to cone and the mission will work.

The only problem with this mission is that 1WP Enemy north can't start line abreast from the position you have them placed. There appears to be some terrain obstacle or something. Move them to the west about a half-click or so, or change the formation. The mission will then work without a hitch. What occurs is that 1WP Enemy north spawns facing north, but moving backwards in the programmed direction of travel, which is southwest. About two seconds after the mission begins, the column tries to "respawn" facing the programmed direction of travel, but there seems to be a vehicle or two which is unable to change positions so instantly because of, as I said, some terrain obstacle or such. Hence the lockup. I hope this observation is useful.