Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
However, this is absolutely not what you should do. Unless you're working on something revolutionary there is surely a more optomised way to do what you want to do. Having a million large array would be a huge memory hog even if it was completely boolean variables, and I assume you want to store far more complex variables than that.
So, maybe that many?
+Also, if the individual bats don't need any AI you could render them as particles - you can have many more particles than objects plus they can have physics properties.
Also, how do i find the index of the greatest element in an array, and then the second greatest...
largest_index = i
}