Horde3D

Next-Generation Graphics Engine
It is currently 23.11.2024, 22:41

View unanswered posts | View active topics


Board index » Horde3D Usage » Showcase

All times are UTC + 1 hour




Post new topic Reply to topic  Page 1 of 1
  [ 8 posts ] 
  Print view Previous topic | Next topic 
Author Message
jimbo
 Post subject: The Broken Vow
PostPosted: 14.08.2009, 13:00 
Offline

Joined: 10.04.2008, 09:13
Posts: 86
I've put up an early gameplay video of a 3rd person action game prototype that I've been developing for a while now.
Goal is to provide a showcase for the possibilities of an elaborate 3D game using secret alien technology.
Many people have helped developing graphics for the game and also on this forum support has been great, thanks to all!

I hope you like it, have a nice day!
Top
 Profile  
Reply with quote  
Volker
 Post subject: Re: The Broken Vow
PostPosted: 14.08.2009, 13:12 
Offline
Tool Developer

Joined: 13.11.2007, 11:07
Posts: 1150
Location: Germany
Wow! That's really impressive work! I've never done anything in Lisp, but it looks like something really professional can be implemented with it :-)
Top
 Profile  
Reply with quote  
marciano
 Post subject: Re: The Broken Vow
PostPosted: 15.08.2009, 00:37 
Offline
Engine Developer

Joined: 10.09.2006, 15:52
Posts: 1217
Awesome work jimbo! I think this is the first Horde demo that can be compared to a commerical shooter.

I noticed that the massive explosion brings the framerate down a lot. How many particles are you spawning? Usually the number of particles used for explosions is surprisingly low in next-gen games, somewhere between 20 and 100. However, I'm aware that Horde's particle system is currently not powerful enough to make a good looking explosion with just a few particles. More complex curves for the parameters and flipbook textures would make the difference.

Out of curiosity, how are you creating the decals?
Top
 Profile  
Reply with quote  
jimbo
 Post subject: Re: The Broken Vow
PostPosted: 15.08.2009, 07:13 
Offline

Joined: 10.04.2008, 09:13
Posts: 86
Thanks for the comments ;). Yes the explosions are are way too heavy on the CPU, also because all barrels explode in a chain reaction. I've been fiddling a lot with the params, but I guess making good explosions is quite an expertise.

These are the emitter params:

Code:
<Emitter name="ParticleSystem1" material="barrel/explosion1.material.xml" particleEffect="barrel/explosion1.particle.xml"
          maxCount="50" respawnCount="1" delay="0" emissionRate="200" spreadAngle="360"
          forceX="0" forceY="0" forceZ="0" />

<ParticleEffect lifeMin="1" lifeMax="2.0">   
      <ChannelOverLife channel="moveVel" startMin="4.0" startMax="8.0" endRate="2" />
      <ChannelOverLife channel="rotVel"  startMin="10"  startMax="210" endRate="0.57" />
      <ChannelOverLife channel="size"    startMin="6" startMax="9" endRate="4" />
      
      <ChannelOverLife channel="colR" startMin="0.4" startMax="0.6" endRate="0.0" />
      <ChannelOverLife channel="colG" startMin="0.2" startMax="0.3" endRate="0.0" />
      <ChannelOverLife channel="colB" startMin="0.1" startMax="0.2" endRate="0.0" />
      <ChannelOverLife channel="colA" startMin="0.1" startMax="0.2" endRate="0.0" />
</ParticleEffect>

<Emitter name="ParticleSystem2" material="barrel/explosion2.material.xml" particleEffect="barrel/explosion2.particle.xml"
          maxCount="50" respawnCount="1" delay="0.1" emissionRate="100" spreadAngle="360"
          forceX="0" forceY="0.5" forceZ="0" />

<ParticleEffect lifeMin="1" lifeMax="4.0">   
      <ChannelOverLife channel="moveVel" startMin="4.0" startMax="6.0" endRate="0" />
      <ChannelOverLife channel="rotVel"  startMin="1"  startMax="2" endRate="0.57" />
      <ChannelOverLife channel="size"    startMin="4" startMax="2" endRate="4" />
      
      <ChannelOverLife channel="colR" startMin="1" startMax="1" endRate="0.0" />
      <ChannelOverLife channel="colG" startMin="1" startMax="1" endRate="0.0" />
      <ChannelOverLife channel="colB" startMin="1" startMax="1" endRate="0.0" />
      <ChannelOverLife channel="colA" startMin="-0.1" startMax="0" endRate="0" />
</ParticleEffect>



There is great particle middleware out there. Maybe creating an extension for one would be a good idea.

The decals are parallax shaded meshes with a small offset from the surface they lay on. Also a semi transparent shader will make them appear to match colors on all materials. They're not perfect and shooting several decals over each other will cause z-fighting.
Top
 Profile  
Reply with quote  
marciano
 Post subject: Re: The Broken Vow
PostPosted: 15.08.2009, 11:24 
Offline
Engine Developer

Joined: 10.09.2006, 15:52
Posts: 1217
I assume the problem with the particles is rather the fillrate caused by the overdraw than the CPU costs. Usually good textures are the key to reduce the number of particles and have them look good.

Something like this: http://www.umbralheights.com/images/ut3_editor/smoketex.jpg
Top
 Profile  
Reply with quote  
PuG
 Post subject: Re: The Broken Vow
PostPosted: 20.08.2009, 09:09 
Offline

Joined: 11.06.2008, 10:34
Posts: 119
Impressive!

_________________

Let's bring 'em out! Any old iron! Any old iron!
A door opens and a homewife brings out a rather sophisticated-looking ground-to-air missile system, and dumps it on the cart.
Thank you.
Top
 Profile  
Reply with quote  
Orm
 Post subject: Re: The Broken Vow
PostPosted: 29.09.2009, 22:07 
Offline

Joined: 09.09.2009, 18:58
Posts: 107
Impressive work. I have to know, because I have not been able to get a definitive answer from any source, is Lisp compiled or interpreted?
Top
 Profile  
Reply with quote  
jimbo
 Post subject: Re: The Broken Vow
PostPosted: 04.10.2009, 14:07 
Offline

Joined: 10.04.2008, 09:13
Posts: 86
Orm wrote:
Impressive work. I have to know, because I have not been able to get a definitive answer from any source, is Lisp compiled or interpreted?

Corman Lisp produces optimized assembly, but as with any good Lisps the compiler is available at runtime. Which means code like scripts can also be written in Lisp, loaded in the game at runtime and compiled "on the fly". A major benefit of this is the possibility of runtime development: while the game is running you can change existing functions and data. So no more restarting the game and reloading resources/gamestates all the time.
Top
 Profile  
Reply with quote  
Display posts from previous:  Sort by  
Post new topic Reply to topic  Page 1 of 1
  [ 8 posts ] 

Board index » Horde3D Usage » Showcase

All times are UTC + 1 hour


Who is online

Users browsing this forum: No registered users and 0 guests

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Group