Hi, > Hi Fredrik, > > Fredrik Andersson wrote: > > >>Have followed the future discussion and though maybe I should share my >>opinions too. I'm very happy with OpenSG. I think it has worked out great >>for us. We started using it a year and a half ago. We had some aspect >>problems that Gerrit helped us with. As he fixed them in a separate branch >>we have been somewhat stuck in 1.6. That hasn't been a big deal since the >>stuff we really would like to see won't appear until 2.0. And I hope that >>our aspect problems will be fixed in 2.0, won't they Gerrit? You haven't >>forgotten about us? ;) >> >> > > Nope, we haven't. You're the power user that's pushing all the bugs in > the multi-thread code. We need more of you! ;) > > >>The major stuff we would like in 2.0 is VBOs and the improved occlusion >>culling. >> > > VBOs are in, Occlusion Culling not yet. OC plays havoc with out-of-order > drawing and setting up a separate drawtree, so we'll have to look into > that more closely.
in the NVIDIA_-_OpenGL_upcoming_features.ppt they talk about conditional rendering, submit a set of geometry to OpenGL that is only rendered if a previous acclusion query passes. Looks like we don't have to change the current simple OC implementation and get a nice speed improvement? Andreas > >>We are also about to add tessellation support in our product and > >>from what I've understood is that the current tessellator in OpenSG is not > >>perfect and it does not seem to be high priority either. What is the plan >>here? Are there any plans to finish it? >> > > I would love to, but I just don't have anybody with the expertise right > now. The basics are there, but the rational support is not done yet. > Akos can probably give you a better idea of what's involved in getting > it done. > > >>I can use another api for the >>tessellation so it's not a big issue. On that note...does anybody know of a >>good tessellator api? Commercial or free. >> >> > > No clue, sorry. > > >>I totally agree with the build problems, it took a while to find out how to >>build OpenSG the first time. I also agree with that we need more example >>codes and demos. As for the documentation, I think it's ok as it is. It's >>much better to put developer efforts into developing. The source code and >>the mailing list can help if something is hard to understand. Although I >>think that the wiki is a good idea. We use trac ourselves and think it's >>great. >> >> > > Good to hear. > > >>On the marketing front I think something should be done to make more people >>choose OpenSG. More announcements on the web and demos. I also think a >>"customer" list would be good. With links to all companies and organizations >>that use OpenSG. So potential new users can see that OpenSG is widely >>used...(as I think....and hope...it is ;) >> >> > > I'm looking forward to seeing your info in the Gallery > (http://opensg.vrsource.org/trac/wiki/Gallery/Main)! :) > > Yours > > Dirk > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Opensg-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/opensg-users > > ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Opensg-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-users
