mtuckner

Scratchy it was with all views, and I never did a cold start while checking. From the runway and even in the sparse quick start missions. It is fixed though now, I did a reinstall of the program and patched to .6 and then .7 and it works now aside from the occasional freezes as mentioned by others.

It's always been there. Might have been broken last patch, not sure.

I did a clean install and my FPS issue is fixed. Similar FPS to the previous patch, only this time the buildings fade in closer to me making the terrain seem flatter. Only flew one mission but did notice those .75 second pauses a few times, I held my breath expecting a crash but it plugged on afterwards. I will have to get some more time in before I form an opinion, but I am already thinking of looking into what I have to do to get the old building view distance back.

Castle, it is this severe as mine? About 75% loss?

Finally gave it a go with the new patch. I have about 8 frames a second at batumi vs about 40 before. Not sure what gives? Same graphics settings...

I guess the trick is to use SPI and only use Attack With and not just generalized attack.

Yeah, I am not 100% sure but the bit test might have something to do with it somehow. I used to always load all but then be lacking my loadout in the DSMS until someone told me to wait till the bit test was complete. I follow that rule of thumb now, even though it might be totally bogus lol.

I thought that Georgian Hammer played the smoothest for me. I enjoyed that one. The shore looks interesting but the bug was a showstopper, and Devil's Cross was a bit overwhelming.

Probably because you loaded all before another critical function. I am not certain, but often when I load all before the bit test on the HUD is complete my weapons aren't in my DSMS.

Awesome ED! Thanks so much. I am still downloading the patch via my country bumpkin internet connection. Less than an hour to go!

I do like HDR, but would rather be able to spot targets!

Looking forward to it Bahger.

I experience this too. I should screen cap a couple this evening to illustrate. It's a problem when trying to see what way the tank is facing when using the old eyeball and not the TGP. You have to get within their guns range to get the LOD to pop. I tried a couple training missions with no TGP and it was dangerous just to see if it was a truck or tank that I wanted to line up on. I know this is LOD to save performance. I might have to tweak that file since I think have have some performance to squeeze.

Yeah, no spaces, but I did it for clarity sake.

I think it is a bug. A UTM or MGRS (military version of UTM basically) has to have an even number of numbers in order for it to work. The first half of the numbers is the horizontal grid number reference, and the second would be the northing reference. The two letters are the map sheet. You could theoretically leave off one number but it is not done anywhere that I have ever heard of, and it would be requested to give a complete grid if that was done. MN 568 030 would never be read out as MN 568 03.

Okay, will let him know. Thanks guys.

This is my favorite mission. More please. :D

Before someone helps you mesh all the systems together in a mission, have you run through all of the training numerous times and have a solid understanding of each component individually, or at least done them enough, and although struggling have a basis for more talk on training?

If the coordinates are not pretty close to the target, I would recommend the general vicinity coordinates be accompanied by a physical description. IE Vicinity MN045487, large forest, in the clearing.

Everything works for my buddy except the speed brake and the pinky switch. He put the .pr0 in the right spot and loaded the .lua correctly. Any ideas?

Oh very nice find!

Looking forward to trying it. I'm one of those anti-social types. My schedule and time is just too random and inconvenient to group up normally. Thanks for thinking of us types.

Yeah, I interpreted it as going to idle from max power will cause a problem, and not keeping it at max power.

Yeah, he was just wondering how far away from the target he was before he pulled up so he didn't stall out before the cue could make it to the release point.

Pulled up at 1.3 nm out.