<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/">
	<channel>
		<title><![CDATA[LDraw.org Discussion Forums - Parts Tracker Discussion]]></title>
		<link>https://forums.ldraw.org/</link>
		<description><![CDATA[LDraw.org Discussion Forums - https://forums.ldraw.org]]></description>
		<pubDate>Tue, 21 Apr 2026 19:44:23 +0000</pubDate>
		<generator>MyBB</generator>
		<item>
			<title><![CDATA[2026-02 Update status]]></title>
			<link>https://forums.ldraw.org/thread-29408.html</link>
			<pubDate>Wed, 25 Feb 2026 18:31:47 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forums.ldraw.org/member.php?action=profile&uid=2">Orion Pobursky</a>]]></dc:creator>
			<guid isPermaLink="false">https://forums.ldraw.org/thread-29408.html</guid>
			<description><![CDATA[Just so no-one worries, I'm on vacation until 3/3 so the 2026-02 update will be about a week late.]]></description>
			<content:encoded><![CDATA[Just so no-one worries, I'm on vacation until 3/3 so the 2026-02 update will be about a week late.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Incorrect reference to Bricklink]]></title>
			<link>https://forums.ldraw.org/thread-29392.html</link>
			<pubDate>Mon, 16 Feb 2026 20:30:50 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forums.ldraw.org/member.php?action=profile&uid=5168">Manfred Schaefer</a>]]></dc:creator>
			<guid isPermaLink="false">https://forums.ldraw.org/thread-29392.html</guid>
			<description><![CDATA[Hello,<br />
<br />
For the upper body 76382p8h, either the reference to Bricklink is incorrect or the color of the hands is wrong. It is an official part.<br />
There are two versions on Bricklink.<br />
<br />
Version 973pb0320c01 with yellow hands:<br />
<a href="https://www.bricklink.com/v2/catalog/catalogitem.page?P=973pb0320c01&amp;name=Torso%20Train%20with%20Logo,%20Three%20Gold%20Buttons,%20Red%20Tie,%20Pencil%20&amp;%20Paper%20in%20Pocket%20Pattern%20/%20Dark%20Blue%20Arms%20/%20Yellow%20Hands&amp;category=%5BMinifigure,%20Torso%20Assembly,%20Decor.%5D#T=I" target="_blank" rel="noopener" class="mycode_url">https://www.bricklink.com/v2/catalog/cat...or.%5D#T=I</a><br />
<br />
and version 973pb0320c02 with light nougat hands:<br />
<a href="https://www.bricklink.com/v2/catalog/catalogitem.page?P=973pb0320c02&amp;name=Torso%20Train%20with%20Logo,%20Three%20Gold%20Buttons,%20Red%20Tie,%20Pencil%20&amp;%20Paper%20in%20Pocket%20Pattern%20/%20Dark%20Blue%20Arms%20/%20Light%20Nougat%20Hands&amp;category=%5BMinifigure,%20Torso%20Assembly,%20Decor.%5D#T=I" target="_blank" rel="noopener" class="mycode_url">https://www.bricklink.com/v2/catalog/cat...or.%5D#T=I</a><br />
<br />
If I were to upload both versions to the Parts Tracker, the reference would be incorrect again the next time it was released, as Rebrickable has an incorrect reference to Bricklink.<br />
For 973pb0320c01, Rebrickable cannot find a part in LDraw.<br />
For 973pb0320c02, Rebrickable refers to 76382p8h, but this part has yellow hands instead of light nougat hands.<br />
<br />
My suggestion would be to change the color of the hands on the official part to light nougat and create a second part with yellow hands.<br />
Then the references in the official part will be correct and the new part should hopefully be referenced correctly.<br />
<br />
Alternatively, I could upload another version with light nougat hands to the Parts Tracker and hope that the referencing works correctly.<br />
<br />
Best regards,<br />
<br />
Manfred]]></description>
			<content:encoded><![CDATA[Hello,<br />
<br />
For the upper body 76382p8h, either the reference to Bricklink is incorrect or the color of the hands is wrong. It is an official part.<br />
There are two versions on Bricklink.<br />
<br />
Version 973pb0320c01 with yellow hands:<br />
<a href="https://www.bricklink.com/v2/catalog/catalogitem.page?P=973pb0320c01&amp;name=Torso%20Train%20with%20Logo,%20Three%20Gold%20Buttons,%20Red%20Tie,%20Pencil%20&amp;%20Paper%20in%20Pocket%20Pattern%20/%20Dark%20Blue%20Arms%20/%20Yellow%20Hands&amp;category=%5BMinifigure,%20Torso%20Assembly,%20Decor.%5D#T=I" target="_blank" rel="noopener" class="mycode_url">https://www.bricklink.com/v2/catalog/cat...or.%5D#T=I</a><br />
<br />
and version 973pb0320c02 with light nougat hands:<br />
<a href="https://www.bricklink.com/v2/catalog/catalogitem.page?P=973pb0320c02&amp;name=Torso%20Train%20with%20Logo,%20Three%20Gold%20Buttons,%20Red%20Tie,%20Pencil%20&amp;%20Paper%20in%20Pocket%20Pattern%20/%20Dark%20Blue%20Arms%20/%20Light%20Nougat%20Hands&amp;category=%5BMinifigure,%20Torso%20Assembly,%20Decor.%5D#T=I" target="_blank" rel="noopener" class="mycode_url">https://www.bricklink.com/v2/catalog/cat...or.%5D#T=I</a><br />
<br />
If I were to upload both versions to the Parts Tracker, the reference would be incorrect again the next time it was released, as Rebrickable has an incorrect reference to Bricklink.<br />
For 973pb0320c01, Rebrickable cannot find a part in LDraw.<br />
For 973pb0320c02, Rebrickable refers to 76382p8h, but this part has yellow hands instead of light nougat hands.<br />
<br />
My suggestion would be to change the color of the hands on the official part to light nougat and create a second part with yellow hands.<br />
Then the references in the official part will be correct and the new part should hopefully be referenced correctly.<br />
<br />
Alternatively, I could upload another version with light nougat hands to the Parts Tracker and hope that the referencing works correctly.<br />
<br />
Best regards,<br />
<br />
Manfred]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Official part 4719 : part variation problem ?]]></title>
			<link>https://forums.ldraw.org/thread-29352.html</link>
			<pubDate>Sun, 25 Jan 2026 15:16:59 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forums.ldraw.org/member.php?action=profile&uid=2236">Bertrand Lequy</a>]]></dc:creator>
			<guid isPermaLink="false">https://forums.ldraw.org/thread-29352.html</guid>
			<description><![CDATA[Hello, I'm still sorting some things out with LDraw parts on RB and I have a question about the part <a href="https://library.ldraw.org/parts/9400" target="_blank" rel="noopener" class="mycode_url">4719</a>.<br />
<br />
apparently two mold variations exist with three different ways of naming them according to RB.<br />
<br />
- the 80's version, with a normal stud over the rear wheel and a normal hollowed stud over the front wheel named 4719 :<br />
<img src="https://rebrickable.com/media/parts/photos/4/4719-4-af7cb56f-d1bd-4d1c-8441-49ad88ca7cf0.jpg" loading="lazy"  width="250" height="250" alt="[Image: 4719-4-af7cb56f-d1bd-4d1c-8441-49ad88ca7cf0.jpg]" class="mycode_img" /><br />
- the actual version, with a hollowed over the rear wheel and a reinforced hollowed stud over the front wheel named 4719 or 65574 :<br />
<img src="https://rebrickable.com/media/parts/photos/4/65574-4-b7a268dc-edf9-4432-b109-0659317ea52c.jpg" loading="lazy"  width="250" height="250" alt="[Image: 65574-4-b7a268dc-edf9-4432-b109-0659317ea52c.jpg]" class="mycode_img" /><br />
The problem is that the part on the part tracker seems to be a mix of both mold.<br />
<br />
Should we fix it, and how ?<br />
- do nothing ?<br />
- 4719 for the old one and 65574 for the new one ?<br />
- 4719 for the old one and 4719a for the new one ?<br />
- 4719 for the new one and 4719a for the old one ?<br />
- something else ?<br />
<br />
Thank you.]]></description>
			<content:encoded><![CDATA[Hello, I'm still sorting some things out with LDraw parts on RB and I have a question about the part <a href="https://library.ldraw.org/parts/9400" target="_blank" rel="noopener" class="mycode_url">4719</a>.<br />
<br />
apparently two mold variations exist with three different ways of naming them according to RB.<br />
<br />
- the 80's version, with a normal stud over the rear wheel and a normal hollowed stud over the front wheel named 4719 :<br />
<img src="https://rebrickable.com/media/parts/photos/4/4719-4-af7cb56f-d1bd-4d1c-8441-49ad88ca7cf0.jpg" loading="lazy"  width="250" height="250" alt="[Image: 4719-4-af7cb56f-d1bd-4d1c-8441-49ad88ca7cf0.jpg]" class="mycode_img" /><br />
- the actual version, with a hollowed over the rear wheel and a reinforced hollowed stud over the front wheel named 4719 or 65574 :<br />
<img src="https://rebrickable.com/media/parts/photos/4/65574-4-b7a268dc-edf9-4432-b109-0659317ea52c.jpg" loading="lazy"  width="250" height="250" alt="[Image: 65574-4-b7a268dc-edf9-4432-b109-0659317ea52c.jpg]" class="mycode_img" /><br />
The problem is that the part on the part tracker seems to be a mix of both mold.<br />
<br />
Should we fix it, and how ?<br />
- do nothing ?<br />
- 4719 for the old one and 65574 for the new one ?<br />
- 4719 for the old one and 4719a for the new one ?<br />
- 4719 for the new one and 4719a for the old one ?<br />
- something else ?<br />
<br />
Thank you.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[[issue ?] A part is not showing in the search result (u9090).]]></title>
			<link>https://forums.ldraw.org/thread-29317.html</link>
			<pubDate>Sat, 17 Jan 2026 14:39:49 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forums.ldraw.org/member.php?action=profile&uid=2236">Bertrand Lequy</a>]]></dc:creator>
			<guid isPermaLink="false">https://forums.ldraw.org/thread-29317.html</guid>
			<description><![CDATA[Hi.<br />
<br />
I was updating a part on RB : <a href="https://rebrickable.com/parts/6954c01/torso-with-wings/" target="_blank" rel="noopener" class="mycode_url">https://rebrickable.com/parts/6954c01/torso-with-wings/</a><br />
I clicked on the LDraw link : <a href="https://library.ldraw.org/parts/list?tableSearch=u9090.dat" target="_blank" rel="noopener" class="mycode_url">https://library.ldraw.org/parts/list?tab...=u9090.dat</a><br />
And got no result. <br />
At first I thaught it was a problem with RB link generation script. <br />
So I searched for the part manualy.<br />
Same result : nothing (RB url was correct).<br />
I checked in my LDraw folder and found the part.<br />
I tried again : nothing.<br />
I tried to search for the wing subpart manualy by typing 6954, the part didn't showed up.<br />
I finaly found it by using the official parent page for minifig tors (973) (<a href="https://library.ldraw.org/parts/14192?official-parentsPage=2" target="_blank" rel="noopener" class="mycode_url">https://library.ldraw.org/parts/14192?of...entsPage=2</a>)<br />
<br />
I know it's not a very common and used part, but I wonder if it's a normal behavior.]]></description>
			<content:encoded><![CDATA[Hi.<br />
<br />
I was updating a part on RB : <a href="https://rebrickable.com/parts/6954c01/torso-with-wings/" target="_blank" rel="noopener" class="mycode_url">https://rebrickable.com/parts/6954c01/torso-with-wings/</a><br />
I clicked on the LDraw link : <a href="https://library.ldraw.org/parts/list?tableSearch=u9090.dat" target="_blank" rel="noopener" class="mycode_url">https://library.ldraw.org/parts/list?tab...=u9090.dat</a><br />
And got no result. <br />
At first I thaught it was a problem with RB link generation script. <br />
So I searched for the part manualy.<br />
Same result : nothing (RB url was correct).<br />
I checked in my LDraw folder and found the part.<br />
I tried again : nothing.<br />
I tried to search for the wing subpart manualy by typing 6954, the part didn't showed up.<br />
I finaly found it by using the official parent page for minifig tors (973) (<a href="https://library.ldraw.org/parts/14192?official-parentsPage=2" target="_blank" rel="noopener" class="mycode_url">https://library.ldraw.org/parts/14192?of...entsPage=2</a>)<br />
<br />
I know it's not a very common and used part, but I wonder if it's a normal behavior.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[New author Viktor Kovacs [kovacsv]]]></title>
			<link>https://forums.ldraw.org/thread-29306.html</link>
			<pubDate>Wed, 14 Jan 2026 17:38:08 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forums.ldraw.org/member.php?action=profile&uid=2">Orion Pobursky</a>]]></dc:creator>
			<guid isPermaLink="false">https://forums.ldraw.org/thread-29306.html</guid>
			<description><![CDATA[Please join me in welcoming our newest parts author Viktor Kovacs [kovacsv].  <br />
<br />
Please support them as they begin their LDraw author journey.]]></description>
			<content:encoded><![CDATA[Please join me in welcoming our newest parts author Viktor Kovacs [kovacsv].  <br />
<br />
Please support them as they begin their LDraw author journey.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Official File parts/2654bps1.dat : color issue]]></title>
			<link>https://forums.ldraw.org/thread-29264.html</link>
			<pubDate>Fri, 02 Jan 2026 10:34:08 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forums.ldraw.org/member.php?action=profile&uid=2236">Bertrand Lequy</a>]]></dc:creator>
			<guid isPermaLink="false">https://forums.ldraw.org/thread-29264.html</guid>
			<description><![CDATA[Hello, I have to deal with this part on Rebrickable, and I have a problem.<br />
<br />
On BL and here, the part is called : [...]with <span style="font-weight: bold;" class="mycode_b">Dark Tan</span> Crescent Pattern, whereas its called [...]with <span style="font-weight: bold;" class="mycode_b">Reddish Brown</span> Crescent Print.<br />
<br />
At first I thaught there was 2 different parts, one tan and one brown and that I encountered a mapping issue. But this part seems to have been used in one set only. and the picture on BL show a reddish brow cressent and not a dark tan one, like the LEGO element render.<br />
<br />
<a href="https://rebrickable.com/parts/2654pr0003/plate-round-2-x-2-with-rounded-bottom-with-reddish-brown-crescent-print/" target="_blank" rel="noopener" class="mycode_url">https://rebrickable.com/parts/2654pr0003...ent-print/</a><br />
<a href="https://www.bricklink.com/v2/catalog/catalogitem.page?P=2654pb015" target="_blank" rel="noopener" class="mycode_url">https://www.bricklink.com/v2/catalog/cat...=2654pb015</a><br />
<a href="https://library.ldraw.org/parts/24301" target="_blank" rel="noopener" class="mycode_url">https://library.ldraw.org/parts/24301</a><br />
<br />
Is it because dark tan printed on black looks like reddish brown ? Or Is there an error somewhere ?]]></description>
			<content:encoded><![CDATA[Hello, I have to deal with this part on Rebrickable, and I have a problem.<br />
<br />
On BL and here, the part is called : [...]with <span style="font-weight: bold;" class="mycode_b">Dark Tan</span> Crescent Pattern, whereas its called [...]with <span style="font-weight: bold;" class="mycode_b">Reddish Brown</span> Crescent Print.<br />
<br />
At first I thaught there was 2 different parts, one tan and one brown and that I encountered a mapping issue. But this part seems to have been used in one set only. and the picture on BL show a reddish brow cressent and not a dark tan one, like the LEGO element render.<br />
<br />
<a href="https://rebrickable.com/parts/2654pr0003/plate-round-2-x-2-with-rounded-bottom-with-reddish-brown-crescent-print/" target="_blank" rel="noopener" class="mycode_url">https://rebrickable.com/parts/2654pr0003...ent-print/</a><br />
<a href="https://www.bricklink.com/v2/catalog/catalogitem.page?P=2654pb015" target="_blank" rel="noopener" class="mycode_url">https://www.bricklink.com/v2/catalog/cat...=2654pb015</a><br />
<a href="https://library.ldraw.org/parts/24301" target="_blank" rel="noopener" class="mycode_url">https://library.ldraw.org/parts/24301</a><br />
<br />
Is it because dark tan printed on black looks like reddish brown ? Or Is there an error somewhere ?]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Suggestion: for primitive reference please add links to actual primitives]]></title>
			<link>https://forums.ldraw.org/thread-29243.html</link>
			<pubDate>Mon, 22 Dec 2025 03:09:55 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forums.ldraw.org/member.php?action=profile&uid=670">Mark Kennedy</a>]]></dc:creator>
			<guid isPermaLink="false">https://forums.ldraw.org/thread-29243.html</guid>
			<description><![CDATA[For the primitive reference page at:<br />
<a href="https://wiki.ldraw.org/wiki/Primitives_Reference" target="_blank" rel="noopener" class="mycode_url">https://wiki.ldraw.org/wiki/Primitives_Reference</a><br />
I would suggest including links to the actual primitives on the tracker so people could view them in 3D.]]></description>
			<content:encoded><![CDATA[For the primitive reference page at:<br />
<a href="https://wiki.ldraw.org/wiki/Primitives_Reference" target="_blank" rel="noopener" class="mycode_url">https://wiki.ldraw.org/wiki/Primitives_Reference</a><br />
I would suggest including links to the actual primitives on the tracker so people could view them in 3D.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Parts Tracker Landing Page]]></title>
			<link>https://forums.ldraw.org/thread-29240.html</link>
			<pubDate>Fri, 19 Dec 2025 18:35:25 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forums.ldraw.org/member.php?action=profile&uid=2">Orion Pobursky</a>]]></dc:creator>
			<guid isPermaLink="false">https://forums.ldraw.org/thread-29240.html</guid>
			<description><![CDATA[<a href="https://library.ldraw.org/tracker" target="_blank" rel="noopener" class="mycode_url">https://library.ldraw.org/tracker</a><br />
<br />
The above is the current Parts Tracker landing page. <br />
<br />
Is this page actually useful? If not, how can it be improved or should we change the landing page to the Activity Log?]]></description>
			<content:encoded><![CDATA[<a href="https://library.ldraw.org/tracker" target="_blank" rel="noopener" class="mycode_url">https://library.ldraw.org/tracker</a><br />
<br />
The above is the current Parts Tracker landing page. <br />
<br />
Is this page actually useful? If not, how can it be improved or should we change the landing page to the Activity Log?]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Certain parts are returning error]]></title>
			<link>https://forums.ldraw.org/thread-29184.html</link>
			<pubDate>Sat, 22 Nov 2025 23:58:54 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forums.ldraw.org/member.php?action=profile&uid=2">Orion Pobursky</a>]]></dc:creator>
			<guid isPermaLink="false">https://forums.ldraw.org/thread-29184.html</guid>
			<description><![CDATA[FYI:<br />
<br />
The are a couple of sticker parts and shortcuts that are giving 500 errors. Since I'm currently on holiday, it may be that this error goes unfixed until next weekend.]]></description>
			<content:encoded><![CDATA[FYI:<br />
<br />
The are a couple of sticker parts and shortcuts that are giving 500 errors. Since I'm currently on holiday, it may be that this error goes unfixed until next weekend.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Mursten]]></title>
			<link>https://forums.ldraw.org/thread-29181.html</link>
			<pubDate>Fri, 21 Nov 2025 19:59:55 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forums.ldraw.org/member.php?action=profile&uid=30502">Peter Blomberg</a>]]></dc:creator>
			<guid isPermaLink="false">https://forums.ldraw.org/thread-29181.html</guid>
			<description><![CDATA[Does anyone know why there are so many Mursten brick fixes on the tracker?<br />
<br />
There are also many new Mursten parts waiting to be reviewed.<br />
<br />
When reviewing Mursten parts, are there any specifics that the reviewer needs to know? If I understand it correctly, the windows and doors have fins that go in the Mursten end slots. Are there any measurements on the slot size or the fin size that need to be checked? What about the total window height compared to a Mursten brick height?]]></description>
			<content:encoded><![CDATA[Does anyone know why there are so many Mursten brick fixes on the tracker?<br />
<br />
There are also many new Mursten parts waiting to be reviewed.<br />
<br />
When reviewing Mursten parts, are there any specifics that the reviewer needs to know? If I understand it correctly, the windows and doors have fins that go in the Mursten end slots. Are there any measurements on the slot size or the fin size that need to be checked? What about the total window height compared to a Mursten brick height?]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Delay after submit]]></title>
			<link>https://forums.ldraw.org/thread-29176.html</link>
			<pubDate>Tue, 18 Nov 2025 19:47:32 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forums.ldraw.org/member.php?action=profile&uid=30502">Peter Blomberg</a>]]></dc:creator>
			<guid isPermaLink="false">https://forums.ldraw.org/thread-29176.html</guid>
			<description><![CDATA[Philo wrote that "... BL keywords are automagically added by PT after "some time"" in the comments of one patterned part.<br />
<br />
How long does one need to wait for that to happen and why is there a delay?<br />
<br />
If the delay is there for a reason, can't the patterned parts be flagged somehow to indicate that it is not yet ready for review?]]></description>
			<content:encoded><![CDATA[Philo wrote that "... BL keywords are automagically added by PT after "some time"" in the comments of one patterned part.<br />
<br />
How long does one need to wait for that to happen and why is there a delay?<br />
<br />
If the delay is there for a reason, can't the patterned parts be flagged somehow to indicate that it is not yet ready for review?]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Learning how to review stickers and patterns]]></title>
			<link>https://forums.ldraw.org/thread-29174.html</link>
			<pubDate>Mon, 17 Nov 2025 10:28:12 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forums.ldraw.org/member.php?action=profile&uid=30502">Peter Blomberg</a>]]></dc:creator>
			<guid isPermaLink="false">https://forums.ldraw.org/thread-29174.html</guid>
			<description><![CDATA[I do not yet consider myself proficient at reviewing stickers or patterns. LDraw could use people with that skill. More than one person. So, why not write about my journey and inspire others to follow?<br />
<br />
Here I am wanting to learn how to review a sticker. Stickers are patterns on a thin part and I don't want to learn the stickerback standard by heart here in the beginning.<br />
<br />
So. I go to the Parts Tracker.<br />
<a href="https://library.ldraw.org/tracker" target="_blank" rel="noopener" class="mycode_url">https://library.ldraw.org/tracker</a><br />
Select the Parts List from the menu bar on top<br />
<a href="https://library.ldraw.org/parts/list" target="_blank" rel="noopener" class="mycode_url">https://library.ldraw.org/parts/list</a><br />
And create a query/filter with the following parameters:<br />
Library Status - Unofficial Parts<br />
Part Status - Needs 1 more vote<br />
Add Rule:<br />
Description Ends with "pattern"<br />
<br />
This will produce a list of patterned parts having already one vote. These should be relatively easy to review.<br />
<br />
I sort the results by Date Updated - Descending to obtain the most recently updated/created parts. I then scroll the list to find a flat pattern - I don't want to begin with a 3D-surface. A flat pattern is best for beginners.<br />
I find 3070bp1s.dat - a 1x1 tile with a medium lavender dog face on top. I open the part page for it.<br />
<a href="https://library.ldraw.org/parts/49928" target="_blank" rel="noopener" class="mycode_url">https://library.ldraw.org/parts/49928</a><br />
<br />
I begin my review process with looking at the parts/file header:<br />
I see the description line (first line) and it contains double spaces before the numbers. The description also ends with "Pattern" as it should. So far so good.<br />
<br />
The Author is RainbowDolphin, who I know to be a good pattern author. This was one of the unmentioned criteria for choosing this pattern to review. Nevertheless, all looks good down to keywords. I make a mental note to check the keywords later. Every pattern also need a Set XXXX keyword. I see one set mentioned.<br />
<br />
At this point, I do not wish to expand the Show Contents. I go to look at the unofficial subparts section. I now see that the pattern is symmetric and it is composed of a half. That half is a subpart that I also need to review.<br />
Most importantly, I see that the unpatterned tile will not need to be reviewed. It is already under official subparts.<br />
Finally, I check the Part Events to see that there aren't any comments.<br />
<br />
I then download the part from the Download Zip File button near the top of the page. I unzip its content in a folder I have named "Review" so that I know which part(s) I'm reviewing now.<br />
The unzipping creates a p folder and a parts folder.<br />
<br />
I start LDPE and open the 3070bp1s.dat file from the parts folder.<br />
Once open, I switch to No Backface Culling view mode and select the Top view. Now I see the part from above.<br />
<br />
Hmm. Now I need something to compare to. I don't have the part so I will need to look for an image. The easiest way is to use the View on BrickLink, View on Rebrickable, and View on BrickOwl buttons available on the parts page. All three links work, but the picture on Rebrickable has the printing slightly on one side, so I choose not to use it. It is, however, the only picture (of the three) directly from above. The three pictures also show that the printing of different colors is not always the same. Compare for example the nose vs the lavender area. They are misaligned in virtually all three pictures.<br />
The pink area appears round in some of the pictures, but the author has likely chosen not to use primitives for it. This is quite common in patterns. It is far more important to follow the base part shape than having the pattern follow a regular geometric shape. Also, it would take too long to fit primitives.<br />
<br />
Next I look at the 3070bp1s.dat file contents and it has the expected structure; the base part first, then the two pattern halves, and finally the joining surfaces.<br />
I see that the vertexes have been rounded to one decimal - good.<br />
The dark purple is confirmed by BrickLink. The Bright Light Blue color is mentioned in LDraw description, but nowhere else. Okay, just leave it. It looks correct.<br />
The Medium Lavender is confirmed by Rebrickable and BrickLink.<br />
The base color of the part is white. This means all 'white'/background parts of the pattern will be color 16. Luckily, there aren't any white parts of the pattern.<br />
<br />
Next I check for potential overlap of the surfaces in this main file. This I do by highlighting each code line in the text window by selecting one or two lines and push the Show Selection in 3D View button. The surfaces are highlighted with red edge lines. Sometimes, it is easier to recolor, comment out, or delete the surfaces I have gone through. I can also use the Random Colors View Mode, but that requires moving the viewport eye to observe flickering of colors. For patterns, I use the recolor/delete method for convenience or out of habit since I use something very similar for prim usage. If I recolor or delete, I need to reload the file to reset any changes made.<br />
<br />
I then go through each vertex to make sure that the vertexes match. I know they match when I select a vertex and the coordinate popup window shows up. If I had selected multiple vertexes, the coordinate window would not show up. Knowing that the author has rounded to one decimal means that vertex mismatches would be visible. It also reduces the possibility of vertex mismatches.<br />
<br />
I also need to check that the whole pattern is at y=0. This is rather convenient to do by looking at the coordinates in the popup window. There are multiple ways of doing it and the best way depends a lot on what else needs to be checked.<br />
<br />
Finally, I run Edger2 (with default settings) to check if it would add any cond lines. It doesn't and everything is fine.<br />
<br />
I switch to Green Frontfaces/Red Backfaces view mode to check BFC. It appears fine and I don't see any gaps when rotating the viewport eye.<br />
<br />
Next I open the subfile and repeat the process. All ends up perfect.<br />
<br />
What a great review experience!<br />
<br />
But I'm not done yet. I check the subfile naming. s01 as it should. Good.<br />
<br />
The Set keyword is convenient to check in BrickLink and yes, it is correct.<br />
<br />
The final thing to do is to go back to the part page and submit my Certify Vote.<br />
Done.<br />
<br />
Now, you try one.<br />
<br />
PS. It doesn't really matter if you can't vote yet. Just do the review and leave a comment on the parts tracker.]]></description>
			<content:encoded><![CDATA[I do not yet consider myself proficient at reviewing stickers or patterns. LDraw could use people with that skill. More than one person. So, why not write about my journey and inspire others to follow?<br />
<br />
Here I am wanting to learn how to review a sticker. Stickers are patterns on a thin part and I don't want to learn the stickerback standard by heart here in the beginning.<br />
<br />
So. I go to the Parts Tracker.<br />
<a href="https://library.ldraw.org/tracker" target="_blank" rel="noopener" class="mycode_url">https://library.ldraw.org/tracker</a><br />
Select the Parts List from the menu bar on top<br />
<a href="https://library.ldraw.org/parts/list" target="_blank" rel="noopener" class="mycode_url">https://library.ldraw.org/parts/list</a><br />
And create a query/filter with the following parameters:<br />
Library Status - Unofficial Parts<br />
Part Status - Needs 1 more vote<br />
Add Rule:<br />
Description Ends with "pattern"<br />
<br />
This will produce a list of patterned parts having already one vote. These should be relatively easy to review.<br />
<br />
I sort the results by Date Updated - Descending to obtain the most recently updated/created parts. I then scroll the list to find a flat pattern - I don't want to begin with a 3D-surface. A flat pattern is best for beginners.<br />
I find 3070bp1s.dat - a 1x1 tile with a medium lavender dog face on top. I open the part page for it.<br />
<a href="https://library.ldraw.org/parts/49928" target="_blank" rel="noopener" class="mycode_url">https://library.ldraw.org/parts/49928</a><br />
<br />
I begin my review process with looking at the parts/file header:<br />
I see the description line (first line) and it contains double spaces before the numbers. The description also ends with "Pattern" as it should. So far so good.<br />
<br />
The Author is RainbowDolphin, who I know to be a good pattern author. This was one of the unmentioned criteria for choosing this pattern to review. Nevertheless, all looks good down to keywords. I make a mental note to check the keywords later. Every pattern also need a Set XXXX keyword. I see one set mentioned.<br />
<br />
At this point, I do not wish to expand the Show Contents. I go to look at the unofficial subparts section. I now see that the pattern is symmetric and it is composed of a half. That half is a subpart that I also need to review.<br />
Most importantly, I see that the unpatterned tile will not need to be reviewed. It is already under official subparts.<br />
Finally, I check the Part Events to see that there aren't any comments.<br />
<br />
I then download the part from the Download Zip File button near the top of the page. I unzip its content in a folder I have named "Review" so that I know which part(s) I'm reviewing now.<br />
The unzipping creates a p folder and a parts folder.<br />
<br />
I start LDPE and open the 3070bp1s.dat file from the parts folder.<br />
Once open, I switch to No Backface Culling view mode and select the Top view. Now I see the part from above.<br />
<br />
Hmm. Now I need something to compare to. I don't have the part so I will need to look for an image. The easiest way is to use the View on BrickLink, View on Rebrickable, and View on BrickOwl buttons available on the parts page. All three links work, but the picture on Rebrickable has the printing slightly on one side, so I choose not to use it. It is, however, the only picture (of the three) directly from above. The three pictures also show that the printing of different colors is not always the same. Compare for example the nose vs the lavender area. They are misaligned in virtually all three pictures.<br />
The pink area appears round in some of the pictures, but the author has likely chosen not to use primitives for it. This is quite common in patterns. It is far more important to follow the base part shape than having the pattern follow a regular geometric shape. Also, it would take too long to fit primitives.<br />
<br />
Next I look at the 3070bp1s.dat file contents and it has the expected structure; the base part first, then the two pattern halves, and finally the joining surfaces.<br />
I see that the vertexes have been rounded to one decimal - good.<br />
The dark purple is confirmed by BrickLink. The Bright Light Blue color is mentioned in LDraw description, but nowhere else. Okay, just leave it. It looks correct.<br />
The Medium Lavender is confirmed by Rebrickable and BrickLink.<br />
The base color of the part is white. This means all 'white'/background parts of the pattern will be color 16. Luckily, there aren't any white parts of the pattern.<br />
<br />
Next I check for potential overlap of the surfaces in this main file. This I do by highlighting each code line in the text window by selecting one or two lines and push the Show Selection in 3D View button. The surfaces are highlighted with red edge lines. Sometimes, it is easier to recolor, comment out, or delete the surfaces I have gone through. I can also use the Random Colors View Mode, but that requires moving the viewport eye to observe flickering of colors. For patterns, I use the recolor/delete method for convenience or out of habit since I use something very similar for prim usage. If I recolor or delete, I need to reload the file to reset any changes made.<br />
<br />
I then go through each vertex to make sure that the vertexes match. I know they match when I select a vertex and the coordinate popup window shows up. If I had selected multiple vertexes, the coordinate window would not show up. Knowing that the author has rounded to one decimal means that vertex mismatches would be visible. It also reduces the possibility of vertex mismatches.<br />
<br />
I also need to check that the whole pattern is at y=0. This is rather convenient to do by looking at the coordinates in the popup window. There are multiple ways of doing it and the best way depends a lot on what else needs to be checked.<br />
<br />
Finally, I run Edger2 (with default settings) to check if it would add any cond lines. It doesn't and everything is fine.<br />
<br />
I switch to Green Frontfaces/Red Backfaces view mode to check BFC. It appears fine and I don't see any gaps when rotating the viewport eye.<br />
<br />
Next I open the subfile and repeat the process. All ends up perfect.<br />
<br />
What a great review experience!<br />
<br />
But I'm not done yet. I check the subfile naming. s01 as it should. Good.<br />
<br />
The Set keyword is convenient to check in BrickLink and yes, it is correct.<br />
<br />
The final thing to do is to go back to the part page and submit my Certify Vote.<br />
Done.<br />
<br />
Now, you try one.<br />
<br />
PS. It doesn't really matter if you can't vote yet. Just do the review and leave a comment on the parts tracker.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Partial reviews]]></title>
			<link>https://forums.ldraw.org/thread-29173.html</link>
			<pubDate>Mon, 17 Nov 2025 08:34:32 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forums.ldraw.org/member.php?action=profile&uid=30502">Peter Blomberg</a>]]></dc:creator>
			<guid isPermaLink="false">https://forums.ldraw.org/thread-29173.html</guid>
			<description><![CDATA[How should partial reviews be mentioned? Is there a short list of items that can be used for classifying partial reviews? Like a,b, and c checked, but d, e, f, and g not.<br />
<br />
Perhaps:<ul class="mycode_list"><li>Edger2 (with default settings)<br />
</li>
<li>BFC, Gaps, Edges<br />
</li>
<li>Overlap, Vertex rounding<br />
</li>
<li>Prim use, complementary cond lines, prim substitution<br />
</li>
<li>Origin<br />
</li>
<li>Fit/clash with other parts, Help<br />
</li>
<li>Links, Number/name, Visual similarity to real part/pictures<br />
</li>
<li>Keywords, Description<br />
</li>
<li>History, Admin stuff<br />
</li>
</ul>
<br />
My review process looks something like this:<br />
<br />
Make a search/filter in the parts tracker to obtain a batch of similar parts for review. If a part has unresolved issues in the existing comments or a hold vote I accept, it won't be selected.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Mainly freeform parts</span><br />
-Edger2 with default settings. On error report findings as hold or comment. When I'm lazy, I only report what Edger2 complains about. Otherwise, I try to figure out why Edger2 complains to make the error report more useful.<br />
-BFC, Gaps, Edges in LDView. On error report findings as hold or comment. Important to mention coordinates.<br />
-Origin, Prim use, Overlap, Vertex rounding, compl cond, prim subst. On error report findings as hold or comment<br />
-Fit to other parts, bottom stud connectivity, Help. On error report findings as hold<br />
-Links, Number/name, Visual similarity. On error report findings as comment<br />
-Vote certify if no error<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Mainly geometric primitives</span><br />
-Origin, Bounding box, Fit to other parts. On error report findings as hold<br />
-Prim use, Edges, Gaps, Overlap, BFC, Vertex rounding. On error report findings as hold or comment<br />
-Links, Number/name, Visual similarity to real part/pictures. On error report findings as comment<br />
-Keywords, Description, History, Admin stuff. On error report findings as comment<br />
-Vote certify if no error<br />
<br />
This means that only a subset of parts in a batch make it all the way through to voting certify. The complementary subset ends up with partial reviews.]]></description>
			<content:encoded><![CDATA[How should partial reviews be mentioned? Is there a short list of items that can be used for classifying partial reviews? Like a,b, and c checked, but d, e, f, and g not.<br />
<br />
Perhaps:<ul class="mycode_list"><li>Edger2 (with default settings)<br />
</li>
<li>BFC, Gaps, Edges<br />
</li>
<li>Overlap, Vertex rounding<br />
</li>
<li>Prim use, complementary cond lines, prim substitution<br />
</li>
<li>Origin<br />
</li>
<li>Fit/clash with other parts, Help<br />
</li>
<li>Links, Number/name, Visual similarity to real part/pictures<br />
</li>
<li>Keywords, Description<br />
</li>
<li>History, Admin stuff<br />
</li>
</ul>
<br />
My review process looks something like this:<br />
<br />
Make a search/filter in the parts tracker to obtain a batch of similar parts for review. If a part has unresolved issues in the existing comments or a hold vote I accept, it won't be selected.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Mainly freeform parts</span><br />
-Edger2 with default settings. On error report findings as hold or comment. When I'm lazy, I only report what Edger2 complains about. Otherwise, I try to figure out why Edger2 complains to make the error report more useful.<br />
-BFC, Gaps, Edges in LDView. On error report findings as hold or comment. Important to mention coordinates.<br />
-Origin, Prim use, Overlap, Vertex rounding, compl cond, prim subst. On error report findings as hold or comment<br />
-Fit to other parts, bottom stud connectivity, Help. On error report findings as hold<br />
-Links, Number/name, Visual similarity. On error report findings as comment<br />
-Vote certify if no error<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Mainly geometric primitives</span><br />
-Origin, Bounding box, Fit to other parts. On error report findings as hold<br />
-Prim use, Edges, Gaps, Overlap, BFC, Vertex rounding. On error report findings as hold or comment<br />
-Links, Number/name, Visual similarity to real part/pictures. On error report findings as comment<br />
-Keywords, Description, History, Admin stuff. On error report findings as comment<br />
-Vote certify if no error<br />
<br />
This means that only a subset of parts in a batch make it all the way through to voting certify. The complementary subset ends up with partial reviews.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[How to review texmap images]]></title>
			<link>https://forums.ldraw.org/thread-29160.html</link>
			<pubDate>Sun, 09 Nov 2025 17:30:15 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forums.ldraw.org/member.php?action=profile&uid=30502">Peter Blomberg</a>]]></dc:creator>
			<guid isPermaLink="false">https://forums.ldraw.org/thread-29160.html</guid>
			<description><![CDATA[How are texmap images reviewed? Is special software needed?]]></description>
			<content:encoded><![CDATA[How are texmap images reviewed? Is special software needed?]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Move to question]]></title>
			<link>https://forums.ldraw.org/thread-29154.html</link>
			<pubDate>Thu, 06 Nov 2025 23:58:39 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forums.ldraw.org/member.php?action=profile&uid=30502">Peter Blomberg</a>]]></dc:creator>
			<guid isPermaLink="false">https://forums.ldraw.org/thread-29154.html</guid>
			<description><![CDATA[When a part number is updated, a move to file is created for the old number. Why does the new part use the subfiles from the old part number?<br />
<br />
e.g. <a href="https://library.ldraw.org/parts/49972" target="_blank" rel="noopener" class="mycode_url">https://library.ldraw.org/parts/49972</a>]]></description>
			<content:encoded><![CDATA[When a part number is updated, a move to file is created for the old number. Why does the new part use the subfiles from the old part number?<br />
<br />
e.g. <a href="https://library.ldraw.org/parts/49972" target="_blank" rel="noopener" class="mycode_url">https://library.ldraw.org/parts/49972</a>]]></content:encoded>
		</item>
	</channel>
</rss>