Re: [Flightgear-devel] Volcano - scenery model or AI scenario?

[Thorsten R. <tho...@sc...>]

> So, if you feel, like you're not interested in coding all this real-time  
> stuff, then it would be really nice to at least build this vulcano thing  
> to make it easy to add the real-time stuff by someone else. :o)

Well, that'd point to a third possibility - write a dedicated volcano  
manager that takes care of

* figuring out whether you're 'sufficiently near' an implemented volcano  
and provides you with the control dialog
* [comparing date with historic records to dial activity]
* [fetching online info about activity]
* notifying the weather code about ash clouds
* dispatching to the individual volcano model Nasal code once we're close  
enough to see the volcano

And have the individual Nasal code set details like particle system  
control parameters, eruption sequence,....

(it can be a very low-performance loop which is opt-in).

I have to say up-front that I really won't code anything in [] above. I've  
coded things I don't personally use at all in FG a few times, and I've  
regretted every one of them a few times over, because these features end  
up being poorly tested (I don't use them...) but I'm still expected to  
support them and explain them. So I'll structure this in a way that it's  
easy to extend, but someone has to step up and do it or it won't be there.

* Thorsten