Welcome, Guest
You have to register before you can post on our site.

Username
  

Password
  





Search Forums

(Advanced Search)

Forum Statistics
» Members: 5,542
» Latest member: Seth Bray
» Forum threads: 6,314
» Forum posts: 52,574

Full Statistics

Online Users
There are currently 348 online users.
» 1 Member(s) | 342 Guest(s)
Applebot, Baidu, Bing, Google, Internet Archive, Seth Bray

Latest Threads
Vertex precision
Forum: Official File Specifications/Standards
Last Post: Orion Pobursky
7 hours ago
» Replies: 5
» Views: 1,583
LEGO Parts Guide - Only 6...
Forum: Part Requests
Last Post: tom alphin
8 hours ago
» Replies: 5
» Views: 200
98138pb0.dat is missing i...
Forum: Parts Authoring
Last Post: Magnus Forsberg
Yesterday, 15:31
» Replies: 2
» Views: 103
How can I install on linu...
Forum: Help
Last Post: Orion Pobursky
Yesterday, 4:48
» Replies: 1
» Views: 75
Castle Ninja / Robber
Forum: Part Requests
Last Post: Carl Rodabaugh
Yesterday, 1:06
» Replies: 0
» Views: 70
help finding ldraw for el...
Forum: Help
Last Post: Brian H
2025-12-30, 23:22
» Replies: 2
» Views: 112
Missing Opal Trans Yellow
Forum: Official File Specifications/Standards
Last Post: Philippe Hurbain
2025-12-30, 19:27
» Replies: 3
» Views: 248
LEGO Icons 2025
Forum: Official Models
Last Post: Philippe Hurbain
2025-12-30, 9:53
» Replies: 4
» Views: 5,074
Minifigure, Head Brown Ey...
Forum: Part Requests
Last Post: Philippe Hurbain
2025-12-30, 9:20
» Replies: 2
» Views: 157
Technic 1992
Forum: Official Models
Last Post: Takeshi Takahashi
2025-12-28, 19:34
» Replies: 29
» Views: 42,250

 
  Rubber band templates question
Posted by: N. W. Perry - 2021-09-10, 15:40 - Forum: LDraw Editors and Viewers - Replies (4)

For band/belt templates in LDCad, the radius of a point is measured to the center of the path. I thought it would be handy to offset the path skin so that its inner edge follow the radius (i.e., the radius of the point is the same as the part it goes around).

I thought adjusting the alignment parameter was the way to do this, but it didn't work. It just breaks the path into segments with wide gaps (and they aren't noticeably offset from center).

Is there a simple way to adjust the template to do this? Or would I have to create a donor part with the origin shifted (and would that even work)?

Print this item

  Command Lines List Argument LDView
Posted by: Leo Juffinger - 2021-09-07, 14:09 - Forum: LDraw Editors and Viewers - Replies (2)

Hello,

I am trying to implement the -CommandLinesList feature from LDView 4.4 into my application.
To do so, I created a text file that looks like this:


.txt   temp.txt (Size: 781 bytes / Downloads: 8)

I then have the following situation: When I run ~/LdView64.exe -CommandLinesList=my_file.txt in the command line, the five .ldr files that are specified get exported to .pov format.
However, the INITIAL values (lat 50, long -111, zoom 0.56 in this case) are used throughout ALL five .ldr files. So for all five models, I have the same viewing angle which is not what I want.

Does anyone have an idea for why this occurs?
Thanks in advance

here are the .ldr files

.ldr   4035_70_0.ldr (Size: 52 bytes / Downloads: 3)
.ldr   4035_110_3.ldr (Size: 53 bytes / Downloads: 1)
.ldr   4035_128_1.ldr (Size: 53 bytes / Downloads: 0)
.ldr   4035_14_4.ldr (Size: 52 bytes / Downloads: 0)
.ldr   4035_17_2.ldr (Size: 52 bytes / Downloads: 0)

Print this item

  Part Request: 93696pb03 SW Togruta Montrals Long
Posted by: Karlee B. - 2021-09-07, 0:03 - Forum: Part Requests - Replies (2)

Hello, I am hoping someone here could build this part (93696pb03) in a CAD software. I would like to be able to make Togruta characters, such as Ahsoka Tano, in LEGO designer programs but I don't believe anyone has made this part in a CAD program before. I would be extremely grateful to anyone who makes this part.



Attached Files Thumbnail(s)
       

.png   Ahsoka Tano (Siege of Mandalore).png (Size: 141.28 KB / Downloads: 50)
Print this item

  Part Request: 41850 / Body, Racers Driver
Posted by: Alex Hoyer - 2021-09-06, 13:45 - Forum: Part Requests - No Replies

Hello,


i want to request this Part:
41850 / Body, Racers Driver


Bricklink:
https://www.bricklink.com/v2/catalog/cat...ge?P=41850




Many thanks for help !

Print this item

  Another possible use for !FLOAT meta
Posted by: N. W. Perry - 2021-09-06, 2:22 - Forum: LDraw Editors and Viewers - Replies (2)

(For those not familiar, !FLOAT is my proposed, imaginary meta command that temporarily overrides the displayed position and other parameters of a part in an LDraw editor or BI maker. It is intended to replace older concepts like buffer exchange, which is confusing and requires extra copies of parts to be added to a model.)


When building a model with lots of moving sections, like a Technic model, you probably build those sections as submodels or groups at orthogonal (90-degree) angles. Then when it's time to pose the model, you apply rotations to those groups or submodels.

