Muskoka

Hi Goran, did a test flight this morning, temperature was -18 Celsius, little cloud, more like ice crystals from the cold. Flew the Duchess, and turned on all the ice data outputs, as well as carburetor heat. The flight was great, and yes, if I got near cloud the ice started to build up. In that case I would turn to avoid anything looking like cloud and the readings would start to drop, very cool. This must be the issue, really need to avoid those clouds in freezing weather. Glen

Well, just tried a few more flights and seem to have found something in common. The aircraft will not climb through clouds, it seems fine until you get into the "total white out cloud conditions" that we see in XPX. If you can still see the ground, even though your in the clouds it seems fine, but as soon as you go into the soup, the rpm's start to drop. I have warnings turned on, didn't get any warning in three separate flights, and every time the rpm's started to drop I tried various positions with the carb heat levers, made no difference. Conditions were cold, below freezing, overcast conditions, pressure was 29.80's. The last time I had her trimmed out nice, everything looked good temperature wise, was in and out of clouds, 3,500ft, then all of a sudden, total white out cloud, no precipitation, and the rpm's started to drop, no warnings on the screen, dropped down out of the soup, made no difference, rpm's never came back, down to the ground we went. I'm going to try another flight right now in another aircraft I have (similar size and makeup) and see if the results are the same. I want to see if it climbs through the clouds, and if I get any warnings. Glen edit: Goran, I don't think it's a problem with your aircraft, I think it's a XPX issue. The other aircraft "Bonanza" exhibited the same behavior. Everything was fine until I got into the soup, total white out, and then the rpm's start to drop to a unrecoverable situation. There are no warnings on screen, nothing. Some weather related effect in the program appears to be over done, like the turbulence. Within less than a minute, you go from normal flight, to these "ridiculous" white out conditions, and the aircraft starts to fail with absolutely no warnings. If it's a icing issue, you should get a warning. All the flights I tested were with real weather.

That's why I was scratching my head, she was climbing out fine, then it was as if I pulled the throttles back. I was able to land, and then sat on the ground for at least five minutes thinking maybe the carbs had froze, or something had iced up. After the five minutes everything still looked ok, temps were fine, it was idling fine, but had no rpm if I pushed the throttles, so I quit the flight. Can't give too much info on conditions, didn't record anything, just going from memory. Flying in Canada this time of the year it's cold, I think the temp was just below 0 Celsius. There was snow in the area and I had gone through some, but it was only for maybe 15 seconds at a time, it wasn't constant. The pressure was low, 29.60's I think. I'm thinking she may have just got heavy with ice maybe, she didn't drop like a rock, but definitely didn't have enough power to sustain flight. I did have one flight this afternoon, and the snow closed in, and then I was in trouble, she went down pretty quick. Again, didn't crash, but it was noticeably different from the flight before. I'll pay more attention to the conditions and see if I can find anything repeatable. She's still nice to fly, looks great, and is easy on the frame rates. Glen

Me too Goran, was going to send you a message and ask about it until I saw this post. Was having a nice flight this morning and was climbing through 6,000ft, then all of a sudden very little power from the engines. I actually had to land in a field, and then I sat there for at least 5 minutes trying to figure out if I had done something wrong. I was looking all over. Made for an interesting situation, was kinda fun, but had me scratching my head. Glen

Double post??

Big improvement with fps on my system, ATI 6970, especially around clouds. Performance has never been an issue, unless near clouds. All my settings are high to extreme, no ai, no HDR. Even HDR is an option now, nice to see. If your system is up to the task, performance is not an issue. One issue though, the cloud draw distance seems to have been reduced. If you are in overcast conditions you get a ring of cloud that extends a equal distance from the aircraft in all directions, and comes nowhere close to the horizon, so the effect of overcast is totally lost. It really doesn't look good. Probably a tweak to help performance, but really hurts the visuals. Here's a screen shot, these are supposed to be solid overcast conditions. Increasing the cloud slider only increases the density of the clouds, not the distance drawn. Draw distance is set on "Very High". Cloud slider was on 60 in the screen shot. Glen

Yes, it seems to work fine. Just finished a nice flight from CYYZ-KBOS, no problems at all. SID's, STAR's everything worked as it should. Glen

Hi Rene, If it's physically installed to the desktop, that address, if your in windows, will look like this. This was mine before I changed it: "C:\Users\Glen\Desktop\X-Plane 10" This is where the problem lies, that address is too long in length. To do a test, you can rename your "X-Plane 10" folder on your desktop to just "X". That is what I did, now it works fine. "C:\Users\Glen\Desktop\X" Glen

Philipp, I'm not getting crash_log.txt either when the CRJ crashes, I used to?? I'm only using XPX at the moment. Glen

Maybe this Philipp, http://www.dixdouze....p/airnavigation Glen Look under features "X-Plane Bridge"

