Levkov

I am going out on a limb here, is your "Pilot controls aircraft lights" option off by any chance in the sim settings?

Reinstalled P3D because I was troubleshooting some GPU (graphics card, not ground power :P ) problems and reverse works as it should in all versions now, it appears it was one of those things that magically resolves itself... :D

Robert, I tried both clicking and keyboard commands, both work on the DC6B and none work on the DC6A.

And when I did that, everything worked as it should on the B version, but never on the A version. The only way it ever worked on the A was when I loaded it mid air and that happened only once and didn't happen again during the same flight...

UPDATE: So I did something I am not supposed to do, I switched to the DC6A while in the air with the default raptor, I managed to land and the reverse worked once. Once I moved the red bar back to the normal operation, I was not able to move it back to reverse setting. There is something going on here...

For the life of me I can't get the red bar to move on the A version, and yet it works flawlessly on the B version. I am running P3DV4. Does anyone have any ideas as to the reason?

I know why the call is there in real life, and it is the default PMDG FO, not an addon program. I just think that perhaps it could be tied to thrust lever position or something similar that would distinguish takeoff from crazy wind. And Alan, I really didn't know that about the FCOM, I always thought the rings were there to remove the pages when maintenance can't be bothered repairing a non essential system, so they just remove the pages referring to it and pretend the item in question never existed

I just checked the FCOM 9.20.11, not a bug, it's a feature. I didn't read the part about spoilers and just assumed it wouldn't be done that way

Taxiing around Prestwick today in 15-20 knot winds, I heard the callout during ground turns 4 or 5 times. Does it sound every time when airspeed indicator moves above certain value regardless of anything else? If my FO did it every time during taxiing in real life, I would probably smack him over the head with the FCOM

As the title says, in the freighter, emergency light don't seam to illuminate the cockpit. I can see the bright circle on the ceiling, but the cockpit stays dark.

So I am coming into Prestwick this evening in the 400 F, and, as someone used to smaller planes, I am too fast in the descent, so I pull the spoiler handle, and looking onto position indicator, I see left side deployed, right side not deployed. I switch to external view, and both sides are deployed. I tried cycling them, tried using mouse instead of keyboard to deploy them, same situation. Screenshot included.

Yaw damper is used to prevent a roll-yaw coupling phenomenon called Dutch roll, I will not go into detailed mechanics of it, you can find more info online, but you can try quickly moving the rudder full left-neutral-full right-neutral in the simulator while flying trimmed straight and level with the autopilot and yaw damper off and observe the behavior of the aircraft (hands off the controls after the rudder input). Yaw damper doesn't help coordinate your turn, nor does it affect the turn rate.

