View Issue Details
| ID | Project | Category | Date Submitted | Last Update | |
|---|---|---|---|---|---|
| 0014176 | The Last Federation | Graphical Bug | Apr 16, 2014 8:24 pm | Apr 17, 2014 10:56 am | |
| Reporter | ElOhTeeBee | Assigned To | Chris_McElligottPark | ||
| Status | feedback | Resolution | open | ||
| Product Version | 0.904 (Hotfix The Second) | ||||
| Summary | 0014176: Gameplay gets choppy after playing a while. | ||||
| Description | I'm honestly not sure what's causing this one, but I had been playing for a little bit - feeling out the game a bit better, just sort of goofing around. I had accepted a mission to help the Evucks fight off some Acutian pirates, but as soon as it started, the game's framerate went straight to hell - everything got all choppy. It stayed like that after I finished the mission and went back to the solar map, and even on the menu screen when I went to save my game. | ||||
| Tags | No tags attached. | ||||
| Internal Weight | |||||
|
|
Reloading the save, there's no issues whatsoever. |
|
|
In .906, perhaps this will help: * The memory handling of large textures for the game is now _vastly_ better. ** Previously it was loading all of the textures from disk in an uncompressed format. This leads to an absolutely-lossless representation of textures, but it requires... rather a lot of RAM. Gigs. ** Now the game is loading a lot of the larger textures in a very high-quality compressed format -- you won't even notice the difference, visually. The downside is that loading images now takes a bit more CPU power as it cross-compresses them, but that is pretty minor overall. ** The upside is that, thanks to this huge reduction in the amount of RAM used, there is no reason to keep loading and unloading textures like we have been for the last while -- that had a much larger CPU and IO cost, and may have been a memory leak as well (hard to tell; if so, it's internal to the unity engine). ** Just how big of savings are we talking? Well, normally the game loads the images as it needs them, rather than all up-front. However, we toggled it under the hood to load EVERYTHING up front, and these were the results: *** Prior to compression, just having loaded everything and sitting at the main menu: 2.689 GB used *** Post compression, just having loaded everything and sitting at the main menu: 1.177 GB used *** Holy cripes, that's a 56% reduction in RAM use overall, and and overall savings of 1.512 GB total! *** Bear in mind that under normal loading circumstances, the memory footprint at launch is only like 0.9 GB in either case. But as people continued to play, in some cases they would get RAM errors. It was only affecting a handful of people out of 160, but that's still way too many people -- and of course, once the game reaches a broader audience, it was going to be one of those things that affected a ton more people. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| Apr 16, 2014 8:24 pm | ElOhTeeBee | New Issue | |
| Apr 16, 2014 8:25 pm | ElOhTeeBee | Note Added: 0036204 | |
| Apr 17, 2014 10:56 am | Chris_McElligottPark | Note Added: 0036227 | |
| Apr 17, 2014 10:56 am | Chris_McElligottPark | Assigned To | => Chris_McElligottPark |
| Apr 17, 2014 10:56 am | Chris_McElligottPark | Status | new => feedback |
