surfdog

Well let me start by saying I will NOT recommend buying another 780. I say that because, as anyone who has dabbled in FS knows, every system is different and I would feel bad if I convinced you to spend money and you didn't notice any improvement. I purchased my second 780 for other games that truly benefit from SLI and it was on sale for 50% off. I wasn't expecting any performance improvement in P3D or FSX when I bought it but was pleasantly surprised when there was:) I might have been misleading in saying that my performance nearly doubled by adding the card. What I should have said was FPS had a slight increase, but the true benefit comes with increasing graphics settings and such. Overcast conditions no longer turn a pleasant flight into a stuttering mess. I can add things like SGSS with Nvidia Inspector without a harsh performance penalty. The sim just feels smoother. So to me performance nearly doubled because the sim looked that much better. But like I said, I cannot recommend anyone go that route because I can't guarantee that it will work for you. SLI is not officially supported for Prepar3d so things like driver updates, changing settings or installing addons can have an adverse reaction and bring the whole thing crashing down. Hope I didn't get your hopes up to high but 85 fps is doing pretty good as it is.

sli DOES work with P3D! But if you don't know if you're running sli then you are not. Also it only works with single monitor OR Nvidia surround. No dual or weird quad setups. To answer your questions, no memory fix is needed and P3D does make better use of hardware to an extent. I find my 4770K is holding back my 2x 780 when running P3D but the performance is almost doubled when compared to a single 780. I would suggest putting a bridge on the 760's and running single monitor or 3 monitor surround to see if that improves performance.

First I want to say awesome video and your sim looks great! Ok, I've taken an accident investigators approach (which is what would happen IRL after a landing like that ) and recreated the flight in a simulator. It all starts on the pre flight. You turned on the INCR REF SPEED and left it on the entire flight. This increases your Vspeeds by 20kts and is the reason you get the stick shaker after take off and on final. That switch should only be on if you are flying through icing conditions. I also suspect the airplane was very close, if not over, max landing weight. If you left it default you most likely were and the center of mass was out of limits as well. This would make the airplane a chore to handle in any condition. You should use the control panel to load the Q400 not P3D. Also, as stated above, the GPWS flap selector was set correctly but you didn't actually set flaps 15 until about 50ft AGL. That is why you got "TO LOW, FLAPS" when you pulled the throttle back. That wail you heard right before touch down was you pulling the throttle into the ground range in flight. Don't chop the throttle like most planes on landing. The tiny Q400 wings need wind from the props to maintain lift and this is simulated quite well. You should be fully configured for landing and stable at 1000 on the RAD ALT. Try flying the approach at flaps 15 and 135-140kts. If you're light, you can lower the speed but I tend to stay above 120. Set torque to maintain a slight nose down or flat attitude, usually 14-18, and a standard decent rate. At 40 AGL start lifting the nose, no more than 5 degrees, and let the plane settle on the runway. Don't touch the throttle until the nose is on the ground! Kind of long winded but hope I can help.

If you run out of installs, simply log a support ticket with Majestic Software asking to reset your install limit and it will be done.

0 views. Really? Is there something wrong with my settings?

I run a dual monitor setup where my VC is on one large display and panels and such are on a smaller display off to the side. All was fine and dandy in the FSX days. Then I got P3D and it was a complete stutter fest. Tried everything with no luck. Today I read that making sure your memory is running an XMP profile can help stuttering in games. Into the BIOS I went and I was already running XMP. But while I was poking around I saw "Multi GPU Configuration." Clicked enable, plugged my second monitor into the MB, started a flight and boom, no stutters. Was absolutely blown away. This isn't going to work for everyone but if your MB and CPU allows it, give it a go. Don't forget to delete the second display lines in the P3D.cfg and delete the shader folder. Also, you may have to enable the display device (mine is Intel HD4600) in device manager and download the necessary drivers. Good luck fellow stutter hunters!

Make sure "Enable weather data download" is checked in the "configuration manager." Click "weather" tab at top. Select "Use real-weather data" then ok. Enter the airport code or use the search function and you will find what you are looking for. There is no need for a flight plan and you should not change any weather themes in FSX, just leave it default.

The simconnect.xml should be located on your server pc in the app data folder (along with your fsx.cfg.) The simconnect.cfg file on your client pc, or laptop, could be in a number of locations. It depends on the app you are trying to connect with the server. For example, the ASN simconnect.cfg is located at Hifi/ASNext_FSX/SimConnectFiles in your install location. Who knows where PlanG simconnect.cfg is but you control it from the app itself. Hope that is helpful and makes sense.

Glad I could help Ron! That's what it's all about. No beers necessary (but sounds good:) After switching to wifi, close the Explorer window and reopen it, see if that helps.

The manual specifically says, "Properly installing and configuring SimConnect is not documented here." It says to open port 445 in the firewall settings on both machines. That is not related to simconnect settings. If you haven't heard of it, do a search for SimConnect Config Tool. It's an awesome little app that makes configuring simconnect a breeze.

I believe the port must be 4 digits between 4000 and 9999. Something like that. Just use 6000. And make sure the IPv4 address matches.

If you play games or watch movies in 5.1 or 7.1 surround, you should definitely re-install the sound card (assuming it supports it). If you are just worried about FSX, forget about it.

I'll try to answer this question more clearly :rolleyes:. You will only see a loss of duct pressure, assuming the isolation valve is closed, if the engine cannot supply the extra demand. For example, if the ducting completely separated, the pressure indicator would would read 0 or very low depending where the separation was. If this were to happen there would be a fire almost immediately and you would have other problems. If there was a small leak in the ducting somewhere it would not be reflected in the ducting indication. It would be reflected in the engine indication in the form of rising EGT as the bleed air valves try to maintain pressure. Only if the 5th and 9th stage bleed air valves are completely open and you still cannot maintain pressure, you will see a decrease in duct pressure.

I did some testing and it seems the NGX does not simulate the relationship between bleed air and engine performance. Now bear with me because I am more a turbo-prop guy than a turbo-fan guy. Opening the bleed air valve reduces the performance of the compressor section of the engine. To compensate, the engine demands more fuel to maintain the desired power setting. This should result in an increase in EGT and possibly N2. N1 should stay the same because that is what the engine is trying to maintain. In a real life scenario, a bleed air leak is a major failure. Bleed air has a temperature up to 600 degrees F and can be very destructive to the air frame. Because of this, the WING BODY OVERHEAT light should come on almost immediately if you have a bleed air leak. I activated this same failure and let the engines run at climb power for ten minutes and the light never came on. This leads me to believe that bleed air is NOT simulated in NGX. Opening the valves will cause an increase in the duct pressure but thats it. I hope this helps and if anyone else has expanding info please help out.

Maybe look for a rise in EGT. The leak may not be substantial enough to lower duct pressure.

Yes. Completely normal. Talk to some aircraft mechanics and have them tell you some more "normal things" that don't make the news.

Try changing your DPI setting to 100%. I had the same problem and it turned out the default DPI on my laptop was 125%

I experience this with Saitek rudder peddles. Try increasing the null zone a little and checking the reverse box for the left and right brakes in the control axis menu.

Can't argue with you there:) I tend to fly for about an hour, 2 tops, mostly in the pattern doing touch and goes and generally flying in an unrealistic manner for a commercial jet. The 737NGX is not my airliner. She is my private jet. But I do fly with service based failures on. Definitely possible but you will drive yourself nuts chasing processes. Short of building an offline, FSX dedicated machine, there is not much you can do.

If none of the above helps, delete your logbook.BIN in your documents folder. This will delete all your records so if they are really important to you do not try it. Instead exhaust all other means. For me, when FSX starts crashing, freezing, and generally running like crap for no good reason, this is the first thing I do and it works almost all the time. I cant explain why or where I learned it, but its the easiest fix possible. I love my records but sometimes you gotta make sacrifices. You can always just edit the new logbook FSX will create.

It seems this is mostly a problem with low end systems. The OP has a high end modern system and should not run into this issue unless he is trying very hard to cause it. I cant think of any reason why you would switch from full screen to windowed and back during a flight anyway. That just sounds like it would cause problems. I never really looked into it but I experience a significant decrease in performance in windowed mode (maybe dual monitors?) so I dont touch it with any plane. Plus it feels like you're flying Internet Explorer and thats not cool.

Hi there, After exhausting every possible fix for the crash problem, I have thrown in the towel. Instead of spending hours scouring the depths of the internet and countless more testing, I have learned to live with it. Having said that, there are several things you can do to minimize fatal errors. -Re-read the manual to ensure FSX is properly configured for 737NGX -Always fly 737NGX in full sceen -Do not change the default flight -Change current location, current time and season, and current weather BEFORE loading 737NGX -After loading NGX, click Fly Now! If you need to change anything, including livery, close FSX and start over -Do not access the menus in flight unless absolutely neccessary. Every time you hit Alt brings you one mouse click closer to fatal error -Do not crash! A crash brings down FSX every time. You can turn crash detection off to solve this, but I leave it on (adds stress and a sense of urgency to every take off and landing) -Upon completion of your flight, exit from the menu by clicking Flight, then Exit. This should be the only time you access the menu I hope this helps. I understand that every system is different, but by following this list, I never have fatal errors anymore. 737NGX is a beautiful but fickle beast and needs to be treated with love and respect!