 | | LPub 4.0.0.4 CLEAR / BUFEXCHG issue [DAT]
|
|
LPub 4.0.0.4 crashes if there is a CLEAR and a BUFEXCHG in the same MULTI-STEP group Two files below, first one is OK, second one crashes on page 2 0 FILE NoCrash.ldr 0 NoCrash 0 NAME: NoCrash.LDR 0 AUTHOR: MLCAD 0 UNOFFICIAL MODEL 0 !LPUB (...) (15 years ago, 6-Feb-10, to lugnet.cad)
|
| |
| | Re: Dungeon Delver: That Frog...
|
|
(...) Wow. I'm glad I posted my little picture, if for no other reason than to bring your amazing work to light again. I only get the chance to pop into Lugnet once in a while now, and had never seen this scnner of yours. It would be pretty amazing (...) (15 years ago, 6-Feb-10, to lugnet.cad)
|
| |
| | Re: "Dither" colors in patterned/sticker parts
|
|
(...) I'm not much of a part author, so my opinion probably counts for even less than usual here, but I actually find myself agreeing with Willy on a issue involving colors. That never happens! ;) But heck, who can argue against freedom and (...) (15 years ago, 6-Feb-10, to lugnet.cad.dat.parts)
|
| |
| | Re: "Dither" colors in patterned/sticker parts
|
|
(...) It would be very interesting which applications can not work with the (RGB colors (of the form 0x2RRGGBB)). Are they useful/necessary/developed? If someone has those application to test and make a summary of that would be great. cu mikeheide (15 years ago, 6-Feb-10, to lugnet.cad.dat.parts, FTX)
|
| |
| | Re: "Dither" colors in patterned/sticker parts
|
|
(...) For what it counts, I'd go for: * Explicitly disallow "dither" colors in all official parts, but allow RGB colors (of the form 0x2RRGGBB) in their place in patterned/sticker parts. This solution would give me the most freedom. I could just (...) (15 years ago, 6-Feb-10, to lugnet.cad.dat.parts)
|
| |
| | Re: LPub 4.0.0.4 CLEAR issue
|
|
(...) Hi William, Welcome to LPub 4.0! Its a bit different, eh? Your expectations for CLEAR are very reasonable. <snip> Thanks for the wonderfully simple example. I made a one line fix for this. After I get the "submodel in PLI" problem fixed, you (...) (15 years ago, 6-Feb-10, to lugnet.cad)
|
| |
| | Re: LPub 4.0.0.4: Submodels in parts list?
|
|
(...) I have found and fixed this one. (...) With it fixed, this should be fixed too. (...) I'll work on this next. (...) Kevin (15 years ago, 6-Feb-10, to lugnet.cad)
|
| |
| | "Dither" colors in patterned/sticker parts
|
|
Please read and respond to this message if you are a parts author, particularly if you have authored any patterned or sticker parts. The LSC is trying to come up with rules for colors for both LDConfig.ldr and official parts. We are having an (...) (15 years ago, 6-Feb-10, to lugnet.cad.dat.parts, FTX)
|
| |
| | LDraw.org Parts numbering scheme for parts with unknown numbers.
|
|
The LSC has just ratified the LDraw.org Parts numbering scheme for parts with unknown numbers. It should allow to add parts to the library where the part number is not known. As the systematic that is used up to now has reached its limits this (...) (15 years ago, 5-Feb-10, to lugnet.cad, lugnet.announce)
|
| |
| | LPub 4.0.0.4 CLEAR issue [DAT]
|
|
LPub 4.0.0.4 doesn't seem to honour the CLEAR command across multi-steps after the page after the clear (see sample below) 7 bricks in a row with steps between - A B C D E F G in three multi-step groups with a CLEAR after group 1 - (A B C) CLEAR (D (...) (15 years ago, 5-Feb-10, to lugnet.cad)
|
| |
| | Re: LPub 4.0.0.4: Callout placement
|
|
(...) Just started using LPub 4 (last used LPub 2!) and came across this. What seems to happen is that the callout placement meta-command *is* created, just after the callout end meta-command. So after moving the callout with the mouse you need to (...) (15 years ago, 5-Feb-10, to lugnet.cad)
|
| |
| | Re: Lego City Policeman and LdrDat2Dxf utility
|
|
(...) The tool is downloadable from (URL) (15 years ago, 4-Feb-10, to lugnet.cad)
|
| |
| | Updated Unofficial parts pack for LeoCAD
|
|
Following LeoCAD official parts update ((URL) here is an new version of my unofficial parts pack. It contains all LDraw unofficial parts available as of February 4, 2010. (URL) (15 years ago, 4-Feb-10, to lugnet.announce, lugnet.cad.leocad)
|
| |
| | Re: LEGO's Internal colour palette
|
|
For those capable of updating LDConfig, please add/change these LEGO colors to these existing colors: (...) No match. The correct color to match to already has an entry, that may also be correct in some capacity. Someone will need to go through all (...) (15 years ago, 3-Feb-10, to lugnet.cad)
|
| |
| | Re: Lego City Policeman and LdrDat2Dxf utility
|
|
(...) Interesting, I somehow missed the announcement of this tool. Did you try Rolf's Lugnet email address? (see (URL) the homepage is still available through Google cache: (URL) (15 years ago, 1-Feb-10, to lugnet.cad)
|
| |
| | Re: LEGO's Internal colour palette
|
|
--snip-- (...) Yeah that would be me speculating on things I haven't read properly... Please ignore. Tim (15 years ago, 1-Feb-10, to lugnet.cad)
|
| |
| | Lego City Policeman and LdrDat2Dxf utility
|
|
Hi everyone, I've started putting a website together with Lego models in various formats. My latest addition is a Lego Policeman. See following link for details: (URL) tried to provide a number of different model format downloads including 3ds, obj, (...) (15 years ago, 31-Jan-10, to lugnet.cad)
|
| |
| | Re: What's going on with 59443.dat?
|
|
(...) Yes, Philo is right. We try to release modifications/improvements to related official parts in the same parts update. That is one reason why some Certfied files get left on the Parts Tracker at each update. Chris (15 years ago, 31-Jan-10, to lugnet.cad, FTX)
|
| |
| | Re: Dungeon Delver: That Frog...
|
|
(...) (full story of its birth: (URL) (15 years ago, 31-Jan-10, to lugnet.cad)
|
| |
| | Re: LEGO's Internal colour palette
|
|
(...) If you can get Peeron/LDraw and Bricklink to agree on all color names, even if they don't match the official names, you win a freaking prize. (...) Yeah...it's hard enough for most people to keep track of a lot of the more common colors as it (...) (15 years ago, 31-Jan-10, to lugnet.cad)
|
| |
| | Re: LEGO's Internal colour palette
|
|
(...) Makes sense. That did look like it was a fairly new color, though the first instance I can recall of that color was the natives from the Indiana Jones graveyard set (the one with the new motorcycle fairing) (...) The what now? Which sets would (...) (15 years ago, 31-Jan-10, to lugnet.cad)
|
| |
| | Dungeon Delver: That Frog...
|
|
Well, I've been working with MLCad and LDView for a few weeks now. Back to it from years back... Spent some time today to buld this little scene. Used MLCad to build it, LDView to catch the snapshot, and Paint Shop Pro to resize and add a little (...) (15 years ago, 31-Jan-10, to lugnet.cad, lugnet.castle)
|
| |
| | Re: LEGO's Internal colour palette
|
|
(...) That's why I went no farther than with the pinks/purples. (...) (snippage) I see 2 possible solutions to this whole mess: 1. Poll/talk with everyone until names we can all agree on are found. 2. Drop names altogether and refer to colors (...) (15 years ago, 31-Jan-10, to lugnet.cad)
|
| |
| | Re: LEGO's Internal colour palette
|
|
(...) Don't burn out your brain trying to figure out how they came up with the official color names. All that is required is to understand that there's some _serious_ disparity between their names and ours. For instance: They call it Brick Yellow. (...) (15 years ago, 30-Jan-10, to lugnet.cad)
|
| |
| | Re: LEGO's Internal colour palette
|
|
(...) I wonder why that color is called Bright Purple? On Bricklink and elsewhere, it's called Dark Pink. It don't look purple at all. What's the diff between pink and purple? Pink = Red + White. Purple = Red + Blue. The pinks and purples seems to (...) (15 years ago, 30-Jan-10, to lugnet.cad)
|
| |
| | Re: What's going on with 59443.dat?
|
|
(...) Yes, they are and remain official. The new version of angle connectors will hopefully become official at the same time as (unofficial) part 59443, keeping coherency in the library. But indeed as you need to use unofficial 59443 the way to go (...) (15 years ago, 30-Jan-10, to lugnet.cad, FTX)
|
| |
| | Re: What's going on with 59443.dat?
|
|
(...) Does this mean that the other angle connectors are no longer official parts and I need unofficial copies? (15 years ago, 30-Jan-10, to lugnet.cad, FTX)
|
| |
| | Re: LEGO's Internal colour palette
|
|
(...) Pretty sure that medium nougat is the middle-eastern skintone from Indiana Jones sets. Bright purple is probably the purple they've settled on to minimise the colour issues (in quite a few sets this year). Tim (15 years ago, 30-Jan-10, to lugnet.cad)
|
| |
| | Re: What's going on with 59443.dat?
|
|
Hi Eric, (...) I have recently updated angle connectors to add the engraved identification number. Doing so I also improved the shape to more closely match real parts. After that I updated 59443 to match the new angle connectors shape. You should (...) (15 years ago, 29-Jan-10, to lugnet.cad, FTX)
|
| |
| | Re: LEGO's Internal colour palette
|
|
(...) Phosphorous Green is Glow-in-the-Dark. It's already noted in the Peeron color chart (far right column for 50 Phosphorous White), but there are at least two distinct GitD colors (noted as opaque and translucent in Bricklink), and I couldn't (...) (15 years ago, 29-Jan-10, to lugnet.cad)
|
| |
| | What's going on with 59443.dat?
|
|
What's going on with 59443.dat? This is the Technic inline axle joiner, the one which has NO circumferential ridges to fit with the drive ring but instead is smooth to match with the other angle connectors. There used to be two different versions of (...) (15 years ago, 29-Jan-10, to lugnet.cad, FTX)
|
| |
| | Re: LEGO's Internal colour palette
|
|
Comparing this list to the LDConfig on my machine, there are three new colors: 221 Bright Purple 294 Phosphorous Green 312 Medium Nougat Unless anyone else volunteers, I'll take some time next week to match them to the BrickLink colors. Scott (15 years ago, 29-Jan-10, to lugnet.cad)
|
| |
| | Re: LEGO's Internal colour palette
|
|
(...) Yeah the full list is much huger. This is just the ones available at present but it gives an idea of eg. the best colours to focus on for renders and potentially other forms of restriction. Tim (15 years ago, 29-Jan-10, to lugnet.cad)
|
| |
| | Re: LEGO's Internal colour palette
|
|
Thanks for the heads up Tim. Looks like that is a list of the colors that are currently in production; as it is almost 100 colors short of the complete historical list. Also, they seem to match closest to the colors found in the instruction manuals (...) (15 years ago, 29-Jan-10, to lugnet.cad)
|
| |
| | LEGO's Internal colour palette
|
|
Hi guys, Not sure if this is really that interesting but I figured I should give a heads up to .cad. TLG have released their internal colour pallette (URL) Good luck finding something to do with it ;) Tim (15 years ago, 28-Jan-10, to lugnet.cad, FTX)
|
| |
| | Re: Instead of ~Moved to
|
|
In lugnet.cad, Allen Smith wrote: <SNIP> (...) Depending on their viewpoint and experience with LDraw, different users might argue that either inclusion OR exlclusion can be confusing. By including both in the library and providing a way to identify (...) (15 years ago, 25-Jan-10, to lugnet.cad, FTX)
|
| |
| | Re: Problem when rendering custom colors
|
|
(...) I tried to add my custom colors to the lg_color.inc file. It works now This is how my lg_color.inc looks: ___...___ // 0 #declare lg_black = texture { pigment { rgb <33/255, 33/255, 33/255> } finish { lg_solid_finish } } // 1 #declare lg_blue (...) (15 years ago, 23-Jan-10, to lugnet.cad)
|
| |
| | Re: Problem when rendering custom colors
|
|
(...) It looks to me like a texture issue rather than the color itself. I would recommend adding your color directly to the lg_color.inc file. Copy the definition for the existing blue and change nothing but the RGB color values for the pigment. (...) (15 years ago, 22-Jan-10, to lugnet.cad, FTX)
|
| |
| | Re: Problem when rendering custom colors
|
|
(...) SNIP (...) I am not very familar with POV-Ray. But could it be that the color 162 is not completely described or that is uses the slope surface here? The problem occur only at that place at the object where the light direct reflect. So I (...) (15 years ago, 22-Jan-10, to lugnet.cad)
|
| |
| | Re: Problem when rendering custom colors [DAT]
|
|
(...) Hello Eric, to further explain my problem Ive rendered a scene. (URL) left part of the fig uses the normal blue (color 1). Teh right part uses my personal color 162 (a darker blue) As you can see, the color 2 part of the torso front looks (...) (15 years ago, 22-Jan-10, to lugnet.cad)
|
| |
| | Re: Problem when rendering custom colors
|
|
(...) It's pretty hard to say what is happening without seeing your files. I need to see the portions of the POV-Ray file which define colors, or the include files which show colors. You could also post an example *.ldr file. Eric Albrecht (15 years ago, 22-Jan-10, to lugnet.cad)
|
| |
| | Problem when rendering custom colors
|
|
Hello, Im new to LUGNET. Although I use LDRAW yet for some years, I recently got interested ib creating and using custom parts (especially minifig torsos). I've created some easy to use template so I can create custom minifig torsos via bmp2ldraw32. (...) (15 years ago, 22-Jan-10, to lugnet.cad)
|
| |
| | Re: Instead of ~Moved to
|
|
In lugnet.cad, Chris Dee wrote: snip (...) The zip archive's chief virtue is not its familiarity, but its cross-platform portability. It's very important to maintain that. (...) I fixed that Bricksmith bug about a year and a half ago, so you don't (...) (15 years ago, 22-Jan-10, to lugnet.cad, FTX)
|
| |
| | Re: LDraw Names for Monorail Parts
|
|
(...) It makes more sense for "Monorail" to be a valid CATEGORY than some of the existing ones, so I added it a while ago. The definitive list is at (URL) Chris (15 years ago, 21-Jan-10, to lugnet.cad.dev, lugnet.trains)
|
| |
| | Re: Instead of ~Moved to
|
|
(...) I think there is some part of your equation that we don't realize/understand? I can view all my LDRAW models without any updating, thanks to the "moved to" concept. The models doesn't become obsolete even though the part numbers are updated. (...) (15 years ago, 20-Jan-10, to lugnet.cad)
|
| |
| | Re: Instead of ~Moved to
|
|
(...) I was going to start my response with "I don't understand", but Orion beat me to it. It is absolutely not necessary to update existing models with the replacement file referred to by the "~Moved to" file, but maybe I am missing something about (...) (15 years ago, 20-Jan-10, to lugnet.cad)
|
| |
| | Re: Instead of ~Moved to
|
|
(...) You should take heart from the fact that this phenomenon has slowed a GREAT deal in recent times, the number of possible renumbers is way way down, and number accuracy is way up. TLG doesn't tend to switch from solid to hollow studs anymore, (...) (15 years ago, 20-Jan-10, to lugnet.cad)
|
| |
| | Re: Instead of ~Moved to
|
|
(...) Hmmm, subparts are used by many parts so I can see how they might be referenced a gazillion times by an extremely large model file like Datsville. (...) What tool makes the movedto.log file that's giving you such trouble? Can it be adjusted to (...) (15 years ago, 20-Jan-10, to lugnet.cad)
|
| |
| | Re: Instead of ~Moved to
|
|
(...) I don't understand what you're saying here, Tore. The ~Moved To files prevent the need to update already existing files by providing a back reference to the old part number. This prevents a part from disappearing from a model simply because (...) (15 years ago, 20-Jan-10, to lugnet.cad)
|
| |
| | Re: Instead of ~Moved to
|
|
(...) Yes, I know my suggested approach has its obvious downsides. But the current system really makes me Yike!, too. When do we reach the point where the downsides of the current system overturn the advantages? I think we've already passed that (...) (15 years ago, 20-Jan-10, to lugnet.cad)
|
| |
| | Re: Instead of ~Moved to
|
|
(...) <snip> (...) (the "fake" number 111 sticks around, and the official design number 2222 points to it) Yikes! So you want everyone stuck with 111 for all eternity? With the current system, I'm free to remove 111.dat if I don't want it, and end (...) (15 years ago, 20-Jan-10, to lugnet.cad)
|
| |
| | Re: Instead of ~Moved to
|
|
(...) <SNIP> (...) The problem is that it doesn't. As I pointed out in my latest post, (URL) , almost every single existing LDraw model file ever made needs to be updated with every parts update realeasd. That has absolutely nothing to do with true (...) (15 years ago, 20-Jan-10, to lugnet.cad)
|
| |
| | Re: Instead of ~Moved to
|
|
(...) For some reason, those 18 "moved to" files in parts\s make a lot of noise for me. I know they shouldn't but they do and I haven't figured out the reason yet. There is another problem. It is kind of subtile, so I don't know if I'm able to (...) (15 years ago, 20-Jan-10, to lugnet.cad)
|
| |
| | Re: Instead of ~Moved to
|
|
(...) Advanced folks could have MovedTo directory and move all the "0 ~Moved To" files there. You can then add MovedTo to MLCad.ini to tell it about the MovedTo directory. You keep the MovedTo files (if you want), MLCad's auto update, and yet not (...) (15 years ago, 19-Jan-10, to lugnet.cad)
|
| |
| | Re: LDDP version 2.1 beta test
|
|
(...) I have not tested version 2.1 yet, but in version 2.0 you could disable polling in the extra menu. Or enable to poll on demand. cu mikeheide (15 years ago, 19-Jan-10, to lugnet.cad)
|
| |
| | Re: Instead of ~Moved to
|
|
(...) Yes, another method will break MLCad's update mechanism. I also like that. But maybe also another solution will work that way, but it has to be implemented. On the other side if we use the proposed way you also will have the latest geometrie (...) (15 years ago, 19-Jan-10, to lugnet.cad)
|
| |
| | Re: Instead of ~Moved to
|
|
Tore, I'm not really seeing the problem in the parts\s directory - there are 18 "moved to" files there. My parts directory has 456 "moved to" files, but there's not really any way around having those -- they serve two purposes: a) provide backwards (...) (15 years ago, 19-Jan-10, to lugnet.cad)
|
| |
| | Re: Instead of ~Moved to
|
|
(...) I'm not much of an expert in this area, but that never stops me from shooting my mouth off! On unix (e.g. Mac), it would be easy enough to use grep/find to find the files that contain "0 ~Moved to" and simply remove them. Cygwin on Windows (...) (15 years ago, 19-Jan-10, to lugnet.cad)
|
| |
| | Re: LDDP version 2.1 beta test
|
|
In lugnet.cad, Philippe Hurbain wrote: SNIP (...) indeed! Also I'd appreciate an option to turn polling off globally and completely would be great. I'm getting sick of getting greeted by tens of Confirm boxes each time I save my part in MLCad and (...) (15 years ago, 19-Jan-10, to lugnet.cad)
|
| |
| | Re: Instead of ~Moved to
|
|
I also agree that the current system is...extravagant. 'litter files' also seems like an appropriate term for the thousands of unnecessary files that clutter my LDraw library. Personnally, I'd like my library to only have actual parts; no ~Moved to (...) (15 years ago, 19-Jan-10, to lugnet.cad)
|
| |
| | Re: LDDP version 2.1 beta test
|
|
Hi Orion, (...) Works fine. (...) Works fine too on everything I tested. (...) OK, indeed inlining works (perhaps I goofed last time). (...) It is. Other things I noticed: - After starting this new version my preferences were again cleared - It (...) (15 years ago, 19-Jan-10, to lugnet.cad)
|
| |
| | Re: Instead of ~Moved to
|
|
(...) SNIP (...) I agree with you! I have to think about the way we have to go with this new approach for the many possible reasons of changing things, but at first look it could be a nice way to minimize admin edit work. Maybe we will have both (...) (15 years ago, 19-Jan-10, to lugnet.cad)
|
| |
| | Instead of ~Moved to [DAT]
|
|
To me, all these "~Moved to" files are just trouble and extra work and lots of extra files in the Parts, Parts\S, and P folders. And for each parts update, the extra work and problems seem to increase exponentially. I know, one can say some of the (...) (15 years ago, 19-Jan-10, to lugnet.cad)
|
| |
| | Re: Minifig Extractor/Manipulator?
|
|
(...) I agree but we still need to standardize where the LDraw.ini will be for each OS. This location has to read/write accessible. My suggestions for the OSs I use are: Windows: $APPDATA\LDraw OSX: $HOME/Library/LDraw -Orion (15 years ago, 18-Jan-10, to lugnet.cad)
|
| |
| | Re: Minifig Extractor/Manipulator?
|
|
(...) Of course: LDraw.ini could host such information in a new section! No risk to violate any existing standard, no need to create yet another file to look for! /Tore (15 years ago, 18-Jan-10, to lugnet.cad)
|
| |
| | LDraw.org Facebook fan page.
|
|
Hi all, With the blessing of the SteerCo, I've created a Fan Page for LDraw.org (URL) (15 years ago, 17-Jan-10, to lugnet.cad, lugnet.cad.dev.org.ldraw)
|
| |
| | Motorized Helicopter
|
|
(URL) Hi folks Last fall we had the swine flu outbreak - it spread here too, of course, and I fell ill too. While my symptoms remained vague, I was in bed for a week. And one week in bed tends to be kind of boring. So I took my brick boxes onto a (...) (15 years ago, 17-Jan-10, to lugnet.technic, lugnet.cad, FTX)
|
| |
| | Re: LDDP version 2.1 beta test
|
|
(...) These are fixed (...) This should work now. Please test on various items (...) Inlining works. Name completion still needs to be re-implemented. (...) This should be fixed. Thanks Philo, keep the bug reports coming. I'm hoping to work out the (...) (15 years ago, 17-Jan-10, to lugnet.cad)
|
| |
| | Re: POV dat for L3P v1.4 - 3626bpse - Minifig Head with SW Scout Trooper Black Visor Pattern - POV
|
|
(...) Sorry for the late answer. L3P v1.4 has L3Version declared, v1.3 has not. #ifdef (L3Version) material { L3Color0 } #else #if (version >= 3.1) material #else texture #end { Color0 } #end (L3P v1.4 does not support PovRay < 3.1) For the studs I (...) (15 years ago, 14-Jan-10, to lugnet.cad.ray, lugnet.cad.dat.parts)
|
| |
| | Re: MPD - add all subfiles as submodels
|
|
(...) Ah, great! I looked at MPDwizard but that trick did not occur to me. Thanks, Philo. Jim (15 years ago, 14-Jan-10, to lugnet.cad)
|
| |
| | Re: MPD - add all subfiles as submodels
|
|
(...) Yes, MPDwizard ((URL) does that fine. The trick is to select your LDraw folder as "unofficial parts" folder, select any empty directory as official parts folder and check "choose unofficial parts over official parts". Everything is recursively (...) (15 years ago, 14-Jan-10, to lugnet.cad)
|
| |
| | MPD - add all subfiles as submodels
|
|
Has anyone written a tool that can append all linetype 1 sub-file references as MPD submodels? Similar to how we sometimes include unofficial parts in the MPD, except recursively adding all needed parts and sub-parts from library. If not, I may hack (...) (15 years ago, 14-Jan-10, to lugnet.cad)
|
| |
| | Re: LDraw Parts of HiTechnic Sensors and Multiplexers now available
|
|
Thank You Philo! ...and Gus for posting. Littlehorn (15 years ago, 14-Jan-10, to lugnet.cad, lugnet.robotics, FTX)
|
| |
| | Re: Simple LDraw viewer code for Processing.org
|
|
(...) On my XP with already installed (and current) Java I did not have to download anything more. cu mikeheide (15 years ago, 13-Jan-10, to lugnet.cad)
|
| |
| | Re: Simple LDraw viewer code for Processing.org
|
|
(...) Yep, I tested it in Safari and Firefox on my Mac and in Firefox on XP before posting it. I already had Java in both cases, but if I understand correctly it does prompt you to download the plugin if you need it, right? Jim (15 years ago, 13-Jan-10, to lugnet.cad)
|
| |
| | Re: Simple LDraw viewer code for Processing.org
|
|
(...) download and upgrade the Java plugin. Will one be able to display this in another browser Chrome or on another platform like MacOS? (...) Me too. This looks very exciting! Jaco (15 years ago, 13-Jan-10, to lugnet.cad)
|
| |
| | LDraw Parts of HiTechnic Sensors and Multiplexers now available
|
|
A couple of months ago I worked with Philo on creating a complete set of LDraw parts for the HiTechnic sensors and multiplexers. These are now available for download from the HiTechnic downloads page. Look near the bottom of (URL). This LDraw parts (...) (15 years ago, 13-Jan-10, to lugnet.cad, lugnet.robotics, FTX) !
|
| |
| | Re: Datsville Link
|
|
(...) No problem. Sorry it took so long for me to catch a clue that it needed to be changed. (15 years ago, 13-Jan-10, to lugnet.cad)
|
| |
| | Re: Datsville Link
|
|
(...) Thanks, Steve! :) /Tore (15 years ago, 13-Jan-10, to lugnet.cad)
|
| |
| | Re: Datsville Link
|
|
(...) OK. (15 years ago, 13-Jan-10, to lugnet.cad)
|
| |
| | Re: Datsville Link
|
|
(...) Meanwhile, we could replace that dead link with some note saying "Waiting for a new site" or something like that. /Tore (15 years ago, 12-Jan-10, to lugnet.cad)
|
| |
| | Log Cabin! (Was: GallaghersArt.com Forums now open)
|
|
(...) Datsville! /Tore (15 years ago, 12-Jan-10, to lugnet.mediawatch, lugnet.cad)
|
| |
| | GallaghersArt.com Forums now open
|
|
I just made my own forums live over the weekend. The main purpose at this time is to allow me to release some of the LDraw files that go with some of my MOC’s, enable more info to be posted without creating more pages and bogging down my main site, (...) (15 years ago, 12-Jan-10, to lugnet.announce, lugnet.cad, FTX)
|
| |
| | Re: Simple LDraw viewer code for Processing.org
|
|
(...) That is the key question. I have not tried a larger model yet (it takes some preparation first to inline the model). I think I first may try to address the question of how to efficiently enable part library access for the embedded viewer. (...) (15 years ago, 12-Jan-10, to lugnet.cad)
|
| |
| | Re: Simple LDraw viewer code for Processing.org
|
|
(...) Incidentally, Processing does have an OpenGL renderer (JOGL), although I haven't done any sort of testing to see how significant the performance benefit is. I used the software renderer for the web viewer I posted just because the support (...) (15 years ago, 12-Jan-10, to lugnet.cad)
|
| |
| | Re: Simple LDraw viewer code for Processing.org
|
|
(...) I tried to write a viewer once too (as a series of experimentation of maybe having done a CAD program for parts authors!) using Tcl and OpenGL, but it turned out to be *REALLY* slow, most probably due to bad subfile handling. While the Animal (...) (15 years ago, 12-Jan-10, to lugnet.cad)
|
| |
| | Re: SR 3D Builder 0.4.5.7 RELEASED
|
|
(...) Please let me know your graphic adapter model and I'll let you know if it can work... better via email since this can bore other users... (...) Please note that ONLY SOME ATI card have problems. So long I get errors with ATI 1300, 1400 and (...) (15 years ago, 12-Jan-10, to lugnet.cad)
|
| |
| | Re: Simple LDraw viewer code for Processing.org
|
|
(...) Here it looks very promising. But what will be the loading time if I have larger models? I would be very interested in this kind of app as it will make things much more easy to display models to the webside visitor (see my "personal OMR" at (...) (15 years ago, 12-Jan-10, to lugnet.cad)
|
| |
| | Re: Simple LDraw viewer code for Processing.org
|
|
(...) That looks very good. I have also made an attempt to build a viewer, but it is also very limited in what it can do (very little files if you do not wait an hour, no optional lines, but it could read subfiles). As I discovered that it is quite (...) (15 years ago, 12-Jan-10, to lugnet.cad)
|
| |
| | Re: Minifig Extractor/Manipulator?
|
|
(...) Here is what I have found out about that META commands: 0 ROTATION CENTER 0 0 0 1 "Custom1" 0 ROTATION CENTER 2 3 4 1 "New Custom" The first three numbers are the xyz values of the rotation point The fourth number indicates the "Allow (...) (15 years ago, 12-Jan-10, to lugnet.cad)
|
| |
| | Re: Simple LDraw viewer code for Processing.org
|
|
(...) The neat thing about Processing is that since it is based on Java it is possible to export Processing programs (excluding some functions) as cross-platform applets that can be embedded in web pages. So, what Andy has created is the basis for (...) (15 years ago, 12-Jan-10, to lugnet.cad)
|
| |
| | Re: Minifig Extractor/Manipulator?
|
|
(...) Me too. I would prefer if we could set a standard within existing META-command sets, but I doubt that it may meet our requirements. Btw, what are our requirements? What do we want achieve? I could think of: 1. Standard tags that indicate... (...) (15 years ago, 12-Jan-10, to lugnet.cad)
|
| |
| | Re: LDDP version 2.1 beta test
|
|
(...) Oops, sorry. I only use the dev vesion of LDDP and neglected to consider this. I'll prevent it from happening in future updates. -Orion (15 years ago, 12-Jan-10, to lugnet.cad)
|
| |
| | Re: Minifig Extractor/Manipulator?
|
|
(...) I support extending the language. Maybe not in the above form but in some form. I'd also love to see something like the MLCad.ini minifig entries standardized. It doesn't have to be officially supported, a de facto standard is still a (...) (15 years ago, 12-Jan-10, to lugnet.cad)
|
| |
| | Simple LDraw viewer code for Processing.org
|
|
Well, in the interests of sharing, as this community does so well, here's the basics of a simple LDraw viewer that I wrote in the Processing language about a year and a half ago. It is by no means complete, but it will display small models (if you (...) (15 years ago, 12-Jan-10, to lugnet.cad)
|
| |
| | Re: SR 3D Builder 0.4.5.7 RELEASED
|
|
(...) Thank you! Looking forward to your next release... :-) -Andy (15 years ago, 12-Jan-10, to lugnet.cad)
|
| |
| | Re: Minifig Extractor/Manipulator?
|
|
(...) So how about this time we do something universal? We've talked this up before at least once: (URL) wants to step forward and propose some generic META commands to at least identify a group of parts that belong to a single minifig? Can we adapt (...) (15 years ago, 11-Jan-10, to lugnet.cad)
|
| |
| | Re: Minifig Extractor/Manipulator?
|
|
(...) Of course the problem with this approach is that you have to learn Yet Another ApplicationTM to do what you want. (15 years ago, 11-Jan-10, to lugnet.cad)
|
| |
| | Re: Minifig manipulator?
|
|
(...) All I can say is WOW! (15 years ago, 11-Jan-10, to lugnet.cad)
|
| |
| | Re: SR 3D Builder 0.4.5.7 RELEASED
|
|
(...) from SR 3D history : "- Now graphics requirements are lower: you need a 1.1 vertex and pixel shader suppor to run application. In option dialog box you can now choose to disable antialiasing to get a 20-70% boost in graphics performance (me (...) (15 years ago, 11-Jan-10, to lugnet.cad)
|