Hi, yes I agree, I had an accident. I guess the point of the post was I shouldn't have. The weather wasn't bad enough to have caused the "accident". I have done some more testing in other aircraft, and it seems to be related to the somewhat "overdone" turbulence. Flying with real weather, in some bad weather, not horrible, but not ideal, 10-15 knot winds, bit of snow, the turbulence jumps all over the place (I watch the data output for weather). It will go from .05 to .3+ in seconds, throw the airplane out of AP mode and within seconds you have an over "G" situation, and your flight is done. Just happened in another payware aircraft. Is there some way to tame the turbulence down, without having to resort to flying without real weather. I guess I could get rid of the "System Failures", would that work?. I'll have to look into it more. Glen

Guys, I think that was the message in the corner of the screen, anyways the aircraft shuts down. This has happened on numerous occasions when climbing out in bad weather, and certainly not going fast enough to do damage to the aircraft. I have posted a screen shot about 2 seconds after it happened, you can see the aircraft starting to bank, but the simulator has already stopped with the error over "G". I don't know what I need to do so this doesn't happen. Is it a XPX, or CRJ thing?? In the included screen shots you see I have the anti-ice stuff on. I also included the "System Failures" "Flying Surfaces" which says the Right wing is inoperative, this I don't understand. I've never changed anything with regards to "Failures". Any help would be appreciated. Glen

Hi Philipp, I removed the plugins I had, here's a screen shot from inside XPX, hope it looks correct. Tried again, exactly the same as before, XPX crashed. Glen Edit: Looking closer, why do the numbers beside the plugins say "2,3,4", where's number 1? Here's my plugin folder in XPX. Forgot, crash_log.txtLog.txt I just looked at the date and time on the crash_log, and it's the one from earlier. The log.txt is current, but the crash_log didn't update? Edit again: Sorry guys, the date on that crash_log says the 24th? Now I'm confused. Log.txt says the 26th at 11:18AM, crash_log says the 24th at 7:02AM.

Philipp, here it is... Glen

Hi Philipp, maybe I can add to this. Started XPX for flight from CYYZ - KBOS. As I start with engines running, reset the IRS's, Off - Nav. Went to POS INT page and entered CYYZ (2LK), copied LAT/LON (2LK) to SET POS (5RK). Went to the FPLN (6RK) page and entered this route "BULGE V252 WELTI J16 ALB GDM4" minus the STAR, so NO GDM4. Then I saved the route and hit the EXEC button (this might have been the other way around, hit EXEC, then save), route looks good on map, everything looks good so far. Checked weather, looks like a 6R departure. Go to DEP/ARR page and select runway 6R and I'm then offered some SIDS, I select the LEST7.06R as you can see in the screen shot, and as soon as I hit the 1LK button, XPX crashes, see the screen shot. There was no "lag" or time in between, it was immediate, click the 1LK button, XPX crashed. Log.txtcrash_log.txt Glen Edit: Here is my status page.

Philipp, guys, thank you very much. Glen

No problem Cameron, I know it's excessive. I just wanted to give as many examples as I could. Glen

More shots from XPX, Sitting on Runway 15 at CYXU ready to go, distance to CYOW is correct, 275 NM. Just after takeoff, making the turn to intercept the route, I've travelled 1 NM. Now look what the distance to destination is, 289 NM. You'll notice that HALBY has gone from 15 NM to 14 NM, that's correct, why has the distance to destination jumped from 275 NM to 289 NM, and I'm 1 NM into the route. Glen

Cameron, no SIDS, no STARS, simple route from CYXU to CYOW. Here it is, YXU V98 YYZ J586 YCF LANRK Here's two screen shots from xp 9.7...I don't make these up.... First is with the route loaded, Runway 9 selected, distance shows correct. Second shot is after restarting XP, exact same procedure, Runway 27 selected, distance is not correct (on the MFD). I'm not trying to give anyone a hard time, I just want to fly. But there is someting wrong in the data or the way the CRJ is using the data, I don't know, but it's repeatable in XP 9.7 and XPX. Glen Edit: And even when it does show the correct distance from the departing airport, it doesn't calculate the distance to destination properly (count down) enroute. When I'm at LANRK which is 40 some odd NM from CYOW the MFD says I still have close to 150 to go. LANRK and CYOW are the only remaining waypoints, there are no more.

