 | | Re: colors completeness
|
|
(...) Neat. Can you explain what you mean by povray include file? A separate file from the model generated by L3P, that contains color definitions? How do you prevent L3P from replacing your custom colors with the default gray, as it does with other (...) (18 years ago, 3-Mar-07, to lugnet.cad)
|
| |
| | Re: colors completeness
|
|
(...) Actually, in conjunction with Bricksmith's "Export Steps" option, LDView could be used to render each step (since each step is exported as a separate file). As recently discussed here, it is possible to run the current version of LDView on (...) (18 years ago, 3-Mar-07, to lugnet.cad)
|
| |
| | Re: LDView 3.1 on Mac OS X!
|
|
(...) Absolutely. Before I started using LDView and realized that Bricksmith could also use its Unofficial folder, any and all unofficial files I downloaded just got dumped in parts. To chime in on the filename length issue, my LDraw folder got real (...) (18 years ago, 3-Mar-07, to lugnet.cad.dev.mac, FTX)
|
| |
| | Re: colors completeness
|
|
(...) I find it easier just to use a different colour for bleys so I can set it up properly in a povray include file. I always use 263 for dark bley but don't yet have a standard for light bley. Tim (18 years ago, 3-Mar-07, to lugnet.cad)
|
| |
| | Re: colors completeness
|
|
(...) My apologies if true. I was going off Steve's assertion in the LUGNET posting I linked to -- I haven't used L3P myself (only LDView). -- joshua (18 years ago, 3-Mar-07, to lugnet.cad)
|
| |
| | Re: LDView 3.1 on Mac OS X!
|
|
(...) As a user (and a programmer; though I've yet to do any work on LDView), I prefer the way Travis is doing things. Not that that makes it right; I'm just saying that you can't (and shouldn't) lump the users and the programmers into two competing (...) (18 years ago, 3-Mar-07, to lugnet.cad.dev.mac, FTX)
|
| |
| | Re: colors completeness
|
|
(...) Correct. As I noted in my other reply, the only way I've been able to render those colors (and a few others) with L3P/POV-ray is to replace the color codes with their 0x02RRGGBB style equivalents, and that's not really the most desirable (...) (18 years ago, 3-Mar-07, to lugnet.cad)
|
| |
| | Re: colors completeness
|
|
--snip-- (...) L3p doesn't support it as far as I can tell... in fact L3P refuses to give bley or dark bley any colour at all. --snip-- Tim (18 years ago, 3-Mar-07, to lugnet.cad)
|
| |
| | Re: colors completeness
|
|
(...) Hi Lutz, most excellent to see some questions from you; it's been a long time since we've conversed. (...) The LDRAW "group" (if you will) has created a color standard in ldconfig.ldr, a text file describing common settings to be used by LDRAW (...) (18 years ago, 3-Mar-07, to lugnet.cad)
|
| |
| | Re: colors completeness
|
|
(...) I think it would be nice if Bricksmith read the ldconfig.ldr file to load color definitions, or if it offered a pane in the preferences or color picker to define new colors. Best of all, if it had an interface like that to read and update (...) (18 years ago, 3-Mar-07, to lugnet.cad, FTX)
|
| |
| | Re: Need (working) program to generate instruction pictures
|
|
(...) yes, I just thought the export option of Bricksmith just would generate pictures, but ended up with single step LDRs. They are of use for rendering, indeed. makes still some work... (...) Yes, I have done as a bypass so far. (...) Ah, thanks. (...) (18 years ago, 3-Mar-07, to lugnet.cad.dev.mac, FTX)
|
| |
| | Re: Need (working) program to generate instruction pictures
|
|
(...) I'd like something like that too. Although I don't think there's currently anything that will make the whole instructions for you, Bricksmith's "Export Steps" option may be a useful start. It creates a separate LDraw file for each step in your (...) (18 years ago, 3-Mar-07, to lugnet.cad.dev.mac, FTX)
|
| |
| | colors completeness
|
|
Hi, I have some questions about all those colors. I am using BrickSmith on Mac, I do not know if MLCAD does offer more colors. Bricksmith is missing the newer transparent dark orange and medium blue colors and some rarely used solid ones as bluish (...) (18 years ago, 3-Mar-07, to lugnet.cad)
|
| |
| | Need (working) program to generate instruction pictures
|
|
Hi, I need some programm to create bitmaps (or other file formats) stepwise instructions, just like the old Ldraw did in DOS. I tried ldglite, but it just shows a white window, even after loading a model. Do I need some addtional software? I am (...) (18 years ago, 3-Mar-07, to lugnet.cad.dev.mac)
|
| |
| | Re: Testing long filenames was Re: Unofficial directory (with non-standard name lenght)?
|
|
(...) showing D:DownloadsShowParameters.exe The second line (Label2) however, stays blank. With friendly greetings, M. Moolhuysen. (18 years ago, 3-Mar-07, to lugnet.cad.dev, FTX)
|
| |
| | I hereby accect long file names!
|
|
(...) It's an utterly complicated way, but it works! Only problem is that GetLongPathName erases all other kinds of command line parameters. Now that I know that at least it is possible to avoid shortened pathnames, I rest my case. I no longer (...) (18 years ago, 2-Mar-07, to lugnet.cad.dev, FTX)
|
| |
| | Re: LDView 3.1 on Mac OS X!
|
|
(...) Indeed. (...) Well that's the part I disagree with. Everyone is different, and making assumptions about what people will want to use is always bad for program developers. The choice should be the user's, not the programmer's. (...) That may be (...) (18 years ago, 2-Mar-07, to lugnet.cad.dev.mac, FTX)
|
| |
| | Re: LDView 3.1 on Mac OS X!
|
|
Before I say anything else, I want to point out that as the author of LDView my comments here are necessarily biased. So keep that in mind as you read them. (...) I disagree that it's not useful to have the unofficial parts in another directory. (...) (18 years ago, 2-Mar-07, to lugnet.cad.dev.mac, FTX)
|
| |
| | Re: Testing long filenames was Re: Unofficial directory (with non-standard name lenght)?
|
|
(...) (URL) on Win2000 SP4 w. (18 years ago, 2-Mar-07, to lugnet.cad.dev, FTX)
|
| |
| | Re: Testing long filenames was Re: Unofficial directory (with non-standard name lenght)?
|
|
(...) My best guess is at that time MS was trying to make things safe for old programs (although it seems senseless for them to have done this with Win32 apps). If you call the Win32 function GetLongPathName on the short path, it will give you the (...) (18 years ago, 2-Mar-07, to lugnet.cad.dev, FTX)
|
