You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When attempting to package, the program needs to cook the content. When cooking the content, the redirect to the Bentley App happens, but unlike the first time around when it works, it takes long and fails to reach any connection to the servers, saying the connection has been refused
This leads to this error appearing, making the possibility of packaging impossible
Hello @GonzaloQSystra,
I'm not sure if the cooking failure is related to the connection issue. To be sure, it would be great to:
run your application once in PIE, without packaging: at some point, you should be asked to login again: please do so, and then exit
re-run the cooking process just afterwards.
If it still fails, please attach the log again, as well as the cooking log file (something like C:\Users\gquintaneroabollado\AppData\Roaming\Unreal Engine\AutomationTool\Logs\C+Program+Files+Epic+Games+UE_5.3\Cook-2024.10.31-10.17.44.txt, but with a different date and time of course...)
Thanks
I'm not sure if you issue is resolved or not, but I thik i have seen something similar to this issue in a different project to the iTwin one
Try restarting your editor, and when it reopens your message log should tell you something about water body collisions or something like that, click on the prompt to the right hand side of it once and then restart your editor again.
Try repackaging and it should be working again! Still not sure what causes it.
When attempting to package, the program needs to cook the content. When cooking the content, the redirect to the Bentley App happens, but unlike the first time around when it works, it takes long and fails to reach any connection to the servers, saying the connection has been refused
This leads to this error appearing, making the possibility of packaging impossible
Attached is the log generated
Log.txt
The text was updated successfully, but these errors were encountered: