johnk51

Are there any library objects for stores like Walmart, Home Depot, Lowes? Or ​restaurants like McDonald, Burger King, and other restaurants? ​ I would like to add them into my sceneries.

I have the same thing. I bought both today. Installed the base just fine, but got the same message as Ralph got with the expansion. I also have the 777. I'm also running windows 10 pro 64bit with 16 gigs of ram. I probably need to us that reg. tool. Don't know if it will work or not.

I'm wondering how pmdg 737ngx works with windows 10 and fsx SE. I have the pmdg 777 and it works great especially after the last update, even in and out of airports like FB ksfo hd and dreamfleet airports. I have iFlys 737 and after I upgraded to win 10, it just sucks up memory then OOM. It's also real jerky and brings down the frame rate to single digits. But no one at their forum has that problem. I've uninstalled and reinstalled to no avail. I had the legacy pmdg 737 back years ago and now I want a 737 that will work. My Level D works and MJC dash 8-Q400 is great, but I want to use the 737 for short trips too.

Thanks for the help.

My flight simulator is set to lbs and not kgs. But when I look at the fuel in phenom, it shows the fuel amounts in kgs. Can I change this instead of having to convert it to lbs?

I'm still having trouble getting the files for fsbuild right. I did a flight from kiah to kelp. It was 587ktm, and fl360. My payload was 1312 for a zfw 8212. Could some one tell me about how much fuel I'd need? The figures that I got was around 39% in each tank. Of course that did work. Now after playing around with the prf file it tells me I need 2076 lbs of fuel. That's over the fuel capacity. A work in progress.

I did find I had a POH I downloaded the other day. I think I've set up a prf for fsbuild. I'll be trying it out to see how it works (no guarantees). But if it gets in the ball park, that will be good enough for me. I did go to fuelplanner.com, but they didn't have a Phenom 100. And I don't know what would be close to it to get a ruff estimate. I'll let you guys know when I've tried it a few times and see if I had enough fuel left or too much.

How do you calculate the fuel needed for a flight. I have fsbuild, but there's no prf files for the Phenom 100. It came with pdf for performance, but how to calculate taxi, t/o, climb, decent and all that. Any help would be appreciated.

The sound problem does happen on other planes, just not as bad as the T7. I don't see anything in the right bottom of the screen. But it's still open because ASN says it's still connected to FSX. That's why I have to run task manager. On the sound, sometimes when I click on the menu bar it will do that stutter. It has to be win 10. It didn't start happening till I upgraded from win 7 pro 64. Maybe some day they will get it fixed.

FSX + acceleration, for the most part is working good. I'm having some sound issues that I can't seem to fix.Most of my aircraft work well, some get a whoos whoos sound when I flick a switch. It does it 4 times, then back to normal, I.E. my LVD 767. My iFly 737 does it with some of the sound like, weather radar test, and during pushback with AES or GSX. Now my pmdg 777 is doing it all the time. It's the recirc fans that are normal for about 2-4 seconds, then whooos, whooos 4 times, then repeat. I can fly but I have to turn the sound way down or hit Q to sound off while taxing or taking off... I can't figure out what is causing this. I even got a new sound card that's newer than my old one. It's a pciE 1 SB audigy FX and it has the windows 10 software I installed. But that didn't solve the problem. I don't know where to look now. It all worked good in win 7 pro 64 bit, and this is win 10 pro 64 bit. I'm running 8gigs of ram and a NVidia geforce gtx 750ti 2gig. Any ideas the problem? Oh, and one more thing is when I close FSX, it shuts down but doesn't totally close. I have to go into task manager and end task. Can't figure that one out either.

I have an Audigy 2 value sound card. The sound works fine for music and other games in win 10. But in fsx I'm having problems with some of my aircraft. In most of my small planes, when I click on the switches or buttons, I get the sound cutting in and out about 4 times. Then it stops. This also happens with my lvd 763. My iFly 737, it will also do it during pb. Now my pmdg 777 is the big problem. It does it constantly. It will make 4 wooosh sounds, normal for about 2 seconds then repeats. I can still fly, but I have to turn of sound so I don't go crazy. I don't know what's causing this. I'm thinking about getting another sound card, (which I probably should), mines quite old. But I don't know if that will fix the problem. In win 7 pro 64-bit I had no problems. And as I said, I can play music and other games with no problems. Open to any suggestions.

