Re: MP isect data passing

New Message Reply Date view Thread view Subject view Author view

Kowsik Guruswamy (kowsik++at++coryphaeus.com)
Thu, 25 Apr 1996 09:09:26 -0700

On Apr 25, 7:22am, dheskamp++at++ldsa.com wrote:
> Subject: MP isect data passing
> Hello:
>
> I have successfully forked an intersection process, and passed data to it
from my application process using
> pfPassIsectData. I then update the Isect data in the Intersection process
and call pfGetIsectData from the application
> process. I DO NOT see the updated data in the application task.
>
> My question: How does one pass data back from the Intersection process to
the application process. pfGetIsectData
> does not appear to work!
>
>
> Dave Heskamp

pfPassIsectData is always downstream only. If you need to pass data from the
Isect process back to the APP, you need to put the results in a shared memory
segment maybe with a mutual exclusion lock. Not to mention framestamping it.

Probably, the easiest thing to do is to have a pfCycleBuffer and every frame
copy the necessary information to the Isect process and then get back the
results.

  cbuf->getCurData(); // Check to see if we have any hits

  // process the hits

  // fill cbuf with new data
  cbuf->changed();

K.

ps: Only catch is that you may not get the results of the collision immediately
in the next frame, since the number of pfCycleMemory's created by pfCycleBuffer
will be dependent on your APP, CULL, DRAW process model.

-- 
kowsik++at++coryphaeus.com     | pirts suiboM a hguorht neeb sah txet sihT
http://www.coryphaeus.com |
                          | You are not you, you are me! - arnie
work: (408)-395-4537 e201 |

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:52:46 PDT

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