Given how others say that their FPS slows down to a shrimp I can't imagine Andy having 57 fps in a park that big, but on the other hand I can barely believe that he'd jump up 57 frames per second. The only thing I'm not sure about is if he jumped from 2.8 fps to 60 fps or that he jumped up 2.8 fps, so from 57 to 60. I'll take a look next week and see if we can come at this from another angle and make editing snappier too. While interacting with anything else in the park though (scenery, coasters, flatrides etc.) it's much faster. The good news is that this is a nice optimisation target, and with a very quick look I've been able to get the framerate much higher (~2.8fps on my machine here to ~60fps), the only caveat being that it slows down again while editing buildings. This level has approximately 131,000 entries in this structure, which is rather a lot! The game was attempting to balance this tree even if nothing has changed within it. The tech explanation is that we use a specific data structure (an AABB Tree) to query how building pieces "merge" with another (the building system in Planet Coaster swaps pieces out with others automatically so that things such as building corners join correctly. It's to do with having so many buildings and building pieces. I've grabbed this park and spotted what causes the massive slowdown. To receive a verified flair, message the mods with proof of purchase of either: VIP, CHC, Early Bird, or Founder Stone.ĬopyPaste for those who don't want to look for it
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |