 | | Re: New LDraw Animation: Rotation Animation
|
|
(...) Well.... Maybe not. -Orion (21 years ago, 25-Feb-04, to lugnet.cad.dev)
|
| |
| | Re: New LDraw Animation: Rotation Animation
|
|
(...) I fixed the problem. -Orion (21 years ago, 25-Feb-04, to lugnet.cad.dev)
|
| |
| | Re: New LDraw Animation: Rotation Animation
|
|
(...) I wanted to print this, so I clicked on LDraw'org's "print" icon, and got this... :( Fatal error: Call to a member function on a non-object in /usr/www/users/peero...serapi.php on line 580 Thanks, Franklin (21 years ago, 25-Feb-04, to lugnet.cad.dev)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) It looks good to me. --Travis Cobbs (21 years ago, 24-Feb-04, to lugnet.cad.dev)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
"Steve Bliss" <steve.bliss@earthlink.net> schrieb im Newsbeitrag news:mna930t5n6agvkl...4ax.com... (...) etc. (...) Good idea, so how about [LDRAW_SEARCH] 1=SHOW <MODELDIR> 2=HIDE <LDRAWDIR>P 3=SHOW <LDRAWDIR>Parts 4=SHOW <LDRAWDIR>Models . . . (...) (21 years ago, 24-Feb-04, to lugnet.cad.dev)
|
| |
| | Re: Guide to LDraw "Star Wars Lego" building/modeling?
|
|
(...) Yes, most of the patterned part for the Star Wars line haven't been made yet but that because pattern parts are relatively difficult to model. As far as the other part, which one are you referring too? (21 years ago, 23-Feb-04, to lugnet.starwars, lugnet.cad.dev)
|
| |
| | Re: Ryan's overhauled site
|
|
(...) Whoa, good timing! Just a few hours ago I was poking around your site to see your LDraw-compatible K'Nex and Lincoln Log stuff, and I noticed the slick new design. Very sharp! One comment, though. The K'Nex and Lincoln Log links from this (...) (21 years ago, 20-Feb-04, to lugnet.cad.dev, lugnet.publish, lugnet.general)
|
| |
| | Ryan's overhauled site
|
|
I'm happy to announce after half a year in the making, my entirely re-designed web site has been launched! Visit (URL) to see it. With its new look, Virtual Construction has a better face for the world, and you can even see a separate experimental (...) (21 years ago, 20-Feb-04, to lugnet.cad.dev, lugnet.publish, lugnet.general)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) [snip] (...) This could be addressed by prepending each value/line with 1=, 2=, 3=, etc. Steve (21 years ago, 19-Feb-04, to lugnet.cad.dev)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
"Don Heyse" <dheyse@hotmail.spam....away.com> schrieb im Newsbeitrag news:HtAD4n.BCJ@lugnet.com... <SNIP> (...) <SNIP> (...) FILE:// style is fully machine dependend as well, so there is no need to put file in front, but I'm open to additionaly (...) (21 years ago, 18-Feb-04, to lugnet.cad.dev)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) ME and the NT variants store the environment in the registry so this would only make things worse for 95 and 98. That said, I'd still prefer to keep things short for the environment version of this. One variable, with as many shortcuts as (...) (21 years ago, 18-Feb-04, to lugnet.cad.dev)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) In DOS/Windows the problem with environment space is (I believe) more a problem of limited total environment space. I don't think there's additional limitations on individual variables. So using multiple environment variables might conceivably (...) (21 years ago, 18-Feb-04, to lugnet.cad.dev)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) Right. In case the variable gets too long we can resort to multiple variables: [LDraw] BaseDirectory=C:\LDraw LgeoDirectory=C:\L2P LdrawSearch01=<HIDE>...MyPrims\In Work LdrawSearch02=C:\LDr...MyParts\In Work LdrawSearch03=<MODELDIR> (...) (21 years ago, 17-Feb-04, to lugnet.cad.dev)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) Something similar (but probably not identical to) the above would have my vote (I'll explain below). I would clarify that if ldraw.ini can't be found in the user's home directory (aka the user profile directory), then the Windows directory (...) (21 years ago, 17-Feb-04, to lugnet.cad.dev)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
Hi Don, "Don Heyse" <dheyse@hotmail.spam....away.com> schrieb im Newsbeitrag news:Ht8vwM.ps2@lugnet.com... (...) <SNIP> > (...) Have you ever tried to pull out a variable under MS-Windows with a length of 500 characters? Or what would happen if the (...) (21 years ago, 17-Feb-04, to lugnet.cad.dev)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) Yes, as Lars said earlier: (...) [LDraw] BaseDirectory=C:\LDraw LgeoDirectory=C:\L2P LdrawSearch="<HIDE>C...MyPrims\In Work| C:\LDrawXtra\MyParts\In Work| <MODELDIR>|<HIDE><LD...BFC\PARTS| <HIDE><P>|<PARTS>|<M...arts\Done" I like the single (...) (21 years ago, 17-Feb-04, to lugnet.cad.dev)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
"Don Heyse" <dheyse@hotmail.spam....away.com> schrieb im Newsbeitrag news:Ht6s7G.1792@lugnet.com... (...) major (...) ini (...) user (...) There is another disadvantage of this methode. Environment variables are very system dependend and usualy are (...) (21 years ago, 17-Feb-04, to lugnet.cad.dev)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) A bit wordy, but not bad. How about a few more predefined tags for the standard directories to save environment space? Like using <P> instead of <LDRAWDIR>\P, <PARTS> instead of <LDRAWDIR>\parts, and <MODELS> instead of <LDDRAWDIR>\models? (...) (21 years ago, 16-Feb-04, to lugnet.cad.dev)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
"Don Heyse" <dheyse@hotmail.spam....away.com> schrieb im Newsbeitrag news:Ht1H5p.1G0v@lugnet.com... <SNIP> (...) ;-)))))) (21 years ago, 14-Feb-04, to lugnet.cad.dev)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) Very true. Perhaps you should arrange for someone to email you whenever we actually agree on something here. Since that seems to be a rare occurance, it shouldn't be much of a burden on your inbox. ;^) Hmm, that'd be a nice addition to lugnet, (...) (21 years ago, 13-Feb-04, to lugnet.cad.dev)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) Ok, I didn't get that. But it's not a problem to change that. Finding things we or some agreed on is a hard job, when you do not know what you are looking for, and follow the discussions regulary. Michael (21 years ago, 13-Feb-04, to lugnet.cad.dev)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) I disagree with the idea of platform specific solutions, especially since we're now thinking about including extra information in the list (such as directives to hide certain paths) to make it more compatible with the list used by MLCAD. If (...) (21 years ago, 13-Feb-04, to lugnet.cad.dev)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) Perhaps the delimiter character needs to be platform dependent? I realize that's not an ideal solution for programs. But I don't think people will be shipping LDraw search path settings between OS's, so it would be alright for users. I don't (...) (21 years ago, 13-Feb-04, to lugnet.cad.dev)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
As has already been stated, Willy asked if I could add a feature to LDView to allow it to view models that are created in MLCad using the new feature of the MLCad beta version. It seemed like a reasonable request, so I added the feature, which made (...) (21 years ago, 12-Feb-04, to lugnet.cad.dev)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) So, it seems like the search candidates are: <MODELDIR> (of the currently loaded model (PROJECTDIR)) <LDRAWDIR>\P <LDRAWDIR>\PARTS <LDRAWDIR>\MODELS <LDRAWDIR>\AnotherDir <LDRAWDIR>\AnotherDir\SubDir C:\LDrawXtra\MyParts\In Work (...) (21 years ago, 11-Feb-04, to lugnet.cad.dev)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) [snip] (...) Yes, I thought we agreed on that long ago (URL) (21 years ago, 11-Feb-04, to lugnet.cad.dev)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) I think old Mac's (before MacOSX) use : as directory delimiter. (...) Only the specified directories. It's up to you to specify e.g. LDRAWPOSTDIRS=C:\Som...eDir\PARTS /Lars (21 years ago, 11-Feb-04, to lugnet.cad.dev)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) Since MLCAD is for fun, you should work on it in whatever way makes you happy. I guess you'll have to weigh the enjoyment you get from freely implementing your own standards against any disappointment you may feel if everyone doesn't agree (...) (21 years ago, 11-Feb-04, to lugnet.cad.dev)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) I think that in general it would be a bad idea to put anything like this in ldconfig.ldr. The reason is that this file is distributed with parts updates, so shouldn't contain anything specific to your particular system. Otherwise you have to (...) (21 years ago, 11-Feb-04, to lugnet.cad.dev)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
"Don Heyse" <dheyse@hotmail.spam....away.com> schrieb im Newsbeitrag news:Hsxs1M.rIC@lugnet.com... <SNIP> (...) Ok right, but when I start discussing new features I'm going to implement there will be a much bigger delay in new MLCad version than we (...) (21 years ago, 11-Feb-04, to lugnet.cad.dev)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) I agree, however I'd like to point out that you could have started a discussion here, before inventing your own personal solution. That's what this forum is for. Getting back to your example, I have some questions. Are all of those paths (...) (21 years ago, 11-Feb-04, to lugnet.cad.dev)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
Hi, Just to give my two cents ... "Lars C. Hassing" <sp.lars@am.hassings.dk> schrieb im Newsbeitrag news:Hsw4I7.MxC@lugnet.com... (...) search paths for parts. (...) usual ones. LDView got its implementation after a preview release of MLCAD 3.01, (...) (21 years ago, 11-Feb-04, to lugnet.cad.dev)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) No, because you already need the LDRAWDIR environment variable, or ldraw.ini, or some other OS specific method to find the LDRAW directory. And since directory paths have filesystem dependent quirks, it's probably best to keep them out of (...) (21 years ago, 11-Feb-04, to lugnet.cad.dev)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) just for the record. first time I came across custom folder support was in mid november 2003 doing betatesting for mlcad's new release. for me one of the most significant improvements in 3.01 'cos for the first time I could separate unofficial (...) (21 years ago, 11-Feb-04, to lugnet.cad.dev)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) Hey, you're right. I wonder how the Windows PATH variable handles that. Probably it just doesn't work... Anyhow, the unix PATH variable uses ':' as the delimiter (at least with the bash shell). So maybe '|' is better, even though you need to (...) (21 years ago, 11-Feb-04, to lugnet.cad.dev)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) Sure, I just chose | because ; is allowed in filenames. /Lars (21 years ago, 10-Feb-04, to lugnet.cad.dev)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) I like this idea. Can you support delimiting paths by ';' instead of '|'? ';' is more in line with the delimitation in the PATH environment varible. -Orion (21 years ago, 10-Feb-04, to lugnet.cad.dev)
|
| |
| | LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
Several users have asked for an option to L3P for specifying additional search paths for parts. LDView already has implemented "Extra Search Dirs" to search after the usual ones. I think it would be of common interest and for the benefit of the (...) (21 years ago, 10-Feb-04, to lugnet.cad.dev)
|
| |
| | Re: [LSC] Colour Definition meta-statement
|
|
(...) I'm not sure you're right there. I think Steve may have been trying to achieve a specific dithered look, different from the effect created by the pre-defined metal code in say ldview or ldglite, probably to better differentiate some static (...) (21 years ago, 6-Feb-04, to lugnet.cad.dev)
|
| |
| | Re: [LSC] Colour Definition meta-statement
|
|
(...) Whoops. Silly me. It's amazing the tricks memory can play on you ;-). (...) While this is still probably do-able, I think my original argument about the possible creation of future tags still holds (unless you're also agreeing to the enforced (...) (21 years ago, 6-Feb-04, to lugnet.cad.dev)
|
| |
| | Re: [LSC] Colour Definition meta-statement
|
|
(...) Well, I don't think that qualifies as an argument for its inclusion in the new !COLOUR statement, since those are already covered by the more precise pre-defined materials. --Travis Cobbs (21 years ago, 6-Feb-04, to lugnet.cad.dev)
|
| |
| | Developers! What softwares? ([LSC] Colour Def...)
|
|
(...) Why not just RGB instead of the not too intuitive VALUE? (I mean, it colud be any parameter value) Developers, what softwares will be updated to support this? L3P? ML-Cad? L3Lab? LDView? ...? /Tore (21 years ago, 6-Feb-04, to lugnet.cad.dev)
|
| |
| | Re: [LSC] Colour Definition meta-statement
|
|
(...) I don't want to specify that some parameters are order-specific, and others aren't. I'd rather they are all one way or the other. Goes back to easier 'correct' parsing. However, I'm sure the entries in ldconfig.ldr will always have their tags (...) (21 years ago, 6-Feb-04, to lugnet.cad.dev)
|
| |
| | Re: [LSC] Colour Definition meta-statement
|
|
(...) Actually, the spec says just the opposite, that tags (keywords) are not case-sensitive: (...) That seems reasonable. Steve (21 years ago, 6-Feb-04, to lugnet.cad.dev)
|
| |
| | Re: [LSC] Colour Definition meta-statement
|
|
(...) Actually, I've most recently used dithering to simulate chrome/metal/metallic parts. Steve (21 years ago, 6-Feb-04, to lugnet.cad.dev)
|
| |
| | Re: [LSC] Colour Definition meta-statement
|
|
(...) OK, I'm alright with that. (...) If that's a needed parameter, I'd rather have it follow the METALLIC keyword. (...) I'm ok with that, too. Is '50%' really an adequate description? There can be many brush patterns... Steve (21 years ago, 6-Feb-04, to lugnet.cad.dev)
|
| |
| | Re: [LSC] Colour Definition meta-statement
|
|
(...) There had been discussion previously about differentiating true comments from meta-statements. The LSC agreed that it seems like a good idea to start prefixing meta-keywords with a punctuation mark, and we chose !. And !COLOUR is shorter than (...) (21 years ago, 6-Feb-04, to lugnet.cad.dev)
|
| |
| | Re: [LSC] Colour Definition meta-statement
|
|
(...) Actually, I was considering the possibility of (patterned) parts including custom color definitions, which would only apply to that part. (...) That's a good question. Think about this: what if file A also has some surfaces hard-coded to color (...) (21 years ago, 6-Feb-04, to lugnet.cad.dev)
|
| |
| | Re: L3PPARTS (Was: Re: Change to existing policy on embedding POV-Ray code in Official Files)
|
|
(...) Me, too. This also solves an issue for having .dat files not too detailed, like the rounded metal parts on 12V train conductor parts. Now the .dat files can contain a square box, which is fast drawn in construction programs and the .inc files (...) (21 years ago, 30-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: L3PPARTS (Was: Re: Change to existing policy on embedding POV-Ray code in Official Files)
|
|
(...) [snip] (...) I think it's a good idea! The only thing I think needs looking at is the naming - should it be dedicated to L3P or to the renderer, eg: RENDERPARTS\POVRAY RENDERPARTS\BRYCE etc. That way, people can provide their own program to do (...) (21 years ago, 30-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: L3PPARTS (Was: Re: Change to existing policy on embedding POV-Ray code in Official Files)
|
|
I Like it :) It is a great solution to a sticky problem. -Chuck (21 years ago, 29-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Matrix mirroring question
|
|
(...) Thanks. I implemented it that way, and it seems to be working so far, so I believe that everything is fine. (...) You're too right. Unfortunately, I can go for a while and do a really good job of commenting, and then I'll slack off for one (...) (21 years ago, 29-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: [LSC] Colour Definition meta-statement
|
|
I have these comments: 1) Why not use COLOURDEF in stead of introducing the'!' ? 2) CHROME | METALLIC | RUBBER seem to me like materials. Are they just shortcuts for convenience? 3) It should be possible to specify RGB color in decimal. Either r,g,b (...) (21 years ago, 29-Jan-04, to lugnet.cad.dev)
|
| |
| | L3PPARTS (Was: Re: Change to existing policy on embedding POV-Ray code in Official Files)
|
|
(...) Yeah, well, it's been three years since the last L3P release, so I guess it's about time for another :-) The current v1.3 release has proven to be quite stable, so I have just collected and implemented a list of wishes from various users. (...) (21 years ago, 29-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Matrix mirroring question
|
|
(...) Since det(AB)=det(A)det(B) I don't think it matters whether you check the determinant (mirroring) at each level or the final level. Too bad you didn't add a comment in your old code :-) I often beat myself for not adding more elaborate (...) (21 years ago, 27-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: [LSC] Colour Definition meta-statement
|
|
(...) When I first read, this, it seemed reasonable, but probably difficult to implement in a renderer. The more I think about it, though, the more I think the difficulty outweighs the niceness. Specifically, I think it would be a royal pain to (...) (21 years ago, 28-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Change to existing policy on embedding POV-Ray code in Official Files
|
|
(...) this is exactly what I was hoping for. w. (21 years ago, 27-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: * LDraw Design Pad (LDDP) 1.53 released *
|
|
(...) F12, F12, F12, F12, .... ;-)))...))), w. (21 years ago, 27-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: * LDraw Design Pad (LDDP) 1.53 released *
|
|
(...) Thanks Ross. I can't believe I forgot to post a URL. -Orion (21 years ago, 26-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: * LDraw Design Pad (LDDP) 1.53 released *
|
|
(...) Most of us know where to get it by now, but for the noobs: (URL) (21 years ago, 26-Jan-04, to lugnet.cad.dev)
|
| |
| | * LDraw Design Pad (LDDP) 1.53 released *
|
|
LDDesignPad (LDDP) is a tool for editing and handling LDraw files in a very comfortable way. Features are: -Fully customizable editor with syntax highlighting -Open multiple files at the same time -Unlimited Undo/Redo -Use/define codesnippets (...) (21 years ago, 26-Jan-04, to lugnet.cad, lugnet.cad.dev, lugnet.announce)
|
| |
| | Interesting BFC finding
|
|
Well, I've finished an initially working implementation of BFC in my next-gen LDView code tree, and discovered that on my particular video card, BFC actually slows the rendering down. A test model renders at about 50 FPS with BFC handling disabled, (...) (21 years ago, 24-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Change to existing policy on embedding POV-Ray code in Official Files
|
|
(...) And now the archive is public (Thanks, Dan!). See the mailing-group list at the bottom of the page at (URL) (Thanks Orion for making the list!) Steve (21 years ago, 23-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: [LSC] Colour Definition meta-statement
|
|
(...) I could go for that. Simpler is better! Of course that means the METALLIC (or PEARLY) tag needs an argument to define the color of the embedded bits. If you want it to be the same color as the substrate, just use the same color code. Don (21 years ago, 23-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: [LSC] Colour Definition meta-statement
|
|
(...) I've been keeping clear on the dither issue so far, because I didn't have a strong opinion one way or another. However, the more I think about it, the more I think we're not seeing the forest through the trees. Because of this, I vote we (...) (21 years ago, 23-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: [LSC] Colour Definition meta-statement
|
|
(...) I would prefer that spaces not be allowed in the color name as well. However, the spec does say that all the keywords are case sensitive (must be all caps), and I believe the original suggestion was that keywords by themselves with spaces (...) (21 years ago, 23-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: [LSC] Colour Definition meta-statement
|
|
(...) I realize many current ldraw rendering programs use a stipple pattern to render transparent surfaces. I do it in ldglite because I'm too lazy to do the sorting required to use alpha blending. However, I don't really want the specs to dictate (...) (21 years ago, 23-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: [LSC] Colour Definition meta-statement
|
|
(...) [snippety] (...) [doo-dah] (...) I was thinking no space. So far, we've avoided wrapping literals in quotes in LDraw (with only occasional trouble). I'd like to keep avoiding quotes. [snippety-ay] (...) Good question. We hadn't thought about (...) (21 years ago, 23-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: [LSC] Colour Definition meta-statement
|
|
(...) But what if Lego prints an opaque dithered pattern on a transparent brick? I think the ALPHA is more versatile if only applied to the VALUE color. You can still get an alpha dither color by using a color code for d which points to a color with (...) (21 years ago, 23-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: [LSC] Colour Definition meta-statement
|
|
(...) I don't think so. What if CODE is part of the color name? I can't think of a quick example for that, but other key words are easy. AlphaTeamRed, BlueChrome... I'll support color names with no space characters, and I'll consider supporting (...) (21 years ago, 23-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: [LSC] Colour Definition meta-statement
|
|
(...) Disregard the NAME suggestion. I'm brain dead today. -Orion (21 years ago, 23-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: [LSC] Colour Definition meta-statement
|
|
(...) How about NAME? (...) I don't see a problem with this. Steve or Jacob? -Orion (21 years ago, 23-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: [LSC] Colour Definition meta-statement
|
|
(...) I won't make any guarantees, but there's a reasonably high probability that I won't even try to support the above, even if it's what the spec says in the end. It's too much of a pain. Additionally, it disallows further expansion of the colour (...) (21 years ago, 22-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: [LSC] Colour Definition meta-statement
|
|
(...) HTML uses # (...) The name should be the characters after the !COLOR keyword and before the next keyword. The only contraint I can think of is that is not be one of the other keywords. (...) ALPHA should apply to the VALUE color and the color (...) (21 years ago, 22-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: [LSC] Colour Definition meta-statement
|
|
(...) I prefer the currently used 0x prefix, but I guess if you picked # to match other file formats in use by ldraw users then I can live with it. I forget, does POV or HTML use # for the hex prefix? (...) No spaces in the name? Alpha-numeric only? (...) (21 years ago, 22-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: 81 million points
|
|
(...) I forgot to mention. I didn't try fly-through mode, but wouldn't expect it to be very usable at 1 frame per second. --Travis (21 years ago, 21-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: 81 million points
|
|
(...) My system is a 2.4GHz P4 with 1GB RAM. However, according to the Windows XP task manager, LDView was only using about 125 megs when the model was loaded with normal-res studs. (This compares very favorable with the current LDView release that (...) (21 years ago, 21-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: 81 million points
|
|
(...) Wow. That must be amazing in fly-thru mode. I'm also curious. What sort of CPU and how much memory do you have, and how much of that was in use by the LDVIEW? (...) I bet you have to get all your display list(s) and vertex arrays into the (...) (21 years ago, 21-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Bram's LDraw and LEdit Tutorial
|
|
(...) I have a copy. Let me know if you still need it and I can email it to you. I still point to the LEDIT portion of this tutorial in the ldglite instructions so I'd like to see this back on the internet somewhere as soon as possible. Don (21 years ago, 21-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Bram's LDraw and LEdit Tutorial
|
|
(...) Name: ldrawtutorial.zip Size: ~410K -Orion (21 years ago, 21-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: [LSC] Colour Definition meta-statement
|
|
(...) Color codes will be defined in decimal notation and the 24-bit RGB will be in Hex. -Orion (21 years ago, 21-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: [LSC] Colour Definition meta-statement
|
|
(...) RGB is actually 3 numbers - I'd suggest something like RGB(r,g,b) where r g & b can be decimal or hex as per other numbers. ROSCO (21 years ago, 21-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Bram's LDraw and LEdit Tutorial
|
|
(...) What would the name of the file be and how big is it approx.? Then I can browse through my 6 year old collection of "Download CD's..." :-) Jaco (21 years ago, 21-Jan-04, to lugnet.cad.dev)
|
| |
| | 81 million points
|
|
I normally don't make posts like this, but I thought the numbers involved deserved a post. Just out of curiosity, I stuck a counter in my development LDView code to count the number of points being drawn. I loaded up the copy I have of town.dat (...) (21 years ago, 21-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: [LSC] Colour Definition meta-statement
|
|
I'll bite. (Note that none of my comments are meant as criticism.) In lugnet.cad.dev, Steve Bliss wrote: <SNIP> (...) I personally think the # for hex numbers is a mildly bad idea. The currently accepted way to specify hexidecimal values is to (...) (21 years ago, 21-Jan-04, to lugnet.cad.dev)
|
| |
| | [LSC] Colour Definition meta-statement
|
|
Here's the initial write up for a color definition meta-statement, to be used in ldconfig.ldr and in any model file. The LSC has a couple of outstanding issues with this spec, let's discuss those in follow-up messages. Please respond with any (...) (21 years ago, 21-Jan-04, to lugnet.cad.dev)
|
| |
| | Matrix mirroring question
|
|
This question is mostly directed a developers that have had to deal with mirroring while processing LDraw files, but I welcome comments from anyone. It seems to me that any model specified with a mirror matrix will be mirrored relative to its parent (...) (21 years ago, 21-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Change to existing policy on embedding POV-Ray code in Official Files
|
|
(...) Save that code! Once an LDraw/POV-Ray library is a going thing (and it looks like that won't take so long), those parts can be submitted there. Steve (21 years ago, 21-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Change to existing policy on embedding POV-Ray code in Official Files
|
|
(...) True, but the 'embedded code' is still code we are effectively certifying as being good, whether it works strictly within LDraw, or in other GDL/SDL's. (...) Sorry, we never got around to making the list public. I'll work on that. Steve (21 years ago, 21-Jan-04, to lugnet.cad.dev)
|
| |
| | Bram's LDraw and LEdit Tutorial
|
|
Attention all, Thinkquest, the site that hosted Bram's LDraw & LEdit Tutorial, recently deleted this tutorial from their archive. Neither Tim nor I had a hard copy of the webpages. While I've contacted Bram asking him if he still has a copy, I'd (...) (21 years ago, 21-Jan-04, to lugnet.cad, lugnet.cad.dev)
|
| |
| | Re: Change to existing policy on embedding POV-Ray code in Official Files
|
|
In lugnet.cad.dev, Kevin L. Clague wrote: [much snippage] (...) The above example parallel directory structure is just an example. I see that there are many possible alternate solutions... POV directory as sigbling of LDRAW subdirectory, where the (...) (21 years ago, 20-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Change to existing policy on embedding POV-Ray code in Official Files
|
|
(...) One thing the project clearly needs right now is a small homepage to tell what it's all about, and outline what people can do to help. That might help pull in more active participants than a lone CVS archive. I've seen your pages, Larry. I bet (...) (21 years ago, 20-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Change to existing policy on embedding POV-Ray code in Official Files
|
|
In lugnet.cad.dev, Larry Pieniazek wrote: <much snippage> (...) As Orion described, we'd rather put the ability of using POV or whatever other renderer you choose outside the LDraw file format, and outside the LDraw format parts library. If we (...) (21 years ago, 20-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Change to existing policy on embedding POV-Ray code in Official Files
|
|
(...) The relatively easy solution on how to make the wrench tool and, even more obvious, the (unofficial) patterned maxifig heads - that solution has become undone. (...) The only thing that ever has frustrated me about LGEO is that I never ever (...) (21 years ago, 20-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Change to existing policy on embedding POV-Ray code in Official Files
|
|
(...) What's entailed? Do you want participants who can test but not do much else? (21 years ago, 20-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Change to existing policy on embedding POV-Ray code in Official Files
|
|
(...) Actually, the only Official Library parts that have embedded P-R SDL are some of Paul Easter torus primitives. Since nothing was ever done in the first place, nothing is being undone now. If you're like me and frustrated that LGEO is (...) (21 years ago, 20-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Change to existing policy on embedding POV-Ray code in Official Files
|
|
(...) Only until 3rd party libraries (like LGEO) become available. ROSCO (21 years ago, 20-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Change to existing policy on embedding POV-Ray code in Official Files
|
|
(...) Too sad. If I got that complicated language correcly, this means that the problem presented at (URL) and was solved by embedded POV-code has now regressed to be un-solved again. /Tore (21 years ago, 20-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Change to existing policy on embedding POV-Ray code in Official Files
|
|
(...) Yes, and if you want to join the project team let me know (this goes for anyone else as well). (...) -Orion (21 years ago, 19-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Change to existing policy on embedding POV-Ray code in Official Files
|
|
(...) OK, but whether or not the P-R SDL code was out of whack would not affect the usability of parts as parts within LDraw format programs themselves, right? (0)Only affect the accuracy or completeness or error state of transformation (by tools (...) (21 years ago, 19-Jan-04, to lugnet.cad.dev)
|
