 | | Re: Subfiles - Question
|
|
(...) Right, but what I want to say is that if the filesize is to big the file needs a lot of time to render. When this is splitted into subfiles the renderer only needs to read smaller subfile. This saves rendertime. Bernd (25 years ago, 22-Mar-02, to lugnet.cad.dat.parts)
|
| |
| | New Part - 2587 Knights Armor [DAT]
|
|
Here is the Knight's Armor. The part isn't quite complete, the front and back mounds of the shouler has not been made until now. CU Bernd 0 Minifig Armor Knight 0 Name: 2587.dat 0 Author: Bernd Broich 0 Unofficial Part 0 Inner Back Plane 1 16 -16 29 (...) (25 years ago, 22-Mar-02, to lugnet.cad.dat.parts)
|
| |
| | Re: Subfiles - Question
|
|
(...) But remember that file size is only a consideration if it makes a difference to the total number of disk clusters it uses. If your disk is formatted to have 4Kb clusters each file takes 4Kb. One 4095byte file containing inlined code will use 1 (...) (25 years ago, 22-Mar-02, to lugnet.cad.dat.parts)
|
| |
| | Re: Subfiles - Question
|
|
(...) In general it's the symmetry, the file size or many repeating items of the part that makes sence to use subparts. In your case you can split it into 4 subparts, each one quarter of the file. So you could save filesize. e.g. only one track-end (...) (25 years ago, 22-Mar-02, to lugnet.cad.dat.parts)
|
| |
| | Fixed Part: 604.dat - Window 1 x 6 x 3 Panorama [DAT]
|
|
0 Window 1 x 6 x 3 Panorama 0 Name: 604.dat 0 Author: Tore Eriksson 0 Unofficial Part Fix 1 16 40 72 4 4 0 0 0 0 0 0 0 4 2-4edge.dat 1 16 20 72 4 4 0 0 0 0 0 0 0 4 2-4edge.dat 1 16 0 72 4 4 0 0 0 0 0 0 0 4 2-4edge.dat 1 16 -20 72 4 4 0 0 0 0 0 0 0 4 (...) (25 years ago, 22-Mar-02, to lugnet.cad.dat.parts)
|
