Reply to Re: Say Goodbye Seq/Frame
If you don't have an account, just leave the password field blank.
Well, there is the obvious question of what happend when there are too many images in one pak file, but then again, if you have 65535 frames in a single sequence, well, there either is a problem, or there will be a problem. Now, since there is a limit to how many images can go into a pak file, why not limit the slot variable to a xxxx variable instead of a xxxxxxxx variable? Would that make much difference in the performance anyway? Also, I think you mean that the slot variable can't exceed 4294967295, cause, er, you didn't count zero.
Also, a pressing question, how do hardboxes fall in line with all this? Is there gonna be a certian couple bytes at the start of the wpak file letting the engine know that the file contains hardbox-images, background-images, music-files, etc? Because, I was thinking, that if you put a single hardbox for a sequence, isn't that easier than multiple hardboxes? That would make it easier, except for the misc. hardbox-image file(s). Or am I completely off tangent, and dink either already does this, or there are not even gonna be hardboxs in Windemere?
G'nite.
Also, a pressing question, how do hardboxes fall in line with all this? Is there gonna be a certian couple bytes at the start of the wpak file letting the engine know that the file contains hardbox-images, background-images, music-files, etc? Because, I was thinking, that if you put a single hardbox for a sequence, isn't that easier than multiple hardboxes? That would make it easier, except for the misc. hardbox-image file(s). Or am I completely off tangent, and dink either already does this, or there are not even gonna be hardboxs in Windemere?
G'nite.
