TonyPitzicatta

Hi, i just got a checkerboard cloud pattern in a kind of overcast sitiuation. The "repreating overcast texture pattern fix" was on, maximum cloud layser at "5". What can i do? thanks!

Hi, I got the same problem. Will the CDU Freeze when i change the STAR and RWY during the flight? I hope there is/will be a fix for the problem. Workaroung is good but hopefully not permanent greets

Hi, I got the same problem. Will the CDU Freeze when i change the STAR and RWY during the flight? I hope there is/will be a fix for the problem. Workaroung is good but hopefully not permanent greets

I found out that when i go back to the Service Pack 2 (3.7.2013.0715), the problem is gone. Downside: WX Avoidance Radar doesn't work.

Hi there, since the last few weeks my REX is missing winds aloft data for waypoints. Has anyone encountered this? My REX Version is 3.8.2014.1211

This was the first nightflight. So, nightscenery is really more processor hungry than daytime? Are there seperate Night and Day Textures? And if so, does Orbx replace both?

Hi, some texture problem is puzzling me. I got very bad textures at night, while at day everything is nice and sharp. The two screenshot are exact the same, just on at night and the other at daytime. I'm using FTX Global, Vector and EuropeLC. It seems as if the night textures seem to need more time/capacity to load, so the time i fly over them they aren't fully loaded. But only at night !?!? I hope someone got an idea. Greetings Tony

Hey guys, I have an issue with my REX essentiels+overdrive build 3.7.2013.0715 the weather is working fine, but the avoidance system doesn' really work. In the random weather mode it just shows the map without any weather and when you move the map it wont extend, so there it is just white beyond a certain area. In the real weather mode it shows the weather, but the map problem stays. hope somebody knows about this thing. greetings tony

@ ofentress i was just trying to help, because i had a similar problem. i wasn't saying anything about what you should use. I was just pointing out that the pmdg 737 can handle both and if you have kg's active and enter your grossweight in lbs (e.g. 164000) the 737 thinks it's weight is 164000 kg. and fyi: i'm using lbs

Check in the pmdg setup what kind of weight measure you have active. KG or lbs. Had a similar problem because i gave the FMC a way to high weight information.

Nevermind! The mistake was a true real life aviation problem that already caused dangerous scenarios: my weight system was set to kilogramms, but i entered my grossweight in lbs. 164.1 kg is a little too heavey So glad now. I'm finally back up there

Hello there, I have a strange problem that is giving me headaches for weeks now. So right to it: I set a route in the FMC, select SID's and STARS etc. and everything is going well. Then I select for example a 26k Thrust settings and go to the takeoff page. There I enter the calculated v-speeds and as soon as i enter the v2 speed, the FMC gives me an "UNABLE NEXT ALTITUDE" error. I know this is due to an altitude restricion in the selected SID. The real problem is that the FMC now calculates a very low climb rate and thinks he can't reach that very altitude restriction. But i flew that SID manually and had to realise that it is perfectly doable. I really don't get it. I would love some help, since i couldn't find a solution yet. I hope i'm making a simple beginners mistake. Greetings, Tony