Ahh Ok. I wasn't even looking in the Window menu. Sorry. My mistake. I was to strict following the manual. I'm aware of the toolbar issues. I was at Epic during the 5 launch until last year working on engine content, demos and tech talks.
After tinkering with it today in 4.27 I realized its static meshes. Got something running which makes me quite happy.
As occlusion is a bit of a problem with all the small pieces now, I'm trying to use the old precompiled visibility route before looking into merging more stuff together.
I'll test UE5 tomorrow.
Thanks for the fast reply!
In my experience, you need to do quite a bit of grouping in Hammer before importing your map, otherwise the default culling can't keep up with all the separate parts. Keep in mind that every brush you import is both a new static mesh actor and a new asset, so optimisation goes out the window if you just import everything separately.
Yeah, I'm aware. Thanks. I will try different methods.
- Merge in UE with build in functionality
- Merge in UE with an own geometry scripting tool
- Try to use the old "compute visibility" route generating a grid (should be still in the engine for mobile)
- trick the occlusion algorithm in UE to be more loose
- and last resprt would be going through the huge maps by hand and make groups (it's not Hammer but NetRadiant for ET