[Suggestion] Curve the npeghole primitives


[Suggestion] Curve the npeghole primitives
#1
One thing that was bothering me for the all time I was using LDraw-powered software, and especially after I started making parts for the repository, is that the npegholes are very oddly unsmoothed. It doesn't look good, it is not accurate, and requires not that much work to do. Maybe update this set of primitives to make corners a bit rounded?
Reply
RE: [Suggestion] Cure the npeghole primitives
#2
(2022-04-23, 21:11)Max Murtazin Wrote: One thing that was bothering me for the all time I was using LDraw-powered software, and especially after I started making parts for the repository, is that the npegholes are very oddly unsmoothed. It doesn't look good, it is not accurate, and requires not that much work to do. Maybe update this set of primitives to make corners a bit rounded?

Can you elaborate a bit more on this?
Reply
RE: [Suggestion] Cure the npeghole primitives
#3
(2022-04-24, 12:47)Orion Pobursky Wrote: Can you elaborate a bit more on this?

Currently it is like this (npegholes, those carvings between connection holes), with sharp ends
[Image: unknown.png]

And I suggest to make it more like this, to make it have more curved edges
[Image: unknown.png]
Reply
RE: [Suggestion] Cure the npeghole primitives
#4
Your images are broken but I think I understand.

We've had the same debate for click hinges and the round/half round 1x1 tiles. My counter point would be that these small rounded edges at a lot of triangles for a feature that is only visible at close zoom levels. Also, developers are free to use primitive substitution to render them with "higher res".

My person opinion is more of the latter and less of the former.
Reply
RE: [Suggestion] Cure the npeghole primitives
#5
Is it that much significant, tho? Modern PCs (something from last 5-6 years) can easily handle pretty extreme polygon counts. Polygon number increase from this for sure will be big, but not exponential. Not something that is a real game changer to make new version of primitives impossible to use. Axle primitives got updated not so long ago, and polygon increase was way more dramatic for those, than what is necessary to have smooth npegholes
Reply
RE: [Suggestion] Cure the npeghole primitives
#6
I totally agree about triangle count but others care about that more than me. 

Also, now that the images are loading, I didn't understand what you meant. That said, if you want to change, you probably have to do it yourself including researching what parts have that shape but don't use the primitive so you can either update to use it or change it so it conforms. If you're up to the task,  you have my encouragement to do this.
Reply
RE: [Suggestion] Cure the npeghole primitives
#7
(2022-04-24, 19:55)Orion Pobursky Wrote: I totally agree about triangle count but others care about that more than me. 

Also, now that the images are loading, I didn't understand what you meant. That said, if you want to change, you probably have to do it yourself including researching what parts have that shape but don't use the primitive so you can either update to use it or change it so it conforms. If you're up to the task,  you have my encouragement to do this.

