flightluuvr

Get them both! You say you've never owned FSX, well let me tell you, you are missing a lot. Don't even think for one minute that buying P3D will satisfy your flight simming urges when you know that you're not playing the most popular and most expandable flight sim package out there. Default FSX is kind of lame depending on your point of view, but it doesn't take much to turn it into a great sim with some quality add-ons and many of those high-quality add-ons are 100% free and right here at AVSIM.

Are you using EZdok or EZ camera add on? I had a problem similar to that when I was using EZ camera add on. It had something to do with not deleting some of the default view assignments. It was mentioned in the manual.

Yes, I've done that, except it was a cheapo logitech joystick.I think when it comes down to it, a hardcore simmer is someone who would rather die than lose their ability to play FS.

I think a hardcore simmer is someone who can talk your ear off about flight simming, has more add-ons that he/she can keep track of, and will often deny him/herself sleep, food, friends, kids and spouses because of their love for the hobby.

I don't know how to get the cargo vehicles to connect with AI aircraft, but if you simply copy an [exits] section from a default aircraft's cfg file and paste it into the AI aircraft's config file you should see the jetway connecting to the AI plane when its parked.If the dimensions of the AI plane don't match the default plane that you copied the [exits] section from, the jetway might not line up with the door. In that case you would have to tweak the numbers in the exit section of the AI plane (x,y,z coordinates for the main door).By the way you can do this to any add-on aircraft too. With add-on aircraft the cargo vehicles should also come when you press shift+e+2 just like the default planes because cargo doors are indicated in the [exits] section. The actual cargo doors don't open though.I've always wanted to make the lights on my WOAI planes stay on when parked too, but I don't have any idea how and I've already spent a lot of time looking for a way to do it. The lights on my Traffic X planes stay on when parked so there must be a way.

Has anyone actually tried to import aircraft or scenery from FSX in to Flight? It worked with FSX and FS9 anyway.

This is now getting a bit ridiculous in my opinion. I mean come on Microsoft, are you really that desperate that you must charge multiple times of a single household? Even MS Office doesn't do that and even allows installation on more than one computer (although I think the limit is three).The more I hear about Flight, the more I feel it will be collecting dust on my virtual shelf (since there's no box). Right next to my copy of X Plane 9.

I agree that its good as far as graphics rendering nicely and smoothly on my wonderslug single-core computer and its looking a bit more detailed than the default FSX did (speaking of free content only), but I really wish they would have included a default world even if it was just bare terrain with some runways like my X-plane 9 default scenery. I for one simply can't afford to be buying add-on after add-on. To me this is like they have cornered the market on FS fans and are forcing us to pay to play. Its actually like an arcade game in that way too.

I had a similar problem. I tried turning off my firewall and that solved it. It failed somewhere in the middle of extracting during two tries, and I didn't remove any folders. The third try was without the firewall and it installed successfully.

I can't get past the first mission (the ballons) because I can't brake no matter what I try so my plane goes off the runway, slams into the fence and boom! Mission failed.On a positive note, I didn't think I'd be able to run Flight on my system because its a single-core 2.7ghz with only 4GB ram and a 1gb nvidia card, but it actually runs SMOOTH with all the settings at low, but even with the low settings it looks twice as good as the default FSX. I haven't tried the higher settings yet. Still trying to figure out how to brake.

I got the FSX Deluxe Edition when it first came out and it was $70. The base version was $50 or $60. Can't remember if it was on sale or not. Anyway I remember hating that many of the good add-ons cost $40, almost as much as the base sim!I almost forgot, I bought FS2004 around when it came out too. I believe it was only $40. I think I had a rebate though because I already owned FS2002 (but I might be confusing the rebate with another FS version since I started with FS5.0).

The default LAX is also very demanding on framerates. Lots of traffic too.

The flight is not in the database, guys. I'm having the same problem. The FMC just says "NOT IN DATABASE".

I spot at LAX a lot. I've never spotted from the two hotels mentioned in that thread, mainly because they cost money. My favorite spot is what they call Imperial Hill. It is on the south side of the airport and is hard to find unless you know exactly where it is. It is a small outdoor observation point on top of a roadside hill.You take Century Blvd to Aviation Blvd, make a right on Aviation Blvd to Imperial Hwy then turn west (right) on Imperial Hwy. The airport should be on your right side. A few lights down you will come to Main St., make a left on Main St., then make another left. That will put you on Imperial Avenue, which goes up a hill. The observation area is at the top of that hill on your left. A 300mm lens is perfect for this spot. The downside to this spot is a lot of heat distortion during the day.My other favorite place is In-N-Out Burger on Sepulveda Blvd. You can pretty much ask anyone there how to get there. If you look on Google maps it is right where the small green park is on the northeast corner of the airport. This spot is on the north side and the planes are only about 100' off the ground as they pass almost directly overhead for runways 24L and 24R. These are the runways that the Qantas A380's use. I don't know which ones the other A380's use. The downside to this spot is that you mostly see the underside of the planes. Have fun!!

If you want the default aircraft to not show up in your aircraft selection all you have to do is go into each default aircraft's folder and change the name of the Panel folder to anything different (like "panelx"). This will cause FSX to not see the "panel" folder as specifed in the aircraft.cfg file and therefore it will not show up when you want to select an aircraft.

I know this is going to sound too easy, but I had a similar problem with FSX a while ago. I would get a stutter every few minutes where the screen would flash or freeze for a second. I found someone's suggestion to turn off either 'flying tips' or 'cockpit tooltips' and that fixed it.

