I am currently working on downloading and mounting a pak file from internet.
Download and mounting seems to work fine. However, when it comes to calling an object from the mounted pak file, textures on the object appear corrrect for a few milliseconds, then a wrong texture from the Engine defaults gets assigned. This happens with all objects on the screne including meshes, blueprint actors, characters, pawns, particles, etc…
Even though “use pak” is set in project settings,
FCoreDelegates::OnMountPak.IsBound()
is always returning false for me. So I’m using FPakFile for mounting downloaded ones.
When mounted,
Meshes are loading ok
Particles are loading ok
Blueprints are working fine
Levels are reachable and loadable
Only textures have this problem. I’m adding some screenshots to show what is going on in app.
First ones are from inside editor, what it looks like originally, second ones are from packaged application that loads another texture (something from engine).
I also [uploaded a video to youtube (click here)][1] to show that textures are loading correctly and getting replaced after. You can also download the same [video from google drive][2] if needed.
i can provide the ini file for my packaging settings, upload does not allow .ini files, so… settings with txt extension
for the minimum project, i might need some time to provide something like that. as some parts of the project is c++, requires our node backend (an adapter and logic part, two apps in simplest form) to run/download paks and also we have a node app to package the files (that uses automation tool and unrealpak in general, removes not wanted assets from main pak, etc).
if you can provide me an email, i can simply add you to our bitbucket git repos and give detailed information how to run the packager, then app and backend together. this will definitely help you reproduce the error.
if the email part is ok, you can send it to emrah.gunduz /at/ markakod.com or my registered email too.
Protocol deems I request you send the blank project via a private message on the Forums. If you can get a link sent to me with a test project then that would be most beneficial.
It sounds like you have a couple of custom processes which could end up making this issue difficult to report. I would say, be sure you have the ‘Full Rebuild’ option checked to make sure everything is being built and added to your Pak file.
Let me know if you have further questions or need additional assistance.
So I took a quick look at your project and can definitely verify the irregularities with your textures having artifacts. The process you are using is pretty new to me so I looped in some additional assistance for clarity on what could be occurring.
What they assumed without digging in too deeply, is that this could be a texture streaming issue. Have you modified any of the texture streaming options, and/or do you have specific requirements you need to meet for your texture streaming?
What you can do to manage and observe your streaming textures is to use the ‘Stat Streaming’ console command, which will bring up a number of statistics you can track. Have a look at our Texture Streaming documentation for further information on how to debug your own textures.
Let me know if you have further questions or need additional assistance.
Wanted to check in to see if you had any updates to your issue?
We have another user reporting a similar issues with Pak files and DLC, and I would like to investigate these together to see if they are related and their cause.
we were not able to correct the texture problem. i checked texture streaming as you requrested, but there is nothing out of the ordinary. at most %5 of the current 1 gb assigned memory is used while we were testing. over budget is always 0…
if i check the list of textures/streaming textures i do not see anything unusual.
the strange part is that, textures all get loaded correctly. after just a few hundred milliseconds, they change to something else from the pool. like my fog particle starting to use a somewhat roboto font’s texture (created on the fly for required text on screen?).
we are currently trying to finish the project and return to this problem later. if you have any other suggestions, i can try them of course.
i am attaching the list of streaming/all textures from console. maybe those numbers might solve the problem, who knows texture log
It has been some time and we were never able to determine the cause of the issue, or even if this is a bug with the engine. We had some others test and got some varying results which is part of the reason as to why a bug could not be entered.
I just wanted to check-in to make sure you weren’t still experiencing the issue, or if you managed to resolve the issue?
Let me know if you have further questions or need additional assistance.
We are still experiencing the problem. This is a deal breaker for us, until this is solved we moved to other projects.
I’m seeing other people also experiencing package mounting issues in here. So, you should really look into this. Wrong textures are being loaded and assigned to meshes/materials.
So after some further investigation and some back and forth with another engineer, we have decided to enter your report as a bug. I appreciate your patience and for providing me with the project to test on our end. You can track the issue following the link below on our new Public Issues Tracker.
Once the issue has been addressed by our engineers, the fix will be added to the release notes for fixed issues within an upcoming full engine or hotfix release.
Let me know if you have further questions or need additional assistance.
By the way how did you manage to mount a pak file properly? I am having a hard time to load a pak file which is downloaded on http. I am able to see the content of this pak file after mounting, but no chance to load assets, neither with asynchload nor synchload.
If you can share this little piece of the code, me and community would be appreciated.
we have just upgraded the project to version 4.13.1. It seems like the packaged content is now loading the correct textures.
If I export wit 4.12.5, still the texture loading has problems… do not know what is changed between these two, but seems like the bug was squashed in between
That is interesting because it is slated to be fixed for a later engine version, however if it is working for you in the 4.13.1 release that is good news!
I know that your issue had a fair number of nuances to pay attention to when setting it up, and you provided a detailed repro case, so it is hard to tell what actually fixed your issue. As long as you do not continue to experiencing issues, then awesome! If you end up regressing and need more assistance, please don’t hesitate to ask.
