Christian Adrigan

Thank you. Sorry, I was mixing up things here, just realized you were talking about battery efficiency. In terms of raw CPU power gain compared to Sandy Bridge / Ivy Bridge, the Haswell isn't that impressive unfortunately. Guess their focus really was on efficiency.

Do you have a source for that? According to all tests around (eg notebookcheck.com CPU benchmarks), the Haswell mobile CPUs are like 10-20% faster than the generation 2 and 3 processors.

Hm.

No more crashes for me after loading saved flights, but I get the "NO LAND 3" EICAS message when I continue a saved flight.

Thanks guys. Turning on SS-AA did the trick, the jagged lines on pic#1 are better now, and surprisingly the split on pic#2 competely disappeared. Having blurry fonts is another topic now, lol... Finding the right balance was really easier on my old nVidia card.

Hello, I can see some jagged lines in the 2D panel rendering. I know the panel bitmaps are 1920x1200 originally, looks like when the FSX graphics engine is rendering the bitmap down to my 1920x1080 native resolution, I get the jagged lines. Interestingly enough, I have seen screenshots of the 2D panel with absolutely NO jagged lines, eg at the simflight.de review. The original hi-res bitmap graphics are perfectly crisp, the rendering result in FSX is rather disappointing imo. My graphics card is an ATI 6970M. Any clues on how to fix them? - Thank you! BR,Christian

Thank you so much, now that was really refreshing and pretty much sums up my feelings. :)

30.

Here you go: http://forum.avsim.net/topic/342558-ctd-after-loading-a-flight-with-ngx/ However, I don't know if they fixed the flaps position saving thing too, maybe Ryan knows. Should not be hard to track down this one.

Same here, flaps position not loaded. There is another bug leading into a CTD when loading flights during desc/app phase (which Ryan said has already been fixed), so maybe this one (the flaps pos not saving) has been fixed too in the process. Search the forum for "load" and you will find the thread.

Gents, there is no 2D 4:3 Panel. The only delivered main 2D Panel on release is a 1920x1200 bitmap file. The Wideviewaspect=True only changes the view aspect in the virtual cockpit. It has no influence on the 2D display.

Looks Ryan has added our problem under "confirmed" in the official issues list now.

+1 Thanks for sharing and submitting a ticket. Looks like the issue is completely reproducable. Some additional info: My FSX is in \Program Files, but with full folder- and file-permissions. (Write-protection turned off, too - but that should not interfere when loading flights). Maybe only a wrong flag in one of the save files.

Thanks Zach, I have already done that (actually it's one of the first things I do when I set up a new FSX). That fixes some CTDs during flight, but not those I am experiencing when loading "some" flights. Some can be loaded, some can't interestingly enough. It's perfectly reproducable, I wonder if I should send a pack with a situation's save files to the PMDG support. Clean install, no add-ons, house livery.

Yes, I remember having that too, trying to load an approach situation. 8% loading, trim wheel sound and crash.

I always crash when I re-load a flight that has been saved during the descent phase of the plane. Don't even get an error report, I remember I got those on my first crashes though. When I re-load a CRZ flight or when the plane is still on ground, it seems to work. Another thing: my flaps position seems not to be saved at all.

Hi all, FSX crashes every time when I try to continue 737NGX flights that have been saved during descent. Additional information: I can load flights that have been saved while the plane is still on ground or in cruise. Whenever I try to re-load a flight that has been saved during the descent phase, FSX will always crash upon re-loading the flight. Checked that all 3 save files are in \Documents and in the \Panelstate folder, looks like something is wrong with the Panelsave/-load code. Anyone else having that problem? Any help is appreciated. Cheers, Christian Adrigan EDIT: And another thing: the Panelsave function does not save the flaps state. I save the flight just prior to T/O with flaps 5, when I re-load the state flaps are on zero.