Engine Update

Engine Update

Hey Guys,

A quick post this time, but I am bringing it to attention because this error, as of current, has significantly reduced my overall progression on my project.

This being, to always check your system regularly and to make sure that your Engine Version files in your main C: Drive, are not clogging up your system. Usually when you are rapidly iterating and needing to build dynamic lighting, the engine will be constantly saving data, until you decide to compile your build; it is this data that will save into your LOCAL DERIVED CACHE in your used Engine Version. 

A patch fix that I did try, and it does work to some extent is located in the link below:

https://answers.unrealengine.com/questions/255793/derived-data-cache-1.html

Although, by re-routing the cache file, it did help locating it (I put it directly into the project file where you would usually locate your BUILD, CONFIG & CONTENT folders) and deleting it after every major build or save was helpful. But the problem still persisted, whereby the folder could get to upwards of 30Gb, so it was helpful to be able to delete it on command, but it certainly didn't assist in the performance of the engine, as I was forced into having the entire build in low settings to keep it at top frame.

So maintaining a clean system will significantly assist in your production speeds, but for me this was hassle trying to wrangle it regularly, so with a fresh engine update it soon became apparent that it was running smoothly, and in addition increased the performance of my project.

After all trying to work like Romero, and trying to maintain high performance and performant work, it is necessary to not just understand the principles in the engine, but also well worth knowing the innards of your engine, in case such problems occur in the future.

In addition, I am also opting for a full packaged build - per iteration, in order to legitimately error proof my work, as I have also had some errors occur post packaging in contrast to PIE (Play-In Editor), whereby some mechanics just simply weren't working. But by also having this method mind, it shows that the work is being performant and will always be ready for publication, opposed to creating project versions to test, and never truly know if it will work when published.

So in order to maintain our user engagement, we need to make sure that our work is always combat ready at every turn, and more-so if we wish to have numerous people test it. Essentially sharpening our own eye, in figuring out what our user will want, as we will experience the same thing, if we were to test it.