I will post tomorrow more informative pictures, as well as primitives, looks like that would be more helpful to the topic
Reply
RE: [Suggestion] Cure the npeghole primitives
#8
(2022-04-23, 21:11)Max Murtazin Wrote: One thing that was bothering me for the all time I was using LDraw-powered software, and especially after I started making parts for the repository, is that the npegholes are very oddly unsmoothed. It doesn't look good, it is not accurate, and requires not that much work to do. Maybe update this set of primitives to make corners a bit rounded?
I agree that current situation is far from perfect (it's even worse for 90° angled beams where the npegholes join together), but changing this is rather daunting, as these elements are often embedded in part structure. The 90° situation was so bad that I already created npeghol17 with cut corners to address the problem in Technic baseplate (https://www.ldraw.org/parts/official-par...rtid=39369)
...Or we could go the other direction and completely remove beam npegholes like LEGO does in his building instructions! Big Grin
Reply
RE: [Suggestion] Cure the npeghole primitives
#9
(2022-04-25, 6:38)Philippe Hurbain Wrote: I agree that current situation is far from perfect (it's even worse for 90° angled beams where the npegholes join together), but changing this is rather daunting, as these elements are often embedded in part structure. The 90° situation was so bad that I already created npeghol17 with cut corners to address the problem in Technic baseplate (https://www.ldraw.org/parts/official-par...rtid=39369)
...Or we could go the other direction and completely remove beam npegholes like LEGO does in his building instructions! Big Grin

I think I didn't completely understand wdym, could you elaborate please a bit? Only thing I think I got is that some new parts have problem of old npeghole primitives having overlapping esges
Reply
RE: [Suggestion] Cure the npeghole primitives
#10
(2022-04-25, 7:34)Max Murtazin Wrote: I think I didn't completely understand wdym, could you elaborate please a bit? Only thing I think I got is that some new parts have problem of old npeghole primitives having overlapping esges
Not only new parts, but also some venerable ones like this one:


Attached Files
.jpg   Capture.JPG (Size: 31.32 KB / Downloads: 175)
Reply
RE: [Suggestion] Cure the npeghole primitives
#11
Okay so, here is more visual explanation of what I suggest to do. 
Currently we have this:

           

It is pretty angular, not so pleasing to see, and, as Phillippe mentioned, sometimes results in pretty unpleasing geometry

Instead, I suggest doing this:

           

Result is more pleasing to the eye, and doesn't have 0-thickness in any places of the part. 

Mentioning once again axle primitives, we already have an example of changing primitives to make them look better, and also with the change get rid of some unwanted geometry interactions, that don't change much due to not being visible most of the time. Liftarms by the way, I want to say, are way easier to notice imperfections with, because npegholes are seen very commonly on the builds, and some smaller ones look very not good with what is currently on hands

I also attach rough concept models of primitives I used for the pictures. These are currently just the concept models, and use no primitives nor have any smoothing. I will make proper versions of those two, as well as other npeghole primitives if idea won't ultimately get rejected, but for now I think it's enough for the discussion


Attached Files
.dat   npeghole.dat (Size: 5.29 KB / Downloads: 2)
.dat   npeghol2.dat (Size: 6.04 KB / Downloads: 2)
Reply
RE: [Suggestion] Cure the npeghole primitives
#12
As I wrote above I like this idea. However, also as mentioned above, it's going to take a lot of legwork. If you don't mind doing this, I encourage you take on this project.
Reply
RE: [Suggestion] Cure the npeghole primitives
#13
(2022-04-25, 14:58)Orion Pobursky Wrote: As I wrote above I like this idea. However, also as mentioned above, it's going to take a lot of legwork. If you don't mind doing this, I encourage you take on this project.

What problems might arise, for example? Currently I see ~20 primitives that just need to be updated, and not much problems updates might cause
Reply
RE: [Suggestion] Cure the npeghole primitives
#16
(2022-04-25, 15:10)Max Murtazin Wrote: What problems might arise, for example? Currently I see ~20 primitives that just need to be updated, and not much problems updates might cause

Changing the primitives themselves probably won't be too much of a problem as long as you don't change the geometry at the edges. It's finding and fixing/updating those parts that either interact with the primitives in a nonstandard way or don't use the primitives at all.
Reply
RE: [Suggestion] Cure the npeghole primitives
#14
(2022-04-25, 14:58)Orion Pobursky Wrote: As I wrote above I like this idea. However, also as mentioned above, it's going to take a lot of legwork. If you don't mind doing this, I encourage you take on this project.

Since this is an improvement, wouldnt it be as simple as updating the one or two affected primitives? I am pretty new around here but I am surprised this would be a large undertaking.
Reply
RE: [Suggestion] Cure the npeghole primitives
#15
The main issue is that the suggested design doesn't work in primitive substitution mode.

Most of the holes in beams are made using the connhole.dat primitive, and when it changes shape, the npeghole has to also adapt.
Many of the npeg primitives are today made using cyli primitives.

Or all beams will end up looking like this:

   
Reply
RE: [Suggestion] Cure the npeghole primitives
#17
(2022-04-25, 15:23)Magnus Forsberg Wrote: The main issue is that the suggested design doesn't work in primitive substitution mode.

Most of the holes in beams are made using the connhole.dat primitive, and when it changes shape, the npeghole has to also adapt.
Many of the npeg primitives are today made using cyli primitives.

Or all beams will end up looking like this:

I already mentioned that this variant is just a plain shape, just a plain model. I am going to make it work with primitive substitution once properly done
Reply
RE: [Suggestion] Cure the npeghole primitives
#18
(2022-04-25, 15:33)Max Murtazin Wrote: I already mentioned that this variant is just a plain shape, just a plain model. I am going to make it work with primitive substitution once properly done
You can make it work in the middle using cyli primitives instead of quads. But that's not possible near the corners.
Reply
RE: [Suggestion] Cure the npeghole primitives
#19
(2022-04-25, 16:46)Philippe Hurbain Wrote: You can make it work in the middle using cyli primitives instead of quads. But that's not possible near the corners.

I have looked into how you have done with the npeghol17, and tweaked it into how I see general npeghole primitive should look

By the way, here it is. It now is composed from primitives and supports substitution. Requires other attached primitives


Attached Files
.dat   npeghole.dat (Size: 6.95 KB / Downloads: 3)
.dat   17-48cylo.dat (Size: 369 bytes / Downloads: 3)
.dat   17-48disc.dat (Size: 721 bytes / Downloads: 3)
.dat   17-48chrd.dat (Size: 2.11 KB / Downloads: 4)
.dat   17-48cyli.dat (Size: 2.46 KB / Downloads: 3)
Reply
RE: [Suggestion] Cure the npeghole primitives
#20
(2022-04-25, 17:20)Max Murtazin Wrote: I have looked into how you have done with the npeghol17, and tweaked it into how I see general npeghole primitive should look
By the way, here it is. It now is composed from primitives and supports substitution. Requires other attached primitives
Going to hires is definitely not an option...
edit:
...but the base idea (reduce width at corners) is a good one. We could possibly make it work.
Reply
RE: [Suggestion] Cure the npeghole primitives
#21
(2022-04-25, 17:38)Philippe Hurbain Wrote: Going to hires is definitely not an option...
edit:
...but the base idea (reduce width at corners) is a good one. We could possibly make it work.

What part of "going to hires" exactly you don't like? Smoothed corners or just general use of those in primitives? If prior, I think non-primitive corners can be used instead
Reply
RE: [Suggestion] Cure the npeghole primitives
#22
(2022-04-25, 17:53)Max Murtazin Wrote: What part of "going to hires" exactly you don't like? Smoothed corners or just general use of those in primitives? If prior, I think non-primitive corners can be used instead
I meant indeed that the small corners really don't need that many faces! As you say, non primitive corners work fine since they are so small. Attached my proposal...


Attached Files
.dat   npeghole.dat (Size: 7.14 KB / Downloads: 8)
Reply
RE: [Suggestion] Cure the npeghole primitives
#23
(2022-04-25, 18:23)Philippe Hurbain Wrote: Attached my proposal...

I like this one...
Reply
RE: [Suggestion] Cure the npeghole primitives
#24
(2022-04-25, 18:23)Philippe Hurbain Wrote: I meant indeed that the small corners really don't need that many faces! As you say, non primitive corners work fine since they are so small. Attached my proposal...

Shape looks fine, but can someone upload picture of this in random colors? Want to see also a primitive composition of it, but wouldn't be able to until the morning otherwise

UPD: Okay, I checked it, and I think I like this one too
Reply
RE: [Suggestion] Cure the npeghole primitives
#25
Looking more closely, looks like the corner rounding should be even more prominent (Even though real shape depends on parts)


Attached Files
.dat   npeghole.dat (Size: 7.56 KB / Downloads: 8)
Reply
RE: [Suggestion] Cure the npeghole primitives
#26
(2022-04-26, 7:38)Philippe Hurbain Wrote: Looking more closely, looks like the corner rounding should be even more prominent (Even though real shape depends on parts)

That's more like it. Looks like general shape of this is a way to go, unless someone inupts a bit more on this
Reply
RE: [Suggestion] Cure the npeghole primitives
#27
Would it be okay to use npeghole.dat as a primitive in npeghol2.dat? Makes the whole file look cleaner, and also saves some disk space


Attached Files
.dat   npeghol2.dat (Size: 1.29 KB / Downloads: 4)
Reply
RE: [Suggestion] Cure the npeghole primitives
#28
(2022-04-26, 12:07)Max Murtazin Wrote: Would it be okay to use npeghole.dat as a primitive in npeghol2.dat? Makes the whole file look cleaner, and also saves some disk space
Yes, prims using prims is possible (and already often done)
Reply
RE: [Suggestion] Cure the npeghole primitives
#29
(2022-04-26, 7:38)Philippe Hurbain Wrote: Looking more closely, looks like the corner rounding should be even more prominent (Even though real shape depends on parts)

That one looks very nice! I really like it.

I guess there is a possibility to use a 8\ prim section of a cylinder in the corners

something like this:
1 16 5.5803 0 1.7 .78 0 0 0 1 0 -.10 0 .78 8\3-8cylo.dat
Reply
RE: [Suggestion] Cure the npeghole primitives
#30
(2022-04-26, 16:11)Gerald Lasser Wrote: That one looks very nice! I really like it.

I guess there is a possibility to use a 8\ prim section of a cylinder in the corners

something like this:
1 16 5.5803 0 1.7 .78 0 0 0 1 0 -.10 0 .78 8\3-8cylo.dat
Good idea, why didn't I thought of it ???
Reply
RE: [Suggestion] Cure the npeghole primitives
#31
(2022-04-26, 18:15)Philippe Hurbain Wrote: Good idea, why didn't I thought of it ???
...but I don't see how to fit a matching ndis. no 8\tang are defined...
Reply
RE: [Suggestion] Cure the npeghole primitives
#32
(2022-04-26, 18:47)Philippe Hurbain Wrote: ...but I don't see how to fit a matching ndis. no 8\tang are defined...

Maybe it's the time to define those then?
Reply
RE: [Suggestion] Cure the npeghole primitives
#33
(2022-04-26, 19:54)Max Murtazin Wrote: Maybe it's the time to define those then?
Not so simple considering the way 48\tang are defined. 
Anyway using a cylo primitive is tricky as it must match the 1-16 tang vertex. The proper method is to a add an intermediate geometry, but it then adds even more faces... So non prim version is probably the best compromise.
Reply
RE: [Suggestion] Cure the npeghole primitives
#34
(2022-04-27, 8:44)Philippe Hurbain Wrote: Not so simple considering the way 48\tang are defined. 
Anyway using a cylo primitive is tricky as it must match the 1-16 tang vertex. The proper method is to a add an intermediate geometry, but it then adds even more faces... So non prim version is probably the best compromise.

What's the deal with 48\tang?
Reply
RE: [Suggestion] Cure the npeghole primitives
#35
(2022-04-27, 9:19)Max Murtazin Wrote: What's the deal with 48\tang?
It is defined as an extension of normal resolution of tang (this is the proper way to do it to allow direct normal -> hires substitution). But then at lo res this become meaningless.
Reply
RE: [Suggestion] Cure the npeghole primitives
#36
(2022-04-27, 9:43)Philippe Hurbain Wrote: It is defined as an extension of normal resolution of tang (this is the proper way to do it to allow direct normal -> hires substitution). But then at lo res this become meaningless.

I don't see much problem with this. Even tho hires is an extension of normal one, it doesn't mean that lores still should be that way
Reply
RE: [Suggestion] Cure the npeghole primitives
#37
(2022-04-27, 9:43)Philippe Hurbain Wrote: It is defined as an extension of normal resolution of tang (this is the proper way to do it to allow direct normal -> hires substitution). But then at lo res this become meaningless.

As there is no prim substitution doen on the level of lo res prims, then we do not need a tang, imho.

PS: the end-condlines of 8/3-8cylo are wrong

Edit: Attached the sample


Attached Files
.dat   npeghole_new_rounded.dat (Size: 3.47 KB / Downloads: 6)
Reply
RE: [Suggestion] Cure the npeghole primitives
#38
(2022-04-27, 13:36)Gerald Lasser Wrote: As there is no prim substitution doen on the level of lo res prims, then we do not need a tang, imho.
You have a point... But then using a cylo has a very limited interest  Big Grin. Looks excellent nonetheless!
Reply
RE: [Suggestion] Cure the npeghole primitives
#39
(2022-04-27, 14:55)Philippe Hurbain Wrote: You have a point... But then using a cylo has a very limited interest  Big Grin. Looks excellent nonetheless!

I also don't see much reason in using cylo besides saving a bit of disk space. 

New shaping looks better tho, I must point out
Reply
RE: [Suggestion] Cure the npeghole primitives
#40
(2022-04-27, 16:26)Max Murtazin Wrote: I also don't see much reason in using cylo besides saving a bit of disk space. 

New shaping looks better tho, I must point out

Yes, it's mostly to reduce clutter in the code

EDIT: But the L-Beam looks very tempting now...
   
Reply
RE: [Suggestion] Cure the npeghole primitives
#41
(2022-04-27, 20:03)Gerald Lasser Wrote: Yes, it's mostly to reduce clutter in the code

EDIT: But the L-Beam looks very tempting now...

For sure the way to go. If anyone don't have anything to suggest, I'll update other primitives tomorrow
Reply
RE: [Suggestion] Cure the npeghole primitives
#42
(2022-04-29, 20:16)Max Murtazin Wrote: If anyone don't have anything to suggest, I'll update other primitives tomorrow

I don't doubt that you are capable of editing a few primitives, but how about the extensive investigation into the geometry of all the parts using these family of primitives. I made a thorough investigation of all the parts with an axlehole, before a dared to suggest a rework.
Have you made a similar investigation of all the parts using npeghole primitives?

IMO it would be wrong to change all the npeg hole primitives, so which one are you planning to edit?
Reply
RE: [Suggestion] Cure the npeghole primitives
#43
(2022-04-30, 8:37)Magnus Forsberg Wrote: I don't doubt that you are capable of editing a few primitives, but how about the extensive investigation into the geometry of all the parts using these family of primitives. I made a thorough investigation of all the parts with an axlehole, before a dared to suggest a rework.
Have you made a similar investigation of all the parts using npeghole primitives?

IMO it would be wrong to change all the npeg hole primitives, so which one are you planning to edit?

All up to the 13 have one same element this topic was about fixing. By the extension, all npegholes 0 through 13 would need an update. As far as I know it, currently all parts with npeghole element use primitives, and with how updated variant is done, it shouldn't cause any problems.

I will go through all the parts using those primitives, but for that I need primitives themselves to be on my hands
Reply
RE: [Suggestion] Cure the npeghole primitives
#44
(2022-04-30, 10:47)Max Murtazin Wrote: All up to the 13 have one same element this topic was about fixing.

IMO that wrong. They are differently used, and designed. And should be different. Editing them all, would create a bad result

(2022-04-30, 10:47)Max Murtazin Wrote: I will go through all the parts using those primitives, but for that I need primitives themselves to be on my hands

When I reshaped the axle holes I edited my own library and then used them coloured.
1.) edit the primitive, place it in your own unofficial p-folder.
2.) hard code the edited prim in a "weird" colour
3.) remove the corresponding official primitive.
4.) examine the result. I used LDFind and LDStructure a lot in my investigation.
Reply
RE: [Suggestion] Cure the npeghole primitives
#45
I'll point out that this doesn't have to be a one person effort
Reply
RE: [Suggestion] Cure the npeghole primitives
#46
(2022-04-30, 16:10)Orion Pobursky Wrote: I'll point out that this doesn't have to be a one person effort

