 | | 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)
|
