Veiter
28-11-2010 20:35:22
Hello all,
we use PagedGeometry 1.1.0 for a game that contains a few aggregations of the same object.
For every aggregation (forest, group of trees and so on) a new treeloader3D is created.
Unfortunately, the game crashes every time a treeloader3D-instance is deleted and an
object attached to another treeloader3D-instance comes in the range of view. Because it is the same .mesh,
i suppose the PagedGeometry-Engine deletes ressources (impostors) that are needed
by other treeloader3D-instances.
For treeloader2D, everything works fine, but i cannot imagine that it is not possible to have
more than one treeloader3D for the same .mesh.
Has anyone the same problem or can help us?
Thank you
we use PagedGeometry 1.1.0 for a game that contains a few aggregations of the same object.
For every aggregation (forest, group of trees and so on) a new treeloader3D is created.
Unfortunately, the game crashes every time a treeloader3D-instance is deleted and an
object attached to another treeloader3D-instance comes in the range of view. Because it is the same .mesh,
i suppose the PagedGeometry-Engine deletes ressources (impostors) that are needed
by other treeloader3D-instances.
For treeloader2D, everything works fine, but i cannot imagine that it is not possible to have
more than one treeloader3D for the same .mesh.
Has anyone the same problem or can help us?
Thank you