Instal Steam
login
|
bahasa
简体中文 (Tionghoa Sederhana)
繁體中文 (Tionghoa Tradisional)
日本語 (Bahasa Jepang)
한국어 (Bahasa Korea)
ไทย (Bahasa Thai)
Български (Bahasa Bulgaria)
Čeština (Bahasa Ceko)
Dansk (Bahasa Denmark)
Deutsch (Bahasa Jerman)
English (Bahasa Inggris)
Español - España (Bahasa Spanyol - Spanyol)
Español - Latinoamérica (Bahasa Spanyol - Amerika Latin)
Ελληνικά (Bahasa Yunani)
Français (Bahasa Prancis)
Italiano (Bahasa Italia)
Magyar (Bahasa Hungaria)
Nederlands (Bahasa Belanda)
Norsk (Bahasa Norwegia)
Polski (Bahasa Polandia)
Português (Portugis - Portugal)
Português-Brasil (Bahasa Portugis-Brasil)
Română (Bahasa Rumania)
Русский (Bahasa Rusia)
Suomi (Bahasa Finlandia)
Svenska (Bahasa Swedia)
Türkçe (Bahasa Turki)
Tiếng Việt (Bahasa Vietnam)
Українська (Bahasa Ukraina)
Laporkan kesalahan penerjemahan
Looking into the enemy aiming, too.
Fun Fact, any other details about your situation?
Seeds seem to be based on current time, which would explain why pausing during the generation would result in something different. Rooting seeding into something stable and consistent would fix it 100%, but I recognize that revamping it this late in the dev cycle can be stressful.
Pausing could still have level gen happening as a background process while paused rather than interfering. However this approach wouldn't account for instances where the NT process is forcibly frozen such as when moving the game's window or window dimensions. And of course instances if the game were to hang temporarily, still being rooted in current time wouldn't help there.
And of course the solution I thought would be taken: buffer the pause input until stage gen is over. Still pauses as expected by the player, still avoids interfering with stage gen as per the goal of blocking pausing during load times.
a) making level generation a background process, unaffected by pausing
b) queuing the pause when the escape key is pressed during generation
c) using a different variable than current_time to modify the seed. common of a method as it may be, any interruptions to the process screws up the process.
EDIT: Yes, what Psycho posted earlier on this very page.