I have posted a test release for LDView 4.4 Alpha 6 to GitHub:

https://github.com/tcobbs/ldview/release...4.4_Alpha6

This release does have some known issues, but it also has quite a bit of new functionality, as well as some significant bug fixes.

Right now, I have only provided installers for macOS and 64-bit Windows. If you would like me to create an installer other than one of those two, please let me know.

The ChangeHistory.html file that is included in the release lists all of the changes. In the macOS version, ChangeHistory.html is in the dmg. In the Windows version, ChangeHistory.html gets installed to wherever you install LDView (C:\Program Files\LDView by default). I think the most important changes are:

1. Support for SPHERICAL and CYLINDRICAL texture maps.
   
2. Support for !DATA meta-command for embedding texture maps into MPDs.
   
3. Support for DPI scaling (AKA High DPI) on Windows, as well as Retina displays on macOS.
   
4. Support for macOS Finder thumbnail generation (toggle on LDraw tab of preferences).
   
5. Support for macOS Dark Mode.
   
6. Multiple important TEXMAP bug fixes.
   

Designer Sets

Hey,

just wanted to say that I started to work on a long-term alternative for LDPE, called LDPartMaker.
This "next-gen" version is an offline web application which runs inside a modern web browser of your choice.
LDPMs main focus should be usability and compatibilty to other operating systems like Linux and Mac OS X.
My personal purpose of this project is to learn something new about modern web technologies.

The big challenge of this project is seamless integration with the local file system.
A web application can't simply read your local LDraw library files or your local subparts from a project.
But, there is currently a very interesting WC3 draft on this "native file system access" topic: https://wicg.github.io/native-file-system/

Project advantages:
- Runs fast on any modern browser (in combination with a standard graphics card).
- Does not need additional runtimes (.NET Framework, JVM, etc.).
- Benefits from hardware accelerated 3D graphics and multithreading.
- Is a web application without the need of a connection to the internet.

Project disadvantages:
- Uses 'state-of-the-art' web standards and technology. It does imply that it probably will not run on older systems.
- The access to the file system is limited. We currently have to wait for the WC3 to finish its work.

Core technology:

• WebGL 2.0 (3D Graphics API)
  
• Angular 9 (Framework)
  
• TypeScript (Programming Language)
  
• HTML 5 File API / Native File System API
  
• WebWorkers (Muticore / Multithreading)
  

Hi all,

I am looking for this one
https://www.bricklink.com/v2/catalog/cat...4#T=C&C=80



Has it been made?

Hi all,

I have a model that has the part 572c01 in it.

LEGO part 14210: String with End Studs and Minifig Grips 21L
Bricklink Item No: 63141
String with End Studs 21L overall with Climbing Grips (16.1cm)
Alternate Item No: 76065, 14210

Is there a template for LDCad for this yet?
If not, can someone make it or tell me how to do that.

In the end, I need this part to go to Stud.io too to make render of the model.
Thanks!

Hi,

Is it possible to get 3813 Minifigure, Utensil Microphone (belville) in LDRAW?.

It's not urgent since I can use a simular part in place of it, it's for a gearbox, and the bar sized part goes inside of the bar hole of a technic knob wheel. I am using 22484 instead but it does not come in black and has no stopper unlike this, which comes in black and cant be pushed too far in .

Thanks, Snipe.

My usual approach placing rings is trail'n'error. I wonder if there is a mathematical way or even a tool which does it for me? I have these cylo:

1 1 50 -37 -10 43.75 0 0 0 0 -43.75 0 10 0 48\2-4cylo.dat
1 1 50 -37 -10 40 0 0 0 0 -40 0 3.125 0 48\2-4cylo.dat
1 1 50 -37 -3.125 40 0 0 0 0 -40 0 3.125 0 48\2-4cylo.dat


and need the external ring.

1 1 50 -37 -3.125 4 0 0 0 0 -4 0 3.125 0 48\1-4rin10.dat

is too large cos the distance is not 4 but 3.75. So ...

w.

Super Heroes sets

Hello everyone,
I'm new here and this is my first post so i hope this is at the right place I've scrolled the forum (it's dense, i have a lot of reading to do !) before writing this.
There's a lot of technical stuff here and i hope i will understand the answer because i'm not highly qualified in this field

Here is something i have noticed lately with the Studio renderer : i used the slope 28192 in my model and when i wanted to get a photo render i imported my mpd file in studio. It was ok, except for the 28192 part which was sitting above its correct position, and in a 90° angle. It was positionned differently than in my model in all three directions indeed.

I got it right by going back in my model and modifying the position of the part with the same translation (that is putting it lower and -90°).

Wondering why it is doing this ?
and if other parts are affected and then it could eventually make Studio renderer difficult to use ? Is it something this community can dosomething about or you would simply recommand i use another renderer ?

Thanks,
Gaelle