You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In dealing with extremly complicated models, thousands of faces, it would be very helpful to look up exact position on the screen or printed views, to match all the angles, not just right edges. Is it possible to implement a script that will re-index edge indices, to match those in viewport?
And after that, would it be possible to export ortho views with those numers attached?
End result I look for is like this pdf: RZUTY.pdf
Is there a way to make it like... a paid request for priority?
The text was updated successfully, but these errors were encountered:
Wouldn't it then be more useful to straight up print the angles on the edges? Like negative degrees for mountain folds and positive for valley or smth.
Indeed, that would have been most useful too. Nevertheless, plans and views would greatly simplify working with them - welding it all together later (laser cut metal plates, complex).
A little thing you can do is to save the UV layout during export and use "Sync UV Selection" to find the edges in 3d. It's far from perfect but it has helped me many times -- I have made some complex models myself.
If the edges were numbered as you suggest, how would you find an edge in the ortho views? I'm afraid you'd have to search through the whole image... that seems quite too slow.
In dealing with extremly complicated models, thousands of faces, it would be very helpful to look up exact position on the screen or printed views, to match all the angles, not just right edges. Is it possible to implement a script that will re-index edge indices, to match those in viewport?
And after that, would it be possible to export ortho views with those numers attached?
End result I look for is like this pdf:
RZUTY.pdf
Is there a way to make it like... a paid request for priority?
The text was updated successfully, but these errors were encountered: