Results 1881 1900 of about 4700.
|
Search took 0.02 CPU seconds.
|
|
 | | Re: Part Authors: opinions sought on T-Junctions
|
| (...) Well actually what txt2dat does is a slightly different problem - it has a few simple closed loops and has to triangulate the complex polygons bounded by them (it uses the excellent (URL) triangle library> to do that). Renderers on the other (...) (20 years ago, 6-Mar-07, to lugnet.cad.dat.parts, FTX)
| |
|   part (score: 0.656) |
|
 | | Re: Part Authors: opinions sought on T-Junctions
|
| (...) I'd really appreciate it if you didn't blame it on the rendering programs. There's really nothing that they can do to fix the problem. I can understand why you might feel that they are at fault, but it really isn't true. As such, you might (...) (20 years ago, 6-Mar-07, to lugnet.cad.dat.parts, FTX)
| |
|   part (score: 0.656) |
|
 | | Re: Part Authors: opinions sought on T-Junctions
|
| (...) Sounds reasonable to me. Any chance a T-junctions FAQ could be created on the parts tracker reference page, and the above could make it into a policy statement in the parts review FAQ? Most of my original post here could be used as the FAQ, (...) (20 years ago, 5-Mar-07, to lugnet.cad.dat.parts, FTX)
| |
|   part (score: 0.656) |
|
 | | Re: Part Authors: opinions sought on T-Junctions
|
| (...) It's not really constrained to high zoom. If you have a 1% chance of any given pixel along any given T-junction boundary edge resulting in a hole, then you'll have the roughly the same number of holes at any zoom level, since in general the (...) (20 years ago, 5-Mar-07, to lugnet.cad.dat.parts, FTX)
| |
|   part (score: 0.655) |
|
 | | Re: Part Authors: opinions sought on T-Junctions
|
| (...) Much as I'd like to agree on this, I don't think the fact that nobody posted back then disagreeing with my statement really counts as consensus. I pointed out the problem, but didn't ask for opinions on whether parts should be modeled that (...) (20 years ago, 5-Mar-07, to lugnet.cad.dat.parts, FTX)
| |
|   part (score: 0.655) |
|
| |
|   part (score: 0.655) |
|
 | | Re: Part Authors: opinions sought on T-Junctions
|
| (...) blah, blah, blah, snip Oops, I was trying to be all ironical in a geeky math sorta way. But apparently I failed. Guess I shoulda used more winkies... Do people still use winkies? Or have they gone obsolete like ASCII art? Anyhow, sorry about (...) (20 years ago, 6-Mar-07, to lugnet.cad.dat.parts, FTX)
| |
|   part (score: 0.655) |
|
 | | Re: Part Authors: opinions sought on T-Junctions
|
| (...) There are T-junctions there, but the ones that produce the most visible dots are between the white stripe and the moon. Both of those colors are light, so the dark background showing through is much higher contrast, which makes the dots much (...) (20 years ago, 5-Mar-07, to lugnet.cad.dat.parts, FTX)
| |
|   part (score: 0.655) |
|
 | | Re: Part Authors: opinions sought on T-Junctions
|
| (...) in all the parts I've made so far there is just one with a t-junction: (URL) (if I remember correctly it's where the two red quads are surrounded by the white border) but it is forgiveable I think, as it was one of the first parts I've ever (...) (20 years ago, 4-Mar-07, to lugnet.cad.dat.parts, FTX)
| |
|   part (score: 0.655) |
|
 | | Re: Part Authors: opinions sought on T-Junctions
|
| (...) Arguably it's probably the algorithms and/or numerical proccessing that are at fault. Certainly when you design scientific code algorithms they should usually be created in such a way that it minimises numerical error. Of course I don't expect (...) (20 years ago, 6-Mar-07, to lugnet.cad.dat.parts, FTX)
| |
|   part (score: 0.655) |
|
 | | Re: Part Authors: opinions sought on T-Junctions
|
| (...) It's possible that by setting up meshes POVray can largely avoid the problem as it rotates points and then joins them. My opinion is that Part Authors should stick to keeping the polygon count down rather than jumping through hoops to try to (...) (20 years ago, 4-Mar-07, to lugnet.cad.dat.parts, FTX)
| |
|   part (score: 0.655) |
|
| |
|   part (score: 0.655) |
|
| |
|   new, part (score: 0.655) |
|
| |
|   part (score: 0.655) |
|
 | | Re: Part Authors: opinions sought on T-Junctions
|
| (...) This is a really old issue. I think the previous consensus was that (URL) T-Junctions are bad.> Look at the bottom of the message for the comments on T-Junctions. Actually this is such an old issue, I could swear there was an ASCII art (...) (20 years ago, 4-Mar-07, to lugnet.cad.dat.parts, FTX)
| |
|   part (score: 0.655) |
|
 | | Naming of Parts (esp. Wheels & Tires)
|
| Hi, Perhaps it is just me, but I am often confused when trying to find matching parts. For example, there is a wheel center 50944 or 42610, which is named 11 x 6 mm. In fact it is 11.2 x 6.4 mm which also more fits to LEGO dimensions. That is not (...) (20 years ago, 4-Mar-07, to lugnet.cad.dat.parts)
| |
|   part (score: 0.654) |
|
 | | New Part x43p01 Flag 6 x 4 with Pirates Pattern [DAT]
|
| 0 Flag 6 x 4 with Pirates Pattern 0 Name: x43p01.dat 0 Author: Tore Eriksson 0 Unofficial Part 0 BMP2DAT2 0.42.3 1 0 -2 50 121 0 0 0 1 0 0 0 0 1 2-4disc.dat 1 0 2 50 121 0 0 0 1 0 0 0 0 1 2-4disc.dat 1 16 -2 50 121 0 0 0 1 0 0 0 0 1 2-4ndis.dat 1 16 (...) (27 years ago, 24-Apr-00, to lugnet.cad.dat.parts)
| |
|   new, part (score: 0.654) |
|
 | | New Part: 30149 Car Base 4 x 5 with 2 Seats [DAT]
|
| Hi all, I've gotten pretty far on my first part (if you can think of a better name, please tell). However, as this is my firts part, I would like people to critique what I have done so far. The only part I haven't finished is where the seats curve (...) (27 years ago, 21-Apr-00, to lugnet.cad.dat.parts)
| |
|   new, part (score: 0.654) |
|
| |
|   new, part (score: 0.654) |
|
| |
|   part (score: 0.653) | More: Next Page >>
|