2019-06-20 08:01 PM
2021-09-23 03:56 PM
Hello Everybody,
GO have brought a real change in the visualisation of information and the communication around the Project. Unfortunately, the limitations described here pose certain limits.
2021-09-23 04:12 PM
A few work arounds for your scenario until the wish is one day granted:
If all 8 houses will keep the same surface, but you want to show different variants: create multiple building materials and swap out the building materials in the composite / complex profile. You can hotlink your houses to different variant PLN files to show these.
If you need multiple unique houses in a row: split up the exterior and interior into two modules and make variant modules. You can nest the interior module back in to your exterior module. You can change the hotlink of the houses to the different hotlinks with the different finishes.
These do take a little bit more time than 'just an override', but are still reasonably fast and hopefully helpful if you hadn't figured out a similar approach yet!
2021-09-24 02:45 AM
@Anarchiteckt wrote:
And the surface painter doesn't affect the Modul file...
No, it won't.
Just like any other change you want to make to a hotlink module, you would have to do it in the original module file and then update the module in the master.
If it is just a case of exploring materials in the overall master file, then maybe work on a copy of the mater file, break the hotlink and then surface paint your changes.
Once you have decided on the correct materials, you can then go back and edit the original hotlink, and then update the original master which still contains the un-broken hotlinks (hence working on a copy).
Barry.
2022-09-26 03:22 PM
Surely the simplest solution would be to allow a GO to work at the polygon level? Ie search the scene to find any polygons using Surface A and override them with Surface B. I use them a lot for visualisation 'styles' but windows and curtain walls are a real issue - using a GO to change the glass surface also changes the frame. This is a real limitation, but working at the polygon level would solve this without any extra complexity in the GO interface.