 | | Re: 11-16 primitives?
|
|
(...) That would be good, I think. (...) Can you have two levels? Level One that still shows the warnings, but doesn't stop, and Level Two suppresses all warnings. (...) I'd keep the current line-format for all parts conforming to the 8.3 format, (...) (15 years ago, 27-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: 11-16 primitives?
|
|
(...) I could update the mklist sources to work handle filenames with 25 chars I was going to add a quietmode commandline option this weekend anyhow. Should I allow 25 chars as the default, and perhaps include an optional command line arg to (...) (15 years ago, 25-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: 11-16 primitives?
|
|
(...) If I understand that, this would mean that we could use a new mklist tool and we can start using that long filenames. The possibility to use MLCad for generating PARTS.LST will be away, but this only a little cut. cu mikeheide (15 years ago, 25-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: 11-16 primitives?
|
|
(...) Were any other issues anticipated? (...) I did a short test of MLCAD with a modified PARTS.LST. The results were mixed - MLCAD seems OK using an altered-format PARTS.LST file, but re-generating PARTS.LST from MLCAD results in an invalid file. (...) (15 years ago, 25-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: 11-16 primitives?
|
|
(...) When the LSC updated the spec to allow 21.3 filenames, I don't think any of us were aware that this would create a problem for PARTS.LST. However, looking at the file, there's a chance that MLCAD will work perfectly well with longer filenames (...) (15 years ago, 25-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: 11-16 primitives?
|
|
(...) Parts Tracker-wise (if I remember right, and if nothing's been changed), there's only one script which needs to be modified to accept 21.3 files instead of 8.3 files. Organizationally, I dunno if there is actually a hold-up. The specifications (...) (15 years ago, 25-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: 11-16 primitives?
|
|
(...) This is the status quo now for many months. What action has been taken to solve that problem? To me it seems only to be a little adjustment to some lines of code (but maybe I am wrong). So my question would be: where is the bottleneck that (...) (15 years ago, 25-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: 11-16 primitives?
|
|
(...) Well... imho this should not be an issue at all - if the parts tracker was updated! Philo (15 years ago, 25-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: 11-16 primitives?
|
|
(...) These truncated filenames never went past the LSC, and as such should probably be held. I personally feel that they are inappropriate, but whether or not I think they are appropriate, I believe that it's the LSC's job to determine that. (...) (15 years ago, 25-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: 11-16 primitives?
|
|
Hi Steve, (...) One reason: the Parts Tracker still doesn't like >8 names :( Philo (15 years ago, 25-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: 11-16 primitives?
|
|
(...) I ditto Phillippe's primary suggestion: use multiple files. It's good for multiple reasons. However, the current standards allow at least 25 characters in the filename, so is there a reason to worry about a 9 character primitive name? Steve (15 years ago, 25-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: 11-16 primitives?
|
|
(...) I would suggest avoiding the problem completely by using a 2-4edge + 3-16edge... In other instances the name was shortened: 3-16cone19 --> 3-16co19 11-48ring19 --> 11-48r19 Philo (15 years ago, 25-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | 11-16 primitives?
|
|
What would be the suggested name for an 11-16 primitive for a cylinder or edge line since 11-16 contains 5 letters and tacking on edge or cyli at the end would give a 9 letter name? (15 years ago, 22-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Reverse Ratio torus naming convention
|
|
I have endorsed the Primitive Generator's naming convention for "reverse ratio" tori (toruses) with a minor update to the Primtives Reference ((URL) of the form r{ff}o{rrrr}.dat represent the outer section of a torus where the minor radius is (...) (15 years ago, 21-Jun-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Reverse torus naming convention
|
|
I have endorsed the Primitive Generator's naming convention for "reverse ratio" tori (toruses) with a minor update to the Primtives Reference ((URL) of the form r{ff}o{rrrr}.dat represent the outer section of a torus where the minor radius is (...) (15 years ago, 21-Jun-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: Stretching cylinders [DAT]
|
|
(...) There is no way to get your shape using primitives, it would require non-linear transformations. So, as mentionned by Michael, the best way is to use Coverer. You can nonetheless get a similar (but quite different) shape using shearing as (...) (15 years ago, 15-Feb-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: Stretching cylinders
|
|
Is this what you had in mind? (...) Basicly changing any of the non zero coordinates will scale along the coresponding axis. You can also accomplish shearing by replacing any of the zero's with a different number. (15 years ago, 14-Feb-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: Stretching cylinders
|
|
(...) AFAIK there is no solution with primitives in this case. I would suggest use one of the tools from Philo ((URL) to fill the space between those 4-4edge.dat cu mikeheide (15 years ago, 15-Feb-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Stretching cylinders [DAT]
|
|
Well, it's my second thread today, but how would you go to "stretch" a cylinder, like a cone, but only in Y-axis, not X-axis? I've again attached a dat file to show what I mean. Basically I'd need a cylinder that'd fit those two 4-4edge.dat:s, any (...) (15 years ago, 14-Feb-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: cylt.dat
|
|
(...) Agh... guess it's going to take some time before I'll master those cyls.dat files. Well, this seems to save me a primitive. (15 years ago, 14-Feb-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: cylt.dat [DAT]
|
|
(...) As far as I can see the same can be build by 1-4cyls.dat like this: 0 Untitled 0 Name: Untitled.ldr 0 Author: Michael Heidemann [mikeheide] 0 Unofficial Model 1 16 -1 0 0 1 0 0 0 1 0 0 0 1 1-4cyls.dat 1 16 -1 0 0 1 0 0 0 1 0 0 0 -1 1-4cyls.dat (...) (15 years ago, 14-Feb-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | cylt.dat [DAT]
|
|
Hello, I've been in need of a primitive something similar to a sloped cylinder, but something little different, so I made such primitive. I can't describe the primitive, though. You'll have to see it yourself. :-) What I'm concerned now is the (...) (15 years ago, 14-Feb-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: naming for some half-primitives
|
|
(...) Actually yeah, that's an even better approach... saves primitives. I guess I should do that instead. (15 years ago, 27-Jan-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: naming for some half-primitives
|
|
(...) If I have such a problem I use those primitives that are not presently available in the main file, while the other stuff goes into the subfile that I then use several times. cu mikeheide (15 years ago, 26-Jan-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: naming for some half-primitives
|
|
(...) I see. I shall use those, then. (15 years ago, 26-Jan-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: naming for some half-primitives
|
|
(...) Please just use the next available axlehoXX and npegholX numbers; axleho10.dat (thats one-zero not ell-zero), npeghol8.dat and npeghol9.dat. I want to sort out a better naming convention for these, but I don't want to hold up creativity. Chris (...) (15 years ago, 26-Jan-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | naming for some half-primitives
|
|
I've got a little little problem with primitives. I'm working on the 61808.dat file (I guess I'll do it with 61811.dat parallel...), and to ease it up and to save disk space the file will be in four quarters. So, to have such things, you inevitably (...) (15 years ago, 26-Jan-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: Missing primitives after part update.
|
|
(...) I don't understand your question. How would you go about doing what? And while you might not know what else the MLCad base path would be, your description of the problem makes it sound like MLCad has to be looking for parts in some other (...) (17 years ago, 27-Jun-07, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: Missing primitives after part update.
|
|
(...) My base path is C:\LDraw. I don't know what else it would be. As for your suggestion, how would I go about that? Thank you so much for your patience -Bill. (17 years ago, 27-Jun-07, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: Missing primitives after part update.
|
|
(...) It sounds like you've ended up with files in the wrong folders, and it doesn't matter how many times you run the Scan command, since MLCad has no idea which files should be where. It just assumes you placed them correctly, and updates its own (...) (17 years ago, 20-Jun-07, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: Missing primitives after part update.
|
|
(...) It sounds like maybe the LDraw directory you have selected in MLCad isn't your real LDraw directory. Go into MLCad and check where it thinks the LDraw directory is (Settings->General->......->LDraw base path). If that differs from where you (...) (17 years ago, 20-Jun-07, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: Missing primitives after part update.
|
|
(...) Thanks Travis. I tried your first suggestion with no success. As for your second, I already have LDView. It seems like several people have had the same problem. What about uninstalling the whole LDraw package and then reinstalling? How do I go (...) (17 years ago, 20-Jun-07, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: Missing primitives after part update.
|
|
(...) a tutorial how to customize the MLCad.ini file with a spot on the scan of unofficial folders can be found here: (URL) w. (17 years ago, 20-Jun-07, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: Missing primitives after part update.
|
|
(...) If you want it to find parts in the Models directory, the MLCad.ini in the following zip will probably make that work: (URL) the MLCad.ini file from the zip into your main MLCad directory (in Program Files by default). If you already have an (...) (17 years ago, 20-Jun-07, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: Missing primitives after part update.
|
|
(...) I'm not exactly sure how to make sure the parts are in the correct directories. As for the "Scan Parts" command I have run that multiple times.What happens is that MLCAD will say a file can not be found but when I search the file is indeed in (...) (17 years ago, 20-Jun-07, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: Missing primitives after part update.
|
|
(...) Not long ago, I had the same problem. Try this: - Make sure that the downloaded subfiles are in the correct directories: some subparts belong to "\PARTS", while other subparts belong to "\PARTS\S" and so on. - After each download, run "Scan (...) (17 years ago, 10-Jun-07, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: Missing primitives after part update.
|
|
(...) Hello William, Would you be using unofficial parts (or models using them)? In that case you are also missing unofficial primitives. One radical solution is to download the whole set of unofficial files here: (URL) doing so, be sure to read (...) (17 years ago, 10-Jun-07, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: Missing primitives after part update.
|
|
(...) Well, I finished the model I was working on and tried your suggestion. After completing the manual download instructions I tried to download a part that I tried unsuccessfully to download a while back. Unfortunately I still have the same (...) (17 years ago, 10-Jun-07, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: Missing primitives after part update.
|
|
(...) Thanks Steve. I'm not computer illiterate, but I'n not exactly computer fluent either. I'll try what you've suggested. One question before I do though: If parts from older versions are overwritten and I reinstall complete.exe, will it (...) (17 years ago, 8-Jun-07, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: Missing primitives after part update.
|
|
(...) Take a look at the Manual Install directions on ldraw.org: (URL) ldraw027.exe will overwrite a number of parts with older versions, so after you install the ldraw027.exe file, you will need to re-install complete.exe. Steve (17 years ago, 8-Jun-07, to lugnet.cad.dat.parts.primitives)
|
