@HDHANAK I know how it feels and I took these steps and my project worked but there was some issues after the packaging was done. May be my experience might help you. Don’t give up and you will figure it out one way or the other.
thank you for your suggestion but disabling these settings makes the problem even worse since i am unable to open my project. It keeps crashing
any other advice or suggestions would be great as it’s urgent
thank you
So when you’re packaging, you want to pay attention to the yellow and the red text.
Red text means it WILL NOT proceed, yellow means it will proceed but things could get weird.
When you have red text, you want to follow the lines up until something seems out of the ordinary, based on the error given. Since you don’t really have an error that’s traceable, you’d just go up the line until you see anything saying “This isn’t right”.
So EVERYWHERE I look up both “Crash in runnable thread background worker” and “failed to set completion port for job object “UE.ShaderCompileWorker.JobGroup”: The parameter is incorrect.” What I find is people saying that it’s an issue with their project. My first suggestion would be to run a verification scan of your engine installation through the Epic launcher.
One person said they migrated all the useful assets to a fresh project and then they could cook and package.
Another person said it was because they were using virtual textures, after they got rid of those and deleted the lighting cook data the problem went away.
This is a pretty rare occurrence apparently. You are running on hardware above minimum required specifications, yes?
but the project i am packaging is the blank template of archviz and i have verified and check for errors but didnt found any
yes i am running on hardware above minimum required specifications
Hi Most likely, the issue with building the project could be related to your computer’s specifications being below the recommended requirements. I had a similar problem back in the UE4 days when I simply didn’t have enough RAM during the build process. If possible, check your RAM usage while building the project — if it’s close to maxing out, then that’s probably the cause of the error.