Well, my approach has always been that if I want to change a primitive, I have to do the investigation.
I can't just upload a changed primitive, and expect someone else to find and edit all the affected parts.
Reply
RE: [Suggestion] Cure the npeghole primitives
#49
(2022-04-30, 16:28)Magnus Forsberg Wrote: Well, my approach has always been that if I want to change a primitive, I have to do the investigation.
I can't just upload a changed primitive, and expect someone else to find and edit all the affected parts.

I know that changing primitive might cause some unexpected problems, and that's why I'm not touching part tracker at the moment
Reply
RE: [Suggestion] Cure the npeghole primitives
#50
(2022-04-30, 16:28)Magnus Forsberg Wrote: Well, my approach has always been that if I want to change a primitive, I have to do the investigation.
I can't just upload a changed primitive, and expect someone else to find and edit all the affected parts.

+1
LEGO ergo sum
Reply
RE: [Suggestion] Cure the npeghole primitives
#47
(2022-04-30, 11:53)Magnus Forsberg Wrote: IMO that wrong. They are differently used, and designed. And should be different. Editing them all, would create a bad result
Actually all numbers up to 13, if didn't misunderstood some of those primitives, are just different kinds of those liftarm insertions of different kind and/or to be used in different context.
Npeghole/2 are normal liftarm one, that have been worked on.
3/4 are used in the case when we have pinhole next to an axlehole. Can be seen on any thin liftarms, and is always smoothed
5 is similar to the 3 and 4, but is used with axle on one side, and some geometry on the other that doesn't add up to the 3 or 4. Example of this primitive is 32475, which does use smoothed edges of npeghole: https://www.bricklink.com/v2/catalog/cat...ge?P=32475
7/7a are just half variants of npeghole/2
8, 9, 10 and 11 are primitives for different alternating hole liftarms/connectivities, which all use smoothing on the npeghole in real life
12 and 13 are wider kinds of 2, and through I wasn't able to find example of usage, most likely they do follow the pattern

