Here are a few notes on animation:
The animation commands for OBJ8 take two changes (a start and end rotation or translation) and two dataref values and map them. For example,
ANIM_rotate 0 1 0 -40 70 0 1 sim/flightmodel/whatever
would rotate the following geometry around the Y axis from -40 to 70 degrees as the dataref goes from 0 to 1. Intermediate values between 0 and 1 are interpolated. (For example, 0.5 maps to 15 degrees.) But what happens if the dataref exceeds the bounds specified?
The answer is: the result is extrapolated. If this dataref goe sto 2.0, the rotation will go to 180 degrees. (How I came up with that is left as an exercise for the reader.)
You can take advantage of this to animate rotating things like radar dishes and beacons using the sim/time/total_running_time_sec dataref. This dataref is the number of seconds x-plane has been running. For examlpe:
ANIM_rotate 0 1 0 0 360 0 5 sim/time/total_running_time_sec
This will cause the following geometry to continuously rotate, making a full rotation every 5 seconds. But why does the animation loop? Well, let’s take a look in detail:
When the time is 0 the rotation is 0. 5 seconds later the rotation has made it up to 360, one full turn. Then what? At 6 seconds the rotation will now be 420 degrees. But 420 degrees is the same as 60 degrees; you can’t tell whether the object has made one, two or a hundred full revolutions before turning the extra sixty degrees. So the rotation is actually becoming a huge number but the wrap-around cannot be seen, making the appearance of continuous rotation.
Rotations always occur around the origin. But what if we want to rotate around another point in our object? We must use the ANIM_translate command to move the rotation to where we want. For example:
ANIM_trans 3 4 5 3 4 5 0 0 no_ref
ANIM_rotate 0 -1 0 -90 90 -1 1 jetway/circle1
ANIM_trans -3 -4 -5 -3 -4 -5 0 0 no_ref
This will rotate the geometry around the Y axis from -90 to 90 degrees as the circle goes from -1 to 1. But the rotation happens around the point 3,4,5.
Note that the animation-translate commands have the same coordinates for both translations and no dataref. This is a static translation – it is alawys the same and its sole purpose is to move the rotation to be around a useful point. It is always followed by an opposite translation.
(It is possible to omit the second translation and simply build your animated sub-part with 0,0,0 = rotation point instead of 0,0,0 = the object’s location in x-plane. But this is an advanced optimization.)
A rotating radar dish
And from the end of the OBJ:
LIGHTS 0 2
TRIS 0 1536
ANIM_trans 20.226 22.468 -0.039 20.226 22.468 -0.039 0.0 1.0 no_ref
ANIM_rotate 0 -1 0 0 360 0 6 sim/time/total_running_time_sec
TRIS 1536 1116
One of the secrets of X-Plane development revealed…Nala supervises my work very carefully to be sure I not introducing bugs into the rendering engine. In the event you get threading errors in the next 830 beta, you now know who to blame!
Scenery loading has changed a lot in 8.30. Before 8.30 we loaded 6 scenery tiles (DSFs or ENVs) and completely built them up into memory before we let you fly. We then loaded any new texures while flying. The result is a possible hit on framerate right after a scenery load for textures, and a very long pause while the scenery area gets built.
In 8.30 we now read the full DSF and build the terrain, then start the sim running. We then build the local 3-d “clutter” (objects and roads) while you fly, but we only build up the ones near your plane. As you fly, the ones behind you are destroyed and new ones in front of you are built.
This means a few things:
– Shorter scenery pauses, because we have to do less before we can start the sim.
– Lower framerates right after a load because the sim is doing extra work while you fly to finish the load.
– Lower framerates occaisionally while you fly as a few more roads are built and objects destroyed. This is pretty minimal though because these items come into range gradually.
– Lower memory usage, since only the roads nearby are fully built, not all of them.
This strategy works out particularly well for people with dual-processor or dual-core machines; some of the work to do this “clutter-building” is done on the second CPU while you fly, so the framerate hit is a lot less noticable. Basically we are taking work that was done by the main CPU while you waited and doing it on the second CPU while you fly.
One problem still in 830: when you place the plane, we do not pre-build the roads (but we DO pre-load the textures). If we did not preload the textures, you would be placed in a gray area and see the textures come in. So hopefully in a later beta I will preload the roads if you place the plane using the airport-picking dialog box. This should help provide good framerates as soon as your plane is placed.
I have a new program called “Env2Overlay” that converts the custom obojects in an ENV file to overlay DSFs. This makes it very easy to convert custom airports to version 8.
However one thing I’ve found is that a lot of ENV scenery contains references to missing objects. The ENV loader historically has worked even with objects missing. The DSF loader will refuse to load scenery if objects are missing.
For now I am going to leave the DSF loader in “unforgiving” mode so that missing objects are an error. I think this is more useful to authors: better to clean up the scenery package while converting it rather than convert it to DSF and continue to have missing objects; I think this indicates a packaging problem or other lost content!
I am pleased to say that I have overlays working in X-Plane 8.30. Overlays are DSFs that contain only objects and are loaded on top of the existing terrain. Overlays allow you to add objects to the global scenery to customize airports, etc.
The overlay system will become more powerful over time, but it should be available shortly when X-Plane 830 goes beta.
DISCLAIMER: the overlay DSF listed below may change in format during beta! This is only illustrated to show the relative brevity of overlays compared to full DSFs. (Users who have turned full DSFs to text know how big they can be.)
To give you an idea of what an overlay DSF looks like:
PROPERTY sim/require_object 1/0
PROPERTY sim/overlay 1
PROPERTY sim/west -71
PROPERTY sim/east -70
PROPERTY sim/north 43
PROPERTY sim/south 42
PROPERTY sim/planet earth
OBJECT 0 -70.999146 42.359913 76.000000
OBJECT 0 -70.997780 42.359650 76.000000
OBJECT 0 -70.997566 42.358742 75.000000
OBJECT 0 -70.996155 42.358467 75.000000
OBJECT 0 -70.993088 42.355259 75.000000
OBJECT 1 -70.999634 42.358353 136.000000
OBJECT 1 -70.998306 42.358078 0.000000
OBJECT 1 -70.996956 42.358261 135.000000
OBJECT 1 -70.996773 42.358913 135.000000
OBJECT 2 -70.999100 42.358513 254.000000
OBJECT 2 -70.994141 42.355080 136.000000
OBJECT 3 -70.992317 42.361107 76.000000
OBJECT 3 -70.998398 42.359409 314.000000
Tools to make overlays coming soon!
I just wanted to say thank you to everyone who has emailed in the last few days – it’s been very uplifting! I’m sorry I haven’t been able to answer everyone individually – but I do appreciate the kind words!
I’ve spent the last week performance tuning X-Plane 830. Performance tuning is a rewarding change of pace from regular global scenery development, because the gratification is instant. Run the sim, get a framerate. Twaek code, run the sim again, get a higher framerate. The gains are immediate and quantifiable.
By comparison, work on global scenery is an exercise in deferred gratification and unpleasant surprises. I write a lot of the code before I have artwork; the results don’t look good until later when the real images are dropped in.
This is a picture of X-Plane 8 beaches with testing textures; Sergio made a beach texture with a descriptive word on each segment and colors indicating their uses. In the simulator, I can verify that the texture placement is correct, the textures line up correctly, they’re not cut off, etc. When people post screenshots of the new global scenery I am usually surprised by what it looks like, because I spent most of the development time looking at images like the one on the left, not the final product.
The unpleasant surprises come from the size of the world: given how big and varied the world is (and how unreliable our global data can be at times), there will always be a location where the particular local data causes our algorithm to make bogus results. A few users have reported vertical walls of water; a classic global data varation problem. Given all of the combinations of shapes of water bodies overlayed on elevation data, our flattening algorithm doesn’t always get it right. Since the water body and elevation data may come from different sources, it’s possible that the water body data is saying there is a lake where the elevation data is saying there is a mountain!
Anyway, enough babbling; Happy Holidays to everyone! Soon we will have a New Year and a new beta of X-Plane – in the meantime, enjoy the time with your families and fly safe!
I’ve received a few emails requesting recommendations for graphics cards…unfortunately I must admit: I do not know which graphics cards will improve framerate the most. The benefit you get from a new graphics card depends on the other components of your system. Also I haven’t tried every graphics card so I don’t have good hard data.
I will suggest this generic advice though: for nVidia cards try the 6600 or 6800 rather than one of the FX series cards. For any card, make sure it supports DX9 pixel shaders (for nVidia this means a 5000 or 6000 series; for ATI this means 9500 or greater, or an x600 or greater). I would not recommend a card with HyperMemory or TurboCache; these schemes use your system memory as VRAM. The cards are cheaper but the performance won’t be as good as real RAM.
I’ve also received questions about settings for the best framerate. If X-Plane 821 is fogging up with the new scenery, 830 may provide some amount of relief; we’re working on performance optimization. I can’t say how much improvement we’ll get, but I would recommend waiting for 830 before evaluating your hardware for an upgrade.
There is one setting that can really help mid-level systems: the “world detail distance” rendering setting. If you can run with a few objects, try changing it from ‘default’ to ‘low’. This will cause objects to disappear sooner as you fly away from them; because the sim will not draw as many objects in the distance, you may be able to turn up the object density. In otherwords, you can trade off the density of near objects vs the density of far away objects.
(Also beware of textured lights; they really impact framerate heavily.)
“Five long years I thought you were my man
But I found out I’m just a link in your chain”
— Aretha Franklin, Chain of Fools
A new version of DSF2Text is out, one that works with the global scenery, and I have already seen authors adding custom objects to the global scenery. Great! I have also received some emails from users having trouble with DSF2Text. Please keep this in mind before you despair:
DSF2Text is designed to be a link in a chain of scenery editing tools; its primary audience is programmers who can feed their program’s text files into DSF2Text to generate final DSF files. I never intended to have people editing 45 MB text files to make scenery; the tutorial on how to add objects to DSFs is really a hack.
Please bear with us; in the next few weeks I hope to unveil some new technologies and tools that will be much easier and faster to use. In the meantime if you can get DSF2Text to work great, but if not, please do not worry; better things are on the way.
(As a side note, if you are working on payware X-Plane scenery and are modifying our DSFs, please contact me by email; the X-Plane EULA allows you to make derived freeware from our artwork, but not payware. The new overlay DSFs will allow you to create DFSs that are totally your own.)
Sergio is on the blog now! Sergio is the Godfather of global scenery; his immense and tireless work very much make the global scenery what it is. Without him all we have is a huge pile of triangles.
Massimo and Cristianno also work on the artwork for the globabl scenery and have put in long hours and really gone the extra mile working on the artwork. To appreciate what the three amici have done, try viewing the raw PNG files from the scenery and witness the care, detail artistry and precision of their work.
[EDIT — this bug is fixed in X-Plane 8.30. so the following only applies to older versions of the sim.]
On to the night…this is a bug that gets reported at least once a day: as it gets darker in X-Plane, lights appear on the cities – a few at a time, then more – then poof! They all disappear and everything goes black!
You may notice that if you turn off both the landing and taxi lights then the city lights come back on again. What’s going on?
Well, this bug has been in X-Plane since the landing light was first introduced, and it’s actually a limitation: X-Plane cannot draw the night lighting overlays and the landing light at the same time because the landing light code was written years ago for older, less powerful graphics hardware. Before we had global scenery with lit cities and night, this was annoying but relatively unnoticable. Now that the cities are bright at night, this limitation is very clear.
Perhaps it can be fixed — I don’t know for sure; I am working with this code now. I can tell you this though: if you have older hardware (GeForce 2, GeForce 4 MX, Rage 128, ATI Radeon 7000, maybe a few others) then it cannot be fixed for you – your card doesn’t have power to draw the effect correctly. If you have a newer card (GeForce FX, 6000 or 7000 series, ATI Radeon 9000 series, or Radeon “x” series) you should be able to use a fix if we can develop one. In the middle are cards whose capabilities I don’t know off hand.