Hello Carsten,

I did some more investigations and found that I have had an error in my 
SceneManager.cpp file. I did not store the clip plane beacon node 
separately. I thought that the setBeacon call would deliver ownership to the 
clip plane chunk. But this is not the case. I have to record the beacon node 
separately.  This should probably be documented somewhere. After correcting 
this I see fine caps in my scene. I  uploaded the corrected files, however, 
so you might see how my code look likes.

In any case, the loading with the 10loading.exe tutorial example still fails 
under all circumstances. The positions of the clip planes are plainly wrong. 
The files interalX.osb and rootX.osb are files I did produce with my 
corrected code. They represent the getInternalRoot() and the getRoot() nodes 
from my scene manager class. Number 1 is without any clip plane, number 2 is 
with one clip plane and number 3 is with three clip planes. If the clip 
planes are defined, you might not see anything. The reason is the gigantic 
planes defined for the clipping planes. However, after zooming into the 
scene the model will be visible.

I think that there is a flaw in my reasoning, because I do control the 
positions of the clip planes myself by the clip plane equation instead of 
the beacon. The beacon transformation is always the identity. I will take a 
closer look into that.

So, to cut a long story short I'm not orbiting anymore and I'm cheerful to 
make some more progress now.

Thanks for your patience,

Best
Johannes 




------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users

Reply via email to