By markjacksonguy at 2012-02-15
Those test buildings are ugly. It’ll be awhile before I can get rid of them.
I’m creating rock instances and writting placement code (geometry and texture will randomlize later). Each rock instance has a PandaNode and all geometry (and anything else) is attached to the PandaNode. I thus, move/rotate the PandaNode to manipulate the geometry’s position and rotation.
This enables me to place collision on the PandaNode instead of the geometry.
Here’s the thing…
I realize I will create a lot of those rock instances in order to fillout the entire landmass. I came up with this method…
RockInstanceA will act like a parent instance. What I did was reparent RockInstanceB’s and RockInstanceC’s PandaNode to RockInstanceA’s PandaNode. I then called flattenStrong() on RockInstanceA’s PandaNode().
My question is, is this way valid? Will all geometry involved with rock instances A, B and C become one? (I’m not sure about what happens to the unseen collision barriers).
I have another question aside from the above one-
If I have a model, self.TreeA = loader.loadModel(“TreeA”), and use the same variable to load another model, self.TreeA = loader.loadModel(“AppleTree”),
what will happend to the first model resource? Will it drop from memory or get lost?
would it be better to call removeNode() first, then load up another resource (using the same varible)?
self.TreeA = loader.loadModel(“AppleTree”)
Might be a good thing to have a loader.replaceModel(), which would infact dump the first resoure and load in the new one, using the same varible.
Darksiders (PC) uses Fmod!