Discussion Forum: Thread 354982

 Author: tprahm View Messages Posted By tprahm
 Posted: Mar 13, 2024 23:39
 Subject: Studio Error from Printed Brick Import (.ldr)
 Viewed: 54 times
 Topic: Related Software
Cancel Message
Cancel
Reply to Message
Reply
BrickLink
ID Card

tprahm (2)

Location:  USA, Nevada
Member Since Contact Type Status
Dec 5, 2023 Contact Member Seller
Buying Privileges - OKSelling Privileges - OK
Store Closed Store: Mosaibrick
When I import a .ldr file into BrickLink, all of the bricks are placed perfectly
sound, except for printed bricks. Even when the .dat item ID matches, in this
case (3069p02.dat), it still doesn't convert the file type to the actual
brick. Even if the brick exists in Bricklink, such as the 3069p02 piece, it won't
budge unless I manually change it. However, I also noticed that occasionally,
but not with this example, bricks such as 3068pb0191 will appear ONLY IF I change
the .dat file name from "3068pb0191" to "3068bpb0191". However,
I would like all of the bricks to be recognized in the Studio software. Any ideas?
And no, manual brick switches are not an option here.
 


 Author: Brickwilbo View Messages Posted By Brickwilbo
 Posted: Mar 14, 2024 02:39
 Subject: Re: Studio Error from Printed Brick Import (.ldr)
 Viewed: 19 times
 Topic: Related Software
Cancel Message
Cancel
Reply to Message
Reply
BrickLink
ID Card

Brickwilbo (1534)

Location:  Netherlands, Gelderland
Member Since Contact Type Status Collage
Oct 24, 2007 Contact Member Seller
Buying Privileges - OKSelling Privileges - OK
View Collage Pic
Store Closed Store: Brickwilbo Betuwe Bricks
BrickLink Discussions Moderator (?)
In Related Software, tprahm writes:
  When I import a .ldr file into BrickLink, all of the bricks are placed perfectly
sound, except for printed bricks. Even when the .dat item ID matches, in this
case (3069p02.dat), it still doesn't convert the file type to the actual
brick. Even if the brick exists in Bricklink, such as the 3069p02 piece, it won't
budge unless I manually change it. However, I also noticed that occasionally,
but not with this example, bricks such as 3068pb0191 will appear ONLY IF I change
the .dat file name from "3068pb0191" to "3068bpb0191". However,
I would like all of the bricks to be recognized in the Studio software. Any ideas?
And no, manual brick switches are not an option here.

The Stud.io related Forum is here: https://forum.bricklink.com/
Helppage: https://studiohelp.bricklink.com/hc/en-us
 Author: 1001bricks View Messages Posted By 1001bricks
 Posted: Mar 14, 2024 12:40
 Subject: Re: Studio Error from Printed Brick Import (.ldr)
 Viewed: 21 times
 Topic: Related Software
Cancel Message
Cancel
Reply to Message
Reply
BrickLink
ID Card

1001bricks (52267)

Location:  France, Provence-Alpes-Côte d'Azur
Member Since Contact Type Status
Sep 6, 2005 Contact Member Seller
Buying Privileges - OKSelling Privileges - OK
Store: 1001bricks
In Related Software, Brickwilbo writes:
  In Related Software, tprahm writes:
  When I import a .ldr file into BrickLink, all of the bricks are placed perfectly
sound, except for printed bricks. Even when the .dat item ID matches, in this
case (3069p02.dat), it still doesn't convert the file type to the actual
brick. Even if the brick exists in Bricklink, such as the 3069p02 piece, it won't
budge unless I manually change it. However, I also noticed that occasionally,
but not with this example, bricks such as 3068pb0191 will appear ONLY IF I change
the .dat file name from "3068pb0191" to "3068bpb0191". However,
I would like all of the bricks to be recognized in the Studio software. Any ideas?
And no, manual brick switches are not an option here.

The Stud.io related Forum is here: https://forum.bricklink.com/
Helppage: https://studiohelp.bricklink.com/hc/en-us

AH, and it's Studio dear, not anymore stud.io