Its pretty clear I would say that it worked with the other persons because their storage just got too full over time and they could clear it through deleting those files. However my storage is probably full after the first snapshot because of my 1240 snapshots. So Im guessing with the last update they put a maximum to that storage.
Hi, nothing helped me either, but I found a solution. You need a PC with a clean uefn installation, it can be your friendâs account. You add it to the team and give it publisher rights, it compiles the project for you and calculates the memory. The only thing it has to do in your project is a fresh snapshot. And everything will work. Try it, I updated my game like this today. Good luck!
I tried it again on another pc where I deleted everything but without completely reinstalling UEFN and it didnt work. I will try to really reinstall everything again.
But even if this works this cant be a long term solution. And if this works I guess there has to be some specific file that just has to be reset.
Or Im just completely wrong, but I will see tomorrow.
Thank you all for your replies
The condition of this algorithm is to make changes to the project and create a new snapshot on a new PC. Did you do this? or just open the project on another PC
No ticket was created since the original thread was edited, so you wonât see automatic updates to the ticket.
For reference, we created a ticket internally: FORT-940617, and the status is investigating.
I used another pc, loaded up the map completely fresh, also had saved and intermediate deleted. Changed something, created new snapshot and launched session and then memory calculation but the same error came up
Today I tried to completely uninstall the Fortnite client and UEFN and clean all the registries, also delete all the project files from the disk and the saved files. I rearranged everything, so that synchronization took place and I received all the projects from the UEFN servers and still got this error, so I think the problem is on the platform side.
Good to know. Im glad Im not the only one where Its still not fixed
Very strange thing, I already forgot about all this and accepted that it doesnât work. And I started making some changes in the project to fix bugs, so that later I could publish the project through the team. And something happened, I was able to flash and calculate the memory on my PC after the snapshot. Then I tried again and an error pops up. But I still made 1 version that is suitable for the update. It seems that this is a very random bug.
So you did nothing except doing changes and it worked for one version?
@Flak So how should those of us where it still doesnt work proceed with this error?
Should we wait and try again everyday till its fixed?
You said we wont get automatic updated, so should we keep writing tickets?
I can just speak for myself but I guess that everybody feels the same way I do. And the Map of mine where Im getting this error is really big and took a lot of work and time. So abandoning it and just starting a new one is not really an option for me.
Experiencing the same issue. Any luck?
Please do not post duplicates; it only slows things down. You can ping me for status, but please remember that troubleshooting takes time.
I am checking with the team to see where we are. I know they are still working on it.
I have news
We have a potential fix, and we hope to have this addressed in 37.10. Weâll need to make sure itâs tested before deployment.
In the meantime, you can try moving an actor or changing a value and then trying again. That has worked for some.
Okay, sounds great. Thank you!
I turn RC off and on a couple of times and changed things, etc. and now it works for me again.
I now have a problem with infinite memory calculation
I have this problem again, itâs impossible, Iâm working on the project until 4 am and I just want to calculate the project. And it doesnât work, it creates a private link every now and then, and at the stage of creating it, the editor loses connection. And because there is no connection with the editor, the memory calculation doesnât work. Help, weâve been suffering for 4 weeks, Iâm not alone, there are many of us!
Still not working for me : (
@Flak Do you have any eta of when 37.1 will drop because we are on 36.3 right now and with how things are pacing, we would be waiting multiple months for a potential fix