For a project I'm currently working on I'm looking for a quick and easy way to get rid of inside geometry of a house model.
This house model has everything in it, floors, inner walls, stairs, kitchen, you name it, but I want to remove all geometry on the inside so I'm basically left with just the "shell" of the house. say if you would "submerge" the house underwater, everything touched by the water I want to keep, the rest I want to be removed (maybe a weird explanation but I hope it's rather clear what I mean).
Because I need to do this process on a lot of different house types, it's simply too much work to do this manually by hand, and I'm therefore looking for a method which can do this quickly.
I use 3ds Max for my modeling, but solutions in different software, for instance Meshlab, are fine too!
Thanks in advance,
Maik Bentlage, iBuild
For a MeshLab solution, this blog entry describes a method to use ambient occlusion to remove interior vertices. In MeshLab 2016.12:
Filters > Color Creation and Processing > Ambient Occlusion
Filters > Selection > Select by Vertex Quality. Play with sliders to select low quality values, i.e. all the interior vertices that are not visible (try min 0, max 0.1).
Filters > Selection > Delete Selected Vertices
This isn't a perfect solution, but may be good enough for your needs. If you can determine a max quality value that works consistently for your models, you could easily script this for batch processing.
It really depends upon how each house was created.
If it’s a hierarchical approach, i.e., the house is a parent and models inside (kitchen, floors…) are children, then you can easily use a simple MaxScript such as this one to delete all children from your scene (inspired by this thread from cgsociety) :
global meshes_list=#()
fn selecting_children ancestors =
(
for i in ancestors do
(
counting = i.children
if counting.count>0 then
(
for x in counting do
(
append meshes_list x
)
)
)
return meshes_list
)
rollout hierarchy_rollout "Hierarchy Operations"
(
checkbox Checkbox_DeleteSelection "Delete Selection" checked:false
button select_children "Select All Children"
on select_children pressed do
(
select objects
sel = selection as array
x = selecting_children sel
select x
if Checkbox_DeleteSelection.state == true do
( delete selection )
)
)
createDialog hierarchy_rollout 200 150
Just make sure that you don’t end up deleting other meshes or houses as well!
If they are not hierarchically ordered, then you can Select by Name (press H) and delete everything manually, but more quickly than selecting them one by one with your mouse.
If the whole house is a single mesh (including props inside), then I am not aware of any existing way to automatically delete everything inside. You can still select by Element (after converting it to an Editable Poly/Mesh) and, after selecting the house (assuming it's a single mesh), pressing Ctrl + I for inverting selection and delete everything. But it’ll still be time consuming.
A workaround might be to attach every house into one gigantic mesh (just open the attach list to select everything at once) and to use the rectangular selection to select only the highest part (which should isolate props or most of them) of everything, in the Left or Right Wireframe Viewport, and then press Ctrl + I.
Related
First of all, I don't have a reproducible example as I am still thinking about the structure of my future dashboard. Here are the requirements:
using a menu on the left (currently thinking about dashboardSidebar() from shinydashboard) with 4 different items: filters, comparison, prediction, and data. Each item has subitems that applies to the current dataset (set of filters, chosen comparison variables)
tabs for each product category (e.g. one tab for fruits, another for veggies, another for meat, etc...). I've read that it is not recommended to use tabset() from shiny with shinydashboard components.
The idea is that the components on the left menu apply to the current tab, but the menu is the same across all tabs.
Here is a visual example of what is expected:
ideal dashboard structure
I am new to Shiny and would highly appreciate the hints from the experts out there. Thanks!
I have been following an old guide ( https://blogs.sap.com/2012/03/22/add-custom-field-to-sc-and-powl/) to add a field to POWL but it doesn't work in my case.
It is required to add the "Supplier product number" to the layout.
Since it's an existing field, I thought it was simple. But it's not the case. Following the guide, the field required is in the structure "/SAPSRM/S_POWL_RESULT_SC_ITM", so no need to add it.
Next, in SPRO, Adjust POWL Layout, Search Criteria, and Pushbuttons, I added the field to different feeders (because it didn't work for any of the feeders I found, I thought it wasn't the right one .. so I played with all of them)
a)
b)
c)
After this, the next step is to check in program POWL_D01 the query that might be cached for this layout and to delete the cache. I deleted all the cache data related to the queries "SAPSRM_FEEDER_SC*" and the result is ...
The field is nowhere to be seen in my layout.
Could you point me into the right direction ?
Regards,
Marius
Hi I am new to blue prism
My question is:
I have button in my application after recording if i try to highlight it is working fine but while executing it is not able to click the button and i am not getting any error.
If you provide a screenshot of the attribute list in your application modeler, it might be easier to provide an accurate answer. However, for now, I can give you some pointers:
For most applications the following can be unticked:
any elements with a blank value
all 'Parent' attributes unless
required to make the element a unique match
the 'Visible' and 'Enabled' attributes usually have no impact if left ticked or unticked, so can often be unticked
With any attributes which may not be persistent and could be prone to changing — i.e. element count, application’s URL, etc.—, it is recommended to untick them or, if required in your process, use the wildcard match type to dynamically build the corresponding values which will allow easy identification.
To speed up finding the elements, it is recommended that the Match Index attribute be used when possible. This works by stopping Blue Prism from trawling through the application model for duplicate elements once one matching element is found.
It is also recommended to add a wait stage at the start of each action. This will handle system latency and provide a correct path for your process:
The above are some pointers that I have consolidated for your ease. However, all the help you need can be found on the Blue Prism portal itself : Blue Prism Documentation
Hope this helps.. Good luck!
I just started using Dia. I'm trying to build a sequence diagram. I would like to represent self-calls. How does one do that in Dia? I can't figure it out.
Thanks.
First place a UML Message object with it's base attached to your lifeline.
Then, double-click the arrow (or right-click, Properties), and change the Message Type drop-down field to Recursive, and you'll get something like this:
Now you can drag the green anchor point around to make the Message arrow look as you'd like. (A note of caution: it seems that with a Recursive Message object, you can ONLY select the object by clicking on it exactly where the green anchor point WOULD BE. I say "would be" because of course you can't actually see that green anchor point when the object isn't selected.)
If you like, you can create another UML Lifeline object, and place it overlapping the existing lifeline, like this:
This isn't ideal, though, because there isn't actually anything attached to this second lifeline. The Recursive Message object doesn't let you choose where to attach it's arrowhead, because it's automatically attached to the lifeline from which it originated. And because the second lifeline isn't attached to anything, if you go moving objects around it will get left behind. But, it does look pretty, if that's what you're after. :)
A self call(or any other association) in UML is better expressed using the standard association notation instead of the message one. In DIA, insert an association notation from the toolbox on the left and add it to your canvas. Then in order to have it connect a class recursively(to itself) double click it and click select "Autoroute" as no. This will enable you to shape the route yourself and wont constrain you to the automatic straight line that gets drawn when linking a class to itself.
You would end up with something like this(in this example its a representation of a Node in a linked list):
Evenings chaps,
I'm using XCode4 to model my entities, but I cannot figure out how to change the cardinality of the relationships so by default they are all 1 to 1 relationships. Someone give me a hint on how to change it please :)
Are you seeing a straight line with one arrowhead? That's 1:1 already and is the default.
To set 1:many, one way is to select the relationship and in the right view pane (you may need to turn it on by clicking the right hand button in the view section in the toolbar) select the rightmost of the three icons at the top. You should see some options under "Relationship", including "Plural" (Maybe "Cardinality" was too long).