Only thing I'm unsure about usage of 6 series, but they look also like similar ones to listed on above, and then most likely will also use smoothed shape
 
(2022-04-30, 11:53)Magnus Forsberg Wrote: When I reshaped the axle holes I edited my own library and then used them coloured.
1.) edit the primitive, place it in your own unofficial p-folder.
2.) hard code the edited prim in a "weird" colour
3.) remove the corresponding official primitive.
4.) examine the result. I used LDFind and LDStructure a lot in my investigation.

Thanks, will be helpful a lot. Both LDFind and LDStructure seem to be unavailable on Mac, are there any options for this system?
Reply
RE: [Suggestion] Cure the npeghole primitives
#48
(2022-04-30, 16:46)Max Murtazin Wrote: Thanks, will be helpful a lot. Both LDFind and LDStructure seem to be unavailable on Mac, are there any options for this system?

I will try and see if these work under Wine. MPDCenter does, so maybe…?

I use LDView's model tree view a lot to check structure, but of course it does far less than these two programs.
Reply
RE: [Suggestion] Cure the npeghole primitives
#51
(2022-04-27, 13:36)Gerald Lasser Wrote: As there is no prim substitution doen on the level of lo res prims, then we do not need a tang, imho.

PS: the end-condlines of 8/3-8cylo are wrong

