Regarding the offset placement when replacing a whole "component" instance with another, it is probably all down to the component set's internal origin point (it's own internal axes nexus, relative to itself) within the 3D modeling source. The replacement probably gets added at the component's on "0,0,0" origin point.
Thanks for the great video. It would be so much better if TwinMotion treated each "component" as an editable component! Then when you add a light source to one instance, all instances get the same light source added. Object oriented. It's shocking to me how broken their way of doing it is. In the meantime, if you were to add a "placeholder" item inside the light fixture component (in the 3D modeling application, Revit, SketchUp, etc), placed where the light source will eventually go via replacement, and then in T.M. replace only that added bit (in each instance), it *might* be less labor intensive.
Hey thank you for the great video. Do you know how to fix the outside lighting in the night because it is always bright, in the version of 2019 it is actually dark..?
That is a tough one, I need to do more research on that. There is auto exposure set to all views and there is not a great way to override this besides the exposure in the image settings. Try that first but I will have to look into the overall issue.
@@ArchitectureVanguard thank you for your answer, Just wanted to say that i read about it, and you can't fix this problem in the new version they will maybe make an update version
Yes that is because the direct link does not allow this to happen. When the Datasmith link/importer is available for Rhino, that will allow you to replace.
Check the export settings in the Twinmotion addon in Revit. My guess is that "Export" MEP families is unchecked. This means your light fixtures would not export to Twinmotion.
I learn many thing ! Thanks !
You are good for explain its very clean 👌
Well done 👍
Thanks so much Jean, very nice to hear that!
thank you! really helpful, hoping to see more revit-twinmotion tutorials
There’s more on the way!
This is great, thank you!
Glad you liked it!
Regarding the offset placement when replacing a whole "component" instance with another, it is probably all down to the component set's internal origin point (it's own internal axes nexus, relative to itself) within the 3D modeling source. The replacement probably gets added at the component's on "0,0,0" origin point.
Thanks for the great video. It would be so much better if TwinMotion treated each "component" as an editable component! Then when you add a light source to one instance, all instances get the same light source added. Object oriented. It's shocking to me how broken their way of doing it is. In the meantime, if you were to add a "placeholder" item inside the light fixture component (in the 3D modeling application, Revit, SketchUp, etc), placed where the light source will eventually go via replacement, and then in T.M. replace only that added bit (in each instance), it *might* be less labor intensive.
Hey thank you for the great video. Do you know how to fix the outside lighting in the night because it is always bright, in the version of 2019 it is actually dark..?
That is a tough one, I need to do more research on that. There is auto exposure set to all views and there is not a great way to override this besides the exposure in the image settings. Try that first but I will have to look into the overall issue.
@@ArchitectureVanguard thank you for your answer,
Just wanted to say that i read about it, and you can't fix this problem in the new version they will maybe make an update version
I tried creating new objects on Rhino then syncing with TM and replacing them with lights however, when I click Start Replacement, nothing happens.
Yes that is because the direct link does not allow this to happen. When the Datasmith link/importer is available for Rhino, that will allow you to replace.
hi my Revit light fixtures aren't visible on twinmotion
Check the export settings in the Twinmotion addon in Revit. My guess is that "Export" MEP families is unchecked. This means your light fixtures would not export to Twinmotion.