Technic and Fabuland figures don’t have an inventory… and that’s logical because
they can’t be unbuilt… but that means there’s no part for them in the catalogue
and that means Studio can’t have them in its palette because they are minifigures
and not parts.
And that’s uncool because they exist in LDraw
So… couln’t those figures be parts too? One-part minifigures.
Technic and Fabuland figures don’t have an inventory… and that’s logical because
they can’t be unbuilt… but that means there’s no part for them in the catalogue
and that means Studio can’t have them in its palette because they are minifigures
and not parts.
And that’s uncool because they exist in LDraw
So… couln’t those figures be parts too? One-part minifigures.
Not unless the database gets redesigned. Currently, minifigures are a special
entity in the catalog and everything really needs to be reworked to undo that.
If that ever happens, then those figures that came as a single unit (Technic,
Fabuland, Scala, Belville, DUPLO, etc.) would be able to be defined as a part
just like all other parts and "minifigure" entries would just be another
counterpart in the catalog added to inventories for figures that are composed
of other parts. But until that is the case, it makes no sense to define figures
in two separate places.
[…]
Not unless the database gets redesigned. Currently, minifigures are a special
entity in the catalog and everything really needs to be reworked to undo that.
If that ever happens, then those figures that came as a single unit (Technic,
Fabuland, Scala, Belville, DUPLO, etc.) would be able to be defined as a part
just like all other parts and "minifigure" entries would just be another
counterpart in the catalog added to inventories for figures that are composed
of other parts. But until that is the case, it makes no sense to define figures
in two separate places.
Thanks for the quick answer again
Ah, yes, the redesign, a.k.a. “l’arlésienne.”
Well, I would say it makes sense to have them in two places if it allows to use
the parts/figures in Studio
At the moment, the only solution is to import them as custom parts (worse, import
their subparts as custom parts if we want to be able to pose them), with no link
to the catalogue for Wanted Lists or inventory management
Technic and Fabuland figures don’t have an inventory… and that’s logical because
they can’t be unbuilt… but that means there’s no part for them in the catalogue
and that means Studio can’t have them in its palette because they are minifigures
and not parts.
And that’s uncool because they exist in LDraw
So… couln’t those figures be parts too? One-part minifigures.
I think it would easier to request a solution to the Studio team instead...
Technic and Fabuland figures don’t have an inventory… and that’s logical because
they can’t be unbuilt… but that means there’s no part for them in the catalogue
and that means Studio can’t have them in its palette because they are minifigures
and not parts.
And that’s uncool because they exist in LDraw
So… couln’t those figures be parts too? One-part minifigures.
I think it would easier to request a solution to the Studio team instead...
100% agree; it's not a BrickLink problem but a Studio one. They could manage
those figs.
So… couln’t those figures be parts too? One-part minifigures.
I think it would easier to request a solution to the Studio team instead...
But I did that too
100% agree; it's not a BrickLink problem but a Studio one. They could manage
those figs.
The problem is that Studio works on the principle that parts have IDs. No ID
= no colour availability, no price, no import/export.
You could say “use the minifigure ID,” but a minifigure isn’t a part. That would
mean Studio needs to make exceptions for these “not-really-parts” in its relations
with the catalogue.
That means exceptions in how Studio gets colours (oh, minifigures don’t have
colours…) and prices.
That means exceptions in how Studio handles Wanted Lists.
That means exceptions in how Studio imports inventories. Studio uses the full
inventory, the one where minifigures are “broken”; those minifigures have no
parts (or only a hat/helmet), therefore, at the moment, nothing is imported.
If Studio were to use the inventory with “unbroken” minifigures, it would break
the import of other minifigures.
Lots of exceptions here and there in the code, with risks of mishandling some
situations (not even talking about bugs).
The conclusion is that both solutions are complicated 😮💨
So… couln’t those figures be parts too? One-part minifigures.
I think it would easier to request a solution to the Studio team instead...
But I did that too
100% agree; it's not a BrickLink problem but a Studio one. They could manage
those figs.
The problem is that Studio works on the principle that parts have IDs. No ID
= no colour availability, no price, no import/export.
You could say “use the minifigure ID,” but a minifigure isn’t a part. That would
mean Studio needs to make exceptions for these “not-really-parts” in its relations
with the catalogue.
Or we could consider that the 12 / 86654856547 Studio projects using Technic,
Fabuland (I adore!) Figures we don't care if it's so complicated.
What many (and me) often do is to 'Photoshop' the instructions to add
what can't be represented
[…]
Or we could consider that the 12 / 86654856547 Studio projects using Technic,
Fabuland (I adore!) Figures we don't care if it's so complicated.
What many (and me) often do is to 'Photoshop' the instructions to add
what can't be represented
Well, if we go this way, then why not forgo Studio or any CAD altogether and
make our models with a text editor… or start raising butterflies (https://xkcd.com/378/
)?
[…]
Or we could consider that the 12 / 86654856547 Studio projects using Technic,
Fabuland (I adore!) Figures we don't care if it's so complicated.
What many (and me) often do is to 'Photoshop' the instructions to add
what can't be represented
Well, if we go this way, then why not forgo Studio or any CAD altogether and
make our models with a text editor… or start raising butterflies (https://xkcd.com/378/
)?
I know we should care of all problems, tiny or huge, but personally I've
more concerns with Studio crashing 80% of times when I close it, like for 1 year
approx
And I know it's not Studio forum.
[…]
I know we should care of all problems, tiny or huge, but personally I've
more concerns with Studio crashing 80% of times when I close it, like for 1 year
approx
1. That’s why I tried to move the burden to the catalogue side 😈
2. 80% is a lot :o
Though, in the November(?) release, there was a bug that made it 100% when
quitting from instructions, but it’s not reproducible anymore (at least for me
).
It’s weird that, for some people, Studio is slow and crashes, while for others
(me ) it’s rather smooth and stable.
And I know it's not Studio forum.
Yes, please, make a detailled report there, with your log files
[…]
I know we should care of all problems, tiny or huge, but personally I've
more concerns with Studio crashing 80% of times when I close it, like for 1 year
approx
1. That’s why I tried to move the burden to the catalogue side 😈
2. 80% is a lot :o
Though, in the November(?) release, there was a bug that made it 100% when
quitting from instructions, but it’s not reproducible anymore (at least for me
).
Yep it's probably this one. But not quitting from Instructions, but anywhere.
It’s weird that, for some people, Studio is slow and crashes, while for others
(me ) it’s rather smooth and stable.
It's super stable here never had any crash I can remember of. Except almost
100% on closing.
And I know it's not Studio forum.
Yes, please, make a detailled report there, with your log files
[…]
Just retried, can't tell if it crashes or not (I had one only).
So used to it... I don't remember since which update it doesn't crash
almost systematically when I quit, but it's very recent (like current one
or such). Going to be difficult.
[…]
Just retried, can't tell if it crashes or not (I had one only).
So used to it... I don't remember since which update it doesn't crash
almost systematically when I quit, but it's very recent (like current one
or such). Going to be difficult.
I blame Windows.
Go Linux! 🐧
It could be who I talk to in Forum also.
Still crashes, difficult to catch; I didn't account this but new PC is far
far faster, so the message appears for a tenth of second, in the other cases
I may simply not see it... See here barely got it, just right now.
France, Nouvelle-Aquitaine
)
USA, Ohio
Spain, Comunidad Valenciana
).