Edit: Attached the sample

So, I have updated all of the primitives using this one

Unfortunately, both LDFind and LDStructure refuse to work on my PC so I can't check if it works properly on all parts.

Help with getting list of the parts featuring npeghole primitives will be much appreciated


Attached Files
.zip   npegholes.zip (Size: 14.53 KB / Downloads: 0)
Reply
RE: [Suggestion] Cure the npeghole primitives
#52
(2022-07-08, 17:08)Max Murtazin Wrote: So, I have updated all of the primitives using this one

Unfortunately, both LDFind and LDStructure refuse to work on my PC so I can't check if it works properly on all parts.

Help with getting list of the parts featuring npeghole primitives will be much appreciated

This is probably a comprehensive list:

https://www.ldraw.org/cgi-bin/ptscan.cgi...scope=file
Reply
RE: [Suggestion] Cure the npeghole primitives
#53
(2022-07-08, 17:23)Orion Pobursky Wrote: This is probably a comprehensive list:

https://www.ldraw.org/cgi-bin/ptscan.cgi...scope=file

Thanks, forgot that you can also search it this way

After I will make edits of parts that need it, what would be my next move? Would I need some, idk, seal of approval before uploading things on the part tracker?
Reply
RE: [Suggestion] Cure the npeghole primitives
#54
(2022-07-08, 17:44)Max Murtazin Wrote: After I will make edits of parts that need it, what would be my next move? Would I need some, idk, seal of approval before uploading things on the part tracker?

