Nova

It's really good visible with the Lufthansa or AirDolomiti paint loaded (grey triangle instead of paint).

Yet another thing i noticed: You cannot use the GPU again, when you have landed at the desired airport. Neither with engine running, nor with APU only.

Not sure if this is know or not, because it's somehow familiar with the round off bug on VOR frequencies: Just tried to tune the EDDN ATIS. Freq is 123.070. however, if i type it in (FMC) and hit 2RK to set it to Nav2 Pre it always makes 123.70 out of it. Freq. like EDDM with 123.12 are functioning. Same for Munich Arrival. Freq is 128.02, but when entering it, it say 128.20. Another issue is wrong flight time calculation. I am currently on my way to EDDN from EDDH. I got a shortcut to TABAT, after passing AMLUH, and had to delete some waypoints. Now the time of arrival for EDDN is 12 Minutes with only 71NM to go. But TABAT is 139NM away, and is reached in 24 minutes. I have not tried to reproduce it yet. Just want to ask if this is known. If not, i will do some more testing on it tomorrow and see if it happens again. Edit: Distance to EDDN is stuck at 71, although its more. Being away 96NM now, but still says 71NM and 9 minutes left. Edit2: Ok, after i inserted additional waypoints after NIBIL (had no STAR selected, was dct EDDN after NIBIL) it is now calculating everthing right again. However, this should not b necessary Ohh btw: could someone please edit the title, i'm not so disappointed any more. I'm even glad i bought it *cough* :

Sadly not by using the x-plane key options. I always used the keyboard to type in my waypoints. Before the release i asked if this was possible, because i had serious doubts about that. Phillipp said yes, back then, via datarefs. I thought those key settings in x-plane are datarefs, but obviously not. Thus the assigned keys don't work for the CRJ. But since i save a lot of time by being able to use airways now, it's still faster.

Whereas the GTX260 is not that bad. I run XP9 there with the same settings i have now, but only getting a few more FPS, although the GPU has about 3-times the power (in benchmarks). Guess it's due to bad OpenGL implementation on Windows. :-\ But your notebook cpu is crap, compared to desktop cpus. Even with bosst it has only 2.8GHz on one core. But wasn't able to figure out how many cores it has.

@TOBS Can you post your flightplan? Then i will check this when i'm at home. If we both have the issue, then it's for sure a mistake of navigraph. In the meanwhile you can use one of these routes: FL096-FL195 ROTWE Y126 TUBLO N850 NATOR N869 BENOT FL246-FL285 ROTWE Y126 TUBLO N850 NATOR UN869 BENOT

