So I should keep it out of the viewer then? I guess I'm still a little
unclear on how to integrate the rest of the systems so they get updated
every frame.
On Sun, Aug 30, 2015 at 7:50 PM, Tony Vasile wrote:
> Hi Sam
>
> You probably don't want all you networking code in the same thread as the
>
We have a bunch of OpenFlight models with have information in some of the nodes
that we use to configure our system. Is it better to use ReadNodeFile and
post-process the file with a NodeVisitor? Or is is better to override
osgDB::ReadFileCallback and somehow exercise our code when it finds a no
Hi Sam
You probably don't want all you networking code in the same thread as the
viewer thread, especially if the networking code could block. You would be
better off using Update Callbacks to modify the scene when something changes.
Tony
--
Read this topic online here:
http:/
The more modern approach would be texture-arrays which might outperform
texture atlas implementation in terms of implementation effort and
memory bandwidth. It requires all textures to be of the same dimensions.
I'm successfully using this for texture variation on terrain and
vegetation. Unfortu
4 matches
Mail list logo