 | | Re: Cross platform GUI
|
|
(...) I just read this on /. This is great news. -Orion (20 years ago, 7-Feb-05, to lugnet.cad.dev)
|
| |
| | Re: Cross platform GUI
|
|
It looks like QT 4 will extend the GPL license to the Windows version. See here: (URL) sent this cad.dev, because this change could actually be useful to the developers.) --Travis Cobbs (20 years ago, 7-Feb-05, to lugnet.cad.dev)
|
| |
| | Re: ldconfig.ldr and dithered colors
|
|
(...) They should be fall back on the 'default spec' -- that is, dither them; don't rely on their counterpart's definition. But that doesn't really (...) Hmm. The LGEO colors don't have edge colors, do they? So using K,J instead of J,K [if J,K isn't (...) (20 years ago, 7-Feb-05, to lugnet.cad.dev)
|
| |
| | Re: ldconfig.ldr and dithered colors
|
|
(...) I'd say a blend of 0 and 1, basically just as if it's counterpart (272) wasn't defined in the ldconfig -Orion (20 years ago, 6-Feb-05, to lugnet.cad.dev)
|
| |
| | ldconfig.ldr and dithered colors
|
|
How is a renderer expected to handle dithered colors not mentioned explicitly in ldconfig.ldr ? The "LDraw File Format" specification says: "Also, colours 256 through 511 are dithered. So if you want to combine colours J and K, figure your colour (...) (20 years ago, 6-Feb-05, to lugnet.cad.dev)
|
| |
| | Re: BFCFixer
|
|
(...) Such components are handled correctly by BFCFixer as "detached" submodels, and are oriented consistently with the rest of the polygons in the file as long as each independant submodel is sufficiently enclosed that a correct winding can be (...) (20 years ago, 5-Feb-05, to lugnet.cad.dev)
|
| |
| | Re: BFCFixer
|
|
(...) Of course, it's that simple - thanks. Except some of the most basic LDraw parts (regular bricks) fail this test because the studs are "stuck on" a complete quad, rather than a surface peppered with stud-sized holes. Chris (20 years ago, 4-Feb-05, to lugnet.cad.dev)
|
| |
| | Re: BFCFixer
|
|
(...) Would you guys want a code repository for this? I have a SVN repo set up that I could easily add this as a project... Just LMK! (20 years ago, 3-Feb-05, to lugnet.cad.dev)
|
| |
| | Re: BFCFixer
|
|
(...) Ask, and ye shall receive. (URL) code is included (hopefully my crude hackings can be deciphered by others) as well as an executable jarfile in the dist/ subdirectory. Enjoy. If you find any major bugs, let me know, and I'll see what I can do, (...) (20 years ago, 3-Feb-05, to lugnet.cad.dev)
|
| |
| | Re: BFCFixer
|
|
(...) Oh yeah! Let me at it. :) Steve (20 years ago, 3-Feb-05, to lugnet.cad.dev)
|
| |
| | Re: BFCFixer
|
|
(...) The way it's been done before is to draw rays from the origin outward. The first polygon a ray crosses is facing inward, and the last polygon a ray crosses would be facing outward. The ones in between *should* alternate facing in and out. Do (...) (20 years ago, 3-Feb-05, to lugnet.cad.dev)
|
| |
| | Re: BFCFixer
|
|
(...) I think it can be done for simple objects, by choosing a random winding for 1 polygon, then processing all touching polygons so they're wound the same way (when looking from the same side - out ot in). This would produce a result that is (...) (20 years ago, 3-Feb-05, to lugnet.cad.dev)
|
| |
| | Re: BFCFixer
|
|
(...) I may be being dense here, but I dont understand how this can be done programatically. The point of BFC is to allow renderers to understand if a particular polygon is facing the camera or facing away from it. If all polygons are wound (...) (20 years ago, 3-Feb-05, to lugnet.cad.dev)
|
| |
| | BFCFixer
|
|
(...) Well, I had some spare time today... so I wrote one. It goes through a single LDraw part file and reorients all the polygons in it to have the same winding. It comprehends the notion of subfiles and already BFC compliant parts, and puts the (...) (20 years ago, 3-Feb-05, to lugnet.cad.dev)
|
| |
| | Re: Parts editing made easy, anyone?
|
|
(...) <snip> (...) Yes, I use MLCad in conjuction with LDDP/LDView for parts authoring. My method is to build the part in MLCad since it does all the rotaion calculations for me and then clean in up and fine tune ithe part in LDDP/LDView. As far as (...) (20 years ago, 3-Feb-05, to lugnet.cad.dev)
|
| |
| | Re: Parts editing made easy, anyone?
|
|
(...) Hi Stefan: I'm chiming in late here, but I've crafted at least a few unofficial LDraw parts, and I thought I might offer some thoughts. My original composing tool of choice was the shareware text editor "PC-Write v4," which no longer appears (...) (20 years ago, 2-Feb-05, to lugnet.cad.dev)
|
| |
| | Re: Bricksaic version 0.1.0
|
|
(...) Xposted to cad.mlcad Perhaps Michael L. could speak up about whether MLCad reads that file, what the proper superset of colors ought to be and other topics. (20 years ago, 1-Feb-05, to lugnet.build.mosaic, lugnet.cad.dev, lugnet.cad.mlcad)
|
| |
| | Re: Bricksaic version 0.1.0
|
|
(...) Bricksaic is using the ldconfig.ldr in it's directory but the problem with the unused colors seems to be that MLcad does not recognize the following colors: Reddish_Brown, Stone_Gray, Dark_Stone_Gray, and Dark_Green. there may be more colors (...) (20 years ago, 1-Feb-05, to lugnet.build.mosaic, lugnet.cad.dev)
|
| |
| | Re: Bricksaic version 0.1.0
|
|
(...) Larry, I looked into what you said and it is correct: Bricksiac is using the ldconfig.ldr file in it's installed directory and MLDraw is using a file named the same ldconfig.ldr in it's installed dirctory. Then if one of the other has a (...) (20 years ago, 31-Jan-05, to lugnet.build.mosaic, lugnet.cad.dev)
|
| |
| | Re: Contributor's Agreement
|
|
(...) And that's a good thing. Come on now. The whole ldraw library is a derivative work and we've already lost contact with the original author, and many subsequent part authors, but they still get credit for a job well done. Good work! Keep it up! (...) (20 years ago, 31-Jan-05, to lugnet.cad.dev.org.ldraw)
|
