From: Brian W. <bw...@sw...> - 2001-09-15 21:45:50
|
Hi All, I'm been experimenting with the render spu and have some food for = thought. All the demos work fine on my machine... but... When you bolt the render spu directly onto a client it breaks. (win2k, = geforce2&3 on my 2 machines). The food for thought is I'm assuming that's because the client is also = opening up a window and now the dll is in the same process they might be = 'stepping on each other toes'. Which leads me to a discussion question... Why is the render dll opening = up a window and creating a gl context? If the render spu is suppose to = be masquerading as the opengl dll then a 'side effect' of opening a = window seems not good. Should the render spu assume a valid context will be created by the = 'app'? (Looking at the code a see a comment about 'extensions', when loaded = they need a valid context or something like that) Why is the render spu doing anything but simply handing off the calls to = the system libraries? Should the crserver be the one responsible for creating the context (if = it going to be rendering)? For instance if you basically wanted vanilla opengl but wanted = everything rendered in pink, you would 'inherit' from the render spu and = make a small mod. You could then just use the new dll directly on the = client and of course you wouldn't want an extra window hanging around = (or worse breaking the code like is does now). Disclaimer: The intricacies of dll's are above my head at this point and = there may be fundamental technical reasons why this discussion is = moronic. Brian Wylie wy...@vi... |