#race condition

[haikcute]

Race Condition - Chapter 1 Convergence

A Ghoulcy Pre-War Fallout/Formula One AU

Summary

Every Formula One race is built on thousands of calculations. The best drivers ignore them. Lucy MacLean has spent her career believing every answer could be found in the data—until the numbers begin predicting people instead of races. As Formula One falls under the influence of Vault-Tec's powerful new technology, veteran driver Cooper Howard becomes the last variable that refuses to fit the model. Together, they'll discover that some things can't be simulated: instinct, choice...and the quiet kind of love that grows between two people who spend years learning each other one heartbeat at a time.

Chapter Preview

There was a particular kind of silence that only existed inside a Formula One garage before dawn. Not quiet—Formula One was never quiet—but a silence born of routine, of hundreds of people who knew exactly what had to be done and saw no reason to waste words while doing it. The circus hadn't arrived yet. That was how Cooper thought of it, anyway. In another hour the paddock would belong to television crews, hospitality guests, sponsors, FIA officials, and reporters who somehow managed to ask the same three questions every race weekend while sounding convinced they'd come up with something original. But right now... Right now the garage still belonged to the team. [...] Lucy MacLean didn't announce her arrival simply by walking into a room. If anything, she had an almost supernatural ability to slip into the background, crossing the garage with her attention already fixed on the tablet tucked beneath one arm as though she'd walked through those doors halfway through a thought and intended to finish it before acknowledging the rest of the world. Cooper noticed her before anyone else did. Not because she demanded attention. Because after eight years of working together, he'd learned the quiet rhythm of her entrances. Lucy always arrived looking as though the day had already begun an hour before everyone else caught up. [...] "You absolutely do not." "I object." "You've used the phrase 'statistically significant' before breakfast." "Because it is statistically significant." He laughed. "There are mornings I genuinely wonder whether you dream in spreadsheets." "I don't." "No?" "I dream in simulation outputs." He regarded her for a long, thoughtful moment before nodding once. "...That's somehow worse." [...] "I found it." He leaned beside her. "That sounded encouraging." "It isn't." "What did you find?" She traced one finger along the branching lines. "This model normally explores thousands of ways a race might unfold." "And now?" "It still explores them." She paused. "...It just keeps deciding they all end almost the same way." He frowned. "The drivers?" Lucy met his eyes. "Everyone."

🏁 Read Chapter One on AO3

[vadapega]

Here's another contender for the most useless fact about a Sonic game

You know that crash in Labyrinth Zone act 1? They never fixed it in Sonic 2

In fact, you can trigger it much earlier if you know where and when to do it, but it's trickier to pull off.

[mentalisttraceur-software]

One frustrating edge case with Syncthing and Git to look out for:

Empirically, just based on observed behavior, it seems that Git has lots of commands that you'd think are read-only, but which in some cases will mutate internal Git state - specifically, the index (normally at ".git/index"). I haven't yet figured out if this can ever happen with other internal ".git" files.

This creates a race condition with any networked filesystem sync - if you do some work on a local checkout of a repo, then switch to another device to continue where you left off, you can't safely check if Syncthing has synced the local changes to the repo in the most intuitive way: by running commands like "git status".

You have to wait until you're sure the changes have synced, or you'll get a Syncthing merge conflict with the Git index file, which will manifest as weird/unexpected results from commands like "git status" and "git diff [--staged]".

(If you want to look more deeply into this, I'd probably start by reading and understanding Git's "Racy Git" documentation, which seems indirectly relevant - it's talking about a different race condition, but I wouldn't be surprised if the optimization which causes that race condition and/or any workaround which mitigates it contributes to this race condition.)

Luckily, it turns out that we can force Git to never mutate the index. With recent Git versions, there's a top-level "--no-optional-locks" flag that will do it: "git --no-option-locks status".

[jessepinwheel]

I feel like talking about my wips somebody ask me questions about them

[toyota-supra]

anyway I don’t know if I’ll play the rest of the demos I saw on this week’s event (hopefully I’ll play more this week because good lord I am lazy sometimes) but I have two games I immediately want to talk about for now. first up is:

