Startup Performance: App::initBlendMaps

[GoogleCodeExporter]

these are issues to track potential improvements in in performance

App::initBlendMaps calculates a lot of data on the fly while they can be cached 
after the first time in an image 

Original issue reported on code.google.com by a.isma...@gmail.com on 30 Oct 2011 at 6:14

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Original comment by Cry...@gmail.com on 1 Nov 2011 at 10:39

• Changed state: Accepted
• Added labels: Component-Logic, OpSys-All, Size-Medium

[GoogleCodeExporter]

We need save and load blendmap (as png) methods working for terrain.
This would be saved in editor and game would just read blendmap png's from 
files.
No idea how much more would that be in tracks size (if too much we drop this).

Original comment by Cry...@gmail.com on 9 Feb 2012 at 11:32

• Added labels: Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Original comment by Cry...@gmail.com on 1 Jul 2012 at 6:43

• Added labels: Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

I'm closing this. We won't save blendmaps, it would increase data too much. (90 
tracks about 1MB for each, that's bad).

Original comment by Cry...@gmail.com on 23 Aug 2012 at 6:06

• Changed state: Invalid