Hi John, I am part of the Epic Games Datasmith dev team and came across your video. Its great to see some tutorials being made on that topic! One comment that I wanted to make is related to the location of pivot points and "random" location. I wanted to give some context around this: a) Rhino don't provide access to pivot points (gumball location) through the 3dm API. To avoid importing all objects with a pivot at 0,0,0 we are computing the pivots using the center of the bounding box. Maybe we should have computed it to the lower corner of it instead. Anyhow that has the advantage of keeping the pivot close to the object and solve some UX issues that otherwise would be showing up. b)The downside, as you correctly pointed out is that the location appears random. However, if you accidentally moved the object, there is a tool for this with datasmith. Right click on the actor and go to Datasmith | Reset Overrides. This will move the object back to where it came from. Datasmith keeps track of local overrides for pretty much anything and you can always decide if Unreal changes wins over Rhino (or revit or anything imported with datasmith). Hope this helps!
hi Pierre! thank you so much for the explanation! we actually spoke once before I think... anyway, thank you for sharing the reset overrides option - I will pass this along to my students for sure. I am sure you're inundated with requests but on the topic of pivots, one thing on my wish list is to have a way to relocate the pivot more easily to the bottom center of the bounding box of an individual object - for positioning of furniture specifically. I know you can reset the pivot but the current method is a bit strained....anyway thank you again!
@@johnford8425 Thanks! Rest pivot in the editor is a long time request. However calculating the pivot to the center bottom would make most sense by default. I'll make not of this in our feature tracking system
Hi John, I am part of the Epic Games Datasmith dev team and came across your video. Its great to see some tutorials being made on that topic! One comment that I wanted to make is related to the location of pivot points and "random" location. I wanted to give some context around this:
a) Rhino don't provide access to pivot points (gumball location) through the 3dm API. To avoid importing all objects with a pivot at 0,0,0 we are computing the pivots using the center of the bounding box. Maybe we should have computed it to the lower corner of it instead. Anyhow that has the advantage of keeping the pivot close to the object and solve some UX issues that otherwise would be showing up.
b)The downside, as you correctly pointed out is that the location appears random.
However, if you accidentally moved the object, there is a tool for this with datasmith. Right click on the actor and go to Datasmith | Reset Overrides. This will move the object back to where it came from. Datasmith keeps track of local overrides for pretty much anything and you can always decide if Unreal changes wins over Rhino (or revit or anything imported with datasmith).
Hope this helps!
hi Pierre! thank you so much for the explanation! we actually spoke once before I think... anyway, thank you for sharing the reset overrides option - I will pass this along to my students for sure. I am sure you're inundated with requests but on the topic of pivots, one thing on my wish list is to have a way to relocate the pivot more easily to the bottom center of the bounding box of an individual object - for positioning of furniture specifically. I know you can reset the pivot but the current method is a bit strained....anyway thank you again!
@@johnford8425 Thanks! Rest pivot in the editor is a long time request. However calculating the pivot to the center bottom would make most sense by default. I'll make not of this in our feature tracking system
Oh, if I am not wrong, especially for furniture. if the geometry is in a block, we preserve the pivot of the block in some way. Maybe that helps.
rhino is great software for design, and now we can see design in realtime. thank for your video
Hi John, I see your model is converted into Mesh before using Datasmith. Does it help fix UV importing issues in UE? thank
No Datasmith showing up in Unreal 5.3... tried on 2 machines
Thanks