I just got on, Map was fully planned and grey boxed, with many assets and details added, all gone??? how and why??
Hey there @ErenJaeger2.0! What engine version are you using? When working on assets that come in the base engine folder, were you using the default map? If at all possible I’d recommend creating a new map when blocking out anything. You may be able to recover some data sifting through the \Saved\Autosaves folder in your project.
sorry for the late reply I was kind of busy, and no It wasn’t a default map, the level was deleted completely, the assets I used still existed In a folder, but not in the level.
And I’m using ue5.2 latest version
I just got back on ue5, I remade what was lost because I had a copy in blender, I got back and the map is deleted again. there’s something wrong with my files is there?
Interesting! Do you have another instance of that project open in another window? Any stray unreal processes possibly accessing the map? Does anything save between sessions or is it just the map itself failing? Does this occur for every map as well?
I don’t have copies of the old map, and saving is fine and everything used to work properly.
I didnt have an instance of the map running in a different window, I was working on a single tab.
This issue happened to a different map as well, but the other map was more like an experimental map, nothing important in there.(One thing to note, the other map wasnt deleted but everything inside it was, it was an empty world
Yesterday I went to the epic games library, and Verified Installation (was a full Redownload). then I created a map and Imported my grey boxed fbx scene. The next day which is today nothing got deleted.
Hopefully i don’t get this problem ever again. If I face this problem again i will reach out for help again
2 Likes
At the moment everything is fine. but I still want to know the possible cause of the issue (if possible)
so I don’t face this tragedy again haha
Today i got an error message from Nvidia, that my version(latest one) had an issue with d3d12 and so i had to download a newer one which i did.
That could be the issue
Glad everything’s working for you now! Definitely keep me in the loop for more issues. I originally figured it was tied to the (common) issue where the engine is always using a file thus failing to write the saves that comes with engine files, but if it’s every file, this is significantly more dangerous and more indicative of the engine having something possibly corrupted, and I think that’s more possible since the validation seemed to fix it.
That said, the D3D warning is just warning you to update your graphics drivers, and wouldn’t stop the saving of maps, but if you experience any Direct X or graphical based crashes after you see that warning, to update to the newest version of your drivers. (Though sometimes it’s better to sit on the slightly older drivers for a bit but that’s a whole other rabbit hole).
1 Like
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.