I think a *lot* of people are waiting for this; I know I am!
If you would like to work on it, I'm willing to help...
> 2) QvLib OS/2 and DOS/Windows ports
> Is anyone interested in these ? Where should I post 'em ?
Yes, and here. If you're doing a Windows 3.1 port, a good first
step would be to fix the filenames so they don't clash in the first
8 characters of their names...
I honestly wouldnt' bother with a DOS port. For one thing, you'd have
to write your own TCP/IP stack.
> 3) CSG modelling
> Once we come to implement physical dynamics of worlds we are going to have
> to take account of things like mass and material composition. Conventional
> surface modelling simply cannot deal with this.
I think we need to examine where this physical modeling is going to take
place. My feeling is that it won't be something that's replicated on each
of the hosts in the simulation; they're far too busy doing rendering to do
the dynamics as well. I suspect that full-blown physical simulation will
be handled by the hosts on which the entities reside; those hosts will store
whatever information they need on a per-entity basis to do the simulation.
> 4) Messaging
> Maybe I'm being a little preemptive here but for worlds to be dynamic we
> need to implement ways in which objects can change themselves and their
> relationships to other objects over time.
I suspect this is something best discussed on the distributed-vr list.
-- Bernie Roehl University of Waterloo Dept of Electrical and Computer Engineering Mail: [email protected] Voice: (519) 888-4567 x 2607 [work] URL: http://sunee.uwaterloo.ca/~broehl