Outerra forum
Outerra Engine => Development screen shots and videos => Topic started by: cameni on September 20, 2010, 06:02:22 pm
-
Here is a short video comprised of some unused pieces of footage made for the Himalayas trip video (http://outerra.blogspot.com/2010/08/himalayas-trip.html).
Shows mainly the failed attempts to land at Lukla and some other sequences. The problem with Lukla runway is that the engine of that particular Cessna has vastly reduced power at that altitude, and cannot propel itself up the slope. One has to touch down at a higher point, using the momentum to overcome it. Which of course usually didn't work as imagined :)
The second half contains many attempts at getting the flyover right; we managed to meet at designated point on like 10th try.
The video ends with one preserved recording of how we always rushed back to the starting positions to make another attempt :)
Himalayas trip - unused footage and failed attempts (http://www.youtube.com/watch?v=pMn7_bsqnow#ws)
-
I loved it! So you're modeling the Cessna's performance at altitude now. That's good; not only is it realistic, but it will leave the skies at the edge of space clear for the vehicle I'd like to see. And it's nice to see the forum getting back on track.
-
You should have used the theme song from the old Benny Hill Show :D
-
Yes the music could have been better; we have an account at ibaudio.com (http://www.ibaudio.com/), a site with production music, but it was getting late and I just took the first one that was fitting a bit :)
-
Hehe, I liked the last bit in the Tatra at insane speeds.....I thought for sure you would crash into that tree (I know you can't actually crash into it yet) and then I thought OK, made it, and out of nowhere another Tatra rushed by at high speed :-)
Thnx for this
-
I thought the last two seconds were the best. Almost had a collision and as well as a good physics moment (even if the Tatra's would have just bounced off each other)! :)
BTW what did you do to get the cessna's tail stuck in the ground at 0:17? :/
-
BTW what did you do to get the cessna's tail stuck in the ground at 0:17? :/
I don't remember exactly, but it's not a problem to get something stuck in the ground. JSBSim stops the simulation if the collision response goes off the limits, slamming to ground at a higher speed does it.
-
Hello,
A friend pointed Outerra out to me about a week ago and I've been following the forums and blog since then. I'm a user and developer for Microsoft Flight Simulator, but I have to say, I'm looking more forward to Outerra and it's applications and development possibilities than I am to Microsoft Flight! :) Keep up the amazing work! ;)
-
Now I know what it feels like to be the dog waiting for the bone to be tossed!
-
After this video: what are you working on now?
Reflections i guess (mirrors werent there :P), maybe networking a little more?
Tell me...
My project is a little lagging behind sadly :(.. Very busy with school... And i was hoping to be rendering some nice planets in my engine in december :(... Well that's of for sure :P
-
Currently we are reworking and updating various key parts of the engine; Angrypig updated an asynchronous job scheduler so it's now much easier to handle asynchronous tasks like loading the resources etc. He's also integrating a new version of JSBSim.
I'm still working on the atmosphere - that must be the hardest thing there to get right btw - that should speed up the rendering and bring a better quality both.
And then debugging the ATI issues will be hell, still behaves absolutely weird and there are no errors reported. I'll have to isolate pieces of code and find the infringing bits, find a workaround and report to ATI .. a clear loss of time for us :(
-
Currently we are reworking and updating various key parts of the engine; Angrypig updated an asynchronous job scheduler so it's now much easier to handle asynchronous tasks like loading the resources etc. He's also integrating a new version of JSBSim.
I'm still working on the atmosphere - that must be the hardest thing there to get right btw - that should speed up the rendering and bring a better quality both.
And then debugging the ATI issues will be hell, still behaves absolutely weird and there are no errors reported. I'll have to isolate pieces of code and find the infringing bits, find a workaround and report to ATI .. a clear loss of time for us :(
Can you explain a little what the weird ati issues are? rendering issues like vertices that arent rendered correct? weird colourisation?
And btw: are you also supporting multiple shaders for different gpu's? like low medium high very high settings? I cant really fix my head around how to implement that clean myself :P. It requires multiple shaders (or branching) but also some things on cpu like tex quality, shader parameters just to mention two.
PS. are you implementing a specific atmospheric scattering algo or developing your own?
-
Most of the ATI problems seem to lie in improper connection between shader stages (vertex-fragment or vertex-geometry-fragment). The issues then manifest wildly - depends on what the variables are used for, colors, misplaced geometry, anything and all. Several of these bugs were reported and fixed already, but there are still some left, and in complex environment like ours they are hard to isolate.
We aren't yet using multiple shaders to differentiate between quality settings, but I guess it will be a mix of conditionals and separate shaders and such.
I'm developing my own atmospheric scattering, loosely based on Eric Bruneton's equations but done differently, simplifying some things to get a better performance.