Hello guys.
I'm playing with Unreal 5 and Houdini Engine. And I have a problem.
The static meshes produced (or inside, unbaked) by the hda's do not show in game mode.
I have a building generator which places some instances in the scene, static meshes and simple door blueprints.
The blueprints work, the static meshes do not. When I press the "G" only their shadow shows.
When I play, they do not appear at all. Their collisions are there, though. In normal viewport anything is ok.
Unreal 5 - Houdini Engine - Static meshes
5228 7 2- dbaciu
- Member
- 11 posts
- Joined: Sept. 2010
- Offline
- peternicolai
- Member
- 37 posts
- Joined: Jan. 2017
- Offline
FWIW, I'm seeing the same behavior. I have a UE5.0 build via the launcher and Houdini Engine v2 installed via the package that came with Houdini 19.0.584 daily build. Very odd.
EDIT: Just tried with latest production build of 19.0.589 install and matching engine plug-in. Same behavior.
EDIT2: I believe, at least in my case, it is related to the World Partition System in UE5. I'm using a default Third Person Template for my testing. IN that map, my HDA geo disappears during both 'sim' and 'pie' but is visible in editor. By default, that map has 2 world partition actors in there ("WordlDataLayers-1" and "WordlParitionMiniMap"). Don't know that they are the problem but they were a clue I could at least test against.
When I spin up a new map (CTRL-N) and simply select "basic", that map does not have the 2 World Partition actors, uses the old streaming level system and my HDA geo is visible in gameplay. Don't know if this is the same as what you are experiencing but it may be worth checking the level set up.
Looks like I'll be reading a bit more about World Partition later tonight.
EDIT: Just tried with latest production build of 19.0.589 install and matching engine plug-in. Same behavior.
EDIT2: I believe, at least in my case, it is related to the World Partition System in UE5. I'm using a default Third Person Template for my testing. IN that map, my HDA geo disappears during both 'sim' and 'pie' but is visible in editor. By default, that map has 2 world partition actors in there ("WordlDataLayers-1" and "WordlParitionMiniMap"). Don't know that they are the problem but they were a clue I could at least test against.
When I spin up a new map (CTRL-N) and simply select "basic", that map does not have the 2 World Partition actors, uses the old streaming level system and my HDA geo is visible in gameplay. Don't know if this is the same as what you are experiencing but it may be worth checking the level set up.
Looks like I'll be reading a bit more about World Partition later tonight.
Edited by peternicolai - April 18, 2022 16:54:19
- dbaciu
- Member
- 11 posts
- Joined: Sept. 2010
- Offline
- sfd15
- Member
- 3 posts
- Joined: Oct. 2019
- Offline
- RooiJakkals
- Member
- 6 posts
- Joined: July 2021
- Offline
I am experiencing the same issue and do agree that it happens whenever world partition is enabled. It's been driving me crazy trying to figure it out but have not found any solution as yet with my own experimentation and researching it online. It is surprisingly hard finding anything on this online, considering what a crucial functionality it is to be able to generate a procedural world
- daverosesumo
- Member
- 19 posts
- Joined: Nov. 2019
- Offline
- C_arnold
- Member
- 1 posts
- Joined: Oct. 2016
- Offline
I can confirm this is also happening to us. In my testing, the HDA is completely removed from the Outliner during Play in Editor. So HDAs with generated geo or instanced geometry are not loaded during Play mode.
HDAs will load fine in maps where World Partition is not enabled, but if World Partition is enabled the HDAs will not load.
HDAs will load fine in maps where World Partition is not enabled, but if World Partition is enabled the HDAs will not load.
- PDGoupil
- Member
- 12 posts
- Joined: Oct. 2019
- Offline
-
- Quick Links