 | | MEGA-POV 1.1
|
|
Hi All, I added support to LPub for POV-Ray 3.5 and 3.6. I was trying to use MEGA-POV 1.1, but it seems to have stopped supporting the find_edges facility. Anyone know how to do the find_edges in these newer renderers. Kevin (20 years ago, 2-Sep-04, to lugnet.cad.dev)
|
| |
| | Re: Blender LDraw support
|
|
I added a feature to automatically generate contour lines for exported objects, and reexported my 6575 model. I'm not sure it's quite the way it should be yet. Also set up a wiki page where I'd appreciate suggestions and questions. The wiki will be (...) (20 years ago, 2-Sep-04, to lugnet.cad.dev)
|
| |
| | LDraw Design Pad (LDDP) 1.5.5 Released
|
|
LDraw Design Pad (LDDP) is a tool for editing and handling LDraw files in a very comfortable way. Download it here: (URL) are: -Fully customizable editor with syntax highlighting -Open multiple files at the same time -Unlimited Undo/Redo -Use/define (...) (20 years ago, 29-Aug-04, to lugnet.cad, lugnet.cad.dev, lugnet.announce)
|
| |
| | Re: Blender LDraw support
|
|
A little bit of extra work, and I'm ready (sort of) to present the first export capable edition. It outputs DAT or MPD files of the current scene, including STEP support. Script pack (since the script now is split in multiple files): (URL) of output (...) (20 years ago, 28-Aug-04, to lugnet.cad.dev)
|
| |
| | LDraw part origin rule
|
|
TrackDraw's parts are 2D models of 3D parts as viewed from the top. TrackDraw attempts to maintain LDraw compatibility by using the same origin and orientation. This allows TrackDraw to read and save layouts in *.ldr format. For parts that exist, (...) (20 years ago, 25-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: Blender LDraw support
|
|
"Ooh, new script." *download* "Hm, fix path, load...will it work?" *jaw drops* DUDE, YOU ARE THE COOLEST PERSON EVER!!! THIS ROCKS!!! *head explodes from all the possibilities* "ewww..." -Stefan- (20 years ago, 17-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: Blender LDraw support
|
|
(...) Thanks alot for this work. It's very much the combination of tools that I am looking forward to working with. We mentioned LCad/Blender ties quite a bit at Brickfest this weekend. (...) (20 years ago, 17-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: Blender LDraw support
|
|
I've worked a bit more on my Blender LDraw import script. Recent additions: * Requires Blender 2.34 for some convenient functions. * Creates materials for each LDraw colour used, but does not fill in colours. * ldrawdir is now high in the script and (...) (20 years ago, 17-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: Blender LDraw support
|
|
(...) Neither am I. However, line 318 isn't in childreBobj in the most recent public version of the script. Since that's the only one that works in Blender 2.34 (and it probably has trouble with some types of files anyway, such as if they contain (...) (20 years ago, 17-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: On My L3P Wish List: Support for camera.dat and look_at.dat
|
|
(...) (URL) hard to search for something like -ic or -ci on lugnet. If there is a way, I can never remember how. Have fun, Don (20 years ago, 16-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: On My L3P Wish List: Support for camera.dat and look_at.dat
|
|
(...) here's one of the relevant posts: (URL) (20 years ago, 16-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: Blender LDraw support
|
|
Well, I fixed that, and it seems to be trying to load the model (I get a busy icon and such), but now it's hanging on another section. I now get this: Traceback <most recent call last>: File "<string>", line 340, in loaddat File "<string>", line (...) (20 years ago, 16-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: Blender LDraw support
|
|
(...) Yes, that is the place. Explorer is probably showing backslashes (\) rather than slashes; you'll have to change those to either \\ or /. A future version of this script will probably try to locate your LDraw directory. So you could change the (...) (20 years ago, 16-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: On My L3P Wish List: Support for camera.dat and look_at.dat
|
|
(...) Yeah, this sounds familiar. I searched, but I can't seem to find it. And I can't remember if we asked for dat files, or command line options to include separate POV files for those sections. Either way would probably work. There are differnet (...) (20 years ago, 15-Aug-04, to lugnet.cad.dev)
|
| |
| | On My L3P Wish List: Support for camera.dat and look_at.dat
|
|
At last, I have really discovered light.dat and its opportunities in L3P. It may have been discussed before, but I think it would be really great to have similar support for camera.dat and look_at.dat. Then the user easily and visually can move the (...) (20 years ago, 15-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: Blender LDraw support
|
|
(...) I found this chunk: libdirs= '/home/yann/Blender/...aw/parts'] def getmdl(path, name): Is this what I have to change? If so, do I just copy the paths the way they are in Explorer? (...) Here's the full error message: I get this when I load (...) (20 years ago, 14-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: Blender LDraw support
|
|
(...) In the current form the path to LDraw primitives and parts (ldraw/p and ldraw/parts) are hardcoded into the script. You'll need to change those before it will load anything referring to the part library correctly. If that doesn't help I'd (...) (20 years ago, 13-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: STEP into using LDAO or LDDP
|
|
(...) Last night I was showing my wife how STEP worked. She was pretty impressed until I got to the code in a _Technic 1 x 2 Brick with Hole_ where it drew the 4 quads at 24y. She said, "Well, what changed?". Being a newbie, it took me a while to (...) (20 years ago, 13-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: STEP into using LDAO or LDDP
|
|
(...) Sort of. I think I broke something in the ldglite polling code when I started fiddling with the search path stuff recently. It only works when I work on a file in the current directory. Gotta fix that. Also I guess I have to add the -p to the (...) (20 years ago, 13-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: STEP into using LDAO or LDDP
|
|
(...) LDDP creates a temp LDR file and has the renderer display that. The polling interval determines how often LDDP will update the temp LDR file to match edits (or cursor moves if draw to cursor is turned on). Of course, the renderer has to have (...) (20 years ago, 13-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: STEP into using LDAO or LDDP
|
|
(...) Eh? I feel left out. Why does it only mention L3Lab and LDView When it seems to work just fine for my favorite "user defined" external program as well? Actually I'm not sure what the polling interval does... Don (20 years ago, 13-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: Blender LDraw support
|
|
Hopefully you're still out there... This is really great that you've written this! Makes things alot easier for us who aren't that good with modeling tools. However, I'm having some problems, hopefully you can help me out? I try to import ldrs and (...) (20 years ago, 12-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: In dev: new ldconfig.ldr file
|
|
(...) color definitions. This new file includes several new colors, including (but not limited to): - New gray - New dark gray - New brown - Dark green - pearl gray - pearl sand blue - trans purple Some of the RGB values were based on the (...) (20 years ago, 11-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: In dev: new ldconfig.ldr file
|
|
(...) Yes ... and no. If we did produce a fully internationalized, multi-namable color definition set, we'd almost certainly include a 'default name' property for the colors. So think of the data in ldconfig.ldr as the color definitions + the (...) (20 years ago, 11-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: In dev: new ldconfig.ldr file
|
|
(...) Well, if you look at Datsville a lot, that would probably be the reason. It won't open in any version of LDView released to date. The next major LDView release (3.0) will open it. I just opened town.dat, and while it took 25 seconds to load (...) (20 years ago, 10-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: In dev: new ldconfig.ldr file
|
|
(...) The very big problem with all the nice options in L3Lab is that they aren't saved anywhere. One place to put all those options stored would be the ldconfig.ldr file, but I think it would be more natural to put it in ldraw.ini or a (...) (20 years ago, 10-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: In dev: new ldconfig.ldr file
|
|
(...) I agree that ldconfig.ldr should stay simple. But it should be possible for people to create and use alternate configuration files, including (but not limited to) alternate color definitions. Let's see, that's 4, or maybe 5, votes for (...) (20 years ago, 10-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: In dev: new ldconfig.ldr file
|
|
(...) <SHAMELESS_PLUG> That's easy, just use LDView ;-). </SHAMELESS_PLUG> It won't let you turn off all type 2 lines, but it will let you turn off all "edge lines", which are all type 5 lines, and all type 2 lines that are color 24. To be honest, I (...) (20 years ago, 9-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: In dev: new ldconfig.ldr file
|
|
(...) The more I think about it, the more I lean towards ldconfig.ldr should stick to handle just 'color definitions' and just default border colors, rather than 'color configurations'. Where 'default' is the traditional "anti-color" that optionally (...) (20 years ago, 9-Aug-04, to lugnet.cad.dev)
|
| |
| | Multiple ldconfig files really needed?
|
|
(...) Me too, but then again, is there really any need for more than two color setups? With this solution, you'll have to change all your alternative ldconfig files when a new color is added. I think just one ldconfig.ldr file would be an advantage. (...) (20 years ago, 9-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: In dev: new ldconfig.ldr file
|
|
(...) Maybe so, but I still like it. :^) Besides, it's really all about backwards compatibility. You're not suggesting we rename the [LDraw] key to [] are you? After all, it's just as redundant. Perhaps I'm a dummy, but I've got all sorts of LDAO (...) (20 years ago, 9-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: In dev: new ldconfig.ldr file
|
|
(...) Isn't "LDraw." redundant? It is, after all, the ldraw.ini file. --Travis Cobbs (20 years ago, 9-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: In dev: new ldconfig.ldr file
|
|
(...) True. Except the current ldconfig.ldr file doesn't specify all edge colors as black. Many of them use color 0 (which is defined as RGB(33,33,33)), some of them specify #000000, some of them use other colors. (...) Hmm, somebody want to setup a (...) (20 years ago, 9-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: In dev: new ldconfig.ldr file
|
|
(...) I never saw any of those discussions, and I pretty much kept silent about the original ldconfig.ldr file, because I never really gave the edge colors much thought. However, it seems to me that making all the edges black should be up to the (...) (20 years ago, 9-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: In dev: new ldconfig.ldr file
|
|
(...) Ah ha! I thought I saw some duplicates in there. Then the only thing left in [LDraw] is the various paths to find things. I like that. (...) Ok, so how about this? [LDraw.Configurations] # FILE Config Name LOCALE 0=ldconfig.ldr default EN (...) (20 years ago, 9-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: In dev: new ldconfig.ldr file
|
|
(...) If you mean the Launcher, LDAO Modeler, and Minifig Modeler keys -- those are old. The current version of LDAO stores these keys in the [LDraw Add-On] section. (...) To me, a dot looks more like a delimiter than a space. It somewhat indicates (...) (20 years ago, 9-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: In dev: new ldconfig.ldr file
|
|
(...) Why would you recommend that? My current ldraw.ini is loaded with search paths in the [LDraw] section. I'd say it's the other stuff that doesn't belong there. [LDraw] BaseDirectory=C:\ldraw Convert=c:\lcad\software\im (...) (20 years ago, 9-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: In dev: new ldconfig.ldr file
|
|
(...) That sounds sensible. Also it's occurred to me since my last post on the internationization topic, that the Color names, and color definitions might be better off split up. 1. If the skins or theme's catch on, there's no sense having a (...) (20 years ago, 9-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: In dev: new ldconfig.ldr file
|
|
(...) How about combining, steve's, andrew's, and your earlier idea with something like: [Configurations] # FILE Config Name LOCALE 0=ldconfig.ldr default EN 1=ldcfgalt.ldr ldlite EN 2=ldconfig_DE.ldr default DE 3=ldcfgalt_DE.ldr ldlite DE (...) (20 years ago, 9-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: In dev: new ldconfig.ldr file
|
|
(...) I'd say we're getting to the point where -- if there are going to be more than a handful of color configurations -- we'd want to think about some alternate distribution/management methods for 'color configurations'. Similar to what other (...) (20 years ago, 9-Aug-04, to lugnet.cad.dev)
|
