 | | Re: *** MLCad V3.30 ***
|
|
There is a bug in the generated partslist when using a new color. For example when I use a part with color 81 Metalic_Green it reports as Chrome_Black. See: (URL) this be resolved with a change in ldconfig or is a real bug in MLCad 3.30? Jaco (15 years ago, 11-May-10, to lugnet.cad.mlcad)
|
| |
| | Re: ML-CAD 3.30 Problem while parts authoring
|
|
(...) IMHO if the rotvector field is active when pressing OK, it should pop up that dialog (or maybe even ignore changes altogether and close the dialog - I do not know nor do I care) if |angle| > 180. Nowhere else. I'd personally want this be fixed (...) (15 years ago, 17-Feb-10, to lugnet.cad.mlcad)
|
| |
| | Re: ML-CAD 3.30 Problem while parts authoring
|
|
(...) Have you been authoring parts again? I thought your therapist warned you about that???? ;) ROSCO (15 years ago, 17-Feb-10, to lugnet.cad.mlcad)
|
| |
| | Re: ML-CAD 3.30 Problem while parts authoring
|
|
(...) Oh yeah. I encountered this one the other day too. The angle gets set to a very large number. I believe that the normal/angle mapping only applies to rotations, not scaling and should be ignored when ||R||!=1. Tim (15 years ago, 16-Feb-10, to lugnet.cad.mlcad)
|
| |
| | ML-CAD 3.30 Problem while parts authoring
|
|
Hello Michael, I have a problem while parts authoring. When I have insert a new primitive and changing the first time it's values, like the size, evrything works fine. But when I want to change the size or so again. Then the "position & orientation" (...) (15 years ago, 16-Feb-10, to lugnet.cad.mlcad)
|
| |
| | Re: MLCad.ini 2009-03 Update Now Available
|
|
(...) Willy, You caught most of the parts that got moved to new numbers, except for: 982.DAT 981.DAT Thanks as always for keeping this file up to date. Allen (15 years ago, 15-Feb-10, to lugnet.cad.mlcad, FTX)
|
| |
| | Re: BTW, Dither What Colors...?
|
|
(...) Also I am thinking that we have to use the original color values for the color 0 - 15 to build the blended colors. Otherwise we get other colors. This range should be known by every LDraw related application.and only overwritten by entries (...) (15 years ago, 12-Feb-10, to lugnet.cad.mlcad)
|
| |
| | Re: BTW, Dither What Colors...?
|
|
--SNIP-- (...) Good thinking. Since the old colours were derived from the EGA colour palette I reckon the dithers would have to be derived from it too. Otherwise you could end up with some very different blends. I like your signature ;) Tim (15 years ago, 12-Feb-10, to lugnet.cad.mlcad)
|
| |
| | Re: *** MLCad V3.30 ***
|
|
(...) If you have any question regarding this, please don't hesitate to contact me, as I have already made DATHeader using this new feature. (...) Yes, I miss that as they are used in parts already. But others already have answered this question (...) (15 years ago, 11-Feb-10, to lugnet.cad.mlcad)
|
| |
| | Re: *** MLCad V3.30 ***
|
|
(...) That is exactly what I was thinking about last days. First load MLCad standard colours (like they have been for year). Then replace all the colors for that you will find an entry in the LDConfig.ldr. I would prefer to really keep the blended (...) (15 years ago, 11-Feb-10, to lugnet.cad.mlcad)
|
| |
| | Re: *** MLCad V3.30 ***
|
|
(...) LDView's blending code was originally written to handle LDLite's 0 COLOR syntax, since that is what was originally used in LDConfig.ldr. LDLite's syntax allows for the dithering of two arbitrary colors, either or both of which can themselves (...) (15 years ago, 11-Feb-10, to lugnet.cad.mlcad)
|
| |
| | Re: Warning: Printing Bug in MLCad!
|
|
(...) Exactly! But there is a work-arround patch available - which has to be introduced into the source code :-< Michael (15 years ago, 11-Feb-10, to lugnet.cad.mlcad)
|
| |
| | Re: *** MLCad V3.30 ***
|
|
(...) I've been surprised by some of this discussion of dithered colors, because when Foundry was created (not by me), it was done as a "clean room" project, based entirely off of specs, so it's the closest thing out there to a reference parser, and (...) (15 years ago, 11-Feb-10, to lugnet.cad.mlcad)
|
| |
| | Re: Warning: Printing Bug in MLCad!
|
|
(...) It sounds like you already discovered the root cause of this, but just in case you haven't, MFC's CDC::TabbedTextOut() always crashes in Print Preview mode in Visual Studio 2005 Service Pack 1. --Travis (15 years ago, 10-Feb-10, to lugnet.cad.mlcad)
|
| |
| | Re: *** MLCad V3.30 ***
|
|
(...) How about just "use the 'dithered' range but apply LDConfig on top of them, overriding any colour that gets in the way"? -Santeri (15 years ago, 10-Feb-10, to lugnet.cad.mlcad)
|
| |
| | Re: *** MLCad V3.30 ***
|
|
(...) I can confirm that. While the LSC may have dithered over the spec, we certainly didn't drop "dither" intentionally. (Mind you, given the number of referenced specs we had to ratify first before we could get onto "the biggie", I'm surprised we (...) (15 years ago, 10-Feb-10, to lugnet.cad.mlcad)
|
| |
| | Re: *** MLCad V3.30 ***
|
|
(...) I think Travis' wording may be confusing. Don't use "the old dither algorithm". MLCad 3.30 draws colors 256-511 as *solid* colors. That's better than using the stippling algorithm from previous MLCad versions. (No new/current software stipples (...) (15 years ago, 10-Feb-10, to lugnet.cad.mlcad)
|
| |
| | Re: BTW, Dither What Colors...?
|
|
(...) Of course, I mean the blending, not the dithering... (15 years ago, 10-Feb-10, to lugnet.cad.mlcad)
|
| |
| | BTW, Dither What Colors...?
|
|
(...) Hmm. "You may think this is easy, but wait 'til I've explained it to you!" (One of my father's favourite standard joke.) I don't know how much difference it will make, but current standard colors are much better than the 16 original LDraw (...) (15 years ago, 10-Feb-10, to lugnet.cad.mlcad)
|
| |
| | Warning: Printing Bug in MLCad!
|
|
Hi, sorry to say, but I just found a bug in MLCad which is caused by the actual compiler I'm using. When you start printing preview in MLCad it is crashing when part lists are printed. I'm working on that .... Michael (15 years ago, 10-Feb-10, to lugnet.cad.mlcad)
|
