LDraw.org Discussion Forums

Full Version: Generate LDCad parts bin custom list.
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2 3 4 5 6
Don't know if this has been posted before, but would it be nice to have a PBG repository too?
"though I have to add the ribbed hoses and tubes."

You can add templates to pbg's too. See for example the 8071.pbg in the sets folder:

-------

[options]
kind=basic
caption=Set 8071
description=Parts in the 8071 set
picture=8071.png
sortOn=description


<items>
path\rigid3mmHose.ldr:[sourceInv=templates] [color=0]
3623.dat:[color=0] [count=2]
2444.dat:[color=0] [count=4]
61409.dat:[color=0] [count=2]

-------


Ps: disabled bbcode as it messes with the [ ] properties.
See above Big Grin

Jetro de Château Wrote:On a related note, would it make sense to create a repository of .pbg files for sets?
In my opinion: no.

I mean, it's just a bunch of set inventories structured in such a way LDCad can use it. We don't have any repositories for .xml inventories, .bsx inventories or whatever other format because it's all the same; just another format with the same data.

With the right program, it's as easy as choosing a set and pressing a button to get a .pbg file. We don't need a repository for that imho.
I agree that a good export function from any inventory website would be much better! Remains the problem of matching database nomenclature between both systems (LDraw vs. inventory website)
That's true. Although Rebrickable (which I mentioned earlier) already has a pretty good Lego part # > LDraw part # database in place, including a lot of patterned parts. It's probably not complete and fully up to date (yet?), but it's a pretty good start nonetheless.
Merlijn Wissink Wrote:We don't have any repositories for .xml inventories, .bsx inventories or whatever other format because it's all the same; just another format with the same data.

With the right program, it's as easy as choosing a set and pressing a button to get a .pbg file. We don't need a repository for that imho.
If only Big Grin
There are XML repositories (like Bricklink and ReBrickable), but the conversion process is far from "easy".

Philippe Hurbain Wrote:I agree that a good export function from any inventory website would be much better! Remains the problem of matching database nomenclature between both systems (LDraw vs. inventory website)
And that's exactly my point. There are a lot of mismatches, but that's not the only ting.
Yesterday I tried to create a .pbg file for the 45544-a EV3 Core set and I ran into a number of more or less important issues:
  • I tried both Bricklink and ReBrickable. Bricklink turned out to have the most complete information - there were more gaps in the LDraw conversion list with ReBrickable than with Bricklink
  • A considerable number of elements do not have any mapping to their LDraw counterparts. For the most part conversion is straightforward and the Bricklink number can be used adding .dat. However, you need to check case by case since it doesn't always work and sometimes there are surprising mismatches. (e.g. the 25cm EV3 wire is BL ID bb601, LDraw ID 11145.dat
  • Colours information is not reliable either. All the EV3 electronics were referenced as black when they are white and rubber elements were simple black, wires were black, but LDCad knows they are black and requires trans to be set for the connectors...
  • Colour assignment in brickutils is incomplete as it doesn't allow for rubber colours and gave me an error with metallic (256 became -1)
  • Not every part is really a part:
    Roland Melkert Wrote:You can add templates to pbg's too
    This of course also requires tweaking the set. Many Technic sets would benefit from having templates included rather than a part reference to e.g. a Power Functions motor.
  • Ultimately, it would be really cool of LDCad included a feature that allowed for easy access to single set element sets. Not by manually modifying some files in the %appdata% directory, but through a menu in the interface. Imagine the option to load or add a set from a menu so the set is displayed under root/sets/<setnumber>. To make this accessible to the average user (not simply those of us who like to play around with progam settings and are not scared of digging into configuration files) easy access to correctly formatted part lists for specific sets woud be an important asset.
Jetro de Château Wrote:Ultimately, it would be really cool of LDCad included a feature that allowed for easy access to single set element sets. Not by manually modifying some files in the %appdata% directory, but through a menu in the interface. Imagine the option to load or add a set from a menu so the set is displayed under root/sets/<setnumber>. To make this accessible to the average user (not simply those of us who like to play around with progam settings and are not scared of digging into configuration files) easy access to correctly formatted part lists for specific sets woud be an important asset.
pbg gui editing is something I have in the pipeline, which should at least make it easier. I could also add a .pbg file drop handler which offers to copy the dropped file to e.g. the sets folder.
Found it, Roland! My PBG of set 8246 is now complete.
Building it in LDCad now took less then 25 minutes... :-)
Brickstock is usually helpful with that. However, it is not 100% perfect either and - even worse - the author does not communicate at all. I tried to contact him on Bricklink (he prefers that according to his own words) and e-mail and he did not reply me a word. Even I asked for such basic things like program sources. De facto, this is a GPL license violation...
Pages: 1 2 3 4 5 6