 | | Re: Large LDraw/MPD Files?
|
|
(...) What are you trying to view the file with? MLCAD has a hard time when the files get too big even if it is a file with multiple-sub models. Forget about LDView it will hog up memory like crazy trying to turn the model. -Ahui (22 years ago, 20-Dec-02, to lugnet.cad)
|
| |
| | Re: Large LDraw/MPD Files?
|
|
(...) As with most large files, the limitation is generally not the program but the amount of memory on your system and the size limit on your virtual memory. -Orion (22 years ago, 20-Dec-02, to lugnet.cad)
|
| |
| | Re: Large LDraw/MPD Files?
|
|
(...) Cool. Not trying to load a file, just want a tidbit of information ;-) -Tim (22 years ago, 20-Dec-02, to lugnet.cad)
|
| |
| | Re: Large LDraw/MPD Files?
|
|
(...) I've got 512MB of RAM and when I run MLCad with some of my big files I make sure that NOTHING else (including background apps) are running. -AHui (22 years ago, 20-Dec-02, to lugnet.cad)
|
| |
| | Re: Large LDraw/MPD Files?
|
|
(...) One of the first things I will probably try to do with LDView after I finally get 2.0 out the door is to work on its memory consumption. But first I have to figure out where all the memory is getting used. Doing some quick calculations based (...) (22 years ago, 20-Dec-02, to lugnet.cad)
|
| |
| | Re: Large LDraw/MPD Files?
|
|
(...) I'm not sure what you mean by this. Ldglite only creates one structure in memory per part file. It's quite frugal with the memory when you use the L3 Parser. Thanks, Lars. I think I've displayed datsville in ldglite on a PC with as little as (...) (22 years ago, 20-Dec-02, to lugnet.cad)
|
| |
| | Re: Large LDraw/MPD Files?
|
|
(...) I meant basically what you just said. Ldglite doesn't create a new copy of the part each time it is used; LDView does. I do this for various reasons, but I believe that when I go back and revisit those reasons now with the advantage of (...) (22 years ago, 21-Dec-02, to lugnet.cad, lugnet.cad.dev)
|