But what if you want to change the pose? Or just revert a section back to its unrotated state for some reason? At least with LDCad, you can't always just rotate the parts the same number of degrees in the opposite direction, because you'll get rounding errors in the matrix.

If it's a submodel, of course you can always just reset the orientation. But then what if the unrotated state is non-orthogonal, like a piston rod or an angled link in the steering column?

With !FLOAT, the idea is that you supply a temporary position/orientation in the meta command, which is what will be displayed until the command is canceled. The type 1 line for the part or submodel would always contain the final or "fixed" position, which is typically what will be displayed in the last step of the model (so you can "float" a part in the building instructions, e.g.).

But if you supply a float position and just never cancel it, then it could actually be used as the position displayed in the finished model. The matrix in the type 1 line would then represent the default or unrotated position of the part, which could be an identity matrix, another orthogonal position, or a rotation of its own. You could then pose the model simply by adjusting the float position, without changing the default position and thus compounding rounding errors (or simply forgetting what that position is).

The major drawback to this usage is that the fallback display (for any software that doesn't recognize !FLOAT) would be with everything in its unrotated state, rather than nicely posed. But I suppose a good editor could get around this by having an option to save a copy of the model with the float positions inlined. And in a way, the pose of a model is more a property of its display than of its construction. The actual parts of a model are immutable and so it makes sense for them to be hard-coded, but things like which way the steering wheel is turned are changeable, and so there's some logic to having that information stored at a meta level, in a way that's perhaps more interactive and portable.

Print this item

  Electric Power Functions IR Remote Control (58122)
Posted by: Roland Melkert - 2021-09-05, 19:28 - Forum: Parts Tracker Discussion - No Replies

I was investigating a bug report for LDCad regarding 58122 not wanting to inline.

It turns out that is because it contains skewed and mirrored parts, which imho is not needed and should be prevented in shotcut/alias parts.

The issues are:

Rough 0.033 in other wise '1 1 1' rotation matrices  (e.g  0 0 -1   0.033 1 0   1 0 0)
The blue slid direction switch is mirrored (and also has the 0.033 rounding error), using "0 0 -1 0 1 0 1 0 0" works for both red and blue sliders no need to mirror.

Print this item

  Missing 2017-2021 most common parts...
Posted by: tom alphin - 2021-09-05, 4:55 - Forum: Part Requests - Replies (7)

Hey all, I've shared my "Most Common Parts" analysis in the past, as it is a good way to find common parts that are missing from the LDraw catalog. 


(It's preliminary because some 2021 sets haven't been released or inventoried yet, and I need to do some normalization to map re-designed parts with new Part ID's to their legacy part Id equivalents.)


> Updated Sept 10, 2021 <

RANK, PART ID, Part Name
  • #666 - 27393 - Wave / Power Blast Rounded Energy with Bar Handle
  • #797 - 36017 - Weapon Sword Hilt with Dragon Head.
  • #867 - 36451a - Infinity Stone.
  • #1001 - 15445 - Weapon Gun Automatic Pistol with Top Clip
  • #1004 - 35032a through 35032d - Various Wave / Power Bursts
  • #1073 - 24183 - Life Jacket (Friends)
  • #1082 - 66727 - Wheel 18 x 12 with Pin Hole and Stud



(I'm continuing to add to the list as I complete the analysis.)

Sincerely,
---tom

Print this item

  Error import 51515
Posted by: DanielAntoszak - 2021-09-01, 8:26 - Forum: Help - Replies (2)

Cześć, mam problem z importem części zestawu 51515, kto miał podobny problem?
[Image: 51515.png]



Attached Files Thumbnail(s)
   
Print this item

  Part Request: 66788
Posted by: Kristopher Wilson - 2021-08-31, 22:46 - Forum: Part Requests - No Replies

This part is Arm and Hand Long with Technic Pin that was introduced in the LEGO Super Mario line. It is very similar to 28660, but a little longer in the curved part of the arm.

Thanks to anyone who can help!

Print this item

  ldc.camera.setThirdPerson API
Posted by: David Manley - 2021-08-31, 9:20 - Forum: LDraw Editors and Viewers - Replies (2)

(Probably for Roland but if someone else has worked this out, please chip in).

Context:
I'm trying to write a (Lua) animation script which will rotate the 3rd person view camera around the Y axis starting at the current view, rather than the start point used in the sample script. From the sample scripts, I can see the purpose of the first two arguments (helped by the description in LD4Studio documentation) but I'm struggling to understand the purpose next 3 angle (?) related arguments. The sample script in the function OnCameraFrame ...

Code:
function onCameraFrame()

  --Rotate a 3rd person camera around the center of the model.
  local ani=ldc.animation.getCurrent()
  local angle=ani:getFrameTime()/ani:getLength()*360

  local cam=ldc.camera()
  cam:setThirdPerson(camPos, camDist, angle+45, 25, 0)
  cam:apply(0)
end
 
... is applying an appropriate angle change to the third parameter. From playing around a bit, it seems that parameters three, four and five are related to a x, y, z coordinate. But even though the code applies the angle delta to the X value (I think), the camera appears to rotate around the Y axis. And that confuses me as I would have though that to rotate the camera around the Y axis would have required the angle delta to be applied to the y coordinate.

I'd appreciate it if someone could clear up my misunderstanding.

Regards,

David

Print this item