I managed to fit it in VC of both, and radio tuning works from VC, but you need 2d open to manipulate other controls. Replace these in panel.cfg Learjet, in panel.GNS folder [Window02] size_mm = 900,900 window_size = 0.5 position = 3 BACKGROUND_COLOR = 0,0,0 VISIBLE = 0 ident = GPS_PANEL gauge00=rxpGNS!GNS530,0,0,900,700 [Vcockpit01] .. .. .. comment out (//) sections that have flysimwaregps in the name and replace with gauge11=rxpGNS!GNS530,-113,70,938,795 MU-2 in panel.main folder [Window02] size_mm = 900,900 window_size = 0.5 position = 3 BACKGROUND_COLOR = 0,0,0 VISIBLE = 0 ident = GPS_PANEL gauge00=rxpGNS!GNS530,0,0,900,700 [Vcockpit01] .. .. .. comment out (//) sections that have flysimwaregps in the name and replace with gauge08=rxpGNS!GNS530,-113,70,938,795 You need to turn gps on both in VC and in 2d for it to work. Hope someone finds this useful...

Thank you very much, I can't figure out how I missed them but some days, the brain just ain't working as it should

For the life of me, I can't find it. I know flood lights are there, L button turns them on, can someone please point me in the direction of the switch?

In fsx, no, in real life, aeroelasticity will tear them off at some point

I don't know if they are modeled, but it is procedure in all turbine aircraft to have igniters firing during takeoff/landing or heavy precipitation/icing/turbulence conditions. Although the jet engine doesn't require external ignition while running, in the event of flame blowout, you need some source to restart the combustion chamber. If you are flying at cruise altitude and experience a flameout, you have ample time to hit the switch and restart, but during takeoff and approach, a flameout can put you in a dangerous situation. So you basically use it every time an engine flameout would bring you into serious trouble, I usually turn them off at about 5000 agl and turn them on when I extend flaps to first position or when I turn on anti ice in all turbine powered airplanes, unless explicitly stated otherwise in the flight manual.

Guys, as far as wing structural integrity goes, there is a safety margin to ensure no structural damage (not even breakage, but plastic deformation) up to 1.5x past the aircraft operating limits. That includes G loading, aerodynamic forces, and fluid-structure integration phenomena (torsion divergence, control reversal, and aerodynamic flutter). So you are not allowed to go past it but if you accidentally do, you will not damage the plane structurally. Bear in mind manufacturer doesn't guarantee stability and control above VNE/MMO. Now, when you get really close to mach 1, wing center of pressure shifts aft making airplanes increasingly stable, but also causing strong nose down moment in aircraft not designed for supersonic operation. So the puller is there to prevent you from going faster than you can actually control the plane. In most civil aircraft, you don't even have enough engine power to cause structural damage in level flight through overspeed, providing you can maintain flight control at that airspeed.

Well, after several years of using the NGX, I started having issues. Today when I parked on the gate and started preparing for my next flight, both of my FMCs have become totally unresponsive, left one shoving landing ref page but with some missing numbers, and the right one (which I haven't used) showed the first init page it does when its powered on. None of the buttons on fmcs seamed to do anything, both in vc and in 2d popup. All of the other displays worked just fine. This issue has occured multiple times over the last month or so, and, even stranger, exact same issue occured on my Majestic dash8q400, fmc frozen and displays working.

A weird thing happens whenever I fly the NGX lately, my FPS is hanging around 13-16 and it usually is around 24+. My GPU usage as shown in my msi afterburner is 0. Sometimes, after a lot of alt tabing, hitting escape, opening some other stuff in background something goes wright, GPU usage goes back to 60ish and performance goes up to normal where it remains for the rest of the flight. It happens in some other planes (for example a2a b-17), but it never happens in their 180 for example. I am at my whits end, I have googled everywhere, and tried pretty much everything. I have a Radeon R9 280 GPU with 3gb ram, core2quad q9505 cpu, 6gb of ram. Currently on ati catalyst 14.12 omega. [please delete the other topic, accidentaly clicked twice]

I say why not, I actually don't know of any other forum that allows image uploading, so I am used to uploading them to storage sites and linking here...

In which axis are you getting the issues, for elevators and ailerons, pots are magnetic so just open the cover and blow out any dust from the casing. If it is the rudder, it is probably the pot itself so you need to open it and clean the inside of the pot with tuner spray or isopropil alcohol. Another possible cause is the wiring to the pots which can get damaged, in that case, you need to change the default wires which are rather thin and flimsy with your own, you will need a soldering iron for the job. Bear in mind that all of the above void your waranty, and I am not in the least responsible for any damage you might cause to your controler.

I have finally solved this, open your fsuipc.ini file and delete any reference to brake axis, it works for me now for both the NGX and MD-11. Use fsx default settings for brakes

This incident demonstrates the power of the comunity. A lot of people contributed when problems arose. I am fairly confident that, even if all the data was lost, the website would have been resurected to former glory. Little ones and zeroes on a hard drive can be deleted, but there is one place that no man can penetrate no matter how hard he tries: our minds. Everything on the forums and in the file library has been made by people who had no financial benefit for their actions. Even if all the files were deleted, we still have the knowledge and love for aviation to do it all over again. I truely hope that AVSIM will outlive all of the people who are reading this today.

I found a fix for this guys, assign your brakes in FSX and manually delete all brakes reference in FSUIPC.ini file.