Water gem and Video Playback gem errors and FBX failing to import

Lumberyard Discussion Other Support
, , , ,
#1

Hey all,

I posted a while ago about how the video playback gem would fail to load in the editor even though the build was successful. Well now when I try to import an fbx that contains just a mesh, I get this error in the asset processor:

25/01/2018 21:52 - RC Builder - C: 1> 0:00 [Gem config file] = D:\Repos\UES-lumberyard\dev\Test1/config/editor.xml
25/01/2018 21:52 - RC Builder - C: 1> 0:00 [Gem config file] = D:\Repos\UES-lumberyard\dev\Test1/config/editor.xml
25/01/2018 21:52 - RC Builder - C: 1> 0:00 [Gem config file] = D:\Repos\UES-lumberyard\dev\Test1/config/editor.xml
25/01/2018 21:52 - RC Builder - W: 1> 0:00 Defaulting engine root path to 'D:\Repos\UES-lumberyard\dev\'
25/01/2018 21:52 - RC Builder - C: 1> 0:00 [Gem config file] = D:\Repos\UES-lumberyard\dev\Test1/config/editor.xml
25/01/2018 21:52 - RC Builder - C: 1> 0:00 [Gem config file] = D:\Repos\UES-lumberyard\dev\Test1/config/editor.xml
25/01/2018 21:52 - RC Builder - E: 1> 0:00 Failed to load dynamic library at path "D:\Repos\UES-lumberyard\dev\Bin64vc140\Gem.Water.Editor.c5083fcf89b24ab68fb0611c01a07b1d.v0.1.0.dll".
25/01/2018 21:52 - RC Builder - C: 1> 0:00 [Gem config file] = D:\Repos\UES-lumberyard\dev\Test1/config/editor.xml
25/01/2018 21:52 - RC Builder - E: 1> 0:00 Failed to load Gems for scene processing.
25/01/2018 21:52 - RC Builder - E: 1> 0:00 Failed to convert file D:/Repos/UES-lumberyard/dev/Test1/Assets\untitled.fbx

It appears that the water gem is causing my fbx to fail to load. I’m using 1.12.0.0 (because from what I can see 1.12.0.1 only adds external projects support, which I do not need). For some reason, the water and video playback gems build successfully but do not work in the editor.

I’m now worried that a lot of gems might also not work even though they build correctly. With the videoplayback gem, I just disabled it since it wasn’t a requirement. For me, the water gem IS a requirement.

I will test my FBX import without the water gem to see if that fixes it, but I would prefer a solution that fixes the water gem

#2

So, @Amonster_LMBR, it appears unticking water gem from project configurator, saving and doing a profile -p game build does not actually remove the gem in bin64vc140, the .dll is still there. Decided to delete all things water from the bin64vc140 folder and am doing a debug -p all build to see if that works. Does -p game not rebuild gems and removed ones not used anymore?

Any solution to this problem, is the team aware of it?

EDIT: Turns out removing the water files is not fixed by a debug -p all build, getting error about the water gem not being built. Guess I’ll try and update this forum post if I can get the fbx importer to work in my new project.

#3

@Amonster_LMBR
Any Answers? I’ve looked at the gem itself, can’t see anything that would cause a problem with fbx files…

#4

Hmm – interesting. Weird that the Gem would block FBX importing. Let me check in with the team on answers. Stay tuned :slight_smile:

#5

Hello @Techtime,

Having the water gem enabled seems to be a known issue for causing FBX import issues in 1.12. I would recommend disabling it and try again. One thing to note is the maximum vertices we support is 65k - if you have an FBX that has more than that many vertices then it is recommended to split the FBX into smaller chunks.

Hope that helps!

#6

Hi, it’s been a while. Has any fix been made yet? Accidentally enabled the water Gem again by accident, forgetting this error and am now unable to import fbx files