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
Good track overall.
Best idea I've got is a two-pronged rating out of 5, from "very easy" to "very hard": "How hard is it to learn?" (based on the layout and obstacles on track; basically "how hard is it to just get a clean lap at speed?") and "how hard is it to master?" (based on how difficult it is to optimize laptimes once one has learned the track and how tough it is to keep consistency)
Something like, say, Shiva's Dance's firmly in a 1/5 "very easy" in both. Conversely, something like Annapurna would be a 5/5 "very hard" in both. An example of an "easy layout, hard to master" would be Druidia. You're not gonna have a hard time getting around it, but getting around it *quickly* is another matter because those pipes provide a lot of options. "Hard layout, easy to master" would be something like Pretoria Stadium. Once you've got the trick, that track's a piece of cake.
Hard tracks would be like Tupu Inca and Sovereign. I considered it, but you can airbrake your way out of this one. This does mean there's a huge gap between average and good players, but average players don't automatically suck eggs like on those tracks.
I need a more scientific classification system.
You have affine mapping enabled, a new feature that tries to emulate PS1 vertex jitter. It doesn't do a very good job of it, mainly because the default values are way too high and changing it is a manual config for every mesh.
This means every track made before the option was added will be messed up if affine mapping is enabled, unless I go through and update dozens of tracks to work around a broken feature in the first place. I think I value my time more than that.
The entry into the opening hairpin's structured such that if you go at it straight-on, you land on the wall or get caught by the wuss wagon. Had to take a few laps to get used to it. Ain't the most intuitive; "steer right to go straight" right off the line, basically. Layout's really fast and tight overall.
Also...I'd bump this up to "hard" on the difficulty scale. The track really does not let up at any point, and even the straightest section undulates like all hell (setting you up for that turbo on the ceiling if you play it right). All in all, this IMO is a little too tough for "medium".
Anyways that being said i was wondering if you could help me out with a problem im having with some of the tracks, you see when i played them the first time, some months ago, they played just fine, but now when i tried playing them it seems that in all the tracks that have trees, like sylvatar for example, the trees move weirdly, slide on to the track and sometimes even block your vision, now i dont know if its because i updated to the beta or if its something i changed in the game options or what, but i was hoping you could shed some light on whats happening and how i could fix the issue, if you dont mind.