 | | Primitive substituion and part reviews
|
|
To what extent, if any, should rendering errors caused by primitive substitution warrent a Hold vote on the PT? An example of this would be a disc shaped pattern surrounded by a ndis. Would it be appropritate to add a small, color matching ring (...) (21 years ago, 27-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: LDGLite outputting gobble-dee-goo to terminal window
|
|
(...) So you're saying that if I ask for the GL_RENDERER etc strings after a window resize I'll get the same ones I started with no matter what? (I added some code to check it anyway just in case) That really sux. Who designed that feature, (...) (21 years ago, 25-Jul-03, to lugnet.cad.dev.mac, lugnet.cad.dev)
|
| |
| | Re: LDGLite outputting gobble-dee-goo to terminal window
|
|
(...) OK, I looked at the code above, and all it seems to do is tell its OpenGL context to update every time the window is resized. If their glut doesn't do this, then it is broken. As far as I know, there isn't any equivalent to this in Windows. (...) (21 years ago, 25-Jul-03, to lugnet.cad.dev.mac, lugnet.cad.dev)
|
| |
| | Re: LDGLite outputting gobble-dee-goo to terminal window
|
|
(...) Found some more info. This makes it even more clear. (URL) it only shows icky Cocoa code. I may have to examine the apple glut sources to see how much of this is actually handled in glut. I wouldn't be suprised to find some bugs there. And I (...) (21 years ago, 25-Jul-03, to lugnet.cad.dev.mac, lugnet.cad.dev)
|
| |
| | Re: LDGLite outputting gobble-dee-goo to terminal window
|
|
(...) The OS is selecting the drivers. If I want to select them myself I have to write all sorts of icky OS specific code. (...) It gets worse. I did some searching on this. Apparently, according to the source on this page, I may need to check if my (...) (21 years ago, 25-Jul-03, to lugnet.cad.dev.mac, lugnet.cad.dev)
|
| |
| | Re: Proposed solution *Test Here* [DAT]
|
|
(...) Yes. No. ;-) There's still a problem with mirrored sub-assemblies. Suppose you have an aeroplane, Plane.ldr: 1 2 0 0 0 0 0 1 0 1 0 -1 0 0 2445.DAT 1 16 0 -8 0 1 0 0 0 1 0 0 0 1 Wing.ldr 1 16 0 -8 0 -1 0 0 0 1 0 0 0 1 Wing.ldr Wing.ldr: 1 4 -80 (...) (21 years ago, 19-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: Vertices not coplanar?
|
|
(...) Right, it is typically an error if the four points of a quad do not lie in a plane. Too bad that the LDraw format has a built-in possiblity of creating degenerate quads. POV e.g. uses 2D points to describe a polygon. See also "Method for (...) (21 years ago, 18-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: Vertices not coplanar?
|
|
(...) What Orion said. (...) Sometimes, it just means the vertices are incorrect. If the vertices are correct, then you should break the quads into two triangles, and put a soft edge (linetype 5) along the common edge. But often, it's worth looking (...) (21 years ago, 18-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: Vertices not coplanar?
|
|
(...) When a renderer goes to render a quad in 3D, it will almost always (perhaps always) first split the quad into two triangles. As long as the quad forms a planar surface, this will result in fairly equivalent results no matter which of the two (...) (21 years ago, 18-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: Vertices not coplanar?
|
|
(...) If I remember my 3D theory correctly, these quads can mess up the normals associated with them. Also, noncoplaner quads cause small gaps in the part since they are, in essence, bent rectangles. Usually these gaps are too small to see, even (...) (21 years ago, 17-Jul-03, to lugnet.cad.dev)
|
| |
| | Vertices not coplanar?
|
|
What troubles do these warnings cause? I see no problems with the renderings, no matter what renderer I use. How do I correct them? By splitting all the quads into two triangles each I guess? If so, why not make a tool that splits them up? /Tore (21 years ago, 17-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: Proposed solution *Test Here*
|
|
(...) Thanks for the info. After further consideration, I realized that there is one other thing that will prevent the -lgeo option from working properly, even for models that don't have mirrored sub-assemblies. Any parts in the part library that (...) (21 years ago, 11-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: List of part numbers with descriptions???
|
|
(...) Ow!!! (just smacked self in head) Thanks! James (21 years ago, 11-Jul-03, to lugnet.cad.dev, FTX)
|
| |
| | Re: List of part numbers with descriptions???
|
|
(...) How about using the peeron master list? (URL) VW (21 years ago, 11-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: List of part numbers with descriptions???
|
|
(...) You can use the parts.lst file in your LDRAW directory. All it is is a master list of all the part numbers/names in the PARTS folder sorted by number or description depending on how you ran MKLIST. --Orion (21 years ago, 11-Jul-03, to lugnet.cad.dev)
|
| |
| | List of part numbers with descriptions???
|
|
I'm still working on my back-burner program to make labels for storage drawers. Does anyone know of a (simple, Windows-based) way to get a list of the parts descriptions? Getting a list of all LDRAW part numbers is no sweat (dir *.dat /b ><filename> (...) (21 years ago, 11-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: Proposed solution *Test Here*
|
|
(...) Two reasons I can think of: 1) Inventories: If you build a submodel using a Left Wing, and then mirror it, the inventory is going to show 2 left wings, when in reality there is 1 left wing and 1 right wing. 2) Instructions: Official LEGO (...) (21 years ago, 11-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: Proposed solution *Test Here*
|
|
(...) That's good to hear. (...) Yeah. I was aware of that. The good news is that it should only be a problem in LGEO if you have mirrored sub-assemblies. Looking at the models I have downloaded over time, I discovered that most people don't do this (...) (21 years ago, 11-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: Proposed solution *Test Here*
|
|
(...) I have tested your program against half a dozen files (including files with large mirrored sub-assemblies for wings and such) and the L3P generated renderings all showed the studs correctly. Well done. However, it doesn't work with -lgeo... (...) (21 years ago, 10-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: Some secrets of MLCad revealed ...
|
|
(...) Yes, that makes sense. Hey, I did a little searching and found some references to "depth sprites" which seem to be supported in some of the latest graphics hardware. I haven't read it yet, but the pictures in this article seem to indicate that (...) (21 years ago, 9-Jul-03, to lugnet.cad.mlcad, lugnet.cad.dev)
|
