Hi Astrid, yes, I noticed that the new version 2406 is trickier to import files from rhino, it only accepts the x_t format for my case. I did not realize that the importer could impact my models this much, although I did try some trial and error in the surface repair which was not too impactful. Thanks for the advice!
1 Like
Hi @encephalon, I appreciate your feedback and I’m sorry if my previous message came across the wrong way. I didn’t mean to downplay the issue or the effort involved—I’m still very much a novice when it comes to Rhino and 3D modeling in general.
I did try looking for solutions on YouTube and attempted to fix the naked edges myself, but it quickly became clear that it was beyond my current skill level. That’s why I turned to this community for help, hoping to learn from the expertise here. I definitely didn’t mean to waste anyone’s time, just looking for guidance to better understand where I went wrong so I can improve in the future.
Thanks again for pointing it out, and I’ll be more careful with my approach going forward!
1 Like
Hi @lander I truly appreciate the video tutorial, it has been extremely helpful! I did not realize that I could/should fine-tune the meshing according to the surface that I am interested in, all along I thought that the settings would be fixed and applied to the entire modelling. Thank you for taking the time to help me out, I hope I can reach that level of skills in my future attempts (fingers crossed)
sorry if that comes across persistently harsh, but your model is such a mess, if you are such a novice, how did you end up working for/with somebody that is involved in simulations?
while that is not for me to judge, your ship basically shows that one would have to train you from scratch and coming in with such a big model that falls apart on all ends is probably quite a rich statement on how you neglected to try and learn the basics of rhino at least.
nevertheless if it is not about trying to actually learn modelling but just to use this mess for simulations with the least possible effort download a V8 trial and try shrinkwrap that will make a mesh out of your geometry but will most likely ensure that all open edges will be closed, i assume mesh is used for simulation anyway.
This is the best community I know of. It’s hard to put words to it. But it’s clear Rhino is the best CAD. 
I just wish I could upload vids at more than 20k KB at a time lol.
here’s some other stuff I did:
and that sums up to about 50% of what I did.
I’ll have to research video quality techniques to conform to this 20MB limit better rofl.
2 Likes
I guess it’s a tradition on this forum to insult people those who don’t know much about Rhino
Appreciate the advice!
My colleagues said the same thing, that Rhino is the best modelling software out there! Your videos have really highlighted the capacities of it, and also helped me out tremendously.
1 Like
yes indeed. i saw you reacting extremely snobbish to someone trying to help you in at least one other topic very recently. and besides contributing zero to this topic you generally only seem to be coming if you need help yourself but never contribute to others problems. not a perfect reference for judging others.
that is where i can point out how well Mia here actually reacted to stern and honest replies, take her as an example maybe.
Show it to me ? When i was “extremely snobbish” ? You talk jtst to talk…
Your arrogance is insurmountable
And why you offended?
OP was insulted. Yes zero contribution because i gave almost zero knowledge but at least im not blind.
Stop looking down on people and scolding them for they dont have knowledge.
Show here where i was extremely snobbish im waiting.
1 Like
the mentioned reply of yours is just 3-4 days old, that tells me what a clean conscience you must have.
i hope not
i think this topic takes an end for us here, please proceed writing in pm if you have to.
you clearly make a good part of the amazingness of this community. It’s much work you’ve put into this to help OP, that’s really cool. Just wanted to mention it.
Also: @encephalon is a much loved and rather constructive member of the community, too. He was just being honest, poor OP should never have gotten such a messed up file to start into Rhino.
1 Like
Yes, this is a big issue for our firm since we often use Rhino to create coplanar surfaces and apply naming conventions in Rhino. However, the HOOPS importer is still available in the new STAR version, but you will need to write a script to get STAR to utilize it properly. Another issue is that Rhino now merges surfaces whenever performing a boolean union, which is also very disruptive to my workflow. This can lead to extra work, as I often have to manually separate surfaces again to maintain the integrity of the geometry.
I’m going to participate in a Rhino webinar in November, where we’ll discuss CFD and CAD, and I will definitely talk about some of the issues I’ve encountered in STAR. But you’re right—using the x_t format does result in surfaces that are easier for the Siemens adapter to interpret correctly.
1 Like
I also enjoy working with coplanar surfaces to create closed polysurfaces, which I then export to STAR-CCM+. In terms of Boolean operations and assigning parts to regions, I tend to handle those tasks within the STAR-CCM+ interface, especially using the Surface Repair to manage any issues that arise (trial and error really). Nonetheless, I do hope that you’ll have a fruitful discussion during the webinar!
I think it’s pretty common to struggle with files transfers between different programs. I often struggle to export STEP or x_t, so that it can be imported into Creo (the watchmakers prefered program) for example. Still waiting for the omnipotent file format 
1 Like
It is fun because when I build the surface differently, say I use edgesrf instead of network surface and one of the curves has an arc. Siemens adapter has a harder time reading it in step then if I did a networksrf.
Siemens adapter where i used edgesrf and networksrf and it gives different result reading the surface (the edgesrf command give a completely wrong result)
in hoops it is a bit more foregiving regardles of the way the surface was build
But I hope onces siemens have a look at the critique I have sent regarding the difference in HOOPS and their adapter it will soon be better again. It is a big problem with the naming and removing of the coplanarsurfaces, since we use those a lot.
I think the reason why x_t works so well is because that format is from a siemens program. But that is just a theory. I try not to use it since rhino cant open the format and if one of the CFD engineer has a problem I like being able to look at how it translated the file from rhino to new format.
1 Like
That should not be a problem anymore. An option to BooleanUnion was added to allow you to turn this off:
3 Likes
Yes. I learned that yesterday. I just always used that function by clicking on the geometries before the boolean union button, so I didnt see that options had been made 
1 Like
NetworkSrf always results in a degree 3, non-rational surface; independent of the degree of the input curves and if any were rational. Note that NetworkSrf may not exactly match the input curves.
EdgeSrf results in a surface or polysurface with degree(s) dependent on the input curves. In each direction the degree of the result will be the highest degree of the corresponding input curves. Also if on input curve is rational the surface will be rational, and the result may be a polysurface. EdgeSrf should exactly match the input curves.
The Siemens adapter may not like rational NURBS surfaces and/or other that degree 3 surfaces.
2 Likes
That make sense 
. I have not looked into the underlaying way the different surfaces are made. I could just conclude that arc and lines in edgesrf is not something that works well in siemens, so I made the surfaces another way.