Messages

* The renames of the global variables must be performed on the asm code too. I could do it easily with a search-and-replace but it is my understanding that the asm files are somehow generated by IDA Pro, so the clean thing to do would be to update the IDA database. Do you know how the process works?

Yup, the originally intended workflow involved alternating between analysis and porting through IDA scripts to keep everything in sync. The process is outlined in the Restunts readme.

(I'm not actually experienced with that workflow, as back in the day I did a fair amount of code reading and note-taking, but no porting. I keep meaning to rectify that, but couldn't get to sit down and focus on it yet...)

I intend to write some detailed doc when I have time. However, for a quick look, have a look at frame.c in Restunts:

Thanks for the useful notes!

On the axes, z corresponds to the vertical axis on the track grid because y is (almost?) everywhere the height axis (even in various places where it isn't relevant to whatever is been done). In any case, there certainly are quite a few confusing names across the current Restunts code! 

Thanks Duplode, feel free to update the rules file.

All right, it's now updated 👍

Welcome, @HerrOtto ! That's a very nice mod indeed. The long line of sight reminds me a bit of @Cas ' renderer, though of course this one is directly playable right now!

The clarification about the 23 drawn tiles is itself very interesting. If you have any notes or code about it that you'd like to share, that would be great 

Lemme sign up while I still can!  Please book October for me.

This track is an amusement park!  So many different lines to try, with the various cars offering wildly different rides.

Sword

[unofficial]

I have prepared an unofficial preview of the PTB situation at the end of the ZCT282 public days (that is, a few hours ago). The hours were counted using my simulator, and so the results might differ from the final implementation in details like rounding. Also, I haven't added any carryover hours from 2024; whether that will happen is yet to be settled. Anyway, here are the numbers:

Räcer		Stunts hours/minutes
Argammon		224:52
Alan Rotoi		103:54
Spoonboy		76:40
Duplode		39:53
Frieshansen		28:17
dreadnaut		25:42
Mortimer McMire		15:56
Zapper		8:28
Cas		4:26
Overdrijf		3:25

The full breakdown of real hours spent at each position is in the attached spreadsheet.


@dreadnaut Re-reading the draft of the rules, I have noticed another difference relative to the proposal. The draft says "Pipsqueaks in first position gain 0.5 bonus points for every 132 hours", which would imply the existence of a PTB +1.5 step between PTB +1 and PTB +2. With there being only three steps, it's probably easier to just have a table listing them:

Hours		PTB points
132		+0.5
264		+1
528		+2

Wow, that's beautiful 

Thanks for the update, @Cas ! Nice to see the integrated command prompt coming along.

Brilliant! Congratulations @Akoss Poo a.k.a. Zorromeister 

The fate of my potential job as a researcher (now I am accidentally working at the sales department) can be decided 17th January 2025, when the public defense of my doctoral dissertation takes place...

The 17th is tomorrow -- may you have an excellent defense!

dosbox for Mac

A tangent: our Stunts tools are unfortunately lacking when it comes to macOS coverage, as the toolmakers among us typically don't have a Mac available for testing or building binaries. CarEdit and several of Cas' tools have DOS builds at least, so they can be ran on DOSBox as a fallback.

And now, something optional: since you're remaking your DOSBox setup, consider switching to DOSBox Staging, which offers a number of nice quality-of-life improvements over vanilla DOSBox (for instance: correct aspect ratio by default; tasteful CRT filters; integrated MT-32 emulation; improved controller support).

I've updated the rules for 2025 with a first draft, have I missed anything?

I think the only thing missing is carryover. Something like this:

• Pipsqueaks who get less than 1 bonus point in a race carry unused hours to the next one. E.g. if you get 100 leading hours in a race, you'll start the next one with 100 leading hours; if you get 200 leading hours instead, you'll bring 68 to the next race, as the other 132 earned you PTB +0.5.

BTW, it's a good occasion to settle what we're going to do about cross-season carryover. More specifically:

• Confirm whether we're eliminating it for future seasons (IMO we should get rid of it); and
• Decide what to do, on an exceptional basis, with the carryover leading hours from 2024 (I think it could make sense to convert them to the new system, in order to honour any expectations from the previous rules).

Can anyone generate side images for the Camaro, Diablo VT, and Oxia? 🙏

Generated and uploaded