 | | DATHeader New Release
|
| The problem is fixed. Now it should be possible to process files with approx. size by 1.5 GByte. Sorry for the trouble that maybe caused this bug to you. cu mikeheide (19 years ago, 4-Sep-07, to lugnet.cad, lugnet.cad.dat.parts)
| | | | | Re: DATHeader ALERT!
|
| (...) I seem to recall it was written in VB? If so, the VB text box has a content size limit of 65K. The only way around this is to work on an in memory string buffer and not store (and read back) the result in the text box. (19 years ago, 2-Sep-07, to lugnet.cad.dat.parts, lugnet.cad)
| | | | | DATHeader ALERT!
|
| Please do not use DATHeader on files that exceed 64k because they will be cut at 64k. I will investigate that problem later. I fixed the problem that I had by mirrored subfiles. cu mikeheide (19 years ago, 2-Sep-07, to lugnet.cad.dat.parts, lugnet.cad)
| | | | | Re: LPUB question
|
| (...) Hi Ludo, There is a bug in the l3p program that LPub uses, causing a single part to always look gray when rendered. To fix this you can either (1) go in MLCAD and create a duplicate of the part in the exact same space (I usually take this (...) (19 years ago, 2-Sep-07, to lugnet.cad)
| | | | | LPUB question
|
| Hi, I do have a simple question. I made a ldr file with one piece, 70501B (Minifig Coin with 20 Mark). I colored it yellow, then saved the file and rendered it using LPUB (V. 2.2.0.1). My "problem" now is: Why is my rendered coin always gray, (...) (19 years ago, 1-Sep-07, to lugnet.cad)
|
|
