phillroath

yep - that's what the quotes were for. :-lolPhill

Nope - both are known "bugs" but the 747 works nicely. I am hoping this will be fixed in SP1.Phill

Some have fixed this (or similar problems) with an added line to the fsx.cfg file. Find the DISPLAY section (could be more than one) and add a line as shown below...{DISPLAY.Device.RADEON 9800 SERIES .0} PanelAsTexture=0 <== add this line.Mode=1152x864x32I dont use much in the way of addons becuase with this line my FPS goes down even further and I don't really have good enough performance as is...Phill

Here is the Microsoft PM. This is the latest and best info we have right now.http://blogs.msdn.com/ptaylor/default.aspxPhill

Go to same folder as your fsx.cfg and rename logbook.bin to logbook1.bin and try again. If that fixes it, do a search on logbook to find a fix.Phill

On the Select Aircraft screen, click the details button...http://forums.avsim.net/user_files/163873.jpgOn that page, enter a new tail number.http://forums.avsim.net/user_files/163874.jpgPhill

Wizard, thanks very much for this. Did as you suggested for the Maule and the 737 and really like the results. I used Image Tool that came in the Deluxe SDK, converted to 32 bit, saved as targa file and loaded that into PSP. Then added layer of 0,0,0 and set to 50% (wild first guess), flatened and saved. Back into Image Tool and convert to DXT1, create Mip Maps and saved as .dds file.Loaded up and checked in day, dusk, and night and it is perfect!Let me add my thanks for this good tip. The default inside reflections just seemed a wee bit much.:-lolPhill

Used to have that a lot but it is now fixed for me. Usually after a flight and shortly after clearing the runway it would happen to me. Good description, mushh! :-lolI do not recall the exact moment it was first fixed, but had to do with the settings and the "bluries" and having to lower my expectations. Here are some of the things I did in my fsx.cfg file...{BufferPools} (note all {} should be square brackets)PoolSize=500000 (that's right, it's half the default){Display}TEXTURE_BANDWIDTH_MULT=340UPPER_FRAMERATE_LIMIT=18 {Main}FIBER_FRAME_TIME_FRACTION=0.20{TERRAIN}LOD_RADIUS=4.500000MESH_COMPLEXITY=70MESH_RESOLUTION=20TEXTURE_RESOLUTION=24AUTOGEN_DENSITY=3TERRAIN_MAX_AUTOGEN_TREES_PER_CELL=1500TERRAIN_MAX_AUTOGEN_BUILDINGS_PER_CELL=1000DETAIL_TEXTURE=1WATER_EFFECTS=4YMMV - this is what I did and I am now at a sweet spot of 15 to 18 FPS for most flights in most situations and loving it.My PC - DELL / P4 2.8GHz / 1GB RAM / ATI 9800 PRO 128MB

Thanks for the replys - glad to know I'm not alone, but sorry the two of you are getting the same thing.

The cabin passenger windows at night (and the tail logo) work with the default B747 and CRJ70, but they do NOT work on the default B737 or A321.Is this known problem or is it my system? Did a search with no luck.PhillSystem: Dell 8200 2.8 GHz, 1.0 GB Ram, ATI 9800 Pro with 128 MB.Windows XP Home with SP2.

Had the same problem and found the solution in an older FS9 forum.Go to your fsx.cfg file and find the display section.(DISPLAY. for me it is 9800PRO ATI .0)Mode=1024x768x32TriLinear=1Panelastexture=0 <------------------------- Add this lineNow the black (with weird specs) display is gone and the 2D panels and/or popups work good. However, my frames took a two or three hit. One step forward, half step back. : )

>6. In the Ultralight, the arms don't always move when turning,>sometimes the hands only move looking like the hand has>"detached" from the arm.Following advice below I downloaded latest drivers for my 6800 (went from 5.7 all the way to 6.7) and hands still detached. Then went to options display and there is a checkbox (work from memory here) just below the place you turn on sum bloom or whatever. I think it's called advanced dynamic scenery or something like that. When I checked the box, the arms remain attached to the hands and the legs move in realistic fashion.Have not seen this solution posted anywhere else.