Part fixes have to be submitted by me. I want a fully complete and ready to go file with HISTORY line submitted to the parts admin address. An archive with all the files is preferred if there's more than a couple of files.
Reply
RE: [Suggestion] Cure the npeghole primitives
#55
(2022-07-08, 17:50)Orion Pobursky Wrote: Part fixes have to be submitted by me. I want a fully complete and ready to go file with HISTORY line submitted to the parts admin address. An archive with all the files is preferred if there's more than a couple of files.

Okay, sent it, hope no problems there are present
Reply
RE: [Suggestion] Cure the npeghole primitives
#56
(2022-07-08, 19:26)Max Murtazin Wrote: Okay, sent it, hope no problems there are present

Got it. I'll be away all weekend so prolly won't get to these until next week.
Reply
RE: [Suggestion] Cure the npeghole primitives
#57
(2022-07-08, 19:43)Orion Pobursky Wrote: Got it. I'll be away all weekend so prolly won't get to these until next week.

Could you please let us know how many primitives have been edited, and also perhaps how many parts are affected?
Did you make any new primitives?

A summary would make the review easier.
Reply
RE: [Suggestion] Cure the npeghole primitives
#58
This is the best I can do until I get home on Tuesday. 

https://www.ldraw.org/cgi-bin/ptreviewsu...?f=npeghol
Reply
RE: [Suggestion] Curve the npeghole primitives
#59
By the way, what should be done with npeghol16 and 17? Both were essentially the version to use in place where two npeghole edges would usually met, but since, this is no longer a problem, both are now obsolete (6a and npeghole can be used instead) and are not necessary anymore
Reply
RE: [Suggestion] Curve the npeghole primitives
#60
Once the official parts that use them are certified, we can make them obsolete.
Reply
RE: [Suggestion] Curve the npeghole primitives
#61
Hello everyone. Going to have internet problems next two weeks, so would likely have problems with fixing problems of new prims. If anyone wants to fix any of those in that time, please feel free to. I will pick it up right after

Sorry to part tracker admins if it's going to be an issue of sort, but it isn't quite a thing in control of mine
Reply
RE: [Suggestion] Curve the npeghole primitives
#62
I made myself a summary of all the descriptions of the npeghole primitives.

   

Yellow cell = updated designs
Blue (6d, 19, 20) = new files
Green (14, 15) = made, but never used or obsoleted
Orange (16, 17) = no longer needed. Obsolete, use npeghole or npeghol6a instead.

In the descriptions:
red = removed/moved text
green = added text

I want to change the descriptions, and use the green text, but should it be "without Extensions" or "without Top Surface Extensions"?
All the un-scalable primitives should use the word "Beam". Correct?
What does "0.125" stand for in their description? There is a mix-up of the usage of 0.25 and 0.125.
Reply
RE: [Suggestion] Curve the npeghole primitives
#63
   

Rounding error in npeghol13.dat resulting in an overlap.

w.
LEGO ergo sum
Reply
« Next Oldest | Next Newest »



Forum Jump:


Users browsing this thread: 2 Guest(s)