search

sideeffects / HoudiniEngineForUnreal

Houdini Engine Plugin for Unreal Engine.
http://www.sidefx.com/unreal
Other
1.36k stars 374 forks source link

Digital Assset in UE4.4.15 problem #69

Closed djczaps closed 4 years ago

djczaps commented 7 years ago

Hi I've compiled and finally being able to run Houdini Engine in UE4 ( ver 4.4.15) My Houdini version like above : 16.0.555, operating system Linux Centos 7 64bit.

When I import digital asset , no matter if .hda or .hdalc extension it opens in UE4. However it pops up a message like this: Houdini Installation was not detected.Failed to locate or load libHAPIL.so. No cooking / instantiation will take place. So it only shows in viewport SideFX logo instead of my asset ;).

When I've compiled Houdini Engine on Centos it shown some warnings regarding Houdini engine environment but it Maked okey in final. here are those messages. I thought that might be related to this problem ? Message warning below during the compilation steps :

Fixing libUE4Editor-UnrealEd.so /mnt/caches/Epic/UnrealEngine-4.15/Engine/Source/ThirdParty/FBX/2016.1.1/lib/gcc4/x86_64-unknown-linux-gnu/release//libfbxsdk.a(fbxutils.o): In function fbxsdk::FbxPathUtils::GenerateFileName(char const*, char const*)': (.text+0x4b8): warning: the use oftempnam' is dangerous, better use `mkstemp'

[2017.03.22-20.06.35:137][ 0]LogCompile: UHT Command Line: /mnt/caches/Epic/UnrealEngine-4.15/Engine/Binaries/Linux/UnrealHeaderTool

[2017.03.22-20.06.35:137][ 0]LogCompile:Error: Missing module info filename on command line [djczaps@djczaps-w2600cr Linux]$ '/mnt/caches/Epic/UnrealEngine-4.15/Engine/Binaries/Linux/UE4Editor' Using binned.

[2017.03.22-20.07.42:693][ 0]LogModuleManager:Warning: No filename provided for module HoudiniEngineRuntime [2017.03.22-20.07.42:693][ 0]LogModuleManager:Warning: ModuleManager: Unable to load module 'HoudiniEngineRuntime' because the file '/mnt/caches/Epic/UnrealEngine-4.15/Engine/Binaries/Linux/' was not found.

What do You suggest to do with that kind of 50% working asset ? Do I need to install special Houdini QT on linux to be able to work with Unreal Engine ?

Greetings

Dawid Januszek

varomix commented 7 years ago

Hi Dawid glad to see somebody else doing this, I've done this before and it works, you are good so far, the last thing is to set the path to houdini, is not done by default on Linux.

in Unreal Engine, create a project then go to Edit/Project Settings > Plugins Houdini Engine there you need to have the exact Houdini version the engine was build against and set the Custom Houdini location to the dsolib location something like /opt/hfs16.0.504.20/dsolib/ After that restart unreal, open your project and it should work.

Let me know if you have any issues, I've been there :smile: image

djczaps commented 7 years ago

Hi Varomix !!!

Thanks for the tip man. I noticed that if I source Houdni setup after installation it will do the same what You suggest. And the Houdini paths and dsoLIb are detected correctly without any warning like I had before. However now after I compiled UE4 again today another problem pops in :

