Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Just to double-check: after the UI change in UE5, HammUEr (and all my plugins, really) only has the menu option at the bottom of the Window list, which definitely should exist?

I was... annoyed that they changed up the whole toolbar button code with the UI changes and just broke it, but not the menu option, and never really... bothered to try bringing it back, since nobody really seemed to be missing it? (I think there might also not have been like, an example of the New Correct Way in the first version of 5.0, but that might just be my faulty memory)

Sorry.
Hopefully that unblocks you, at least.
If not, we have... deeper problems.

Maybe I'll re-add it down the line somewhere.


Also: HammUEr doesn't really touch any of the UE BSP stuff (because it has always been a massive pain), everything gets imported as static meshes

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

It's indeed in the Window menu. Really sorry. I overlooked it.