Some VOR's only work above a certain altitude, so it could be that you just weren't high enough....or that VOR doesn't exist in FSX, but you should be able to see it in map view or in the FSX flight planner (I guess that would be cheating if you're flying VFR).Another way to check if it exists is to click the "direct to" button on the GPS and try inputing the VOR's three-letter identifier.

I had that problem too (in FSX). I found out its because of a conflict with the WOAI traffic and the default AI. What you need to do is either delete or rename the file 'trafficaircraft.bgl' in your FSX/scenery/world folder. That file contains all of the default AI flight plans. Its probably best to make a backup of it before doing anything just in case.

I used to not like abacus because i bought a CD of add-on planes from back when FS98 was current, and then found the exact same planes available as freware, but I recently gave in to a tempting $10 sale price for their A380v2 at a local store and although this plane has its shortcomings, I ended up liking it a whole lot and I'm glad I spent the $10.At first I thought it was impossible to taxi but then I read a review which noted that you have to take turns very wide just like the real A380 and it worked. The cabin lacks detailed textures and the VC seems compressed in space somehow but there are points about the aircraft that I really like, like the ground service set, the engine sounds and the exterior models...and it flies ok too.

I just spent several hours tweaking my FSX to get it running optimally on my rather slow 2.0ghz computer and am happy to report that I have FINALLY acheived what I wanted: average 20-35 FPS with scenery on very dense, and AI airliner traffic at 60%. Getting flyable frame rates even in the 747 virtual cockpit mode. I am ecstatic! The distant mesh scenery is basically flat and looks like a giant fingerpainting but all the buildings, jetways and traffic are there and it is nice and smoooth. Well worth the many hours of random tweaking!AMD Sempron 2.0ghzGE Force 7600 GS (256MB)1.5gb RAM

One thing I forgot to mention...Cut the throttle at about 50' AGL or the plane will float over the runway. You can either lower the speed setting on the autopilot or kill the autothrottle and press F1.Also, you'll want to arm your speedbrakes and autobrake sometime before you land. I usually do it very early while waiting for the glideslope.

>i dont know what i am doing wrong, out of the maybe 10>landings ive recently tried, i only got 2 good landings.>>so far i know to set nav1 freq to the runway ils freq, switch>it over to the primary nav thing.>>and to set things straight, i am using the FSX default 737>>to get the plane to turn to final, what should the AP be set>to? APP or VOR LOC?>>should i have flight director on or off?>>and i think the last thing i can think of is, do i keep alt>hold on for the duration of the approach/landing?>>my latest landing attempts had me descending too fast and>another time i was too high, and this is after i activate the>APP button>my latest attempt can be viewed here:>>http://www.youtube.com/watch?v=SMsJ7EHtlNY>>>now back to the speed thing, i found a tutorial on these>forums, and it says to be at 180 KIAS at 10 nm out, but some>people tell me that thats too fast and i should be at 130>kias, so that makes me ask, what speed should i be at?Here is how I do it and it has always worked for me...I will use the numbers that I use with the FSX 737 here. Note that I always make sure my fuel for landing is around or below 30% capacity. Most commercial flights land with little fuel because taking on extra fuel actually causes more fuel to be burnt (tankering). Some extra is taken in case of emergency or diversion.15 miles out:SPEED: 210, FLAPS: 10, GEAR: up, HDG: 45 degrees or LESS off of the runway heading, ALTITUDE: around 2-3,000'AGL, NAV1: set to ILS frequency and IDENT ON (so you'll know when to switch to APP/GS), Autopilot: VOR/LOC, ALT, HDG, SPD10 miles out:SPEED: 180, FLAPS: 20, GEAR: up, ILS is probably now active (IDENT beeping) so switch from VOR/LOC to APP/GS. Make sure the ALT button did not go off (it will if the ILS frequency is not yet in range), should be intercepting the localizer and be well under the glideslope.GLIDESLOPE ACTIVE:(this is when you see the glideslope indicator start moving)SPEED 135-150 depending on weight, GEAR: down, FLAPS 30, Check attitude on HSI when plane stabilizes on glideslope. If nose is high, increase speed, if nose is low, decrease speed. Good time to adjust outside view if neccessary.That should get you down towards the runway without any problems. Remember to kill the autopilot around 100' AGL and arrest the descent (flare) just before touchdown. Happy flying!

Turn on "Auto Coordination" in the Aircraft>Realism options. This will link your rudder to your aileron input so turns will be coordinated in the sky, but also so you can steer on the ground with your sim yoke (since you don't have rudder pedals).

It sounds like there is a conflict between your CH pedals and another input device (joystick, gamepad, etc.). Try disconnecting all your gaming devices, then connect only the pedals, start up FSX with only the pedals connected and see if you can get theem working right. IF you get them working, then connect the joystick or yoke and see if they still work. I noticed that the order in which things are connected does make a difference.For the record, I have CH pedals and a CH yoke (both USB) and they work fine in my FSX. The only time I had a problem like yours was when I had an additional joystick connected too (by mistake).

That there is a pretty helpful guide!You may also want to install 'TreesX' downloadable at the file library under FSX utilities (I believe). It is reported to have a noticeably good effect on framerates. I installed it but never ran the program without it so I can't compare. But I can tell you that with only a 2.0ghz AMD processor, geforce 7600gs video card w/512mb, and 1.5gb ram I am getting between 12-25fps around LAX with scenery set to 'dense', airport vehicles at 'low', airline traffic at 14% and other sliders set very low or off. Not too shabby for a slower system so maybe the treesx helped.Also,if you have Anisotropic filtering available, be sure to check that along with Anti-aliasing, and set your framerate limit to unlimited. Those made a big difference in my framerates.