I recompiled UE4 (v4.1.15) again with Unreal Plugin form 23.03.2017 on GitHub. This time I had no warning during "making" process. Houdini paths and dsolib was detected along with Houdini installation path correctly ( [2017.03.23-18.57.21:309][ 0]LogHoudiniEngine: Loaded libHAPIL.so from HFS environment path /opt/hfs16.0.555/dsolib) However when I try to import digital asset this time it shows in the Content browser. But it does not show ijn the World Outliner even if selected. When I try to drag'n'drop digital assest .hdalc on the veiwer it pops a choice window ( like in the picture attachment here: uecrash2

(. Whatever I choose Unreal will crash immediatly. Some logs show like that after it : 2017.03.23-19.17.18:372][ 0]CrashReportClientLog: Sending HTTP request: https://datarouter.ol.epicgames.com/datarouter/api/v1/public/data?AppID=CrashReporter&AppVersion=4.15.1-0%2B%2B%2BUE4%2BRelease-4.15&AppEnvironment=Release&UploadType=crashreports&UserID=0002bf0e0903110f001801f95fc8f689%7C%7Cb800d766fc834a6b8e1583b7d15b1b26 [2017.03.23-19.17.18:878][ 0]CrashReportClientLog: OnProcessRequestComplete(), State=SendingFiles bSucceeded=1 [2017.03.23-19.17.18:878][ 0]CrashReportClientLog: State change from SendingFiles to SendingFiles [2017.03.23-19.17.18:878][ 0]CrashReportClientLog: All uploads done [2017.03.23-19.17.18:878][ 0]CrashReportClientLog: State change from SendingFiles to Finished [2017.03.23-19.17.19:347][ 0]LogLinux: FLinuxPlatformMisc::RequestExit(0) [2017.03.23-19.17.19:347][ 0]LogGenericPlatformMisc: FPlatformMisc::RequestExit(0) [2017.03.23-19.17.19:379][ 0]CrashReportClientLog: Final state (Receiver) = Finished [2017.03.23-19.17.19:380][ 0]CrashReportClientLog: Final state (Receiver) = Unknown UploadState value [2017.03.23-19.17.19:380][ 0]LogExit: Preparing to exit. [2017.03.23-19.17.19:381][ 0]LogObj: Freed 0b from 0 cluster array pools. [2017.03.23-19.17.19:381][ 0]LogExit: Object subsystem successfully closed. [2017.03.23-19.17.19:383][ 0]LogModuleManager: Shutting down and abandoning module HTTP (12) [2017.03.23-19.17.19:412][ 0]LogModuleManager: Shutting down and abandoning module SSL (11) [2017.03.23-19.17.19:414][ 0]LogModuleManager: Shutting down and abandoning module CrashDebugHelper (8) [2017.03.23-19.17.19:414][ 0]LogModuleManager: Shutting down and abandoning module QoSReporter (6) [2017.03.23-19.17.19:414][ 0]LogModuleManager: Shutting down and abandoning module Analytics (4) [2017.03.23-19.17.19:414][ 0]LogModuleManager: Shutting down and abandoning module CoreUObject (2) [2017.03.23-19.17.19:415][ 0]LogExit: Exiting. Engine crash handling finished; re-raising signal 11 for the default handler. Good bye.

It looks like that the version before was detected better even with problems to connect to HFS installation path. I noticed that when I sourced houdini setup via terminal it helped to find proper HFS path before compiling and "making" UE4 again.

Greetings

Dawid

varomix commented 7 years ago

I always source Houdini before making, yes that's the proper way and is not crashing for me, working really well actually

djczaps commented 7 years ago

Hi varomix ! I watched Your yesterday session about installing HEngine on Linux. I have exactly the same problem with running digital assets on Linux. No matter what I do it will crash when drag n drop on centos 7.xx. How to live man ? ;)

varomix commented 7 years ago

hehe not sure, now I have the same issue, it was working great then something broke it and can't figure what

djczaps commented 7 years ago

I've even tried to chmod 777 whole dsolib folders content. To be able to write there as standard user and not root only like Houdini was needed to be installed. Didn't help either. ;(

varomix commented 7 years ago

Hey try with your own asset, seems like is crashing with OLD assets, I just made a new one and it works.

djczaps commented 7 years ago

Yep!!! :)

Varomix it works with the new created asset indeed. !! Voila ! ;)

djczaps commented 7 years ago

p.s Are You also running Houdini on Centos 7.xx ? or Mint / Fedoras

varomix commented 7 years ago

seems like there are issues with old assets pre Houdini 16 so don't use any of those and just create your own. Yes I use CentOS 7 for everything :)

djczaps commented 7 years ago

but it's strange cause my old assets I did also in Houdini 16xx earlier versions.

varomix commented 7 years ago

I can import assets that I previously made in Houdini 16, maybe the version and the changes that had happened not sure