 | | Re: I want to become a reviewer —Orion Pobursky
|
| | | (...) Since stud logos are not part of the DAT format, the fact that they are rotated or mirrored is not a problem with a part. That said, since most users like to use the stud logo option for some renders, if problems with the stud logos are (...) (20 years ago, 4-Nov-04, to lugnet.cad, FTX)
|
| | | |
| | | | | Re: I want to become a reviewer —Chris Dee
|
| | | | (...) Yes - these kind of errors are not a cause for a hold. I'm with Orion on stud rotation, but I'd prefer not to have parts/subparts designed in a way that causes mirrored studs. We have set a precedent with car doors, by moving the stud from the (...) (20 years ago, 4-Nov-04, to lugnet.cad, FTX)
|
| | | | |
| | | | | | Re: I want to become a reviewer —Niels Karsdorp
|
| | | | | (...) So I understand that studlogos may face any direction as long as they are not mirrored? How about a mix of rotated studlogos on one single part instead of all studslogos facing the same direction? E.g. some studlogos readable when the part is (...) (20 years ago, 4-Nov-04, to lugnet.cad, FTX)
|
| | | | | |
| | | | | | | Re: I want to become a reviewer —Chris Dee
|
| | | | | | (...) Not a reason for a hold. If you have the energy to correctly orientate the studs, that's great, but we won't prevent a file being released for this reason alone. Chris (20 years ago, 4-Nov-04, to lugnet.cad, FTX)
|
| | | | | | |
| | | | | | Re: I want to become a reviewer —Dave Schuler
|
| | | | (...) Is this true? I've been out of the "official update" loop for a while, but when I suggested this method a year or so ago it was rejected due to "sub-part clutter" and the fears of an unreasonable burden upon parts-authors. Has this changed (...) (20 years ago, 4-Nov-04, to lugnet.cad, FTX)
|
| | | | |
| | | | | | Re: I want to become a reviewer —Chris Dee
|
| | | | (...) Yes - check out 3821.dat and 3822.dat issued in the 2003-03 update - they both use s3822s01.dat but include the stud reference in the main file. I'm not looking for a mass of existing parts to be re-submitted just to implement this technique, (...) (20 years ago, 4-Nov-04, to lugnet.cad, FTX)
|
| | | | |
| | | | | | Re: I want to become a reviewer —Niels Bugge
|
| | | | (...) Hi all If it's combined with BFC-ing or other fix I think mass resubmitting is ok. I think I've managed to pursuade GuyVivan to do exactly that when he's BFC-ing... Just remember that if you whish to check a file for this error you have to (...) (20 years ago, 5-Nov-04, to lugnet.cad, FTX)
|
| | | | |
| | | | | | Re: I want to become a reviewer —Niels Karsdorp
|
| | | | | (...) Or use a modified stud.dat primitive with a logo: 0 Stud 0 Name: stud.dat 0 Author: James Jessiman 0 Original LDraw Primitive 0 LDRAW_ORG Primitive UPDATE 2002-02 0 BFC CERTIFY CW 0 2002-04-04 SEB Modified for BFC compliance 1 16 0 0 0 6 0 0 0 (...) (20 years ago, 5-Nov-04, to lugnet.cad)
|
| | | | | |
| | | | | | Re: I want to become a reviewer —Chris Dee
|
| | | | | (...) Yes - that's what I meant. If a part is being resubmited for other fixes, then by all means repair this fault. But stud mirroring alone is not a reason for a re-submit. Chris (20 years ago, 5-Nov-04, to lugnet.cad, FTX)
|
| | | | | |
| | | | | | Re: I want to become a reviewer —Orion Pobursky
|
| | | | (...) This is exactly why I consider mirrored studs to be a non-issue. This error manifests itself on only one program (L3P) and is able to be compensted for (LDView). I strongly suspect (although Lars will have to confirm) that the next version of (...) (20 years ago, 6-Nov-04, to lugnet.cad, FTX)
|
| | | | |
| | | | | | Re: I want to become a reviewer —Niels Karsdorp
|
| | | | (...) I use a modified stud.dat with logo. (I want to build virtual Lego models, not MB ;-) Then mirrored studs also occur in MLCad and LDGlite and L3Lab. Niels (20 years ago, 6-Nov-04, to lugnet.cad, FTX)
|
| | | | |
| | | | | | Re: I want to become a reviewer —Lars C. Hassing
|
| | | | (...) L3P is not going to handle the mirrored studs in the next release, but maybe in the next again. It will require a fundamental restructuring of the program, because currently L3P does not walk the tree. Also support of LGEO parts is an even (...) (20 years ago, 7-Nov-04, to lugnet.cad)
|
| | | | |