Guys, there is still an issue, I tought it was solved, but it's not. Screen shot one, flight plan entered, departure runway selected, distance to destination showing correct, 275-6NM. Screen shot two, FMS showing actual plan, distance from aircrafts current location to the destination on the FMS is correct 197NM, the distance to destination on the MFD is not correct 237NM. That's a frozen snapshot in time, how can the FMS show 197NM and the MFD shows 237NM. Screen shot three and four show the remaining waypoints (Act Legs pages 1 & 2). If you add the shown distances remaining it is close, the distance on the MFD is not. The map view of the MFD shows the same waypoints. Something with the MFD math (distance) is not correct. The math (distance) that displays on the FMS is fine, hope that makes sense. Glen Edit: Yesterday when I thought it was ok, I never actually did a flight, I just confirmed the shown distance to destination from the departure airport. Screen shot two now confirms there is an issue (something's odd), this is from an actual flight.

Philipp, it's fixed, you fixed it..... Just by putting the Departure runway in, all is well in the world again. You can see in the screen shot, I put in the departure runway "9", and now the distance to destination says 275NM, whoooo. You can also see the whole flight plan with CYOW still as the destination. Why it works this way, I don't know, one for you to figure out . Most FMS / FMC's I've used will calculate the distance to destination without putting in a departure runway, but if that's the way this one works, fine with me, it works. Thanks to all for the help. Glen

Ah, now I remember putting that in before, pilot error, cut in my pay, thanks Philipp, one down. Glen **Edit**: Philipp, just sorted out the issue with the engines shutting down when using the hat switch, deleted my prefs. A few days ago I reinstalled XPX and updated to 10.03r2. Then did the installs / reinstalls of the CRJ updates. So, XPX didn't like something after doing the updates. I even tried assigning the different 3d views to different toggles and buttons on my Saitek stuff, didn't make a difference. Anyways it's working properly now, that's all that matters. Glen

Hi guys, just got back from the tooth fairy (dentist). Ok, as usual, fired up XPX, CRJ is sitting at the terminal at CYXU with engines running, move the hat switch on my Saitek yoke so I can look around the cockpit and the engines stop. No biggie, just reload the aircraft, just letting you know it still happens. Maybe I should delete my prefs, although this is a new install of everything, XPX and CRJ..geeeez. Ok, here's some more screen shots. First, I entered the flight plan, actually loaded from a save, loads fine. You can see the route on the MFD. Notice the last waypoint is CYOW, nothing after. There's no SID, no STAR, no Destination runway selected, and hence, no Missed approach waypoints. Then I proceed to put the current temperature in the OAT on the Thrust Limit Page, 2 deg celsius, no N1 Percentages. Second screen shot is again of the MFD showing CYOW as the Destination waypoint, and the distance to that waypoint is 290NM, it should be around 275NM. It's not a big deal on this flight, I can almost do it with my eyes closed. Because I have done it so many times I know what my TOD is, but if it were a flight I was unfamiliar with, and the Destination Distance on the MFD was not correct, your starting you descent at the wrong time / distance. That distance figure has to be accurate, or you could be in trouble. Saying things you already know, I'll be quiet now. Glen

The point is, the route is PHYSICALLY only 275NM, not 290NM. From waypoint , to waypoint , to waypoint, only equals 275NM. The whole route is not 290NM, where is that figure coming from. I don't like doing this but it seems to be the only way to get the point across. Here is the same route in the LDS 767 in FSX, and it has the correct distance of 275NM. Glen Edit: Here's the same route from another flight plan service. Notice the distance to destination. Here's some other screen shots, showing the remaining waypoints and the distance to destination. Guys, I'm 38NM from LANRK. LANRK to CYOW is roughly 35NM, so I'm 38 from LANRK, and LANRK is 35 to CYOW, so the total should be around 73NM, not 143NM that's on the MFD. Edit: Sorry, forgot to say, this is the latest version, downloaded last night, and was XP 10.03 rc2.

Hi Philipp, still have a issue with the destination distance on the MFD. Here's screen shots of the actual route and the distance between the wayoints. If you add them all up they don't equal what the MFD is displaying for distance to destination. The math :15+12+14+8+25+53+38+69+35=269..........not 290. Where is the extra 21NM coming from? Here's the route from SimRoutes: YXU V98 YYZ J586 YCF LANRK......No arrival procedure entered. They list the route with a CAPTL9 arrival, and it's still only 275NM. I still have the oddity with the Saitek yoke, engines shut down everytime I touch the hat switch after initial load of XPX. I do start XPX with the engines running as apposed to cold and dark, that may be obvious. Also, now when I input a temperature on the Perf Page, there's no values for TO, CLB, CRZ, and MCT, there used to be? Screen shot included. I started my usual flight, and gave up, well had no choice as the engines shut down around 16,000ft. It has happened before, just didn't say anything. The odd thing is, the engines all of a sudden shut off (start to spool down), you can hear it, but the gauges don't indicate the the engines have shut off. There are no warnings on the display, they just shut off. Always carry an extra hour of fuel, so it's not the problem. Similar things have happened in another aircraft I fly on a regular basis, starting to think it may be a XPX thing, not the CRJ. Haven't tried XP 9.7 yet. Glen