Topics

Starting from last year's thread, these are the guest tracks booked for the new season!

• ZCT175 (starts Feb 15) - Duplode
  
• ZCT176 (starts Mar 13) - ?
  
• ZCT177 (starts Apr 10) - Dreadnaut
  
• ZCT178 (starts May 08) - ?
  
• ZCT179 (starts Jun 05) - Shoegazing Leo
  
• ZCT180 (starts Jul 03) - ?
  
• ZCT181 (starts Jul 31) - Alan Rotoi
  
• ZCT182 (starts Aug 28) - ?
  
• ZCT183 (starts Sep 25) - ?
  
• ZCT184 (starts Oct 23) - ?
  
• ZCT185 (starts Nov 20) - ?
  

(and we are done on December 18)

Anyone else up for a guest track?

Lifting this thread up, I'd like to hear some feedback about the public replays in the 2015 season

Professionals up there on the scoreboard: did your strategy change a lot? did you wait two weeks before looking at the track, or raced for the LTB points?

Newbies and fellow slower pipsquaks   was it helpful to see replays earlier during the pipsqueak or did you just ignore them? was it helpful to start and discover tricks, or stuff was impossible anyway?

And what about 2016? Do you want them gone, or do you have any tweaks to the formula to suggest?

Slaloms, jumps, more slasloms! (and a few more)

Concrete walls everywhere on this fun track. Also, another good track for the "share you last-frame screenshot"

I thought checking the last second of the replay would give enough information, but it doesn't seem to work as expected:

• if you press Esc immediately after a crash, you get a replay ending with just a few (<20) zeros, but...
  
• if you wait until the game takes you back to the Evaluation, the replay will end with 4 seconds of zeros (about 80 bytes)
  

Checking for the last second being empty works then only for replays saved in the first case. I could check to see if exactly one second is empty, no more no less, but someone might be able to press Esc at the right time and get the right number of zeros at the end of an incomplete replay.

Any suggestions? :|

Changes regarding replay upload and storage are now online

I started a test race which I plan to completely delete in a couple of days. Please spend a second to submit a replay and see if everything works and the changes make sense.

Zak, there's some new code related to replay emails. Can you check if everything looks fine on your side?

Should we try to have a live race every four weeks or so?

Let's start with January, in the weekend 17-18!

I'd say: F40 and Lotus out, Skyline and Speedgate in.

Although I would love to drive that Subaru

I was making some changes to the website, fixing pieces of the registration process, when I realised that Rokker and Boller are likely to be just ghosts. Talk about demotivation

I've been looking into automating the permanent competition, and it's not too difficult. The only thing, I think it's a bit... uninteresting: most tracks have already incredible records, probably all driving Indy, stuck there for more than ten years. Then again, there's no information about which cars were used.

So I thought about this:

• we archive the current permanent competition
  
• we clear up the scoreboards, and restart with the 6 original tracks
  
• I add automatic upload, and store the replays on the website
  
• these replays are public and downloadable
  
• scoreboards filtered by car
  
• every year, we add a new track!
  

Everyone can of course resubmit their original replays, and they'll start at the top of the scoreboard, but these time the replays will be there for everyone to see

Dstien's rpldump gives us the car coordinates; Duplode's annotation language makes it possible to set up section boundaries.

What are we missing? Just something that scans a replay dump and tells us when the car crosses a section line?

[newbies]

Now that we have many (!) newbies around, it could be nice to refresh the newbie guide and the driving school.

• For newbies: what would you like to see there?
  
• For veterans: anything you would like to add? want to help?
  

-
From a previous thread: the full text of the newbie guide, and some ideas for the driving school.

Have they changes in the years?

The code points to 0.10 ? 0.01, but in earlier seasons there are strange numbers like 0.11, 0.17, etc.

PHP has been upgraded to 5.4 on the server hosting stunts.hu, which is the equivalent of changing tablecloth without moving food and plates from the table.

I hope I fixed all that was necessary in the previous days, but if you see anything weird or missing, let us know

Since Zak has updated the version number, new thread for suggestions and complaints!

Still, driving in these is not easy!

• Night Rider Turbo
  
• Hotline Trail

Refreshed the cars coefficients page. Track names now link to the track page, where you can find the coefficient chart.

@Zak: it's also easier to update for new seasons, more comments inside the code

Now here: http://zak.stunts.hu/articles/

Anyone (logged in) can add articles directly on the page, but Zak (or an editor) needs to approve them for publishing. And you can go back and edit your old texts if you need!

Default format is markdown, which means you don't have to bother with html tags, but editors can switch to markdown + html, html code, php, anything actually.

This should make Zak's work lighter, I hope, and easier to submit articles!

Thanks go to Duplode for helping with converting the old texts!

Has anyone tried to make one of those, and put Stunts on it?

No time tonight, but I might give it a try in the future, for CTG's joy!

I was thinking about putting together rplinfo and the replay upload to show details about the replay before this is submitted for the competition. This way one could tell if he's submitting the right file rather than an incomplete run (or some secret trick!).

On the other hand, this would require two step, upload and confirm. Would that be a problem?

I was thinking about something like this. For ZakStunts it's easy to keep stuff up to date, while others (CTG?) would have to edit the .json file manually —it's easy text though.