Gildor's Forums

Game: Little Nightmares

Supported by uModel UnrealEngine 4.13

Screenshot:
(http://i.imgur.com/L9IY1Lv.jpg)

You can add this one to your list Gildor. Thanks for this amazing tool.

Supported: Mesh, animations, textures. (couldn't test sounds)

Added this game to the table, thank you!

Hi there, People!
I need some help with understanding UModel's behavior viewing asset \Content\Characters\Player\SKM_Player.uasset. There are others like that one - strange coloring (texturing) and therefore importing in ue4 leads to the really strange results - engine creates objects with _2, _3 in the names => I can't assign the needed references... Why is it happening and where to look at all? Maybe, I do perform importing wrong way or something like that? 4.13 - for sure. Thanks in advance!

There's still not enough information (comparing with our talks at facebook). It would be really great if you could provide information letting understand the problem without trying the asset itself. For instance, record a video showing the problem. It's important that you'll verify the asset in viewer itself (some people even not aware that they can VIEW models in "UE Viewer")

Well, first of all - this is one of the models here which looks strangle - what does these colors mean? It is yellow only (with a little of dirt) in-game...

You might need to reconstruct material yourself. UModel is using heuristics to produce a simple material from UE3/UE4 complex ones, and these heuristics doesn't work well all the time - sometimes even displaying checkerboard texture instead of anything useful. This is actually a FAQ question.

1. Are those ones the links to the other objects?
2. UModel converts them to _2, _3 - will show later tonight...

Show me these materials in package "explorer" and in your export directory. I see there's a little unusual thing: mesh consists of multiple sections, and some of them are using the same material (or material which has the same name but located in a different folder).

Things break after - on the 3ds max's territory and/or after that - when importing in the ue4...
Here's UModel's side, though:

No idea then. Probably Max importer add suffices itself when it imports the same material twice or more.

ActorX Importer isn't yours one?

Mine one. But I don't have 3ds Max installed anymore, so doing any updates there would be very hard for me.

Anyway - what to do to make it ready to work - how to figure out all that with this particular game? Also, how can I recreate these material instances? Maybe, there is some potential improvement for the UModel itself?

You may reassign materials in UE4, so they'll match. And remove duplicated materials. Regarding recreation of instances, it's hand work. No improvements to UE Viewer are possible.

This is not the case when you make some custom build of the UModel?

What kind of customization did you mean? UModel can combine identical materials, but this would mean: head, legs, hands - everything will be covered with a single material, model will lose division to parts. If designers decided to preserve a possibility to change these materials independently (e.g. "red legs" and "blue hands"), the possibility will be lost.
Is it so hard for you to do the fix by hands? It's a few seconds of work.

What fix do you mean here that I can try myself?

Also, tried to unpack GameFolder totally (everything) and received such an error:

TArray: index 0 is out of range (0)
Sequence <- Keys <- DoExportPsa <- ExportObject: Skeleton'SKEL_BoltCutter' <- ExportObjects <- ExportPackages <- UIMenuItem::HandleCommand <- UIMenu::Popup <- UIBaseDialog::WndProc <- UIBaseDialog::CustomMessageLoop <- UIBaseDialog::ShowDialog: modal=1, title="Choose a package to open" <- CUmodelApp::ShowPackageUI <- Main: umodel_build=1483

Could you send me a set of files which crashes umodel? (it's some animation which is bound to SKEL_BoltCutter). You can use "Save packages" to get them outside of pak, but please test with saved files again, to be sure that you saved enough data for error reproduction.

@Gildor: I couldn't reproduce the error with latest game version and 1487 umodel build, the whole "Game" folder can be exported just fine with default umodel and export settings (with psk/pskx). There is possibility that the error is not directly related to umodel (like path length limit for windows or something).

The error happens when some AnimSequence is EMPTY, I already saw it before with one of Fortnote assets - but I lost the information about reproduction, so I wasn't able to fix that.

@Gildor: More info on the matter - SKEL_BoltCutter asset exists only in Little Nightmares II (demo), which is different game. Imho, it looks like umodel was used on root folder / merged folders, so internally some animation could refer to similar asset from different game (or something). Again, "Game" folder from LN2 demo can be fully exported just fine without any issue. Maybe that problem with Fortnite was also because of some leftovers and it shouldn't happen if single game version is opened at a time.

This happens with the LNII Demo Project (Steam) - sorry, everyone, I haven't mentioned that on time. Gildor, may I help here somehow?