I've been experimenting with adding the fire models to other scenery 
objects - like the flare stack:

http://flightgear.stockill.org.uk/testing/flare.jpg

The results are quite nice, but there does seem to be an issue with sub 
models and scenery objects. Using this to create the model:

<?xml version="1.0"?>
<PropertyList>
  <path>generic_flare_01.ac</path>
  <animation>
   <type>range</type>
   <min-m>0</min-m>
   <max-m>25000</max-m>
  </animation>
  <model>
   <path>fire.osg</path>
   <offsets>
    <x-m>0</x-m>
    <y-m>0</y-m>
    <z-m>200</z-m>
   </offsets>
  </model>
</PropertyList>

with fire.osg in the same directory as generic_flare_01.ac results in a 
"not found" error for "./fire.osg" specifying 
<path>Models/fgfsdb/fire.osg</path> still gives a not found error, but 
for "./Models/fgfsdb/fire.osg" - the path is always relative to the 
current working directory rather than relative to the model, or relative 
to the data path. Either copying the file to the directory you're 
starting the sim from, or changing to the model directory before 
starting solves the problem, so the loaders all work, there's just a 
problem with the search path.

Now I just need to learn more about the osg file format for particle 
systems, smoke and steam for chimneys and cooling towers aren't too far 
away.

I'm using an nVidia 6500, and the impact on frame rate seems to be 
minimal. There are z buffer issues when fire is displayed in front of a 
cloud layer though - that could just need the particles adding to the 
correct part of the scene graph though.

Jon

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Reply via email to