Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs

NT Entertainment

96
Posts
144
Followers
3
Following
A member registered Feb 25, 2016 · View creator page →

Creator of

Recent community posts

Sorry, no.
You *can* convert your materials from UE to Source to some extent to help with visualization, but that's it.

HammUEr explicitly doesn't read compiled BSP files, only source files for maps, sorry.

Unfortunately, Source 2 support will never be added.
Sorry.

Thanks.
Yeah, there's no animation support in HammUEr, and I'm guessing this one has no mesh information at all.

Yes, eventually, when there's a "proper" one and no longer release candidates.

Not... sure?
I'm going to need more information that "it always crashes when importing models". What models? Are there any error messages?

Sorry, most of the settings were moved to an actual unreal settings page in the most recent version, so you can find everything in the actual project settings now

Sorry, most of the settings were moved to an actual unreal settings page, so you can find everything in the actual project settings now

Not... sure? 
I mean, it compiles locally with launcher UE4, and has since the very first version, so...
That line number doesn't seem to match with latest source, and you didn't specify *which* UE4 you're trying to build for, so I have no idea where the problem could be...

Anyway, find any public class property that's a UPROPERTY but doesn't have a Category = "<something>" bit in it like all the others, and add one I guess, see what happens?

Hopefully the switch to VTFLib fixes this.

Not... explicitly no, sorry.
Could maybe look into this for the next version.

I'm... unsure.
I know that Valve models sometimes have different names inside of them than the one the map expect, so you might have to look for the closest matching one and copy/rename it?

Hi!
I've updated the default algorithm in the new Back to School update for 4.26 and 4.27, which should hopefully take care of this problem for you.

I'll do some investigating while I do my rewrites for UE5, and release the same changes in an UE4.26 version

I will be releasing an UE5 version down the line.
I've got a preliminary port working, but I'm going to take this opportunity to rewrite some things, and the current EA build is... not very plugin creation friendly.

I don't think I changed anything in how the model importing code works recently...
You have any more information for me?

The Christmas versions should now import your 220 maps without problems.

Sorry for the slightly longer delay, there were a few other fixes I wanted to get in, and then the pandemic got in the way.

(1 edit)

This should hopefully be fixed with today's Christmas Fixes, if it's the same problem as REVEL303 had downpage.

Sorry, that's one I've never seen before.
I'm guessing one of your textures is broken, or not supported.
Try checking the log to see where it fails, or try breaking up your texture directory in a couple different ones, and then import them one by one to try and narrow the problem that way.

(1 edit)

Thanks, that helped me track down the problem.
I've got a fix that'll go in the next fix drop for 4.25 (around 4.26 release, so hopefully soon).

A workaround that _might_ work until then is to add a "wad" property, so it forces the parser down the classic map path...

Strange.
As far as I remember, it should autodetect Valve 220 maps, and the Q1 rotation stuff should only be necessary to make things line up as expected, not ungarble UVs completely.
Can you pastebin (a section of) the map with the problem so I can test it locally? (with a list of expected texture sizes)

Sorry, no support is planned for exporting anything from compiled versions of Source maps.

I'll make some changes to how HammUEr handles the waaay too short internal names for models in the next build, which should... hopefully go live by the end of the month.
I remember there was a reason why I kept it to the internal name by default, but I don't remember what it was, so...

(1 edit)

Think it depends on what your brushes look like, how you used the nodraw options for them and if they're grouped or not. There's also smoothing/normal options on the ConfigUEr tab you could experiment with.
Other things you could try on the UE side is to maybe join the two meshes together, and let UE recompute the normals itself.

Do you mean VMTs?
It should support a subset of them, at least.

If it's your own game and assets, that's down to whatever engine licensing deal you have going on.
If it's not your own game and assets, then... no? Absolutely not? Because that's illegal and this shouldn't even be a question.

HammUEr is a tool to help people that are more comfortable working with old BSP-based level editors still use those in UE4 with its mesh-based workflow, that's it.

More explicit version of the terms of use now prominently on the page.

Unfortunately, besides the fact that I'm not really supporting the 4.16 version any longer since it's over 2 years old, there's not much information in those images, so I can't really help.
Do you have an actual log?

Sorry it took a while, but every Entity class now has a GetOriginalData function that'll return a std::map of the data the plugin read from the VMF file.

Basic two texture blend materials for displacements should be supported

By default, it imports models with the name field stored in the actual model file, but there's a checkbox on the PropUEr tab that imports models with the actual filename as well.

Good catch.
That's what happens when you try to marry two systems that use the same term for opposite things.
Fixed in the 4.22 build.

Most of them should compile from previous source, as long as you disable them before packaging, because UE likes things to be just the way it wants them to

Have you looked at the import logs?
Do you know which textures they are?
Is there something special about them?

This is something you should contact itch.io support for.
There's nothing I can do to help you.

This weekend, possibly.

My apologies, you're right about the info_overlay parsing, and the UVs should be correctly read passed through as floats in the 4.21 build.
Unfortunately, I can't release the source for the lib, and don't really have much time to do active development these days, so I don't see myself doing any major refactor work.
Would a basic thing for unknown entity types (or a separate array for all of them) that'd be a hashset or something that you can parse yourself on the UE plugin side work?

Can you try splitting the source directory up into a couple of smaller ones and importing those one by one?
That should at least help narrow down the problem somewhat, while also remove the need to reimport the same things over and over again.

I have no idea what to tell you, except that I can't reproduce your problem at all.
I just ran a test with a cable materials directory (so just "SplineRope" and a "$basetexture" field), and those all imported fine without needing to change or edit anything in the VMTs, so I have no idea what was going on on your machine. Any unknown types should default to the LightmappedGeneric handler anyway...

Which version of the 4.19 importer are you using? The fixed one?
Also, are you sure your material setup is correct?

I'm afraid not.
HammUEr doesn't exist to import random levels from games, it was created to help level designers that prefer CSG brush editors over more recent model-based level creation workflows to get their work into Unreal Engine.