Since I'm already hearing digital beeping siren noises, perhaps some other curious track makers out there would be interested in contributing to this discussion before Drive2Survive and I annihilate what little's left of our brains... well mine anyway...
Vert Talk
LagTest4.zip (223k)
Vert Talk
I have a model I've been playing with which seems to be more than mtm2 can handle up to this point, I'm not asking for help with it, I'm just offering it up for whatever it's worth on the vert talk insanity ;o)
to get this thing to look right in game it'll take a minimum of 18 frames, each frame is unique (no repeats). The problem is that 16 is all the game will take before I get the access violation, 17 and over kills the game.
the animation consists of 152 vertices and 600 faces per frame and uses a single 256x256 texture. the test was done on a track with no other models within range.
to get this thing to look right in game it'll take a minimum of 18 frames, each frame is unique (no repeats). The problem is that 16 is all the game will take before I get the access violation, 17 and over kills the game.
the animation consists of 152 vertices and 600 faces per frame and uses a single 256x256 texture. the test was done on a track with no other models within range.
I don't know how obvious it is, but I think we missed one. Why do the converted evo models give the access violation, but d2s' wind generators give the too many verts message. The difference, since we worked hard to equalize the vert count, is textures. Too many 256's compared to a couple 64's.
Which raises a secondary question, which lags more, animated bins or animated textures?
Well, it's a thought anyway.
Which raises a secondary question, which lags more, animated bins or animated textures?
Well, it's a thought anyway.