 | | 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: STEP into using LDAO or LDDP
|
|
(...) OK, I looked it up. You want to make sure both of the following menu options are checked: Process->External Programs->Polling->Poll to L3Lab and LDView Process->External Programs->Polling->Poll to selected line only Then when you launch either (...) (20 years ago, 13-Aug-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: STEP into using LDAO or LDDP
|
|
(...) I'll check that out immediately. At the moment, I'm trying to figure out how to make the Polling option in LDDP to work as a stepper. I'm rendering existing parts by blocks of code to see how you folks created them. The STEP function will (...) (20 years ago, 12-Aug-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: STEP into using LDAO or LDDP
|
|
(...) The LDAO Editor has a setting to draw up to the current line only. It's on Options -> Stop-at-Cursor. Steve (20 years ago, 12-Aug-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | 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: STEP into using LDAO or LDDP
|
|
(...) I had a really hard time finding that option also. And yet even so I'm not convinced it's in a bad place, since once I found it it made sense. I'm pretty sure it's in the polling menu. --Travis Cobbs (20 years ago, 11-Aug-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: STEP into using LDAO or LDDP
|
|
(...) Thanks. That's just what I'm looking for. But please pardon my ignorance. I have the basic LDDP without much plug-ins. I searched every option in the standard issue, but couldn't find the _draw to selected line mode_ option. Is that option (...) (20 years ago, 11-Aug-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: STEP into using LDAO or LDDP
|
|
(...) You can try LDDP draw to selected line mode. This will output the model from the beginning to the selected line. -Orion (20 years ago, 11-Aug-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | STEP into using LDAO or LDDP
|
|
Other than commenting and uncommenting blocks of code, how can one step through the lines one by one? I'm trying to teach myself how to author by following examples. I'd like to be able to step through the lines of code and see what is being (...) (20 years ago, 11-Aug-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | 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)
|
