Hi Sebastian, On 26 February 2015 at 14:48, Sebastian Messerschmidt < sebastian.messerschm...@gmx.de> wrote:
> It worked with older osg-versions, so database generation can be rules > out. It stopped working with the 3.3.3 developer release. > If bugs existed in the original database format that have been addressed in new versions, but don't have a workaround for these old buggy datasets then one certainly can't rule out database generation being a problem. This is why I've asked about generating database from scratch. so little to go on. > It is visible only from the back-side, so stirring around with the > mouse will display it. The information is in the thread, so I can only try > to resummarize, what is going on. > Any idea what might got broken on the way? > No. > With all due respect, and I have a lot for your work, I don't think that > unintentional incompatibilities regarding the format can be tolerated. > While I'd love to see the OSG bug free there is limit on what I can do to fix bugs that I don't have enough to work on to fix. > In retrospective you encouraged me and others to try the trunk, and there > we are ... I found a couple of bugs and tried to give as much detail and > context as possible here - and also I offered to do whatever needed t chase > down the bug. > I do understand, that you cannot spend your time on chasing arbitrary > bugs, with no samples, context etc. provided, but please try to see it from > my point of view: Things got broken, and I don't know how to fix them. > FYI, none of the hours I have worked this month have been paid for. I just working away here for free trying to get OSG the best shape I can. But like everyone else I have bills to pay. So please understand when I push back it's because I *really* can't afford to keep chasing things without anything solid to work with. Robert.
_______________________________________________ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
