Instalar Steam
iniciar sesión
|
idioma
简体中文 (chino simplificado)
繁體中文 (chino tradicional)
日本語 (japonés)
한국어 (coreano)
ไทย (tailandés)
Български (búlgaro)
Čeština (checo)
Dansk (danés)
Deutsch (alemán)
English (inglés)
Español de Hispanoamérica
Ελληνικά (griego)
Français (francés)
Italiano
Bahasa Indonesia (indonesio)
Magyar (húngaro)
Nederlands (holandés)
Norsk (noruego)
Polski (polaco)
Português (Portugués de Portugal)
Português-Brasil (portugués de Brasil)
Română (rumano)
Русский (ruso)
Suomi (finés)
Svenska (sueco)
Türkçe (turco)
Tiếng Việt (vietnamita)
Українська (ucraniano)
Comunicar un error de traducción
This can be easily implemented while maintaining a real-time simulation.
ADDENDUM: This can also be implemented in such a way as to allow the user to decide the ticks per second either for the entire simulation, or on a per-park or per-coaster basis (or both). Note that the difference between 100 and 200 tps is probably not noticeable, while the difference between 100 and 50 tps may noticeably impact simulation results, especially on very long rides.
Edit: Also things like high speed switch tracks would be useful, but I'm guessing that can be done with scripting.