I don’t know what is wrong with my Unreal, I got a good specs laptop to support the weight of the software, but for some reason, every time it saves it takes probably at least 15 minutes, even there are few modifications. Here are the specs for my laptop. Does anyone know what the issues might be?
Most relevant hardware spec for saving is the hard drive latency. Mechanical hdds do a lot worse because of the random access of many small fragmented pieces. Either way, even for big projects saving shouldn’t take more than a few seconds with some exceptions like after imports etc. I suggest creating a new project to test if there is something wrong with your project.
There’s more likely to be something wrong with the unreal install.
Verify the engine files.
Also, schedule a chkdsk /f because the drive must be experiencing some sort of bad sector error to take 15minute.
Unless you are overly exaggerating because 15 seconds feel like 15 minutes when waiting on something that should take .05 seconds.
I wish I was tbh, but I use unreal for my school work and every time it saves i have to do other stuffs instead of waiting because it takes too much time.
Those are good ideas, I don’t think my project is that heavy on landscape cause, it’s all grass and mountains, I do have quite a few tiny props and such. I’m not really sure how to check cause I’m fairly new at this lol, but the project in general is nearly 50 gb.
The only way you’d see a difference is if your main harddrive is sata and your project is on an m.2 running in pcnve x4.
Or a thunderbolt or something similar with much more bandwidth than sata.
As far as the OS running side by side.
Usually the OS inst writing things to disk constantly. Usually. Reading, Maybe.
And in regards to the external drive thing.
Don’t you have a USB3 or usbC port to use for better bandwidth?
i just checked and the main umap itself is 104,873 kb, and there are a couple of umaps within the project but I don’t really do anything with them, but one of them is 173,053kb and the other is 1,607kb.
PNG16 isn’t a a light file format to begin with.
But why would it save again if no changes are made at all? / is it actually doing that every time you “save all” ?
I have taken them apart every which way possible.
There’s just no way that you can get AAA quality performance when using the landscape system.
And it’s not for lack of trying, but by design.
I honestly don’t quite understand how Brucks & Co spend all that time working on what has basically dead technology for at least 6, maybe 8 years. (Except maybe providing backwards compatibility to stuff like world machine)
Octree mesh placement based on a flat file of vericis would basically offer 10 times the speed at an overall cost reduction on almost all fronts.
But there’s better ways to that too - procedural driven. @MaximeDupart has some great a t stuff going with infinite procedural stuff to name one.
That said, 8k ^2 is a lot of vertex points to keep track of regardless of how you look at it, isn’t it? (That’s the largest landscape size you can cook up, a wopping 2GB saved).
Best way to use the landscape system, is firstly being a maso chist, and secondly baking it down to a mesh.
Useing only meshes.
And now of course Houdini is a great alternative to creation too - at least going by their videos. They even have a world composition implementation thing going…