Comments on: The Autogen Is Really Fast https:/2016/03/the-autogen-is-really-fast/ Developer resources for the X-Plane flight simulator Tue, 05 Apr 2016 13:17:46 +0000 hourly 1 https://wordpress.org/?v=6.6.1 By: Ben Supnik https:/2016/03/the-autogen-is-really-fast/#comment-12789 Tue, 05 Apr 2016 13:17:46 +0000 http://xplanedev.wpengine.com/?p=6902#comment-12789 In reply to Rod T..

This topic is now BANNED. If you guys want to spill more ink discussing the version numbering scheme, please do it on the org.

]]>
By: Rod T. https:/2016/03/the-autogen-is-really-fast/#comment-12786 Mon, 04 Apr 2016 16:18:01 +0000 http://xplanedev.wpengine.com/?p=6902#comment-12786 In reply to Steaven M..

At the end it does not matter where mathematically the number scheme falls. It is what it is.

I mean, Laminar Research has named this release X-Plane 10.50. Not X-Plane 10.5.

]]>
By: Longranger https:/2016/03/the-autogen-is-really-fast/#comment-12785 Sun, 03 Apr 2016 20:56:05 +0000 http://xplanedev.wpengine.com/?p=6902#comment-12785 In reply to bascon.

No, w2xpl doesn´t do the same. It uses the information of single buildings from the OpenStreetMap DataBase and places in this location either a preconfigured building from its database or generates a building from facades. Only in areas where it doesn´t get any information it can switch the X-Plane autogen on.
So I don´t see what the problem should be, if the X-Plane autogen works differently.

]]>
By: Ben Supnik https:/2016/03/the-autogen-is-really-fast/#comment-12780 Sat, 02 Apr 2016 22:47:27 +0000 http://xplanedev.wpengine.com/?p=6902#comment-12780 In reply to Hans.

I have both an NV and an AMD card for my PC, and if I pull both I can use the Intel mobo graphics. The AMD card happens to be what’s in there right now. It gets left in there a lot because it’s what my Linux partition has drivers for. (Leaving both sets of drivers on Windows works fine, but on Linux you have to swap driver installs, which is painful.)

]]>
By: Hans https:/2016/03/the-autogen-is-really-fast/#comment-12779 Sat, 02 Apr 2016 16:55:45 +0000 http://xplanedev.wpengine.com/?p=6902#comment-12779 Great news and looking forward to 10.50. What was interesting for me is that you develop with an AMD card. I just tested a 390X and the performance for X-Plane was really bad compared with a GTX970, both on Windows though and in 4K. We are speaking about a 10fps difference here. And I honestly went down to minimum rendering settings for testing.

]]>
By: Ben Supnik https:/2016/03/the-autogen-is-really-fast/#comment-12778 Sat, 02 Apr 2016 03:41:10 +0000 http://xplanedev.wpengine.com/?p=6902#comment-12778 In reply to John.

Wait, I don’t agree with either of you; the single core performance of gamer-class CPUs is, per watt, getting better. This is a mix of smarter architecture, larger on chip control structures, etc. The growth is not nearly as large as the improvement in process density, but it’s not -nothing-. I have computers of varying ages in my office, and while the tick from a single generation isn’t huge anymore (maybe you see 10%), over a few generations, it matters. Don’t try to run X-Plane on a 2008 Mac Pro, for example. 🙂 (My previous PC, which was Sandy Bridge, had 2.5x the memory throughput.)

Anyway, there is no question that multi-core is where the most hardware gain is available, not hoping for faster single core speed (either by clock rate or efficiency improvements). We always keep this in mind when constructing new performance sensitive code.

]]>
By: Ben Supnik https:/2016/03/the-autogen-is-really-fast/#comment-12777 Sat, 02 Apr 2016 03:37:08 +0000 http://xplanedev.wpengine.com/?p=6902#comment-12777 In reply to Russ Barlow.

The mobile version of X-Plane (the flight simulator) does not network with the desktop version right now. Xavion and control pad (I think) do.

I agree that there should not be autogen obstacles in the flight path or unrealistic contours on the runways. We already do some processing to try to prevent that, but soemtimes the algorithms are tricked by the data or have bugs. Roads with unrealistic contours is really more of a design problem: the elevation data isn’t accurate enough to reflect the real-world “grading” done locally when a road is constructed.

]]>
By: John https:/2016/03/the-autogen-is-really-fast/#comment-12776 Fri, 01 Apr 2016 23:58:21 +0000 http://xplanedev.wpengine.com/?p=6902#comment-12776 In reply to roymar.

