Brian Plumb

UPDATE Didn't help - still graphics related

Well the bad news is the problem is back and I'm 99% sure it is graphically related. I have the NY area scenery from the .ORG which has some pretty heavy demands outside of the autogen. At night the demand must be less and that is when it worked. During the day on my last test it didn't. Areas which have higher framerates appear to work better. The good news is at least it isn't Gizmo.

I just updated my other post on this where it appeared (in my case) the PFDs (my post has MFD listed) the Gizmo plugin in the Resources\plugins folder was causing the problem. Not saying that it is the problem, but at least my first attempt after moving the folder out of the plugins the displays did light in a heavy scenery area (KEWR).

Thought I'd send another update - I noticed I had the Gizmo plugin in the "plugins" folder (directory). So I moved it out and sure enough on 10.10b6 all of a sudden I have the PFD's back.

Based on those system specs your ATI card is killing you - that card is an entry level 3D gaming card and X-Plane (even 9) is a bit demanding. Not sure what resolution you are running at but you may want to try lowering it. You may also want to try getting the latest ATI drivers as well: http://sites.amd.com...on_win7-32.aspx 64bit Windows will not help as X-Plane 9 and (for the time being) X-Plane 10 are 32bit applications that can only use up to 2GB of memory. If none of that helps you may want to look at mid-level ATI 7000 or NVIDIA 600 series card with at least 1GB of memory. I wouldn't go high-end since your processor is only an i3 and your probably looking at replacing the whole machine instead of just the graphics card.

Problem occurred again in a high scenery area. Decided to reset to default and put everything back into place I had before except I adjusted the texture resolution from Very High to High and that seemed to fix it. Apparently the other thread with the graphics demand on XP 10 seems to be causing the problem.

OK so the typical - let's reboot the computer and see what happens actually fixed it. I did have a heavy scenery area loaded on the first attempt so the graphics being overdriven may have been part of the problem. Thanks for the suggestions.

No luck - I really should avoid being on the bleeding edge.

Looks like the primary MFDs are staying blank. Even tried reactivating. That's why they call it "beta" NVIDIA GTX580 Going to try to reinstall and see if that makes a difference.

Just making some notes here - I know we are in beta for 10.10 but I figured I'd alert everyone to what I've seen with the CRJ: 1) N2 very slow to "spin up" when starting 2) Flipping the fuel switch at even 18% N1 will kick ITT up to around 1000 - no fire detected though (whew) 3) Oil Pressure high even at idle. At 83% N1 showing 163 PSI. Doesn't appear to hurt anything 4) Autopilot still funky when raising flaps - seen VS drop to under 0 ft/min Flight model "feels" the same.

Thanks for the compliments. I'm running on a WIndows 7 64bit. Core i7-920 with 12GB memory and a NVIDIA GTX 580. Frame rates around 40 in those shots but you can easily drop to 20 near the ground. I've recently been running into trouble the OpenGL driver timeouts which sucks since you never know when they will happen.

With regards to the taxi speed issue - I've determined that (at best guess) that in X-Plane 9.70 with N1 around 48% should keep you rolling at a speed to keep ATC off your back and around 33% N1 for X-Plane 10.04r3. Engines much more powerful with XP 10!

Minor issue - the TAS and GS do not appear when on the ground. It's nice to see GS so I'm not guessing. I went from 1.4.2 to 1.4.4.

On the Topic of frames - It would be great in a future release to have the system save the current pop-up MFD positions. I always move them every time I open up. I know the bugs come first

I was at KCYS (Cheyenne, WY) and trying to enter a flight plan that included the VOR LAR (Laramie) and it crashed every time I tried inputting it, whether it be the first point or in LEGS or in FPLN. I ended up entering the next VOR to get past the problem. I think there are more than one LAR in the database and it is crashing due to that. Using the latest Navigraph data. Just wondering it I'm the only one that can crash it out on this. I know there is an update coming just figuring I add one that appears to be consistent. X-Plane 9.70 Windows 7 64bit

Sorry for the delay very busy work week 1) I was adding it to the LEGS page for a RNAV approach I decided on 2) OK 3) Got it

The second thumbnail (clipboard01) is the "N" based format and the second is missing the route lines. I turned on Airports and Navaids to show that LNK VOR is there (first thumbnail). Once I'm airborne and reach LNK the route lines appear.

Couple of things of note: 1) I remember this problem way back during the 1.1 or 1.2 release. I'd tried to insert a fix into the new FMS on the LEGS page and it crashed to the desktop. The fix was NOT replacing the current waypoint. 2) I was able to crash to the desktop when I tried to use DEL and choose the destination airport on the initial FLPLN page. Not that I would regularly do that but I was messing around with it. 3) The route lines do not show up on the format page referencing the heading (my apologies for not knowing the exact name of that particular screen, it's not the one referencing North AND not the VOR type) until the first waypoint is reached. The previous version showed the route lines immediately. I did get the latest distribution (re-released) X-Plane 9.70 Windows 7 64bit.

I've been tweaking the default pilotview.dat file quite a bit and I'm pretty happy with this one so I figured I'd share it. Position #8 is my favorite for those bumpy rides through the clouds. I'm running in a Window at close to 1920x1080 with a FOV of 70. Be sure to copy your original first! I'm also attaching a Checklister file for those that haven't seen the one floating around out there. It is not perfect but I use it every time I fly just to make sure I don't miss anything. Credit to the original uploader. I just realized I should have posted this in the General Area. If a moderator could move it for me? TIA PilotView.zip clist.txt

FMS now working properly after re-install Display "blurriness" appears during the day as well. Again, they are readable, almost like everything is in a bold font. Engines appear more "normal" after taking off - the taxi power level speed scared me at first

Screenshots left in PNG format X-Plane 10 Screenshot: X-Plane 9 Screenshot I had both lighting dials set the same (or as close the same as possible). As you can see they are still readable, but just appear to be a bit blurry and this may be just some stuff in XP10 we have to wait for. The pop-up displays look perfect as they did in XP9. I'm really not concerned about this particular issue. Still can't get the Parking Brakes to display so I'm going to re-install and see what happens. I recall running into this problem with XP9 and a re install fixed it. I'll post a follow-up on that.

Thanks for the quick replies. I'm going to try to fly again later today (Eastern US Time) in night mode on XP10. Right now I'm back on XP9 to see if I'm just not paying enough attention to the displays and if they are actually the same. I typically don't fly at night in XP9 since I have orthophotos not converted to LIT yet. I know what you mean about the engines - I try to keep cruise under FL300 as it seems to really struggle after FL220 to get to altitude (usually I slowly drop down to 500fpm to maintain reasonable speeds).

Didn't see these - sorry if repost FMS Unable to get External Ground Power Unable to get any additional information on the MFD Menu (eg. NAVAIDS, AIRPORTS) MISC. Engines seem way more powerful - usually to taxi I need around 48% N1 and now it's moving with only a little power added Blurry (barely readable) readouts (tested with night) Note: I did not actually fly as I was concerned about the engine power Windows 7 64bit NVIDIA GTX 580 (latest drivers) 10.03 b10 HDR on with FXSAA Shadows - Global Medium My biggest concerns are with the FMS and engine power