Ok, maybe the only average textured co-pilot? : ---- When you load the plane cold and dark, everything is dark However, if you turn on the battery, no matter if it is day or night, then the fmc comes to life, as all other buttons. While the dome and overhead lights are still of, the "integral lights" are set to about 3/4 of illumination. The knob is not set to 0 when the plane is being loaded. Left panel, the one just right to the display lights knob (which has no function any more :'( )

Do you have the intersections displayed in your FMC? This is causing me some trouble, like you said. Or do you have the beacon on? I cannot do any night flights with the CRJ because, in the moment it the beacon flashes, i get 0 fps. While being day, it's not a problem.

YAY! I'm not alone with this opinion. ;D As long as "red line" means the course of the flighpath between two points. Because my version of the CRJ has white lines between intersections. : PS: Really don't wanna be in your skin right now. Guess these days you guys have 500% of the stress you had over the last 2,5 years.

Since i got TrackIR this i not a big problem any more to me, but i can understand it. If i don't move my head a lot, i have hard times to read the FMC or get to the baro/nav panel. That's a feature i like in the Dash8, although, not that much of a deal anymore thanks to TrackIR.

Hmm, i will stick to the original one. Since i always had the feeling that ground sounds were too loud, i have set it to 50% since the very first days of XP9. Avionics fans are at 50% as well, and weather only at 25%.

Ok, now comes the tricky part. I used EDDH again with Rwy 33. I made an takeoff without a flightplan, enables navaids, ndbs, airports. Nothing chnaged. Not even with 320NM vision. Then i enabled the fixes/intersections. And it worked. Even with 320NM with the display being more or less only white. So after a few miles, i flew back on heading 180, and made the flightplan (the same EDDH EDDV flightplan i posted earlier). Still no issues. Then i reset the plane again. Same flightplan, AMLUH departure, set AP on etc. No lag occuring any more. But i don't think, that i made something different. Yes it needs a few seconds to update when having 320NM set, but thats completely understandable. This is useless anyway since you can't read anything. *did some testing - not posted yet* Args, and just as i wanted to post it (plane turned to DH525) it started again. Lag even with only 5NM range. Happens when fixes shown, gone when fixes hidden. *did some more testing - not posted yet* DARN!! Now done it the 4th time (this time with engines running), and it occurs when he is on FMS course. Did now testing with QuteScoop, because in the 4th try, i had it running in the background. And right after i that lag started. So i closed it and reloaded the CRJ. Thought this might have been the problem (read here something about openGl getting messed up by other apps). So i closed X-Plane, to give openGL the chance to be loaded completely new, or to reset or whatever. But yet again, all was fine with range 20 and all visible, until passing DH251. With the right turn to DH252 lag began. Edit: Just another small issue: Range 160 and 320 are shown as 16 and 32. Got a bit confused right now.

Displaying anything else than the fixes makes has no impact on the sim. As soon as i enable them the whole sim "freezes" just for a millisecond and the frames go down to 25(?). Can't see how low they get, because they get to 45 again. But this is repeating all the time, until i either stop moving, or turn off the fixes.

You mean, that all displays have the same mirror image, just mirrored so the left 3 get another then the right 3? Edit: Oh and one thing i always forgot to mention. When you switch on the battery, all lights are off, except the ones that illuminate the A/P panel and buttons/knobs on the left side of the cockpit. Arg damn...just can't remember how the are called.... *searching through the manual* Found it: Integral Lighting

Done.

Yes, it's me...again... Anyone else noticed frame drops every half of a second or maybe only every second when you turn on the Navaids (intersections have the most impact)? While standing on the ground, i'm getting 45 fps (X-Plane clean install, only CRJ 200 running there, i don't even have textures installed there). As soon as i begin to move, and the display has to draw all navaids new, its stuttering. Could please someone check that? I would like to have the navaids displayed, although having them not is not a big deal. Thanks

WANT IT NOW!!111elf

The exterior looks, at least from the far, nice, although wingflex looks a bit hard at the outer engine. What about the interor/cockpit? Is this for free or payware?

CRJ: The installer will ask for your email and pass of your X-Aviation account. And that's it. MU: Plane will ask for activation in the sim. You need to the email address, hit generate key, go back to x-aviation site, enter your account, look for the license page and then write the license key into the appropiate field. Then hit ok, and it's activated.

It's a know bug. It chages, because you are obove the lo cirrus/stratus cloads, that seem to draw "shadows" only on these parts.

I know that i am too high. This was only to show what the A/P is doing on route. The slower you are, the more precise it is. I now made a complete new install of 9.69, only with the CRJ. Same route and settings, but FL330 with M.72. I had another scale on the route map, but you can see, that it's pretty much the same. Green = fresh install with missing ground textures Gray overlay = previous screenshot @Japo and/or others I don't want to let the plane look bad, by repeating things. I just want to make sure, that it's not my fault, and/or give you data to work with. If the reason is too much speed, then it should be gone by now. The only thing i didn't try, was 1/2 bank. I will try that tomorrow.

And how do i know, what cruise speed is right, when the plane itself allows me to get that fast? The Pilot handbook has no information regarding that.

I still had about 20-30 ktn until the overspeed protection would have engaged. As long as i'm not running into it, the plane should be able to behave normal. I would even go as far as to say that he has to turn perfect, even while being in "overspeed climb", because this is not different to a normal climb, except for security. I know that the overspeed protection comes in way sooner as the speed tape shows.

Ok, i have now made a very short example flight with the following data: Weather conditions: No Winds or turbulences, everything set to 0ktn, 25NM visibility, weather download off, all layers set to clear (no clouds), temperature 20°, with an QNH of 1013. Load and fuel is standard (when loaded cold and dark). Route: EDDH AMLUH M852 ULSEN EDDV Departure Runway 33 at EDDH with AMLUH7G SID. Arrival ILS27R at EDDV with ULSEN4P STAR. While overshooting the SID is not such a huge problem (climbing at 3500fpm @ 250ktn) it gets one when reaching ULSEN that turns right to OBATU, which then makes a right turn to CEL VOR. I have made 22 screenshots, that show various situations, but i will only post 3 of them. One, showing speeds etc, the other the route from above. 1) Route visible 2) Right before the first turn 3) Flight path The bigger the angle is, the more it overshoots. @3) The terrain is visible at multiple buttons, when zoomed in. The switches are not circles, but more like octagons. And in between the space of the switch and the space of the octagon, you can see through. Not that a big deal, but just wanted to report that. I hope this data helps to find the problem, or that you can at least see if it occurs to you too.

Although i'm not affected by CTDs, my plugins folder has one additional file. Japo32 wrote: In addition to those i got QtCore4.dll in there. It is also located in the "Resources/plugins/vascore" folder. Is this a problem that may lead to A/P problems (referring to my overshooting issue), or did you miss to include that in your list?