 | | Re: LPub mask generation
|
|
(...) I'm not entirely sure, but I'm pretty sure you can create a 32bpp BMP file. Normally, 8 bits in each pixel would then be ignored. However, I don't see any reason the data wouldn't be there for you to interpret yourself. --Travis Cobbs (20 years ago, 15-Sep-04, to lugnet.cad.dev)
|
| |
| | LPub mask generation
|
|
I added mask generation for assembly images into LPub. It now can generate a specific mask for each assembly image. I plan on using this for the layout process, where you provide a backdrop image for a page, and LPub uses a mask to superimpose the (...) (20 years ago, 15-Sep-04, to lugnet.cad.dev)
|
| |
| | Re: l3p -check without using l3p
|
|
Thanks guys, I believed there had to be some kind of easy fix to the problem (too stupid). Now I feel a lot more comfortable certifying parts! -NB (20 years ago, 12-Sep-04, to lugnet.cad.dev, FTX)
|
| |
| | Re: l3p -check without using l3p
|
|
(...) Actually LDDP has a built in, full l3p check. You have to turn on the co-planarity checks under Tools->Options->Configuration Values -Orion (20 years ago, 12-Sep-04, to lugnet.cad.dev, FTX)
|
| |
| | Re: l3p -check without using l3p
|
|
(...) LDAO can be used to run l3p -check without even seeing a command prompt ;) ROSCO (20 years ago, 11-Sep-04, to lugnet.cad.dev, FTX)
|
| |
| | l3p -check without using l3p
|
|
Just a quick question: Is there any programs that can give you a full l3p-check other than l3p? (I not old enough to have done anything but starting games from prompt ;-) ) It seems like LDDP is pretty close to do that but although it’s able to find (...) (20 years ago, 11-Sep-04, to lugnet.cad.dev, FTX)
|
| |
| | Re: Postscript output
|
|
(...) Has anyone gone anywhere with this? -Tim (20 years ago, 11-Sep-04, to lugnet.cad.dev)
|
| |
| | Re: Parts with lengths
|
|
In lugnet.cad.dev, Kevin L. Clague wrote: [snip] nod, I agree with everything you wrote. (...) Long term (*very* long term), there's nothing to say the language can't be extended to allow a different linetype for parts-with-lengths. Steve (20 years ago, 10-Sep-04, to lugnet.cad.dev)
|
| |
| | Re: Parts with lengths
|
|
(...) Sure! Tattle on me so I get in trouble! Actually I've just been prototyping more compact part usages for hoses, using variable length cross sections instead of fixed length cross sections. (...) Kevin (20 years ago, 10-Sep-04, to lugnet.cad.dev)
|
| |
| | Re: Parts with lengths
|
|
(...) I think Kevin's done some work on the code that hasn't been uploaded to the CVS repository so the current CVS source may be out of synch. -Orion (20 years ago, 9-Sep-04, to lugnet.cad.dev)
|
| |
| | Re: Parts with lengths
|
|
(...) Just in case, the source code for lsynth is here. (URL) the CVS Repository link for instructions on how to fetch it all, or follow the Browse CVS link if you only want to examine it. Have fun, Don (20 years ago, 9-Sep-04, to lugnet.cad.dev)
|
| |
| | Re: Parts with lengths
|
|
(...) Jindroush, True length is a topic that is near the top of the list for LSynth. Orion and I talked about it at BrickFest. There is at least one implementation out there by Frederick Glockner (using emacs) that supports true length. Since LSynth (...) (20 years ago, 9-Sep-04, to lugnet.cad.dev)
|
| |
| | Re: Parts with lengths (lsynth?)
|
|
(...) Yeah, exactly this. I knew I couldn't be the first to think about it ;-) Jindroush (20 years ago, 9-Sep-04, to lugnet.cad.dev)
|
| |
| | Re: Parts with lengths (lsynth?)
|
|
(...) You know, this did actually come up before in the context of lsynth. This post from 2 years ago mentions LENGTH and UNITS options for the lsynth meta commands. (URL) think it's been mentioned since then as well. In my opinion that's probably (...) (20 years ago, 9-Sep-04, to lugnet.cad.dev)
|
| |
| | Re: Parts with lengths
|
|
(...) i haven't suggested that. We don't have separate part file for every known color, but instead, there is part and color info in the dat. I think the length should be put in somewhat similar way in the dat, so that it could be easily extracted (...) (20 years ago, 8-Sep-04, to lugnet.cad.dev)
|
| |
| | Re: LPub - background images for pages, PLIs and BOMs.
|
|
(...) Trying to do this may of course completely blow away how I render part list images with background images. (...) Kevin (20 years ago, 7-Sep-04, to lugnet.cad.dev)
|
| |
| | Re: LPub - background images for pages, PLIs and BOMs.
|
|
(...) A quick search of the POV newsgroups yielded this suggestion: (URL) (20 years ago, 7-Sep-04, to lugnet.cad.dev)
|
| |
| | Re: LPub - background images for pages, PLIs and BOMs.
|
|
(...) I believe that the general answer is yes, it is possible to take a jpg, gif, or bmp and place it into a rendered scene. One way it can be done is with texturemapping onto a rectangle. What you would presumably need to do then is position and (...) (20 years ago, 7-Sep-04, to lugnet.cad.dev)
|
| |
| | LPub - background images for pages, PLIs and BOMs.
|
|
Hi, I've got a mask generation facility working pretty well for partial assembly images. The technique I use is to add the concept of chromakey color. I render the image with chromakey color (user selectable) as the background color. I then examine (...) (20 years ago, 7-Sep-04, to lugnet.cad.dev)
|
| |
| | Re: Parts with lengths
|
|
(...) I don't think making a separate part file for every known length of a part is the right approach, for at least two different reasons. First, it would significantly increase the number of parts in the LDraw library, making it that much harder (...) (20 years ago, 7-Sep-04, to lugnet.cad.dat.parts, lugnet.cad.dev)
|
| |
| | 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)
|
| |
| | Re: In dev: new ldconfig.ldr file
|
|
(...) Err, I missed that point in the search path discussion - or I would have recommended putting them in a different section. If [configurations] is too generic, then how about [LDraw.configurations]? Steve (20 years ago, 9-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: In dev: new ldconfig.ldr file
|
|
(...) To be honest, I don't remember for sure, but I doubt it. My general standpoint on these kinds of things is that LDraw is a 3D-library, not a database. And language issues are (mostly) outside the scope of the library. However, I think Don had (...) (20 years ago, 9-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: In dev: new ldconfig.ldr file
|
|
(...) Well, we *did* change it from "0 !COLOR" to "0 !COLOUR" to honor the austrailian roots of the ldraw system. Does that count? (...) Actually, Steve's idea of listing multiple versions of the config file in the ldraw.ini would handle this (...) (20 years ago, 9-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: In dev: new ldconfig.ldr file
|
|
Was there ever any discussion about internationalized versions of this file? I was thinking that we could support various languages like this: 0 !COLOUR CODE 0 VALUE #212121 EDGE 8 0 !COLOUR NAME en 0 Black 0 !COLOUR NAME fr 0 Noir 0 !COLOUR NAME de (...) (20 years ago, 9-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: In dev: new ldconfig.ldr file
|
|
(...) Actually, if ldcfgalt.ldr contains the ldlite colors it should work quite nicely on a black background. After all, ldraw used a black background, and the ldlite colors were based on it. And to be totally honest, the default ldlite edge color (...) (20 years ago, 9-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: In dev: new ldconfig.ldr file
|
|
(...) Yes, I like it. However, is it different from the way we decided to number the search paths? Last I remember, we decided to stick them in the generic [LDraw] section and number them like this. [LDraw] LdrawSearch01=<HIDE>...MyPrims\In Work (...) (20 years ago, 9-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: In dev: new ldconfig.ldr file
|
|
(...) How about a ldcfgblk.ldr? For those of us who prefer to edit on a black background instead of a paper white one? I suppose the software could just swap edge=0 for edge=8 and vice versa, but what about the non-black and white edges? -Kyle (...) (20 years ago, 9-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: In dev: new ldconfig.ldr file
|
|
(...) Yeah, I could see a section in LDRAW.INI like: [Configurations] 0=ldconfig.ldr 1=ldcfgalt.ldr ... (...) Well, yeah -- but then there'd have to be another interface element to allow the user to select the colorblock. I think it would be easier (...) (20 years ago, 9-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: In dev: new ldconfig.ldr file
|
|
(...) The DOS tools won't use the file, but DOS users may still unzip new part libraries to an 8.3 filesystem. (...) I like it, but I'll have to spend some more time comparing. Many of the colors vary a bit from the ldlite defaults, and some of the (...) (20 years ago, 9-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: In dev: new ldconfig.ldr file
|
|
(...) I like the black edges. They're what LEGO use, after all. (...) I'll take that bet! :-) As long as I get to pick the focus group. :-) More seriously, I'm glad that Steve is going to go with an alternate version of the file, as long as it's not (...) (20 years ago, 9-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: In dev: new ldconfig.ldr file
|
|
(...) nbd. :) (...) OK, thanks for clarifying. Most comments I've heard in this area have been from people who prefer black edges over colored edges, which is why ldconfig.ldr has the more depressing style. (...) I don't see why not. How's this? (...) (20 years ago, 9-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: In dev: new ldconfig.ldr file
|
|
(...) Sorry about that. I really don't like it, except for printing out paper copies. And that's probabably only because of inkjet printer limitations (there's almost always a black cartridge). (...) Sure, but I've mostly ignored it because the file (...) (20 years ago, 9-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: In dev: new ldconfig.ldr file
|
|
(...) Are you being entirely ironic about this, or only partially? That is, do you like or dislike the mostly-black edge colors? I can't tell from your post. Either way, I must mention that I haven't changed most of the data; the current 'official' (...) (20 years ago, 9-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: In dev: new ldconfig.ldr file
|
|
(...) Ewww! Who picked the yucky edge colors? I mean, black edges are fine for *printed* instructions, but in my personal opinion they're not nearly bright and cheerful enough for on screen modeling. :-< And I'm fairly certain that 9 out of 10 focus (...) (20 years ago, 9-Aug-04, to lugnet.cad.dev)
|
| |
| | In dev: new ldconfig.ldr file
|
|
Since the LSC has come to agreement on a 1.0 standard for the !COLOUR meta-statement, I've prepared a new version of the ldconfig.ldr file. The new file has been converted to use the !COLOUR statement in place of LDLite's COLOR statement. Besided (...) (20 years ago, 9-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: I have an idea . What if we make a game
|
|
(...) have made it possible to run a multiplayer session and now is possible: - to chat - move around spots and the other playes can see a message saying your location in game , for now in text but later i will make it so that we see us as lego (...) (20 years ago, 7-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: Status of BFC
|
|
(...) -Wayne (20 years ago, 4-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: Status of BFC
|
|
(...) It's listed. It's on the Specifications page under the Standards heading with the title of "LDraw Language Extension for Clipping (BFC)". Here's a direct link: (URL) (20 years ago, 4-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: Status of BFC
|
|
(...) Alll: Could somebody please tell me where the BFC documentation is? I've read the specifications at LDraw.Org and I see no mention of it. -Wayne (20 years ago, 4-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: I have an idea . What if we make a game
|
|
I made a screenshot of the gui for the game I need help as I don't know how to do it most of it mainly the internet parts (URL) (20 years ago, 3-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: Status of BFC
|
|
(...) Some part authors have been making major advances in getting the official library BFC compliant - notably Guy Vivan has been submitting BFCed files almost daily in recent months. These revised parts are in the Parts Tracker waiting for review. (...) (20 years ago, 3-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: Status of BFC
|
|
(...) I'll be supporting it in the next major LDView version (3.0). I really don't have an estimated completion date for this at the moment, but I at least hope to have it out before the end of the year. There could be minor LDView updates before (...) (20 years ago, 2-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: Status of BFC
|
|
(...) Yes it will... Once all the parts in the library are made BFC complient. (...) Since it's not full implemented library wide, most tools haven't been able to take full advantage of the benefit of consistant winding. POV-Ray is a ray tracer as (...) (20 years ago, 2-Aug-04, to lugnet.cad.dev)
|
| |
| | Status of BFC
|
|
Hi there. I just found this about BFC. As I understand it, it's intended to be used to reduce the amount of polygons etc. in the modell that is renderd, in some way? If I've understood this correctly, is thisthen used in any current tools for (...) (20 years ago, 2-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: Request change to ptreleases.cgi
|
|
(...) I tend to agree with your thought, and I'm going to switch the script over to a flat-list model. Although I think the hierarchy of release -> distr type -> file format makes the most sense; and (somewhat) addresses your earlier question about (...) (20 years ago, 2-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: Request change to ptreleases.cgi
|
|
(...) I actually considered that when you made your original post. However, there are actually multiple different perfectly valid heirarchies, and for this reason I think the flat list is better overall. Here's an example with a different (...) (20 years ago, 2-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: Request change to ptreleases.cgi
|
|
(...) Looking at this some more... The script currently returns XML with 3 lists of distribution files: BASE - file ZIP - file ARJ COMPLETE - file ZIP - file ARJ UPDATE - file ZIP - file ARJ - file ZIP - file ARJ - file ZIP ... It could be argued (...) (20 years ago, 2-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: Request change to ptreleases.cgi
|
|
(...) Thanks, Chris! I'll add this shortly. Steve (20 years ago, 2-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: Request change to ptreleases.cgi
|
|
(...) In XML::Simple the root element name is controlled by the RootName option (RootName => 'string') (URL)_'string'_#_out_-_handy Chris (20 years ago, 1-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: Request change to ptreleases.cgi
|
|
(...) There's no significance, AFAIK. The Perl module, XML::Simple, wraps the <opt> tag around everything automatically. I scanned the docs, but didn't see how to control it. Steve (20 years ago, 31-Jul-04, to lugnet.cad.dev)
|
| |
| | Re: Request change to ptreleases.cgi
|
|
(...) I'm not really up on XML, but it looks fine to me. I do have a question, though. Is there some significance that I am missing to naming the root element "opt"? --Travis Cobbs (20 years ago, 31-Jul-04, to lugnet.cad.dev)
|
| |
| | Re: Request change to ptreleases.cgi
|
|
(...) OK, the URL is still temporary, but the script should be more-or-less done. Have at it, look for deficiencies, bugs, etc. If you don't remember the options, try adding ?help=1 to the url. I haven't thought very hard about the XML format -- if (...) (20 years ago, 31-Jul-04, to lugnet.cad.dev)
|
| |
| | Re: Request change to ptreleases.cgi
|
|
(...) Yeah, but I was thinking more for programs that were developed to support one dataset, and couldn't cope with a different model for distribution files. I know, I know -- require the coders to work more intelligently. ;) Steve (20 years ago, 29-Jul-04, to lugnet.cad.dev)
|
| |
| | Re: Request change to ptreleases.cgi
|
|
(...) Pft. Make ptrelease support a library version field, which would be 1 for the current lib, and 2 for the new one. :) (20 years ago, 29-Jul-04, to lugnet.cad.dev)
|
| |
| | Re: Request change to ptreleases.cgi
|
|
(...) That's one. :) (...) Michael had asked for that awhile ago. (...) Good point, I hadn't thought of that. (...) Hmmm, what *is* up with those dates? I'll go fix'em. (...) Yeah, I dunno. We certainly could go create ZIPs for those old updates. (...) (20 years ago, 29-Jul-04, to lugnet.cad.dev)
|
| |
| | Re: cant compile ldglite in gentoo linux
|
|
(...) Ok, I'll try to fix that in CVS. Meanwhile, what does it print in the console window when it starts up? I like to track the opengl driver developments in the various linux distributions. (20 years ago, 28-Jul-04, to lugnet.cad.dev)
|
| |
| | Re: cant compile ldglite in gentoo linux
|
|
(...) Yes, now it opens in the right directory. (20 years ago, 28-Jul-04, to lugnet.cad.dev)
|
| |
| | Re: cant compile ldglite in gentoo linux
|
|
(...) That's what I thought. Try commenting the call to platform_sethome() in main.c and rebuilding. Maybe that'll fix it. (...) I agree. This was a quick hack to appease those icon clicking Mac users until the LDRAW.INI search settings are (...) (20 years ago, 28-Jul-04, to lugnet.cad.dev)
|
| |
| | Re: cant compile ldglite in gentoo linux
|
|
(...) My home directory. Acctually, I think it's perhaps better to start it from the current directory, instead of the home directory. Maybe it's just me, but I usually start programs from other directories, and the files I want to use are often in (...) (20 years ago, 28-Jul-04, to lugnet.cad.dev)
|
| |
| | Re: cant compile ldglite in gentoo linux
|
|
(...) Should I make a "somewhat newer stuff" section? :^) (...) That's odd. I may have broken it with my recent tinkering. I think I was trying to make it look in the home directory if it didn't see anything like a dat file on the command line. I (...) (20 years ago, 28-Jul-04, to lugnet.cad.dev)
|
