You're talking about FSX. Again, X Plane is vastly different. It handles memory completely differently.

Yes it will arbitrarily reduce scenery detail, usually resulting in a sudden fog bank appearing in front of you, which is one of the features I don't like with X-Plane-9. I was hoping X-Plane-10 would leave this up to the user what details to reduce when it runs dry, or when it thinks my performance has dropped below 19FPS.

Yes it will arbitrarily reduce scenery detail, usually resulting in a sudden fog bank appearing in front of you, which is one of the features I don't like with X-Plane-9. I was hoping X-Plane-10 would leave this up to the user what details to reduce when it runs dry, or when it thinks my performance has dropped below 19FPS.

I suppose you could always turn that fog feature off, Tom.

I suppose you could always turn that fog feature off, Tom.

and how do you do that????

and how do you do that????

Isn't it obvious??? Oh good Lord your're right Tom. Just taken a look at rendering settings and I always thought there was a tick box. The only way then would be to reduce your settings to reduce frames and stop the automatic fog rolling in or ...(most likely not what you want to hear) buy a new system. Let's hope X-plane 10 changes all that.Cheers

clear skies plugin:Clear Skies, a plug-in for WindowsClear Skies for Mac Plug-in, UNIVERSAL-

clear skies plugin:Clear Skies, a plug-in for WindowsClear Skies for Mac Plug-in, UNIVERSAL

Have it, but that doesn't stop X-Plane from reducing visibility for performance. I wouldn't mind if it did that to reduce memory, after all if you're running out of memory (VAS) your going to CTD or OOM if you don't, that is what happens in FSX. I do object to the system taking over because I dropped below 19FPS. I feel that should be my choice, whether or not I want to fly at a lower frame rate.

I think I remember Austin saying that if you hit the button that indicates you are going to make a movie, the fog will disappear, and you can fly at whatever framerate you are getting.

The reason for the fog is that the flight-model computation needs a minimum number of frames per second to work. Thats why you can not select a framerate lower than 19 - the "fog" will always roll in on you. If you set your minimum frames to 40 the fog will move in below 40.I find this system a lot more clear than the "framerate target" that FS uses.If you need to, turn on the corresponding warning in the "operations and warnings" tab. Then you will get a hint every time your shiny PC or MAC can´t keep the framerate up enough. Then you will just have to lower your rendering settings (good ones are number of objects and rendering distance).There is no going below 19fps in X-Plane (at least not for a longer duration) - and (this is my personal opinion) if you are simulating flight at below 19fps you are not in it for simulating flight. I remember the MSFS days when anything over 20fps felt smoooooth to me, though...Jan

You're talking about FSX. Again, X Plane is vastly different. It handles memory completely differently.

Well Goran, let's stay honest. You know what the error is called in xplane and you eventually know my thread on this issue over at x-pilot.com.In short, and that's directed at JSkornas post, it is not about "running the sim faster". It is about running the sim in a situation with lots of details, that the computer COULD easily handly with nice framerates, but the 32-bit limitation is in the way. And boom, there you crash to destop.It's called: "xmapped out of memory" in xplane.

It is really too bad that some people think that 64 bit software will solve the world's problems. They should read up on the fact that 64 bit programs run on 64 bit OS systems only run marginally faster or better.

It's not about running faster, it's about lifting the 4GB memory limit which is certainly a worthwhile benefit.

Well Goran, let's stay honest. You know what the error is called in xplane and you eventually know my thread on this issue over at x-pilot.com.In short, and that's directed at JSkornas post, it is not about "running the sim faster". It is about running the sim in a situation with lots of details, that the computer COULD easily handly with nice framerates, but the 32-bit limitation is in the way. And boom, there you crash to destop.It's called: "xmapped out of memory" in xplane.

I have to be honest and say I have never had this error. I've had an openGL error once or twice but my last one was at least a year ago.xmapped OOM is a new one for me.

A little bit of an AI plane visible in this one:

Unfortunately it is of very low resolution and has crappy video compression though.

Oh and was that a go-around I saw at 2:26, before even reaching the threshold? Definitely not a proper missed approach pattern.

As long as I've been flying, there is no "proper time" to go missed, it's the pilots discretion. When we talk about go arounds, the sooner the better is always the smartest, safest time. I've gone missed "in real life" long before crossing the threshold of the runway, It's not improper to do so. Go pick up an FAA flight book.

As long as I've been flying, there is no "proper time" to go missed, it's the pilots discretion. When we talk about go arounds, the sooner the better is always the smartest, safest time. I've gone missed "in real life" long before crossing the threshold of the runway, It's not improper to do so. Go pick up an FAA flight book.

Yes, but you follow the approach heading until you reach the missed approach point which is generally passed the runway. In this video, the planes were veering off before the runway threshold.

Yes, but you follow the approach heading until you reach the missed approach point which is generally passed the runway. In this video, the planes were veering off before the runway threshold.

Usually the MAPt on a precision approach is right at the runway threshold and the procedure calls for some minimum altitude to start making a turn. This way the procedure guarantees no problems with obstacles if you can make the basic 2.5% gradient.There could also be a missed approach that calls for a climb straight ahead to some altitude, followed by a turn to a fix - so if you start the missed approach fairly high you could pretty much immediately turn, long before reaching the vicinity of the runway.There also is the possibility of ATC giving you some immediate instructions after you call the missed approach. Something like "when able turn right heading... climb...".So while I would say that I fully expect XP10s ATC to have flaws and deficiencies for the first few versions - the pattern of go-arounds seen in the video doesn´t look entirely impossible to me.Jan