Re: pfuSmoke problems

New Message Reply Date view Thread view Subject view Author view

Daniel Jia (xilin++at++cagiva.cambridge.com)
Mon, 19 Aug 1996 15:36:32 -0400

In solving the problems of pfuSmoke, such as the second one indicated below, I
rewrote pfuSmoke routines with pfGeoSet and pfGeode. Basically, puffs are
constructed with pfGeoSet's and pfGeoState's. The "Smoke", which is derived
from pfGeode, then references the pfGeoSet's. So each "Smoke" is a pfGeode,
 and can be created, instanced, attached, and deleted freely.

I don't know why pfuSmoke isn't done this way.

>From uunet!holodeck.csd.sgi.com!guest Mon Aug 19 13:31:09 1996
>Message-Id: <199608191708.KAA11093++at++sgi.sgi.com>
>Date: 19 Aug 96 13:04:00 EST
>From: "Robert Reif" <uunet!rdvax.ntsc.navy.mil!reif>
>Subject: pfuSmoke problems
>To: "info-performer" <uunet!sgi.com!info-performer>
>
>I am having two problems with the pfuSmoke routines. There appears to be
>a bug when a smoke is stopped and restarted. I was getting a floating
>puff above the restarted smoke. This is easily fixed by adding the
>following two lines to pfuSmokeMode():
>
> smoke->startPuff = smoke->numPuffs = 0;
> smoke->prevTime = -1.0f;
>
>The second problem is much more serious and not as easily solved. There is
>no way proper way to delete a pfuSmoke once it is created. The pfuSmoke
>routines keep an array of pointers to all pfuSmoke structures created by
>pfuNewSmoke(). If you delete the value returned by pfuNewSmoke,
>pfuDrawSmokes will continue to use the deleted memory which is not a good
>thing.
>
>Are there any plans to fix this problem in a future release or has someone
>else already addressed this problem?
>
>=======================================================================
>List Archives, FAQ, FTP: http://www.sgi.com/Technology/Performer/
> Submissions: info-performer++at++sgi.com
> Admin. requests: info-performer-request++at++sgi.com
>
=======================================================================
List Archives, FAQ, FTP: http://www.sgi.com/Technology/Performer/
            Submissions: info-performer++at++sgi.com
        Admin. requests: info-performer-request++at++sgi.com

New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:53:23 PDT

This message has been cleansed for anti-spam protection. Replace '++at++' in any mail addresses with the '@' symbol.