This keeps the FPS more consistent throughout. they are all created at start and kept inactive until needed). 7-hour rain and snow forecast for Des Moines, IA with 24-hour rain accumulation, radar and satellite maps of precipitation by Weather Underground. there is a fixed amount of them that keeps getting re-used) or pre-cached (I.e. Precip data do you want to stay up to date of all news. Pooling and caching objects - the TL DR is that creating and destroying objects on the fly is very no bueno on lower performing systems and can cause micro-stutters.I'm actually happier with the result than I initially expected to be! Ultimately, I replaced them with circular sprites that resemble the 3D ones. The oil fire mechanic is probably one of the most fun to use, but not when your FPS drops to 15. Replace 3D particles with 2D (rain and fire) - this was again a frustrating decision, but I experimented with so many variants of our 3D particles, different settings for transforming them, caching, materials.I haven't figured out a good replacement for them yet Get rid of the rain puddles - no really, those EAT the frames per second for breakfast.I found a good compromise between quality and performance that's roughly equivalent to the "medium" settings on PC 😄 Those helped a bunch and, due to the game's simplicity and Smitch's small screen (in handheld mode), they aren't too detrimental to player experience. Drop general settings - texture filtering, shadow quality, etc.Drop Bloom and Ambient occlusion - as much as I wanted this to work, it just eats up way too much of the GPU time 😢 I tried 2 different alternate Bloom solutions, but they performed even worse than the built-in Unity one.So, what kind of changes were necessary to make the game playable? Thus ensued the week of madly reading through the Swutch Docs, watching various "Unity Optimization Tips" GDC talks, and getting chummy with the Unity Profiler that tells us exactly where our bottlenecks are.
0 kommentar(er)
