Recommended Posts

Posted (edited)
50 minutes ago, SylvainLS said:

I believe that’d be over the line of what is lawful.

Yes you are right. I didn't think of that :snicker:

Anyway here is the list so far:
part id => replaced by
30007 => 4215
32239 => 6588
41070 => 32008
45173 => 42060
46212 => 2454
47577 => 93565
52035 => 89536
57722 => 71986
59577 => 57558
60677 => 55676
60700 => 6015
61988 => 53788
63021 => 62699
63153 => 61804
64871 => 32278
82610 => 4034
86210 => 60603
86209 => 60601
88513 => 53451
88701 => 87777
89500 => 85961

There is another set of part IDs that are checked but those are not replaced by another ID, rather they seem to have a special behavior. I'll post what I find.

Edited by polymaker

Share this post


Link to post
Share on other sites
Posted (edited)
2 hours ago, SylvainLS said:

Whereas finding the list could fall under “interoperability,” I believe that’d be over the line of what is lawful.

(IANAL)

IANAL: How would a patch like this be different from patch of let’s say Diablo 2 that gives you unlimited money ? 
 

On another note i wonder why these replacement pattern were hard coded into LDD ?

Edited by M2m

Share this post


Link to post
Share on other sites
9 hours ago, M2m said:

IANAL: How would a patch like this be different from patch of let’s say Diablo 2 that gives you unlimited money ? 

I don’t know what needs to be done to Diablo 2 but if it’s a modification of the executable and you distribute it, it’s IP infringement.  And if there are protections against it that you need to break, it’s DMCA / EUCD.

IOW, it’s not because it’s commonplace to crack and hack games and that only the big bad players are sued that it’s lawful.

Share this post


Link to post
Share on other sites
Posted (edited)
2 hours ago, SylvainLS said:

I don’t know what needs to be done to Diablo 2 but if it’s a modification of the executable and you distribute it, it’s IP infringement.  And if there are protections against it that you need to break, it’s DMCA / EUCD.

IOW, it’s not because it’s commonplace to crack and hack games and that only the big bad players are sued that it’s lawful.

If you distribute the modified exe then yeah copyright infringement, I agree. And yes if there is effective protection against modification then its DMCA / EUCD.
 

But distributing a patch (or trainer program) that modifies the an executable shouldn’t be an issue as along as its not to circumvent effective copyright protection, so I’m not talking about a hack that disables copy protection (because this is illegal as you point out - at least in a couple of countries in Europe). Anyway it goes a little off the core topic of a Lego forum. 

Edited by M2m

Share this post


Link to post
Share on other sites
28 minutes ago, M2m said:

Anyway it goes a little off the core topic of a Lego forum. 

Yeah, but not so long ago, it was frowned upon to talk about customizing LDD here.  Granted, it was before it was officially abandoned.

Share this post


Link to post
Share on other sites
On 3/12/2021 at 5:06 AM, polymaker said:

part id => replaced by
30007 => 4215
32239 => 6588
41070 => 32008
45173 => 42060
46212 => 2454
47577 => 93565
52035 => 89536
57722 => 71986
59577 => 57558
60677 => 55676
60700 => 6015
61988 => 53788
63021 => 62699
63153 => 61804
64871 => 32278
82610 => 4034
86210 => 60603
86209 => 60601
88513 => 53451
88701 => 87777
89500 => 85961

None of these parts IDs (the left columns) is available in the Unity pack from Lego. Maybe they really don't like these parts for some reasons (quality, durability issues ?)

Share this post


Link to post
Share on other sites

Anyone have the latest LDD file? I need to add the new differential to LDD.. And the planetary hubs.. 

Share this post


Link to post
Share on other sites
On 3/12/2021 at 5:06 AM, polymaker said:

Yes you are right. I didn't think of that :snicker:

Anyway here is the list so far:
part id => replaced by
30007 => 4215
32239 => 6588
41070 => 32008
45173 => 42060
46212 => 2454
47577 => 93565
52035 => 89536
57722 => 71986
59577 => 57558
60677 => 55676
60700 => 6015
61988 => 53788
63021 => 62699
63153 => 61804
64871 => 32278
82610 => 4034
86210 => 60603
86209 => 60601
88513 => 53451
88701 => 87777
89500 => 85961

There is another set of part IDs that are checked but those are not replaced by another ID, rather they seem to have a special behavior. I'll post what I find.

Hey polymaker,The Brick Studio isn't compatible with the GPU from AMD on my computer,It appears to go into no-response after starting,But it working with the GPU from NVDIA,Can i do anything?

Share this post


Link to post
Share on other sites

Is it possible at all to change the default color of the bricks? I'd rather have them black over red.

Share this post


Link to post
Share on other sites

Heya good people!

 

Encountered a bug with the same part I requested last time:
ebdb62b1b0073ac97e5433d2672699c5.png

It doesn't seem to be working with the cross-axle attached to 11214 (displayed above). Dunno what's wrong.

Share this post


Link to post
Share on other sites
6 hours ago, The Mugbearer said:

It doesn't seem to be working with the cross-axle attached to 11214 (displayed above). Dunno what's wrong.

I will look into it!

Share this post


Link to post
Share on other sites
18 hours ago, The Mugbearer said:

The 6542 GEAR WHEEL Z16-Ø4.9 seems to be lacking technic pin connectivity.

Yes, I think it is illegal in real life to do that since the pin remains compressed due to the teeth.

10 hours ago, GeorgeVB said:

would new road plates be included into the next update?

I might be able to include them (with prints as well).

Share this post


Link to post
Share on other sites
On 3/30/2021 at 7:07 AM, Stephan said:

I will look into it!

Fixed. New files can be downloaded from Github Pre-Release.

Share this post


Link to post
Share on other sites
11 hours ago, The Mugbearer said:

The one I had problems with in LDD is this

I will check this!

Share this post


Link to post
Share on other sites

Hey, since the LDD-to-POVRay converter needs to refer to the original lib.DLL as a conversion reference, and it's not compatible with the modded parts (I kept it, and renamed it, as a backup), I can't use the converter in order to render scenes that utilize all of these great new pieces. Are there any workarounds for this? Any alternative rendering solutions I can start learning about?

Share this post


Link to post
Share on other sites
10 hours ago, Eggyslav said:

Haven't heard from you guys lately, how's the new update coming?

New parts are building up nicely. Two handfuls of new parts, updated new parts, updated original parts, and a bucket load of new prints. The update that you are used to comes in about two weeks. In the meantime you can download all new parts from my pre-release Github.

Share this post


Link to post
Share on other sites
3 hours ago, ForteNoir said:

Hey, since the LDD-to-POVRay converter needs to refer to the original lib.DLL as a conversion reference, and it's not compatible with the modded parts (I kept it, and renamed it, as a backup), I can't use the converter in order to render scenes that utilize all of these great new pieces. Are there any workarounds for this? Any alternative rendering solutions I can start learning about?

Stud.Io's Eyesight Renderer is your best friend. You can do it like I do: build MOCs in LDD and then export them to Stud.Io for rendering and other features LDD doesn't have.

Share this post


Link to post
Share on other sites
2 hours ago, The Mugbearer said:

Stud.Io's Eyesight Renderer is your best friend. You can do it like I do: build MOCs in LDD and then export them to Stud.Io for rendering and other features LDD doesn't have.

Stud.io absolutely butchers my LDD builds when it converts an .LXF. I don't like it, I don't trust it.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.