If(PlayerPrefs.GetInt('Player_' + playerStats + '_inactive') = 1) When i load my data i use this code: // load player stats. PlayerPrefs.SetString('Player_' + playerStats.charName + '_EquippedArmr', playerStats.equippedArmr) PlayerPrefs.SetString('Player_' + playerStats.charName + '_EquippedWpn', playerStats.equippedWpn) PlayerPrefs.SetInt('Player_' + playerStats.charName + '_ArmrPwr', playerStats.armrPwr) PlayerPrefs.SetInt('Player_' + playerStats.charName + '_WpnPwr', playerStats.wpnPwr) PlayerPrefs.SetInt('Player_' + playerStats.charName + '_Defence', fense)

PlayerPrefs.SetInt('Player_' + playerStats.charName + '_Strength', playerStats.strenght) PlayerPrefs.SetInt('Player_' + playerStats.charName + '_MaxMP', playerStats.maxMP) PlayerPrefs.SetInt('Player_' + playerStats.charName + '_CurrentMP', playerStats.currentMP) PlayerPrefs.SetInt('Player_' + playerStats.charName + '_MaxHP', playerStats.maxHP) PlayerPrefs.SetInt('Player_' + playerStats.charName + '_CurrentHP', playerStats.currentHP) PlayerPrefs.SetInt('Player_' + playerStats.charName + '_CurrentExp', playerStats.currentEXP) PlayerPrefs.SetInt('Player_' + playerStats.charName + '_Level', ayerLevel)

PlayerPrefs.SetInt('Player_' + playerStats.charName + '_inactive', 1)

PlayerPrefs.SetInt('Player_' + playerStats.charName + '_active', 0) Д®lse if () When i save my playerprefs i use this code: // save character infoДЇor (int i = 0 i < playerStats.Length i++) I dont understand how this is possile since they are stored with different keys and values based on if the gameobjects is active or not. so it will set all the gameobjects active or inactive. but when i load the playerprefs it will load for only one key and one value. Unity will store the values with correct key and value i checked regedit. I'm not knocking the system, I'm just saying that it's a great addition not replacement for the benefit of any readers.ДЇinally, I was assuming that your approach uses one texture for several objects, by that I mean it's atlased within.Unity does something weird when i use playerprefs to store an int value if a gameobject is active or inactive in hierarchy. If your system is using dynamic batching, then this is also solvable with LODs if groups are clusterable. You will also have issues for example if another object passes behind or inside a distant imposter vs just having say, a 100 poly mesh which likely costs exactly the same as the imposter to render. One good example is you render a few soldiers in various angles while they animate and can then approximate an army that's animated for low cost.ДЄnother issue with imposters vs just having a low poly representation is that there's no depth and lighting can quickly become incorrect. when compared to a correctly set up scene with LODs.Д«ut imposters can really save the day when it comes to distant rendering of terrain as seen in far cry 2, 3 and 4, where they impostor most of the terrain in the far view.Д®ssentially it's currently better than not doing anything at all, but it's not wise to use it for a lot of objects unless it's situational and they have to animate. In isolation, it's clear there's performance benefits from imposters but lots of imposters may be slower than just effective lod management and not having to render to texture / burn ram. Regarding point 2: the performance gains can vary on a modern GPU, it can be that there's a loss of performance due to the overhead of say 1,000 objects being managed (specially when turning) vs just having low poly lods which don't require rendering to texture.

Unity web player demos