Messages

I have a nice track concept in mind but it might be more appropriate for R4K. The basic sketch has no loops/ramps/hills because they do not fit the theme (also no splits but this could change), so it seems suitable for clean and precise driving but not for the usual jump shenanigans and tricks that the pros seem to like.

Sounds nice! And yes, OWOOT track design can be a rather distinct affair -- but one that's no less interesting 

@Cas Noted, thanks! Though again, we might wait a little longer to see if anyone not yet on the calendar wants to join. (In particular, @HerrNove mentioned elsewhere he might want to.)

I believe it already is. If you bring 131:59 of carryover (the maximum amount in the new system) into a race, and then earn 396:01 in it, you'll get PTB +2, and from that point no further bonuses will be available in that race, even if you lead all the way through the rest of the month.

Yes, there is. I think HerrNove meant 2.5 points over two races.

Hello and welcome @Fmarci75 ! For the quickest way to get Stunts running, begin by installing and starting DOSBox. On a PC, you'll see a number of "cycles" on the title of the DOSBox window, which will probably be 3000 the first time you run it. Press Ctrl + F12 a few times to increase it to about 20000, to make sure the game runs well. Then, on the DOSBox prompt, enter...

MOUNT C path\of\your\stunts\folder

... to make your Stunts folder available, navigate to C: and start the game as you would in DOS.

To avoid having to redo these steps every time you want to run the game, it's indeed a good idea to have a dosbox.conf file. Below is a small example configuration file. Change the Stunts folder path and the name of the Stunts executable to the ones you actually have, then save it as a stunts.conf text file and start DOSBox with dosbox -conf stunts.conf from the command line (or create a desktop shortcut which runs that).

Code Select Expand

[cpu]
cycles=20000
core=dynamic

[render]
aspect=true
scaler=normal3x

[autoexec]
mount C path\of\your\stunts\folder
C:
your-stunts-executable

Feel free to ask us about anything you need to get started!

Let's update the calendar, then, with @alanrotoi (thanks!) now on ZCT284. ZCT291 and ZCT293 remain available!

By the way, I probably should try setting a lap time on the "A" track...

Done! 

@HerrNove Indeed, partial carryover does lead to some weird edge cases. Similar situations were also possible with the LTB system that we had until last year: under that, 120 leading hours in one race and 360 in the next would give two points, while 360 and 120 would give just one point (plus 120 h carryover).

Why even have partial carryover, then? That's a fair question. I'd say partial carryover came about as a compromise between two things:

• On the one hand, the main goal of carryover is making it rewarding to earn hours at lower rates. That's especially important now with PTB, given that it's impossible to reach PTB +0.5 in a single race from 4th place or below.
• On the other hand, not having carryover after PTB +1 is meant to introduce jeopardy, and tactics, to fights for the lead. The spirit of it is that if you want PTB +2 (which is a fairly large reward in a linear point system like ours) you gotta be prepared to defend your lead and settle the matter in the current race, without relying on carryover into the future.

Allowing carryover in all cases would make the system essentially continuous, so that summing the hours across the twelve races would be enough to know how many points one gets. That would mean a system that's easier to make sense of, but perhaps a less exciting one as well.

On a somewhat related note, something I'm curious to see -- and that, I guess, we'll only find out in practice -- is whether fights to reach (or prevent!) PTB +2 will be common. If such fights fail to happen, we might have a separate reason to consider adding PTB +1.5.

Mind

Here is the Folyami update after ZCT282! After an eventful first race of the new season, personal best ratings were attained by Argammon (+2 atop of his leading position), Frieshansen and Spoonboy (moving in tandem towards the 2000 points mark). Sizable gains also include those by race winner Alan Rotoi (+36, now nearly back to the 2200s), Overdrijf (+46, biggest increase among ranked pipsqueaks) and Shoegazing Leo (+33, continuing a long-term trend of steady improvement). This race also saw afullo, KyLiE and Usrin returning from breaks. Below is the updated evolution chart:

A minor update (way more minor than the ones by @dreadnaut in last year's thread): in the sent replays stats page, the bar chart for specific races now includes days before the official start (a common case being the Sundays when a track is posted), and subtly highlights the days in which the different phases of the race begin (official start, non-public days, and quiet days).

hard

Comeback Time, Groovy! 

Coordination is an important aspect of it, and it does work as a rule of thumb. It seems to ultimately boil down to how tight the deadline is. For instance:

• A 15 minutes deadline certainly requires coordination.
• A 60 minutes deadline also requires a certain amount of coordination. While, much like in a Formula One qualifying session, we typically won't see everyone starting to race at the same time, all pipsqueaks nonetheless need to join at a time reasonably close to the start.
• A 24 hours deadline arguably doesn't require meaningful coordination in this sense, as pipsqueaks have an entire day to drive and send their replays. The choice of date for the race might make people more or less likely to join, but to an extent that also applies to a monthly race.

Yeah, I haven't been able to catch up with the most posted threads. If I find where, I'll comment. Otherwise, @Ryoma is invited to post here too

It was on the ZakStunts shoutbox (Ryoma doesn't have a Forum account at the moment).