 | | * 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)
|
| |
| | Re: Change to existing policy on embedding POV-Ray code in Official Files
|
|
(...) Yay! The right place for POV code is in external libraries. Does this mean (URL) is going to be developed? Is a new L3P release in the works? It's been over a year and a half since this tantalizing message was posted. :^) (URL) Don (21 years ago, 19-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Change to existing policy on embedding POV-Ray code in Official Files
|
|
(...) Basically, The POV team controls the syntax, functionality, and implementation of the POV-Ray Scene Description Language (P-R SDL) format. While the POV Team is very good at maintaining backwards compatibility, they have in the past change the (...) (21 years ago, 19-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Change to existing policy on embedding POV-Ray code in Official Files
|
|
(...) Could you give a bit more info on the compatability issues (or a pointer to where they're discussed)? (21 years ago, 19-Jan-04, to lugnet.cad.dev)
|
| |
| | Change to existing policy on embedding POV-Ray code in Official Files
|
|
The LDraw.org Standards Committee (LSC) has recently discussed the issue of embedded POV-Ray code in Official Parts Library files. After careful consideration and with inputs from leading non-LSC members, most notably Lars Hassing and Chris Dee, we (...) (21 years ago, 19-Jan-04, to lugnet.cad.dev, lugnet.cad)
|
| |
| | Re: Friction pins no friction?
|
|
(...) Look's good, Though you may want to just make the primitive have the friction bits alone without the connector. That way you possibly could be able to use it on parts like 6558 and 32054 as well. (21 years ago, 19-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Friction pins no friction?
|
|
I have submitted the first in the line of confric# primitive to the LDraw Parts Tracker. (URL) is use the the part 43093 Axle Pin with Friction. (URL) should give people a better idea of what I have planned. With this new line of primitives we will (...) (21 years ago, 18-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Need partnumbers and some partnames
|
|
(...) OK - I have moved the existing x322.dat out of the way (to x289.dat). Chris (21 years ago, 17-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Need partnumbers and some partnames
|
|
(...) When I tried to upload this part, it got rejected because there was a x322.dat already on the PT.... Before this rejection I have uploaded two subparts s\x322s01.dat and s\x322s02.dat. Niels (21 years ago, 17-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Black seems wrong in ldconfig.ldr
|
|
(...) Well, I hope the final syntax for the color definition statement will allow some space for programs to support their own special syntactic needs. So you hopefully won't need a super-custom meta-statement for LDView, just a special flavor for (...) (21 years ago, 17-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Black seems wrong in ldconfig.ldr
|
|
(...) The good side of the LSC is that with the reduced number of people, you are hopefully able to actually come to a consensus in a reasonable time frame. The bad side is that since the discussions are private, you have to deal with hecklers like (...) (21 years ago, 16-Jan-04, to lugnet.cad.dev)
|
| |
| | SIGGRAPH 2004 Themepark
|
|
I received a note about this document over email. Is this something LDraw developers would be interested in participating in? (URL) (21 years ago, 16-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Black seems wrong in ldconfig.ldr
|
|
(...) Thanks. That's a good idea. I'll have to think about it, though. Up until now, I have purposely avoided creating any LDView-specific meta-commands. On the other hand, this would be one of the few reasons that might convince me that an (...) (21 years ago, 16-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: [Parts Tracker] Security Change underway
|
|
(...) Woo-hoo! :-) I can review parts now! --Travis (21 years ago, 16-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: [Parts Tracker] Security Change underway
|
|
(...) As of tonight, here's where things stand: - I've finished updating all the restricted-access scripts (those are the scripts under cgi-bin/tracker). - I've turned off the old authentication -- so you won't be prompted by your browser to log in. (...) (21 years ago, 16-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Black seems wrong in ldconfig.ldr
|
|
(...) You could put your custom information in an ldviewconfig.ldr file which you supply with the LDView install. Then add a setting to LDView, allowing the user to specify multiple pre-processing files. Default the setting to (...) (21 years ago, 16-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Black seems wrong in ldconfig.ldr
|
|
(...) We're working on it. Give us another 24 hours to have something to present. Not a final 'done deal', but at least a decent writeup. Steve (21 years ago, 16-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: [Parts Tracker] Security Change underway
|
|
(...) Hopefully not too much longer - I'm working on the last script now. Steve (21 years ago, 15-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: [Parts Tracker] Security Change underway
|
|
(...) hi steve, could you please keep us updated how long we will need to log in twice? many thx, willy (21 years ago, 14-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Black seems wrong in ldconfig.ldr
|
|
(...) Where else would you put it? What if you break the material settings up into two parts? 1) a material tag on the COLOURDEF line: 0 COLOURDEF 334 ChromeGold 15 0xFFC40026 MATERIAL metallic 2) a MATERIALDEF line added to the end of the file that (...) (21 years ago, 14-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Inline POV code in official parts?
|
|
(...) That's a very heavy argument against EmbPOV. It would be a great thing if we could just have a very few basic features, say clipped by, pattern wrap and maybe one or two other and make it a generic syntax for alternative code. (...) Despite (...) (21 years ago, 13-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Black seems wrong in ldconfig.ldr
|
|
(...) I agree that something of that sort would be a good idea, but in the case of my metallic colors, I actually hand-tweaked the settings for each metallic color. They aren't all the same. This was done partially to differentiate between chrome (...) (21 years ago, 13-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Black seems wrong in ldconfig.ldr
|
|
(...) Why not use the optional MATERIAL bits from this old discussion (URL) come up with a modified ldconfig.ldr? Then implement some code in LDVIEW to enable your metallic lighting goodies when ldconfig.ldr contains the proper MATERIAL settings. (...) (21 years ago, 13-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Black seems wrong in ldconfig.ldr
|
|
(...) Given that ldconfig.ldr is part of the LDraw parts library, I was referring to the color reference on the LDraw.org site (noted in another message). However, it might make sense to use the colors above, since they came directly from Lego, and (...) (21 years ago, 13-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Black seems wrong in ldconfig.ldr
|
|
(I switched to FTX due to an unusually long link.) (...) I was referring to the one at ldraw.org (URL) (LDraw definitions at the bottom). I believe that the LDraw color definitions there came from some version of the LDraw FAQ. When I said (...) (21 years ago, 13-Jan-04, to lugnet.cad.dev, FTX)
|
| |
| | Re: Black seems wrong in ldconfig.ldr
|
|
(...) In fact the official LEGO colour chart mentioned here (URL) uses 27, 42, 52 for black. ROSCO (21 years ago, 13-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Black seems wrong in ldconfig.ldr
|
|
(...) (er, which official color chart?) (...) Uh, Travis, it's *black*. It's *supposed* to be dark. People have questioned/complained that it's not 'true black' (ie, 0,0,0). You might be right about the origin of the 33 value, but I believe I was (...) (21 years ago, 13-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Black seems wrong in ldconfig.ldr
|
|
Sorry to immediately post a follow-up to my own post, but I just noticed that RubberBlack is defined with the same 33,33,33 color (not surprisingly), and I feel it needs to be updated as well. --Travis Cobbs (21 years ago, 12-Jan-04, to lugnet.cad.dev)
|
| |
| | Black seems wrong in ldconfig.ldr
|
|
The ldconfig.ldr file currently being distributed with the parts library seems to have the wrong definition for black. It uses 33,33,33 as the RGB color, when the official color chart uses 51,51,51. Two things to note. First, 33,33,33 comes out (...) (21 years ago, 12-Jan-04, to lugnet.cad.dev)
|
| |
| | Friction pins no friction?
|
|
It struck me as odd that the 3673 Technic Pin (no friction) and the 4459 Technic Pin with Friction looked identical. Why are they the same? Where is that friction? I feel there should be a line of connect primitives that clearly show this friction. (...) (21 years ago, 12-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Need partnumbers and some partnames
|
|
(...) I think putting Motor Cutout in the keywords would work, if we can't reasonably fit it in the part title. (...) OK, I think Stop and Proceed are OK for the names. (...) So the light bulb can be physically removed from the complete part? But (...) (21 years ago, 8-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: primer/tutorial on BFC?
|
|
(...) [snip] (...) I just wanted to add one more post in an attempt to clear up any confusion that may have been caused in this thread. What Andy says above is correct, and my earlier post indicating otherwise was incorrect. The two dimensional (...) (21 years ago, 4-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: primer/tutorial on BFC?
|
|
(...) Hmmm, very good point. I don't like treating specific object specially, but I don't see any way around it. I played around with the stud and with a 'solid' cylinder object, I couldn't find a way to get L3Lab's BFC handling to fail. Steve (21 years ago, 4-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: primer/tutorial on BFC?
|
|
(...) Actually, I *think* it's the new ATA controller card I installed, and LDView was just an innocent bystander. However, since LDView doesn't do BFC, I guess I didn't miss anything. (...) Yes, you could use INVERTNEXT, but that introduces (...) (21 years ago, 4-Jan-04, to lugnet.cad.dev)
|
| |
| | Proposed changes to MOTM Submission guidelines
|
|
After formal running the MOTM contest for a month, I've becomed concerned with the fairness of the contest. In response to my concerns, I'd like to make the following changes to the rules for MOTM in order to level the playing field. - All (...) (21 years ago, 4-Jan-04, to lugnet.cad, lugnet.cad.dev, lugnet.cad.dev.org.ldraw)
|
| |
| | Re: primer/tutorial on BFC?
|
|
(...) You're right; I'm wrong. I'm still having a hard time visualizing it, but your stud example below convinced me that negating the one value in the matrix will indeed flip a 2D primitive like a disk, and this is the expected behavior. In fact, (...) (21 years ago, 3-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: primer/tutorial on BFC?
|
|
(...) I do this all the time, too. Just a minus sign in stead of 'BFC INVERTNEXT' each time can save some diskspace, which I've been told is something to go for, too. Niels (21 years ago, 3-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: primer/tutorial on BFC? [DAT]
|
|
(...) I think it works just fine. L3Lab correctly detects that the matrix is mirroring, see View/Tree View... and click the BFC radio button, it should say INVERT in front of the line. When we discussed the BFC business the general assumption was (...) (21 years ago, 3-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: primer/tutorial on BFC?
|
|
(...) If this is the case then we need to go back through all the BFC'd parts and find instances of this type of matrix. Since L3Lab allows inverting the sign of the Y component and it's currently the only program to easily check for correct (...) (21 years ago, 3-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: primer/tutorial on BFC?
|
|
(...) L3Lab supports BFC INVERTNEXT. /Tore (21 years ago, 3-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: primer/tutorial on BFC? [DAT]
|
|
(...) I do agree that it isn't supposed to work, because the BFC spec very carefully states that any polygons drawn with an aggregate matrix that causes mirroring must be flipped back. (...) I'm sorry that LDView is crashing your system, but it (...) (21 years ago, 3-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Need partnumbers and some partnames
|
|
(...) There are trainbases with and without motorcutouts, some with the same size. That's why I suggested to add the cutout to the name. Also for seeking those parts as one of them is just a plate. Perhaps adding Motorcutout as a keyword can help to (...) (21 years ago, 31-Dec-03, to lugnet.cad.dev, FTX)
|
| |
| | Re: Need partnumbers and some partnames
|
|
(...) x389.dat Technic Brick 1 x 2 with Hole and Thin Top x290.dat Magnet Holder for Train Base 6 x 22 Type I x303.dat Train Base 6 x 22 with Cutout Type I x303c01.dat Train Base 6 x 22 with Cutout Type I with Magnets (Complete) x304c01.dat ~Train (...) (21 years ago, 31-Dec-03, to lugnet.cad.dev)
|
| |
| | Re: primer/tutorial on BFC?
|
|
In lugnet.cad.dev, Chris Dee wrote: [snip] One other thing: before you update a file for BFC, be sure there are no serious L3P errors -- vertex order is the big problem, but you should also take care of non-coplanar quads and singular matrices as (...) (21 years ago, 31-Dec-03, to lugnet.cad.dev)
|
| |
| | Re: primer/tutorial on BFC? [DAT]
|
|
(...) That shouldn't work -- the rendering program should detect that you've mirrored the object, and adjust accordingly. Unfortunately, I see that it does 'work' in L3Lab. LDView is crashing my system right now, so I couldn't check it. What you (...) (21 years ago, 31-Dec-03, to lugnet.cad.dev)
|
| |
| | Re: primer/tutorial on BFC?
|
|
(...) I started parts authoring without knowing about BFC. When I read something about BFC-ing here on lugnet, I started to dig myself into it, reading documentation (from www.ldraw.org), trying things out and now I know enough about it. I only (...) (21 years ago, 30-Dec-03, to lugnet.cad.dev)
|
| |
| | Re: primer/tutorial on BFC?
|
|
(...) I use LDDP and L3Lab with "Poll to L3Lab & LDview" + "Poll to selected line only" turned on. going through the code with CRTL+W (orion please don't forget my special request) rewinding what's needed. w. (21 years ago, 30-Dec-03, to lugnet.cad.dev)
|
| |
| | Re: primer/tutorial on BFC? [DAT]
|
|
(...) For the two-dimensional primitives (disc, ndis, ring, chrd) you can do the following: Say you have a disc in the x-z plane, like: 1 16 0 0 0 10 0 0 0 1 0 0 0 10 4-4disc.dat If this has the wrong BFC winding, you can just flip (mirror) the (...) (21 years ago, 30-Dec-03, to lugnet.cad.dev)
|
| |
| | Re: primer/tutorial on BFC?
|
|
(...) I use Notepad (NOTEPAD.EXE), until the DAT file gets too huge, whereupon I use WordPad (WORDPAD.EXE) to continue editing the file. I use a calculator and scratch paper (to do a rough sketch and to keep notes of important locations). Whenever I (...) (21 years ago, 30-Dec-03, to lugnet.cad.dev)
|
| |
| | Need partnumbers and some partnames
|
|
Now the parts update 2003-03 is released, I started to make some parts I have already created ready for upload to the parts tracker. I need partnumbers for the following parts. I also want to know if the partnames are correct. * Technic Brick 1 x 2 (...) (21 years ago, 29-Dec-03, to lugnet.cad.dev)
|
| |
| | Re: BFC And Mirroring (LDS)
|
|
(...) Thanks Steve. :) (21 years ago, 29-Dec-03, to lugnet.cad.dev)
|
| |
| | Re: primer/tutorial on BFC?
|
|
(...) OK - it's not a technique I use, but in an email conversation recently somebody convinced me that inverting the matrix would switch the winding. Now that I test it again I found I was mistaken. Chris (21 years ago, 28-Dec-03, to lugnet.cad.dev)
|
| |
| | Re: BFC And Mirroring (LDS)
|
|
In lugnet.cad.dev, Tore Eriksson wrote: [snip] (...) Yes. Steve (21 years ago, 28-Dec-03, to lugnet.cad.dev)
|
| |
| | Re: primer/tutorial on BFC?
|
|
In lugnet.cad.dev, Chris Dee wrote: [snip] Thanks for writing this up, Chris! Your explanation was very good in all respects except for one small point: (...) Actually, negating the transformation matrix should not invert any object; and even if it (...) (21 years ago, 28-Dec-03, to lugnet.cad.dev)
|
| |
| | Re: primer/tutorial on BFC?
|
|
(...) I think ease or difficulty depends on which tools you use to author parts. I use LDAO as the editor with L3Lab for preview and find it reasonably easy. Others may wish to comment with reference to their favourite tools. To BFC an existing DAT (...) (21 years ago, 27-Dec-03, to lugnet.cad.dev)
|
| |
| | BFC And Mirroring (LDS)
|
|
As I am into a major revision of the LDS Compiler, I have stumbled upon the problem with mirroring and extruding and their effect on BFD winding. My question is: Is it correct to rewind the points if a polygon has been mirrored an odd number of (...) (21 years ago, 27-Dec-03, to lugnet.cad.dev)
|
| |
| | primer/tutorial on BFC?
|
|
Anyone out there willing to teach me how to certify a DAT file for backface culling (BFC)? Posting to LUGNet would be preferable, especially if you are providing images (visual aids are usually helpful when teaching a complicated subject). I recall (...) (21 years ago, 24-Dec-03, to lugnet.cad.dev)
|
| |
| | Re: Linetype/color question
|
|
(...) Hi Travis: Thanks for your input. LDview is a fine program, by the way. LDview, along with Lars' L3Lab, has been indispensible for me when designing complex parts and models. Thanks again for the info. Dave! (21 years ago, 24-Dec-03, to lugnet.cad.dev)
|
| |
| | Re: Linetype/color question
|
|
(...) Hi Orion: Thanks for the response! I don't mean to dispute your answer, but I have made dozens of clone parts in LEdit that use the color range 256-512 for linetypes 3 and 4. Granted, some of the colors appear a little different in LEdit than (...) (21 years ago, 24-Dec-03, to lugnet.cad.dev)
|
| |
| | Re: Linetype/color question
|
|
(...) LDraw/Ledit doesn't accept non type 1 line with colors 256-512. While there is nothing perventing you from making a model that has quads, triangles and lines with color 256-512, we enforce this rule for the Official Library in order to ensure (...) (21 years ago, 24-Dec-03, to lugnet.cad.dev)
|
| |
| | Re: Linetype/color question
|
|
(...) I don't know why the restriction exists, but I do believe it is enforced for parts in the parts library. At a guess, the restriction comes from the orginial LDraw program itself. I know that my own program (LDView) completely ignores this (...) (21 years ago, 23-Dec-03, to lugnet.cad.dev)
|
