New Unreal Brick Builder

[Chief]

Hello there!

I am working on a Brick Builder that works in Unreal Engine 5 called the "Click It" system. It utilizes the LDraw library and lets users import Stud.io files or build their own creations from within the Unreal Engine (no Blender steps needed). It is still very WIP but I wanted to share some screenshots of the builder and get some feedback on common features and functions people like to have so I can make it the best it can be!

Youtube video of builder: https://www.youtube.com/watch?v=y9fP4SOn...NewHorizon

If you don't want to use the link, search "Veins of a New Horizon" (my youtube channel) and click on the " Click It" Digital Brick Builder Update video. 


Here are some screenshots of the builder loading files from Studio, the last couple ones are in UE in the game we're making to go along with it. Apologies in advance for the quality, the limit on posts is brutal at times

   
  84_TT_GG.PNG (Size: 220.64 KB / Downloads: 84)                    

[Hageta]

Does it support textures (either LDraws !TEXMAP or Studios version)?

Does/Will it support primitive substitution to show higher quality models?

[Chief]

Does it support textures (either LDraws !TEXMAP or Studios version)?

Does/Will it support primitive substitution to show higher quality models?

I am currently working on a better disconnection system but texture support (tex map) is planned along with a special stud and tub removal system. There are currently two different supported model variations: low and high poly (similar to Stud.io's versions) with each supporting a smoothed variation. Currently working with the dev who designed the meshing components used to support lines for better part delineation as well.

Here's an example of the higher poly model without smooth shading     

I am not as familiar as I'd like to be with Stud.io's texture system, if you have any pointers I'm all ears!

[Hageta]

I know that buildinginstructions.js supports on older version of studios texture format, but I do not think it supports the current one.

PS: I wish studios extionsions to LDraw were properly documented

[Jeff Jones]

i would like lgeo and maybe something similar to ldd's hinge align tool/sr3d builder and maybe real time cloth/hair physics

[Orion Pobursky]

PS: I wish studios extionsions to LDraw were properly documented

Please post this on their forums and other places. If enough users complain they might actually document things and make the program more LDraw compliant.

[Chief]

i would like lgeo and maybe something similar to ldd's hinge align tool/sr3d builder and maybe real time cloth/hair physics

We will be adding support for hinges and movement in general. The data model we are using to support the builds allows us to get away with millions of triangles in a single screen but makes adding movement and other environment interaction elements more difficult than you would get with a simpler approach. At the end of the day, our goal is to let people take their LDraw, Studio, and UE generated models and simulate them actually doing the thing they were built to do. Want to make a crane? Can do, spaceship? Already done. Conveyor belt? In progress. 

Regarding cloth and hair physics, it's in consideration but way down on the list of things to add. The focus right now is getting performance up while keeping performance in a good place. For a build size example, that LMS Explorer picture over a planet was a screenshot being captured at 30FPS with an unoptimized LMS Explorer containing well over 3 million triangles just in the nose of the craft while rendering the planet in the background. We want to keep that build size while making performance better overall AND add the other cool stuff (so to answer your question, I want to, it will just take time)

Hope that answers your questions, I really appreciate the suggestions and I'm keeping tabs on what folks mention to make sure it gets added in the future!

[Chief]

I know that buildinginstructions.js supports on older version of studios texture format, but I do not think it supports the current one.

PS: I wish studios extionsions to LDraw were properly documented

I did some consulting with a teammate and we are currently looking at two options, the first is the Text map from LDraw but the other will be a more UE compatible/friendly vector graphics approach to enable users to interact with the textures. Something I didn't mention in the main post is the desire to enable people to actually interact and use their builds within a digital sandbox. This means if you make a button, you can make it do stuff, that goes for buttons on textures too. But to enable that kind of functionality, you need to change how you store and represent the textures. So in all, we're aiming to support TEXMAP but our focus will be primarily on moving towards a vector graphics and interaction based approach to enable you to use what you build, not just look at and admire.

Hope that answers your question from earlier!