CHola

Illegal account access attempt 20 Aug 2015, someone from 185.65.135.226 tried to illegally access my account. Mods, feel free to permaban the IP.

Hello, posted this a couple of times before, but got no straight answer, so I'd like to hear something "official" on the following: I've mapped mouse to pitch/roll/yaw axis (and unmapped the same from view control) in FC2, but the game doesn't seem to recognize that. Is it supposed to work and I'm doing something wrong, or not at all and if so, why is that option present in controls menu?? Thx

@grandkodiak, I've noticed Mavericks work significantly worse in Patch 1.12b and I can't lock onto tank with "K" Maverick farther than 1.5km! I think that's "increased realism" tweak...

No, they don't work better than on low altitude, but they work less bad in comparison to drag, hence better top speed.

Any jet engine works with the amount of air it can process and it's expressed in maximum airflow in kilograms of air per second (kg/sec). So, during Winter due the low temperatures, the air is more dense than hotter Summer air and contains more oxygen for burning. The other benefit is that the turbine is better cooled and so allows higher compression for the same max. turbine temperature and therefore higher thrust.

Yes. You need to replace all clouds textures with empty pictures and that should work. Not sure, but I think I saw someone packed this in a MOD file. It should be somewhere around here.

Download correct (the more exact the better) driver for monitor, instead of using generic. Obviously, Windows reset your freq. setting since they can't "see" 100Hz, most probably due monitor driver...

Try overriding Pixel/Vertex shader to older versions (from 3.0 to 1.3 f.e.) and see what happens. Be advised that shaders often register as changed in most drivers while driver remain in new shader version mod, so it'd be good to repeat shader forcing a few times just to make sure they actually changed. If that doesn't help and shaders won't switch, there are specialized tools that do that. like this one.

@Lange 666, I don't know how to fix nVidia, but you could try and go into DXdiag and in the last tab "Help", click last option "Override" and set this value to 100Hz. That may do the trick, since LO works in D3D.

"Yea, he was giving him a birdie"...("I hate when he does that to me") :D

Good news! One practical question. Will FC2.0 share open FM/cockpit/ architecture like BS originally has and thus enable easier and more precise modding?? Thx.

In "Options" menu, "Difficulty" submenu, uncheck "miniHUD".

It's most likely not the question of LO, but your driver setting. Go into driver panel and set refresh rate for FULL SCREEN 3D, since many drivers keep desktop (2D) and games (3D) vertical refresh, separate. Hope this helps.

Did you accidentally rebind fire button, or is your joystick malfunctioning?

HUDs in real planes are focused always in infinity, to keep the same degree of sharpness regardless of distance the pilot is looking at, in the real world. HUDs are using holographic technology to achieve that.

@Aero, Nice vid, a few points though. Split-S is performed when braking off from at least neutral/advantageous position, while in turn in close combat, so what you did is a Returneman maneuver. If you're gonna dodge the enemy's missile at such high speed as in the in vid, you'd be better off doing Immelmann, than Returneman, because you'd trade speed for height. This way you lost both, speed in high g maneuver and height and dashing on burners at 500ft is never a good idea due enemy IR SAMs. So, if you went up instead of down, you'd loose enemy's missiles more quickly and draw enemy's attention more effectively, leaving your low wingman with a good chance to fire, unobserved. Now, I don't say I'd do it better. Just a few things to think about. :)

Simple flight model actually means, that all planes fly as if they had FBW, except Su-25T.

Yea well, what can I tell? I'm a logistic nightmare. :)

Actually, at ~300-350kts, Sparrow is dead accurate. It hits velocity vector indicator at 20° dive, EVERY SINGLE TIME. I hit 4 parked Migs25, out of 4 Sparrows, routinely. LOL AMRAAM flies all around and is really difficult to hit anything with it. It has smokeless engine so it's difficult to correct fire, but it seems it hits somewhere below the Sparrow (below velocity vector), but I can't tell where exactly, since there's no visual reference.

@Talon The troubles you're having with your wingmen are normal and everybody has them. The thing is in AI, which flies in full AB at any opportunity and which hasn't been corrected until today in any patch. Still, with a flight of Mig-29A! I've managed to make ~370km combat radius (~750km range) and still shoot down an An-30 and 2 Migs23 escorts, somewhere at half the way. Needles to say, I flew VERY carefully and watched after every drop of fuel. The way to do it is to never accelerate in AB, since wingmen need to catchup. Don't let autopilot turn you on waypoints, cuz it'll use AB again. Don't climb too steep, cuz wingmen will go on AB to catch you. Don't shift open/close formations since wingmen will use AB during maneuver...There's a lot more detail that need your attention, but in the end it pays out and you can do some really long patrols with your wingmen.

Do you have such artifacts in other 3d games, or in Windows desktop?

Yes, that's just like driving the car. You always need to make small corrections to maintain the driving direction. That's called "fling with your a$$", meaning fling upon the feeling, not by instruments, since those can't read such small variations. Sometimes those inclinations are so small that are barely (if) visible, but try driving a car with locked steering wheel, even on a dead straight highway and soon, you'll end up outside the road.

Positive cambering is a way to fabricate the wing to make it have some degree of lift even when at alpha (AoA) 0°. Such wings pull the nose down when accelerating, since the Cp (lift point) moves backs, behind CG (center of gravity) as the alpha and Cl (lift coefficient) decreases. During acceleration in flight, a pilot (you) of any but CCV (Control configured vehicle = FBW) aircraft needs to either push stick forward permanently, or keep trimming the aircraft if he chooses to hold stick in constant position. If your nose is going down, you should trim "nose up" (contrary to nose movement) to reduce the effect of Cp moving backward. The trouble with any joystick (that I've seen) and that's why I fly with mouse, is the lack of continuous control input. Today's joysticks work like a flystick in F-16, but Falcon has a FBW computer which handles this automatically. Other nonFBWed (mechanically controlled) aircraft don't have flystick which auto centers and the pilot can incline the flystick by 0.5° f.e. to counter a slight imbalance due wind blow, a different pressure air pocket, etc, much like you can do with mouse. Same thing happens in LOMAC.

pauldy, the way to test the trim is to put the plane on "speed hold" autopilot mode, key "J". Then you can test trim, properly. BTW, does "Attitude Hold" autopilot mode (Key "H") works correctly? Ok, just saw your movie and the plane is behaving perfectly normal. The plane is pitching down during acceleration (not up as you said), indicating positive cambered wing. Either way, real plane never flies dead zero Vspeed and oscillations you experience are normal. It's strange, if you don't experience such behavior in other planes, though.

Dunno. I fly by mouse and I don't need trimming at all. However, you should be able to achieve Vspeed=0, with given trimming range. You can check, if your trimming input is working by going to external view while trimming. If elevators move then it's just a matter of finding a right position for given speed. However, once you accelerate or decelerate, you'll need to trim again and after the autopilot, trimming is mandatory, too. Trimming is a full time job, on nonCCV aircraft. Short of that, your joystick may be malfunctioning.