I have assets that have textures in the editor, but once published as a private code, other players cannot see the textures. I am still able to see them, but I believe it is only because I have the files on my computer. I also created a material for barriers, but other players cannot see that texture either. Not really sure what the problem is.
Steps to Reproduce
Import mesh
Wrap mesh with texture
Publish map to private version
Expected Result
Anyone who joins the map should be able to see the texture.
Observed Result
I am able to see the textures (project was created on my pc with uefn), bot no other player can even when published.
The resolution for all of the textures used on the meshes and barriers are all 1024x1024. Yes, other players see the grey checkerboard pattern while I still see the textures. The people I had join the map were on console since I donât have someone around to join on pc. Where is the setting for âUsed with Naniteâ? The only thing that is checked on all of the materials is âNanite Override Materialâ, but is set to None.
If you click on the material output node. (the thing on the far right that everything plugs into) youâll see the âused withâ flags. (Itâs probably not this, but I saw some UEFN popups recently asking me to enable this flag)
While you are there, if you click the gear icon you can filter by âShow Only Modified Propertiesâ to see if there are any funky settings. (Sounds like this may be a material generated by an fbx import)
Also, is there anything âcomplexâ going on in the Material Graph?
I found the Nanite setting for the material I created for my barriers which was unchecked, I will enable it and test it once I have someone to get on the map.
Also, the assets that show up with the checkerboard pattern have material instances on them, but when looking at the material that the instance was created from, it is completely blank. I just realized this so I feel like this is the problem? Or no?
Note: These assets were imported into UE5 and then exported as fbx to bring into UEFN
Hm, having a blank parent-material sounds like a problem, Iâm surprised the Material Instances would work though. (I wonder if there is anything complex or nonstandard happening in the Parent Material still)
Another thing to try would be to create a new dead-simple material, insert the textures, and apply this new material directly to your assets.
So I went into UE and looked for the parents of these materials and I realized I never brought them into the current project in UEFN. Which Iâm not sure why the instances would work without the parent material.
I brought the parent materials into my project and once imported, I saw the checkerboard pattern. It seems as though I have to manually change the parent of all the instances to what it should be. Without the parent materials, it was defaulting to a âDefault_Opaqueâ parent.
It seems like once I link the correct parent it should work? I can attach a screenshot of the graph for the parent if needed. Iâm not sure what would be labeled as nonstandard or complex.
I added the correct parents, but it shows me the checkerboard pattern. The only way I can see the correct texture on the assets is if it its parent is âMI_Default_Opaqueâ, which is a blank parent and doesnât even exist in the project.
At this point Iâm lost, but I really do appreciate all of your help.
My guess is that the materials were imported with broken or missing references to the textures. (Or there are references to textures that exist as variables inside of the Material Instances)
Iâd try just creating a new Material â Open that Material and reference/apply the textures in it. Then open up the mesh in the Static Mesh Viewer, and change the Material to your newly created material. - Dead simple, No material instances involved.
I was actually able to make everything link correctly after migrating the assets from UE to UEFN instead of exporting. The correct parents come up and everything. I really do appreciate all of your help.
The only problem that is occurring now is that there are illegal references in some of the material instances. I changed the âillegalâ textures within the materials, but the error keeps coming up that the instances still reference the âillegalâ texture. I thought if I changed the material that the instance would update, or do I have to create new instance?
Happy to help. Are there texture variables inside of your materials? I could imagine that if a Material Instance has a dynamic/settable/variable texture, and the texture moved/does not exist, than it would complain about missing(illegal?) references.
The options available in the instances should update when you update the parent material.
Sorry I only have a small amount of knowledge around materials and textures, so Iâm not sure if I understand. I will explain what is going on though.
In the material there are 2 cubemap textures in âParamCubeâ nodes which were referencing /Engine/MapTemplates/Sky/Desert_Outer_HDR. I then replaced these textures with a different sky dome that showed up as an option which was âCubeMap_Apollo_Dayâ. After replacing these textures I am still getting an error that it is referencing the illegal one.
Watching a few tutorials on the Texture â Material â Material instance system would help get you up to speed. (Itâs the same in UE as UEFN)
Cubemaps could be adding an extra layer of weirdness.
That /Engine/ folder is specific to UE5, and those assets donât exist in UEFN.
It looks like weâre able to use those FN cubemap textures. Itâs strange to me how the name changes to âCubemap_Apollo_Dayâ when I select âCubemap Fortnite Day 01â
I was able to launch a session without any errors.
Iâd try importing your own cubemap. (Or exporting/importing a cubemap from UE5) And then see if the error still happens when using the imported cubemap.
I imported a different cubemap and I went to look at the instances and they were manually referencing the âillegalâ cubemap. I unchecked all of them and there are no more errors. It let me publish a private code for my map finally.
I will be testing to see if other people can see the textures in game soon. Iâm sure they will be visible now since the parent materials correctly migrated to my project. Thank you again for all of your help!
