DANEQ99

Hi all, Currently transitioning from P3D to MSFS. My goal is to fly the study level aircraft like Fenix/PMDG etc...But before I get to my first true flight, are there any things that I should look into to help ease the transition for those already experienced with simulators? Are modules like FSUIPC needed? Where can I find performance tips and tricks etc... My main ask is should I treat this sim as something new and need patience for, or are there shortcuts for those more experienced with flight sims to get to my first flight?

This problem occurs mostly at complex airports. Anytime I want to load the aircraft, let's say at Aerosoft EGLL, after reaching 100% and the VC shows, P3D stops responding. I've tried lowering the settings, deleting the CFG, and reinstalling the aircraft but this continues so happens at the complex airports and only with this aircraft. Loading the 747 at the default airport does not result in the sim not responding. Dane Quartel

I know the difference between the two and how to execute each procedure. Sadly I do not know what airports use which. I have heard NADP 2 is more favoured for airlines and is the standard procedure in most US based airports. Are there any charts or any bit of information which says which procedure the airport is using?

Alienware X51 was my first gaming PC I have ever owned and I did not understand anything about building PCs. Anyway, running FSX is a bit of an issue considering I have the I7 3770 not overclocked and GTX 660. I have read people managing to upgrade the X51 with GTX 670s and one case a GTX 700 series I think. So what I want to know: Can I replace the I7 3770 with I7 3770K and add a coolant, and also upgrade the graphics card to GTX 670 or GTX 700 series or even higher seroe which would all fight. And what supplies would I need with your recommend upgrades, OR build my own PC (Only if the upgrade options aren't available/or they will not make much difference. Thanks

Before I am accused of a pirater...well take my word I am not. I bought the 300 a couple of weeks after its release. I load in and I found out non of the click spots are working. This is at EGLL UK2000.

I got my saitek yoke a couple of weeks ago and the calibration is farely annoying. When I boot my computer up the SST program never centers the yoke it always drifts to the right. I tried the saitek fix of deleting something in your registry but then I cannot open the SST program. Help needed please. here is a picture of the calibration error. It only centers when I unplug and re plug it back in after every reboot but that sounds bad.

I have trackir 5, not the pro clip. When I try using it, I cannot see my gauges very well because the centre is too high. I would have to zoom out to about 0.4 to have the gauges reasonably shown, but then it is too tough for my eyes to see. I cannot look down far enough also because then the track clip losing signla as well. Also would the track clip pro help more for this.

The Cfg just contain the graphics and sliders in my FSX. The whole CFG I can show you but I tweaked it for my system. I run it through bojotes tool just to get some extra tweaks which I did not find looking online easily. I can show you my whole cfg if you want but I think the bufferpools may be wrong for your system. Mine is not as powerful as yours.

FSUIPC has the ablility to send a ping noise when your FSX reaches above 3.7GB i think. It recommends you save your flight and quit FSX.

LOD 4.5 reduces your chance to get the OOM. I changed to 5.5 because I am able to without suffering the OOM. The CFG entries, I recommend you copy and paste and remember to backup your CFG in case they do not work. I think the entries I provided will adjust your sliders so they will be the ones I use, but I will still put the picture showing you my sliders. Getting the OOM message in your flight could mean an addon is causing a memory leak. FTX vector has been reported to cause a leak. Unless you are flying addon airports constantly I do not understand why OOMs are occurring for you an hour or so in your flight. One thing I do is de-select airports I will not be using and scenery and only select those I will be using. Like EGLL to KJFK. Only enable heathrow and New York and it works pretty well. Try to find the free DX10 fixes since the fixer is not available now. I think they pretty much do the same thing as the fixer but you do all the stuff. Hopefully this link will take you to the picture. http://tinypic.com/r/k1e1v/8 My weather is at 60 miles in FSX. 60 - 80 in active sky next.

These are some of the things I have done to prevent OOMS for me. The biggest culprit was AI traffic. DX10 is the first step to saving you from OOMs. Second step, remove AI traffic to around 10-15% if you have a high end PC. I used to suffer with PMDG 777, AI traffic between 25-30% and Orbx regions with add on airports and FSDT KLAX. Now when I land. VAS around 3.7, the max 3.85. Pretty high I know but it is about the OOM that actually matters. My FSX can be at 4 GB and no OOM message. That only happens with DX10 and a 64bit CPU. So anyway remove all AI traffic, you can maybe keep GA but commercial needs to go unless you want to stay at default airports. Second DX10 and third look at some sections in my CFG. Before I could only run 4.5 LOD to save me from some OOMs. Now I can run 5.5 Just landed at FSDT KLAX with 5.5. VAS at 3.7 with GSX and PMDG 777. I made this sound confusing I know but for the last time I will go over the points. 1. NO MORE AI TRAFFIC, well above 15% really. DX10 with free fixes, DX10 Fixer is not available and we are not allowed to share it those who purchased. I was lucky and got it before. 3rd. The parts in my CFG have all contributed to no more OOMs. Also one thing to avoid is running ORBX regions like FTX england with UK2000 heathrow. That is the bane of FSX. Those two addons should never be used with high settings and PMDG aircraft. You should basically quit FSX before you land. So try out these things in your CFG and tell me how they worked out. [GRAPHICS] AC_SELF_SHADOW=1 AIRCRAFT_REFLECTIONS=1 AIRCRAFT_SHADOWS=1 ALLOW_SHADER_30=1 COCKPIT_HIGH_LOD=1 D3D10=1 EFFECTS_QUALITY=2 ForceFullScreenVSync=0 GROUND_SHADOWS=0 HIGHMEMFIX=1 IMAGE_QUALITY=0 LANDING_LIGHTS=1 MultiSampleQuality=0 MultiSamplesPerPixel=4 NUM_LIGHTS=8 See_Self=1 SHADER_CACHE_PRIMED=1693500672 SHADER_CACHE_PRIMED_10=1693500672 TEXTURE_MAX_LOAD=1024 TEXTURE_QUALITY=3 Text_Scroll=1 [TERRAIN] AUTOGEN_DENSITY=3 BATCH_AUTOGEN2=1 DETAIL_TEXTURE=1 LOD_RADIUS=5.500000 MESH_COMPLEXITY=90 MESH_RESOLUTION=25 SWAP_WAIT_TIMEOUT=2 TERRAIN_MAX_AUTOGEN_BUILDINGS_PER_CELL=3000 TERRAIN_MAX_AUTOGEN_TREES_PER_CELL=800 TEXTURE_RESOLUTION=29 WATER_EFFECTS=4 [TrafficManager] AirlineDensity=9 AIRPORT_SCENERY_DENSITY=1 FreewayDensity=14 GADensity=6 IFROnly=0 LeisureBoatsDensity=3 ShipsAndFerriesDensity=4

I will take your word on it. But is there any way we could see this in a video. Not to be a buzzkill but pictures are easily altered. I do believe in a product like this but the amount of other threads outside avsim discussing 32bit programs using more then 4gb has resulted in a no or very unstable.

Okay how does this work? There is no info providing it. Search the internet and you basically are unable to do this unless you have full control over the program itself. I am afraid I have to conclude a scam.

Okay thank you. My navigraph is updated to latest 1408. I updated one program to latest airac and that seems to have fix the problem for now.

http://tinypic.com/r/2it4sv8/8 This image is the bane of my FSX. The only thing that crashes my FSX at the moment. It may not be a CTD but it always freezes FSX before happening, especially when loading an addon airport. I have looked on Microsoft forums for answers but not account for this error.