karambiatos

It looks like its as twitchy as ingame

you can put a naval unit anywhere you wish with ctrl+c ctrl+v

if the undetailed area is as detailed as the current map, that's going to be pretty amazing, minus the towns and cities of course.

i can say MP and being in a TOR or tunguska is a real blast, especially when you coordinate with fighters so you bait the enemy to go into kill zones.

superior at 22GB/s transfer rates. you do that.

its not 256 bits wide, since it can either use the 224bit or 32bit so one part might as well be sand paper. to me it probably wont make a difference, but seeing as its not whats on the box, im just not going to buy nvidia again, even if nvidia collectively kissed my feet.

it does in a really convoluted way that can't be accessed at the same time, however its not 256bit, and its not 64ROPs, which is the problem

its not about the whole "its still a good card" Its about false advertisement, heck if you bought a device that said, it poops out gold, but instead it only pooped out silver, it'd still be pretty amazing, it just wouldn't be the thing you bought. Like i said before, if they get away with this, expect even worse things in the future, all hidden away behind a nice wall of "BUT ITS STILL GOOD".

and ones flight path is akin to a thrown rock.

What luck i have :) yeah, i was more asking about the way it bounces the stick, more than there actually being a system that stops the aircraft from doing it. but Svend answered it, so thanks to the both of you.

Even if the planets align, and nvidia fixes this and actually replaces 970s with proper ones, i still wont buy from nvidia ever again. What's stopping them from putting a paperweights inside of the card, and saying "it's how its suppose to be"

if nothing else at least the jokes are good

double rocket pods, oh man

no its the one where you pull high g and have the stick all the way back, then in the plane the stick starts jumping back and forth, as if the FBW system is letting go and grabbing the stick.

ill be annoying and bumb my question, since it really interests me http://forums.eagle.ru/showpost.php?p=2304886&postcount=171

This guy says, there isnt even .5gb of slow ram on the card, its just system ram that it's using. https://www.facebook.com/enbfx

they also need to market the fact that its 512 bit buffer with 4gb of ram :)

Toms analogy is absolutely terrible.

Well i kind of expected this, it being a 256 bit card with 4GB of ram, while AMDs 4GB cards are all 512bit, i never thought it could use 4GB effectively, though my knowledge of how it works, may not be correct.

I'd like to ask when you are pulling high G, the stick starts jumping back and forth, as if the FBW is grabbing and then letting go of the joystick, is this normal behavior for the su-27?. track in 1.2.14.36041 FBWJoystickBounce.trk

Testing the damage model, I ran into some issues. When a certain part is shot at or shot off it causes the entire plane to catch fire. Track "27Stabilizer": Shooting one of the stabilizers off causes the plane to catch fire. Track "27Wings": Shooting a wing causes the entire plane to catch fire (disregard fire that appears on the wing) Track "27RearAilerons": Shooting both of the rear stabilizers off, causes the entire plane to catch fire. Track "27ParachuteCone": One or a few bullets into the parachute cone causes the entire plane to catch fire and start falling apart. Recorded in 1.2.14.36041 27Stabilizer.trk 27Wings.trk 27RearAilerons.trk 27ParachuteCone.trk

I can confirm, while in direct control the 27 is more stable in a straight level flight, requiring minimal trim input to keep it straight.

That must be some weathering if the entire corner is gone. The 27 in DCS does actually look that good. At 1:46 You can see the shadow from the missile on thermals passing the engine cowling, forgive me if im wrong but it shadows dont show like that on thermals

tell why is the plane flying with a damaged stabilizer.