this topic is so helpful for technicians working in the landscape field. thank you for sharing!!!
@user-hf6ws9jn6f8 ай бұрын
Does your tool allow for isometric analysis between the existing and proposed? Eg in Civil3d it will allow you to colour code the depths of cut and fill across the site. The most deepest cut would be red and highest fill would be green
@Arch-Intelligence8 ай бұрын
Check out our Elevation Analysis. Let us know if this solves your problem: kzbin.info/www/bejne/eKnTmpqVm6-Lbassi=FTEhiWgPeKkis1F-
@siramehaboo8 ай бұрын
Is there any platform i can learn more about this, i already bought this soft
@Arch-Intelligence8 ай бұрын
Here's a couple of great tutorial playlists: kzbin.info/aero/PLgafqmBQgpHm-LjO5VE_EB1c5ei3KE8C6&si=oX9flTSLdrX7JRNe Or this one with tips and workflows: kzbin.info/aero/PLgafqmBQgpHlYgVw2rYR3hiMK9LN4NkDk&si=V7meeZnx3fHtNMdm Beyond that, we have a comprehensive user guide here: archintelligence.com/user-guide/
@adori1762 Жыл бұрын
I'm attempting to cut into a toposolid and usually without Archintelligence I would cut into the new terrain with void mass, but the issue was with fill which wouldnt work. Now with Archintelligence, the fill parameter works but im not sure how to get a cut to register, although a lot of times im getting a calculation error. What would be the proper way to cut into a toposolid, for a example for a basement.
@Arch-Intelligence Жыл бұрын
Hello Drori, The proper way to get the cut calculation of a basement is to simply model the basement with a new toposolid under its Floor. As long as you have an existing toposolid in your model the new toposolid will show you cut and fill. the meaning is that you dont actually have to cut into the existing toposolid. If you are getting the cut and fille error I would ask you to please send some screenshots to Contacts@Arch-Intelligence.com so we can take a look at it and see where is the error. Thanks for the comment.
@user-ke3dx3dx9n6 ай бұрын
its keep calculation failed
@Arch-Intelligence6 ай бұрын
These hiccups do occur occasionally. One suggestion would be to test if the function runs smoothly in a different file or on a different topographical element. Sometimes, complex geometry can cause such issues. The good news is, we're currently working on upgrading this feature. Soon, you can expect it to perform even better and be more accurate. Thanks for your patience! 💚