Leaderboard

That kind of trim does not exist in a helicopter. In a helicopter (well, most helicopters), you have magnetic brakes and springs attached to the flight controls. When the force trim button (and that's what it is called, "force trim" specifically, not just "trim") is NOT pressed, the magnetic brakes are energized, and any movement of the controls is against the springs. So you could just let go of the stick and it won't move (same with pedals and collective, if they use the same system) since the springs will hold the controls in place. Pressing the force trim button deenergizes the magnetic brakes, so that moving the controls gives no feedback. When you are done moving the controls, you release the force trim button, reenergizing the magnetic brakes, and you have spring tension again in the new control position. During maneuvering, the force trim is constantly being pressed and released, or sometimes even just held down for extended periods. During straight and level flight, you can go for quite a while without hitting the force trim button.

Nice Ironhand... In some of our older military birds (w. steam guages), the mechs paint on the airspeed arcs with paint on the glass of the instrument itself. Helps a great deal to set rpm, and not exceed limitations in combat even when the guage didn't sport any colors in the first place (other than a red line).

Happy birthday :yay:

Happy Birthday ICE :blow:

IMPORTANT: The following applies to V1.12. The files in V1.02 are different. And, yes, you must set it for each aircraft's cockpit. There is no global setting that I'm aware of. The place to set the default zoom for TIR in the cockpit differs depending on whether or not you have the Z-axis (the "zoom" axis) enabled. With it enabled, the setting lives in view.lua. Change the 2nd number in the "Camera views angle limits" section for each aircraft. -- Camera view angle limits {view angle min, view angle max}. CameraViewAngleLimits = {} CameraViewAngleLimits[PlaneIndex.iSu_27] = {20.0, 170.0} CameraViewAngleLimits[PlaneIndex.iSu_33] = {20.0, 120.0} CameraViewAngleLimits[PlaneIndex.iSu_25] = {20.0, 120.0} CameraViewAngleLimits[PlaneIndex.iSu_39] = {20.0, 150.0} CameraViewAngleLimits[PlaneIndex.iMiG_29] = {20.0, 120.0} CameraViewAngleLimits[PlaneIndex.iMiG_29K] = {20.0, 120.0} CameraViewAngleLimits[PlaneIndex.iA_10] = {20.0, 170.0} CameraViewAngleLimits[PlaneIndex.iF_15] = {20.0, 170.0} Without the z-axis enabled--in other words, you use the keyboard or a joystick slider or whatever to zoom--the default cockpit zoom is set in snapviews.lua. It's the 'viewAngle" setting for the #13 position for each aircraft. (Example: Snap[1][13]["viewAngle"] = 117). BTW, this number also controls the default cockpit zoom when you are not using TIR as well. In case you're wondering, the flyable aircraft are identified by number: PlaneIndex = { iSu_27 = 1, iSu_33 = 2, iSu_25 = 3, iSu_39 = 4, -- Su-39 or Su-25T iMiG_29 = 5, iMiG_29K = 6, iA_10 = 7, iF_15 = 8, Hope the above is sufficiently clear. Experiment and find numbers that are comfortable. Rich

I'm no expert here--but I can tell you that with the Ka-50, how the trim works. In a helicopter, the trim does not work like it does in an airplane. Untrimmed, you are flying along--and then when you hit the trim button, the helo in 3D space is put into memory, and the actual physical stick stays where it was when you initiated the trim. Essentially it holds the stick in place. For non-force feedback sticks it's a little tricky. When you hit the trim button, you have to release the stick and the rudder to their physically neutral positions. The helo will then fly in the new "attitude" with your stick and rudders in their physically neutral position. Not sure if this is the way it is in all helicopters, or not.

some comparisons might be helpful Download: http://www.lockonfiles.com/modules.php?name=Downloads&d_op=viewdownloaddetails&cid=123&lid=1177&title=Fire_and_Smoke#dldetails cheers :beer:

Today, for the first time, I saw the image included in your post from the 19th (damn work computer uses an ancient version of IE--I'm viewing from home today). I have to say, if I were an aircraft manufacturer, I would take exception to your description of what you have marked with a yellow band as "Limited Operations". I think they would prefer the term "normal". For that matter, I'd probably take exception to marking it in yellow rather than green or blue. Speaking of "blue", I ran across this image in the FAA Airplane Flying Handbook (FAA-H-8083-3A) in the multi-engine section: It's the only image that I've seen showing a blue band in addition to the single blue Vyse tick mark. Unfortunately, the image was simply being used to point out the red Vmc red tick at 80 knots. So it was chary in describing the rest of the dial. I'm also wondering about your description of the white tick mark as "Takeoff speed". As a practical matter, that might be true but every description I've seen of various airspeed indicator markings describes something that's true while you're airborne. I'm searching for Su-25T cockpit images to see if there are any placards describing the various airspeed "hallmarks". Our sim cockpit certainly has no such descriptions. BTW, if any of you are interested, that FAA handbook has a lot of good basic info in it. You can download it from the FAA website: FAA AIRPLANE FLYING HANDBOOK. Rich

Nice, HAPPY BDAY MAN, HOPE YOU HAVE A GOOD ONE.

Я бы уточнил все-таки. "Может" (а не "будет") биться на равных, если знает особенности тактики и некоторые основы. К примеру - я с выбитой гидрой относительно легко уходил от той призовой пары - над ними довлел-таки опыт Ила. Но обучение идет быстро - второй раз ошибка не повторяется. Впрочем, я там участвовал мало, у меня класс пониже все-таки, да и летаю редко - это бы лучше попытать СуперМутта, Алдерса, Скарта, Ника, Гошу. А вот тут совсем неправда, тебе, видимо, не те бойцы попадались. Как раз признак (по-моему) отличного ганзиста в ЛО - умение стрелять на скрещивающихся курсах навскидку. И их (бойцов) есть много. PS То есть - упреждение, конечно, не всегда считается правильно. И это тоже правильно :)

You should. :)

I spilled spot remover on my dog, and now he's gone. I bought some powdered water, but I don't know what to add. I stayed up all night playing poker with tarot cards. I got a full house and four people died. -Steven Wright

A really cheap and nasty way is to blow up a bridge or a building near your actual target. That will burn for ever and you will always be able to see it day or night from quite a distance. Not exactly a politically correct method, but hey it's war.......

I'll explain my point to you a bit clearer then , no offence , but your the most paranoid regular I know in HL. It wasn't long ago you were sounding out every guy that lagged as a print screening cheat. Now your trying to make out that everything is easier now LUA export has been disabled.:smilewink: It seemed easier to shoot you down the other day but im sure that has nothing todo with TacView or does it.:alien:

Yup, and now they use tungsten because DU is dangerous for everyone and everything around it :) Better pile it up at some nuclear facility rather than poison everyone involved, on both ends of the bullet/armor/bomb. Sure the risks are nill, sure, that's why they finally start using tungsten, no harm at all with DU... /sarcasm.

The burn time for vehicles has been extended and is now adjustable in the LUA files for various vehicles types. The ricochet effect is modeled only for AP ammunition and small arms. Everything else is HE and explodes on impact.

There's also a cheaper solutiuon called Free Track, couple of LEDs, Web cam and some 35mm camera film for filtering out backlight if any! But you can also use your mouse to pan your head around the cockpit, check it in the Setup UI!