• Advertisement

Archived

This topic is now archived and is closed to further replies.

PR_SetParticleTimeLimit

This topic is 5912 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

The documentation says that the numframes parameter of PR_SetParticleTimeLimit is the number of frames for the particle to live. Is this correct? If so, then the total distance travelled by the particle would be frame dependant. Wouldn''t it be better to give a time-to-live parameter?

Share this post


Link to post
Share on other sites
Advertisement
Not true. It used to be frame based, and you would skip frames according to the ticks passed.

However since the timer has changed to return floating point values, the particles are updated according to ticks rather than frame updates.

Share this post


Link to post
Share on other sites
Ok, that makes more sense. Perhaps you should change your definition in the header and the documentation.

I also notice that the parameter is a DWORD. Shouldn''t it be a REAL if it''s based on ticks now?

Share this post


Link to post
Share on other sites
Could be, but I didn''t want to change more than I needed to in the API.

I don''t think people care about making a particle last 0.016667 of second longer.

Share this post


Link to post
Share on other sites

  • Advertisement