The main problem I'm having with fsx and win 10 is my sound. I have a SB Audigy 2 value with drivers that should work with win 10. But on my smaller planes ie Seneca V, The sound will wooosh, wooosh 4 times then back to normal. This is also the same with LVD 763. My iFly 737, I'll get the stuttering not only when pushing buttons and switches, but like when being pushed back by GSX or AES. Today I went to try my PMDG 777 and that wooosh sound was constant. It would do it 4 times, then a 5 to 10 second normal and do it all over again. I probably need to get a new card that has the win 10 drivers. My current card is obsolete. Any recommendations? The other problem is when I shut down fsx, it closes like it did in win 7 pro 64bit. But if I try to start it up, I get a message fsx is already running. So I have to use task manager to shut it down completely. I have no Idea what's keeping it from completely closing. In task manager it shows 0% cpu usage and it shows i.e. 112 mgb in memory. And I could let it sit there for hours and it wouldn't close. So it's not that I'm not waiting long enough. It doesn't shut down.

Do I have to select dx 10 preview since I'm now running windows 10? I do have the dx10 fixer installed and running and have dx10 preview selected in fsx. When I had windows 7 I just used dx9.

Do you need DX10 scenery fixer if you upgrade to DX11? My new video card came with the option to update to dx10 or 11. I'm still on dx9. I have fsx +acceleration.

Thanks for the help.

Is there away to change the volume in FS2Crew with 1.4? My iFly 737 and Level-D 763 has volume knobs for the FO and Flight attendants. But I can't find away to change the pmdg 777. I would need to lower the volumes for the 777.

Today I got my first OOM since I got windows 7 pro 64-bit. I know it was because I was doing a flight from KOTH to KSEA. As I turned at UGB vor to head to OLY is when I started getting the beeps and then it said out of memory. I 8gigs of ram, but I guess it can't handle Mega scenery Oregon/Washington, and mega city Portland OR. So if I'm not landing at KPDX I should turn off the mega city Portland I guess. I was at 17000 I guess 3 very large scenery coming together at 1 time is just too much.

I just got Mega scenery Washington and Oregon. I also have Mega city Portland OR. I've notice that some of the airports don't line up with the scenery. I start FSX at Pacific City OR KPFC. When I look done, the sceneries airport is off with fsx. Shouldn't they be the same? I use ADE for my afcads and could adjust the airport to the scenery. Any one noticed this with any of the Mega sceneries?

Is there away to have the tcas only show aircraft 2000 or less above/below? It shows everything right now and it can get cluttered.

I redid the makerwys and did a flight from phnl to klas this time. And once again crossing 8L and taxing onto 8R no approaching rwy. 4L and R I got approaching 4L and 4R. When I lined up on 8R I got on rwy 8R. When I got to FSDT's klas I got all the calls. Approaching when on final crossing 19L. I don't know what it is at phnl. But it does work.

Last night I did a flight from fsdt phnl to fsdt klax. I requested 08R. When approaching 8L/26R raas didn't tell me approaching 26R nor 8L. When I crossed 4R and 4L it told me approaching both of those rnwys. When I started taxing onto 8R it didn't say anything, but when I lined up it said on rnwy 8R. When I approached 24R at klax it said approaching 24R, but nothing when crossing 24L. Today I did phnl to FlightBeam ksfo and the same thing happened when taxing to 8L. No approaching 8L, but announced on runway 8L. There was noting when approading 28L at ksfo. It's kind of hit and miss when approaching runways. Any ideas how to fix this? Or wait and see what happens after the release of sp1.

iFly is going to have a weather radar for their 737 that will work with ASN. From the screen shots they've posted it looks nice. They said sometime in February it should be released.

Lately my ATC has started getting crazy. Yesterday I was flying to FlightBeam KPHX using iFly 737 and ASE weather. When ATC had me descending, it then assigned me 26 even though ASE was showing winds out of the east at about 5. But where I was it was out of the west. On approach there were planes landing on 26 and 25L but then there were planes t/o from 7L and some on final for 7R and 8. So there were planes coming in from all direction. This has happened at KIAD, KLAX. It hasn't been like this until lately. I will be upgrading to ANS. It would be nice if you could set the distance that you can capture the destination airport weather. When I use to use fsmeteo you could do that. I know that ASE has a 80nm radius and can't be changed.

I've got this also, but only at FSDT klax and starting t/o roll. When I'm on 25R it's just after engaging auto-throttle. Today I also tried 24L and the same thing. It only happens with T7 and not with my iFly 737 nor level-d 763. I can also land and taxi to gate.

I've had the problem of fsx minimizing in full screen on it's own. I'll be on a long flight and just cruising along and go somewhere come back and fsx is minimized. I just open task manager and select fsx and tell it to come to front and it's back. I'm running win 7 pro 64. Didn't have this problem with fs9. But at least it didn't crash and have to start over.