chennuts

Vsync shouldn't cause any decrease in fps with one exception. It's only function is to limit the maximum possible fps so as to not exceed your monitor's refresh rate, thus preventing the tearing effect you describe.

Different strokes... :p

Having played the Lost Coast demo numerous times, I assure you that this effect is available with HDR effects. If you look into the sun, then away, your "eyes" adjust, and vice versa. Is this not what you're asking for?

Putting your computer through that is the equivalent of eating a massive deep fried triple cheeseburger.

Well, that depends. What exactly is a tupid? :p

A favorite tactic of mine is to draw the enemy's attention, lock them in TWS, and "fire" at or even outside Rmax. A smart pilot (what this tactic counts on) will have me locked as well (don't care if it's TWS or STT), and know my range. He will also know that I have apparently fired at a very long range and that he can, with a minmum amount of effort, evade or trash my missile (he won't be going defensive and will continue to track me). The key point here is that he doesn't know that I've fired it. He only assumes I've fired it, as he know I'm searching and when the active missile shows up on his TEWS, he'll assume a TWS shot at very long range (since I'm still near Rmax). The catch is that I haven't actually fired anything. I have a wingman or two that I'm vectoring to the target, who will acquire visually and fire within the NEZ without ever turning on their radar. I try to vector them so it looks like the missile has come from me (or from their six so it slams right up their pipe and their only chance is to go completely defensive or to accelerate in my direction, bad deal either way). If there are other threats in the area, I vector them so that they'll approach the target hopefully without being spotted by the other planes in the area (or so that they can intercept my target without entering range of the other bandits in the area). How they're vectored to my target depends entirely on the threat level in the area and where the bandits are. I prefer to have a second eagle hang close to me and also scan, hopefully picking up anything I've missed and assisting with the vectoring of our buddy to the target. I don't often get to use this tactic online, but when I do, it's quite fun. If you do everything right, your team will end up with a lot of kills and no losses. You'll probably also end up with some pretty frustrated opponents. Key is, if the guy up front gets in trouble or loses track of his target, turn and burn. You've got your buddies to fall back on who are still tracking the target(s) and can engage to cover you. Same thing if you're spotted. Don't put yourself in a situation where you can be killed and you won't be. If your buddies up front get spotted before they can unload, this doesn't work. Period. Also, if you're going up against a team using this tactic, it doesn't work so well. You tend to spot each other's guys out front before they can get WVR and smoke you.

Your airspeed will affect your pitch stability. The faster you go, the more your nose will want to pitch up and vice versa. edit: typo fixed

It's the player's responsibility to set their configuration to the correct connection speed setting for their system and bandwidth. Do you leave your graphics settings at default after a fresh install, then get upset because the settings aren't what you think they should be? :)

I don't think a -short- track will be possible with this bug. I'm willing to record tracks for all future online sessions until it happens again, documenting -when- in the track it happens before sending it to ED. Would this perhaps be an acceptable solution? Would everyone else be willing to record tracks for each flight until it happens again? It seems to be the best way to squash this bug.

FYI, a lot of the monitors with really fast response times use 6-bit panels, which look like poo compared to a nicer 8-bit panel. Also, just because it's listed as 6ms or 8ms does NOT mean it's going to transition quickly across the board. Sure, the fastest transition should be the listed number, but the slower transistions could be well over 20ms. It would be best to compare the response curves of different monitors rather than going by the response time number, which is a guessing game at best.

practice bomb?

Mine have fins in 1.1. That being said, the model doesn't show up for me in the payload editor.

I made a track with the a10, su27, su25, and su25t, each of which did a toss/loft bombing. It was a very short track, only a couple of minutes, and I forgot to save the damn thing. I have to pack for a move tomorrow, so I'll get it there eventually. Looks like someone got you a track anyway.

I haven't flown the vanilla frog in a while, but I believe this can be accomplished by turning on your laser designator. Once it's on, place the designator on the target and press and hold your weapons release button. You then fly over the target and the bombs will be released at the correct time. You may toss/loft the bombs in the same manner, just increase your pitch after designating the target.

Try adding in some failures, serious turbulance, wind, weather, etc. You don't seem to be trying to make things harder for yourself. I can't say I have an easy time in zero visibility at low altitudes, especially when I can't tell my altitude because of failures. If you're forced to restrict or change your tactics, the fight will be harder, period. Surely, you'll still find it too easy, but there appear to be options you haven't explored.

For starters, why aren't you flying with your fuel at 100%? You said you wanted more of a challenge, so try handicapping yourself.

Witness #2. The 23 was doing some tremors style stuff, while a 25T was underground and seemed frozen underneath each player simultaneously (F5 view from ANY place would look straight down to a point x feet below the ground). Got really screwy with AWACS calls at one point.

I was trying to clean up LOMAN, and got into turbo mode. I inadvertently uninstalled a 1.02 mod instead of just removing it from the list, and upon doing so, it replaced some 1.1 files with the backup 1.02 files. I need the following: su-25.cmd su-25-collision.lom su-25-fonar.cmd su-25-oblomok.cmd su-25-oblomok-wing-l.cmd su-25-oblomok-wing-r.cmd Feel free to PM me or post to arrange a transfer via an instant messenger or FTP, etc. Thanks.

Yes.

I think I have the issue isolated. The bug only occurs when you switch aircraft using alt-j. I created a track where I start as a spectator, immediately jumping into an A10. You'll notice that the cannon ammo counter reads 1174 instead of 1350. I proceed to fire off continuous bursts, watching the counter reset first to 5000 something, then 9000 something the second time it runs past 0. A10 Cannon Bug.rar

I've discovered quite the odd bug in the A10. If you hold down the trigger, you'll fire off 1000 rounds before the burst stops. Proceed to fire another burst. Instead of running out of ammo, the counter runs past zero and starts again at 9000 something (presumably 9999). Continue with the 1000 round bursts and you will never run out of ammo. I've reproduced this 3 different times now and will attempt give it another shot. I didn't think to make tracks or take screenshots at the time, but I certainly will next time I try. Before anyone asks, no, my ammo is NOT set to unlimited.

I agree. It would make for some pretty sweet scenarios.

I'm not having a problem seeing the image...

Cool, thanks.

Boxed Version: The product will contain 1 CD which will include: - the Flaming Cliffs title with Starforce Professional Keyless protection. This will require the user to keep the CD in the drive, and will not require online activation. - Quickstart manual in pdf format - Flaming Cliffs manual in pdf format - Four Seasons If I buy the boxed version, how can I download the free movie pack?