[kvloover]

I'm modelling the flow over a fin with louvers and added an inlet and outlet region with different meshing.
I did this by adding a frozen geometry infront and gave them a seperate automatic method in ansys mesher (as shown in http://www.youtube.com/watch?v=RELLrEJ9chg starting 9:45). The mesh looks good in ansys mesher but when I open fluent I get these errors:

Warning: Flow boundary zone 33 is adjacent to a solid
zone (9). This problem MUST be fixed before
solution can proceed!

It seems that a wall was made at the outlet face (33) aswell as the outlet boundary condition. So I managed to fix this changing the boundary on 33 to an interface.

However it seems I'm having the same issue with the interfaces between the outlet region and the actual fin region. But there I can only chose between:
*fan
*interior
*porous-jump
*radiator
*wall

It also has a shadow zone on the same places (I presume one due to the face of geometry 1, other of geometry 2)

I figured interior would be suitable, but can't change it as it spouts the following error:

Cannot change wall-part-2-part-solid to interior because
adjacent cell threads are of different types

How can I remove these "walls" and still have seperate meshing zones
(hex in inlet/outlet, tet in actual studied geometry)?

[kvloover]

Or perhaps a better question:
What is the proper way one makes different regions for different meshes from one geometry ?

(if making them multiple frozen geometries isn't sufficient)

[kvloover]

ok so i managed to get rid of the flow boundary errors for now by removing the nozzle (part was also made wrong, it seems, in ansys geometry)

The only problem remaining is the interfaces between the inlet and outlet regions. Does anybody know how I can resolve this?
Or perhaps the standard way of making multi-regions (seperate mesh types) ?

I'll post a pic of it when I get back home.

[kvloover]

and seems to be fixed (for now):
forgot two things
- make the added parts fluid (default to solid)
- make the parts into one multibody part (takes care of the interfaces)