Kent Watsen (watsen++at++netcom.com)
Sat, 31 Dec 1994 07:42:28 -0800 (PST)
I've just recently parallelized my DIS simulation
application , it took less then a day, but I still
have one nasty issue to address...
In the unparallelized version, I would load all geometry
from disk at load time. This geometry included the
terrain and an instance of each moving model likely to
be needed. Also at this time I would d/l the textures
associated with the geometry into hardware texture memory.
When parallelized, the above code is considered to be in the
app process space, but the d/l-ing of textures must be in
draw process space.
I have considered several approaches to this, but they all
seem kludgy (having to use a first-time static variable to
indicate the need to do the work). I figure that there must
be some support or, at least, a commonly accepted approach
to do this work efficiently.
Anybody?
Kent Watsen
DCS Corporation
Simulation Branch
703.683.8430 x369
This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:50:46 PDT