Latency Critical-ism

Devrim Erdem (devrim++at++infotron-tr.com)
Wed, 28 Apr 1999 15:57:03 +0300

• Next message: Stephen M. Guest: "pfFlux problems"
• Previous message: Rob Body - HR Mardyn: "Changing the position of the sun"

I have an app where I have some positioning and intersection
work. Performer Pguide says that latency critical processing
shall be before pfFrame and non-latency critical process shall
be after pfFrame.

My app recieves the positioning info from some other app and
utilizes intersectors to position them properly. In my opinion
both are critical. But isect process documented as async and
my isectors don't seem to be correctly computing the intersection
points. What might be the reason ? Currently the order is

        pfSync
        Receive position info
        Compute new pos using isectors
        pfFrame

thanks,

-- 
/*===============================================
M. Devrim Erdem            devrim++at++infotron-tr.com
		                   Chief Engineer
                Simulation & Software Development
                              info(+)TRON, Turkey
http://www.infotron-tr.com
http://abone.turk.net/mderdem
===============================================*/

• Next message: Stephen M. Guest: "pfFlux problems"
• Previous message: Rob Body - HR Mardyn: "Changing the position of the sun"

This archive was generated by hypermail 2.0b2 on Wed Apr 28 1999 - 06:01:20 PDT

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