This is what I was trying to get at gently. Each years fastest i7 is about the performance of the last (sometimes lower if you take over locking into account) even if the rest of the line is slowly catching up. Unless Intel stumbles across something that lets us jump to 8-10ghz at reasonable TDP, additional cores is where it’s at.

I have full sympathy though. You guys are jamming a ton of polygons into a scene and reality requires multiple passes. Global lights and shadows, and reflections and scattering and clouds, it’s kind of astounding any of it is going near real time.

AMD and Nvidia still have some room to throw silicon at the problem, but we are pretty stuck at a minimum time a single core can churn through the main loop.

I know it’s a ton to ask, but hey, if it works out there’s at least 6 years worth of 4+ core machines out there and potential people to benefit (unless jamming data over the bus is already the limiting factor?)

(I know this is one of the hardest CS problems, so none of this is a complaint)

]]>
By: Russ Barlow https:/2016/03/the-autogen-is-really-fast/#comment-12775 Fri, 01 Apr 2016 20:17:01 +0000 http://xplanedev.wpengine.com/?p=6902#comment-12775 This may be a bit off topic but I have two gripes about autogen… I think it is responsible. One is buildings, trees, and other obstacles in the glide path. A good example is at LOWI RW 26. There is a single tall building that is very unrealistic as it extends well into the TERPS limitations for obstacles in the glide path. There are many examples of tall trees right off the end of runways that obscure sight of the touchdown zone if you fly the correct glide path.

The second is that a certain airports the runways and taxiways side to side ( roads are even worse too) follow unrealistic slopes and contours. I think XP autogen should create a reasonable apron around all runways and taxiways where gradients are limited ( side edge to side edge ) and then create a fillet to match the terrain surrounding them.

This is an awesome sim and I really feel bad complaining about these realatively small problems. I run 3 50″ 4K monitors ( albeit at 1080p for now) with an i7 and gtx 770 and get quite good frame rates ( 45-60) if I take it easy on the clouds and don’t use HDR.

Also… Do you know if the new improved iPad version will allow networking with the desktop version so as to display cockpit instruments or other views on the iPad as a slave computer?

]]>
By: roymar https:/2016/03/the-autogen-is-really-fast/#comment-12763 Wed, 30 Mar 2016 21:34:16 +0000 http://xplanedev.wpengine.com/?p=6902#comment-12763 re ” Computers also just get faster over time, so I suppose I could solve this by taking a ten year sabbatical. ” Ben, unfortunately they are not getting faster, and I don’t think anything will change in 10 years!!
A couple of years ago I wrote an addition for the “FSX Guide” on this subject and excerpt some of it here:

Back in 1965 Gordon Moore, co-founder of Intel, noted that from the invention of the IC in 1958 to 1965 , the number of transistors on a chip had doubled each year. He predicted that this trend would continue for at least another decade.
He later revised the doubling period to every two years and the prediction became known in computer circles as “Moore’s Law”. This trend has continued to this day and remarkably expected to carry on for at least another 10 years.

Up to 2003, processor clock speed increases followed the same “Moore’s Law” trend and as an example, Maximum PC’s (May 2001) Ultimate gaming machine included the latest fastest CPU from AMD, a 1.3GHz Athlon.
Maximum PC’s (Sept 2003) Dream machine which they described as the “best hand-built PC ever” included the latest Intel 3.2Ghz Pentium 4C.

Here we are 10 years later and the fastest processor you can buy is 3.8Ghz!!
As noted, “Moore’s Law” relative to transistors on ICs (read processors) still prevails, so what’s the holdup on speed?
What’s happened was in the last 10 to 15 years we increased how much power you burned on a chip every time you had more transistors. We ran into the limit of what you can economically dissipate, about 100 watts, in about 2003,
Clocking processors any faster would result in them melting their own circuit boards!
Since then, rather than having very inefficient single processors on a chip, we have made a transition to multiple, much more efficient processors.
It’s not because we had a breakthrough in programming, it’s because power limits us.
If we want to take advantage of “Moore’s Law” , the only way we could get more performance was parallel computers (i.e. multi-core processors).
This means we have changed the programming model, which is one of the biggest changes in the last 60 years of computing.
But Houston, we have a problem…..
Writing software to make effective use of multi-core processors is still extremely difficult for programmers –most of all existing software is incapable of making use of parallel computer technology unless it is re-written.
Overclocking is the ONLY way we are going to get faster computers in the foreseeable future.
In general, with good equipment, expect to end up around 4.5Ghz, Also remember why the manufacturers do not sell the processor rated above 4GHz, they cannot guarantee it’s life expectancy or stability above that setting. That is also presumably why they switched their marketing from locked to unlocked multipliers, the onus is on us if we want higher performance, while they maintain their market share.
Regards
Roy

]]>