The emitter definition is tricker to do because how to do positioning anf frequency is ambiguous. It might be necessary to make subclasses for each so positions can be relative or absolute, and frequencies can be on a scale based off an external variable, random or absolute. This also means that emitters have to be cloneable so each entity can have its own.

It might be good enough to have a class where location and orientation can be configured each update step, and the frequency can be set from a scale based on a percentage updated at each update step.

This would also be a great time to create a triangle soup emitter which can take a mesh with an arbitrary number of faces and emit from random locations subdivided from the triangles in the face. (That is, so bigger engine surfaces can have non-point source emitters) Obviously this is a large set of changes, but very important to resolve since we want to use these more generalized emitters for things like debris trails on damage ships, or smoke and sparks from damaged components.

Severity:

Status:

Owner:

Assigned To:

Created:

This Bug is Inactive

A direct link to this page is: http:///projects/?bID=394