Race Condition

good lord my screenshots are so low-res. I don’t know why that is. anyway this is a simple circuit racing game - just accelerate and brake - but it’s the kind of game for people that like Trackmania and that kind of game. I did a time trial for a bit until I got like 128th place on leaderboards (pretty good!) and then did a race against the CPU like the above (I got 3rd place). I like how well the menu interface and stuff works; it’s all very well-made! the cars also flash a red light at the back when you’re going too fast for a corner which is cool (well you can still try and cheese a drift but yknow). game comes out March 1st!

Grand Mountain Adventure: Wonderlands

looks like shit in my low-res screenshot again

I’ve never played any ski/snowboard games except on like. a few instances in birthday buffets and I wasn’t very fond of them. but this is really good! it’s a nice very charming game with simple but very carefully implemented controls, fun objectives, a lot of exploration, etc; it reminds me of art of rally if that game was about snowy mountains instead of rally racing history. I played it for about 13 minutes and REALLY enjoyed what I experienced. it’s in my wishlist now hehe. game comes out March 10th!

[linuxgamenews]

Race Condition arcade racing and a Linux port

Race Condition low-poly arcade game developer evaluating a port for Linux with Windows PC. Thanks to the effort and further detail from developer Ravine Studios. Which is currently available on Steam with 93% Positive reviews. Swedish indie developer Ravine Studios released their physics accented arcade racing game, Race Condition. Which is doing well on Steam right now. A game that also takes place in a modern low-poly arcade world. While players of Race Condition find themselves as a rookie in a highly competitive open-wheel racing league. A rivalry with the suspiciously good opponent Mr. Dickmann takes them on a tour across the world. One that also unfolds a series of intense races with their fair share of crashes, pit-stops, and strategic choices. Now that you have the premise of Race Condition. I reached out to Ravine Studios regarding Linux support. Doing so in partial response to the Discussion post. But also as a follow up to the ongoing emails.

As for a Linux port, we are still evaluating the cost/benefit of this. As you know, Steam are pushing Proton quite heavily (even more so now that Steam Deck has come out).

Since Proton is one of the issues here. I did test out Race Condition myself, yes it works, as does the Steam Demo. But the game is developed in Uniy 3D, which does make the porting process far easier. As a result, Ravine Studios will continue to evaluate a port. Interested Linux gamers can vote via the Discussions link above. If you're undecided, check out the gameplay trailer.

Race Condition Trailer

Taking its low-poly looks and simple controls from the arcade hits of the past. Race Condition adds in realistic car behavior to end up with arcade racer. One that also looks deceptively simple, but provides a real racing challenge. Doing through a simple David and Goliath story. In true arcade fashion, the races are only a few speedy minutes long, and there is no heavy car setup. Coupled with fast loading times, players might just find themselves lost in a “just one more go” loop. Resistance is provided by the opponent AI which has been carefully crafted to play fair. Whatever the AI manages, the player could do the same. The best chance of beating them might just be with a more clever pit-stop strategy. Race Condition ships with three distinct game modes:

World Tour Travel the world by beating rivals and unwinding the story of who will be the champion. Set on four continents, the 21 tracks (including 10 reverse versions), unlocks as the player progress through the tour.

Quick Race Play the unlocked tracks to climb the online leaderboards, or go head-to-head with friends in local split screen racing.

Time Trial Practice makes perfect. Here, the player can enjoy the unlocked tracks without pit-stop concerns or AI drivers getting in the way. Speed is crucial though, as the player searches for the perfect race lines in an attempt to beat the global lap records.

Race Condition will have you delve into low-poly arcade world. Which is available on Steam for Windows PC, but holds hope for Linux. All priced at $12.99 USD / £10.29 / 10,79€.

[script-ease]

[tradeshanty]

Some programming algorithms require a series of operations to execute in the correct order or with the correct timing. In a multithreaded or distributed environment, this can be difficult to control, and a poorly-written algorithm can suffer from bugs if it does not enforce checks on the sequence. If an attacker discovers the flaw, he can use malicious code to try to exploit the bug in his favor. This attack vector is known as a race condition.

Image: Wind River