Messages

I had a quick look to see if I could single out the faulty procedure in Restunts, but I could not find it. I think the algorithm to calculate the bounding box of the explosion is still only in disassembly form; in the code ported to C the part concerning the explosion only kicks in when the coordinates have already been computed and converted to the screen reference system.

Since my track is as good as ready and the accompanying piece of purple prose almost complete, I don't mind swapping with @Argammon and giving him two extra months. Unless he'd prefer to swap with someone later in the calendar.

I'll add a vote for Hexa, Lada Niva and Citroën XM.

I'll take ZCT298. I have a crazy idea for a track, which might fail spectacularly.

I went into a creative frenzy and created the track already. It could be used as January track in case of emergency, though it's not a good start-of-season circuit and should better appear in May as programmed.

I've been testing the latest version for quite some time now, and while it works great for the most part, I've been experiencing occasional random crashes, whereas previous versions never did.  Today I discovered a way to repeatedly replicate a crash, so I thought I'd report it.  Here is the procedure:

• Start the game with the graphic level set to "FULL".
• Go to the car selection menu.  The Countach should be selected by default.
• Continuously cycle through the different colours.

After about 15 seconds, the game will crash.  I've experienced in-game crashes as well, but I haven't figured out a way to repeatedly replicate those.

I guess this version will remain a side branch then. When I find the time I will port the new features (unlocked zoom, etc.) on v1.6.

Thanks for your report!

I'll take ZCT298. I have a crazy idea for a track, which might fail spectacularly.

Glorious! I love how it does not even fit in the showroom screen

Orthogonally to the other proposals for PTB I would suggest to not carry over the time bonus across seasons: at season start every driver should be on a blank slate. Moreover, with inter-season carryover, on the final race of the year drivers with nothing at stake would be incentivized to alter their replay posting habits to try to carry as many hours as possible to the new season, i.e. staying just below the 132.5 or the 265 threshold. A ruleset should not force the competitors to pursue these strange goals.

(The replay controls aren't redrawn on every frame, so printf debugging kinda works.)

This was a funny part in my writeup If you need something more sophisticated, I recommend intro_draw_text which does the job quite nicely (example)

If you are analysing conformance, I remind you that the ported `update_car_speed` is currently disabled because it leads to desyncs with respect to the original game.

Looking at the leaderboard now it's awesome how well calibrated the car balance is. Not sure how the Diablo manages to be so competitive vs the Lotus despite lacking the special grip values of the latter, but the chronometer does not lie 

First, I'd like to congratulate you again for your title, Argammon.

It's a pity you have decided not to aim to win the next season. Now, dedicating less time to games and more to "real life" can be a wise choice and I don't want to dissuade you from doing that. And yet, things said and decided after a hard competition, when the adrenalin is still running high, might not always be the right ones. So I would suggest you to check your plans in a couple of months, when hopefully some of the negativity of these last months will have subsided. I think nobody will hold it against you if you announce you've changed your mind and are ready to challenge us full-time in 2026.

Whatever your final choice will be I'm looking forward to see your replays in the upcoming races!

@GTAManRCR If you are interested in alternatives, Cloudflare and Netlify offer free hosting: Cloudflare has unlimited bandwidth, Netlify has a generous 100 GB/month free plan.

@Argammon , congratulations for your Championship title! 🎉🎉 A really dominant performance!

Thanks for the quick fix!

There are no exploits. There is a limit of 2 ptb per race.

The limit does not guarantee the absence of exploits. In certain (rare) circumstances a driver could get more points by doing less.