33:11 landmines

I feel like i miss these every time. When do the GP's start?

Someone selected Gravity Track and there weren't enough start positions for the racers, so the server gave up and quit. In other words, the Grand Prix got busted. Also, the last race was busted, so there was that, too.

Someone started the races too soon and the teams weren't set up, so...it's a bonus race :-p

Verry funny the gp

Crystal bringing up the inevitable suffering of playing add-ons.

Thanks for the good time!

Rowdy Thank you... We need people like you to create content for this game that brought us nothing but joy and action. Thanks again.🙂🙂

Wow how you modified the game. Those sounds... Indicates that you play on Windows

When the 1.5 version will release?

Hey

25:39 sus chat

0:26 let me teach these guys a lesson and get away with it - rowdyjoe's swatter :}

also i like your sound effects. They sound like my old game. :}

hello, youtube! :}

Fun races.

tbh Idk what exactly I should fight for in this gp

Jamal is goated.

0:00-2:34 great win rowdy and also nice win of rauldux 31:53-34:36

always close and hard racing between me and haen

of 3!

37:23-45:23 polo came from nowhere and destroyed everybody in ravenbridge and stk enterprise exept when he disconected in black forest lol

10:36 THATS ME

Was fun racing

💥💯

Pretty weird, the icon is fine on my pc, can you help me check if there's icon file in the folder, thx!

im trying to compile this on ubuntu, but its not working, i need a full guide on how to install it, i dont know which cmake command to use, t just says cmake .. without anything else, that does not work

"f u ark", classic quote lol 😂

any idea how to get artist debug mode on mobile?

9:19 🤡🤡🤡

4:52 Flying Matthou ‼

4:08 ☠☠

3:01 ☠

2:41 MOVE YOUR ASS

10:15 faiill!!

7:26 ☠

7:24 nyahahahaha

7:20 grrrrr

7:12 hehehe

I didn't publish the races from yesterday because the audio on my Manjaro system was busted in some very weird ways so I didn't record the races. Too bad because there were a lot of funny moments and some incredible racing. After analyzing the PulseAudio configuration, I figured the root cause was some sort of software conflict. To find the software that should be installed, I installed a fresh version of Manjaro on another drive and compiled and ran SuperTuxKart from there, then I verified that my A/V capture method worked there. After doing that, I compared the software that was installed in the test environment against my production environment. Specifically, I found the set of software that was installed in the test installation that wasn't installed in the production system. Once I found that set, I issued a command to install that software on the production system: `sudo pacman -S chromaprint gcolor3 gst-plugin-pipewire intel-ucode lensfun lib32-mesa-utils libportal libportal-gtk3 manjaro-gstreamer manjaro-modem manjaro-pipewire manjaro-settings-manager-notifier memtest86+-efi openmp pamac-gtk3 pipewire-alsa pipewire-pulse pipewire-session-manager plymouth plymouth-theme-manjaro xorg-server-devel xorg-util-macros` Pacman then prompted me to uninstall a bunch of conflicting packages, most of which had to do with the audio subsystem. I then rebooted and tested and now everything works amazingly well 😎 In the process, I revised the command line for the A/V capture: `ffmpeg -use_wallclock_as_timestamps 1 -f pulse -i $(pactl list short sources | grep "stereo.monitor" | awk '{print $2}') -framerate 60 -f x11grab -i :0.0 -codec:a libopus -codec:v hevc_nvenc -rc constqp -preset:v p1 playing_$(date --iso-8601=seconds).mkv` This command uses FFmpeg for the video and audio capture. Specifically, this command: 1. Uses the wall clock time (i.e., the hardware realtime clock) as the time reference to make sure the audio and video streams are synchronized. 2. Specifies PulseAudio as the input format for the audio. 3. Essentially grabs "alsa_output.pci-0000_0a_00.6.analog-stereo.monitor" as the audio source. The "monitor" source is the outgoing audio of the system (i.e., the game audio). 4. It captures at a constant 60 frames per second 5. Specifies "x11grab" as the input format for the video capture. 6. Specifies the screen as the input video source. 7. Encodes the sound as Opus Audio. 8. Uses Nvidia NVENC hardware encoding for the video, using the HEVC (i.e., H.265) video codec. 9. Specifies the use of the constant quantization parameter rate control method for the video, which uses lots of bitrate for complex areas of the scene and less bitrate for simple areas. 10. Uses the fastest and simplest video preset for realtime capture. It still records in excellent quality, at the expense of more disk space. 11. Saves the video in a Matroska multimedia container with a name that looks something like this: `playing_2024-07-27T13:25:38-05:00.mkv` Here are some notes about this recording method: 1. I record at 60 FPS because that's the maximum frame rate that KZbin supports. 2. I use the constant quantization parameter rate control method because it's efficient at storing video at a high quality while also saving significant amounts of space. Also, the computational complexity of this rate control method is comparable to other methods and it's easy to use and get excellent results. 3. The Matroska multimedia container format is resilient against corruption, including truncation, so if your computer crashes while you're racing and recording, you'll be able to salvage everything that had been written to storage with no trouble. 4. I use a dynamic name for the file so I can easily avoid name collisions so I don't overwrite a recording by accident. The source code of the comparator, in Ruby: ```ruby def grab_first_column(file_path) # Initialize an empty array to store the first column first_column = [] # Open and read the file line by line File.open(file_path, 'r') do |file| file.each_line do |line| # Split the line by whitespace columns = line.split # Append the first column to the array first_column << columns[0] unless columns.empty? end end # Print the resulting array return first_column end production = grab_first_column("Production_installed.txt") test = grab_first_column("Test_installed.txt") puts "Installed in the test environment but not in production:" puts (test - production).map { |x| "pamac info #{x} " } puts "sudo pacman -S " + (test - production).join(" ") puts " " puts "Installed in production but not in the test environment:" puts (production - test).map { |x| "pamac info #{x} " } puts "sudo pacman -R " + (production-test).join(" ") ``` To generate the files: `pamac list --installed > Production_installed.txt`, then do similar inside the test environment. Run this script against the files to see the differences. It'll be different for Ubuntu.

I didn't publish the races from yesterday because the audio on my Manjaro system was busted in some very weird ways so I didn't record the races. Too bad because there were a lot of funny moments and some incredible racing. After analyzing the PulseAudio configuration, I figured the root cause was some sort of software conflict. To find the software that should be installed, I installed a fresh version of Manjaro on another drive and compiled and ran SuperTuxKart from there, then I verified that my A/V capture method worked there. After doing that, I compared the software that was installed in the test environment against my production environment. Specifically, I found the set of software that was installed in the test installation that wasn't installed in the production system. Once I found that set, I issued a command to install that software on the production system: `sudo pacman -S chromaprint gcolor3 gst-plugin-pipewire intel-ucode lensfun lib32-mesa-utils libportal libportal-gtk3 manjaro-gstreamer manjaro-modem manjaro-pipewire manjaro-settings-manager-notifier memtest86+-efi openmp pamac-gtk3 pipewire-alsa pipewire-pulse pipewire-session-manager plymouth plymouth-theme-manjaro xorg-server-devel xorg-util-macros` Pacman then prompted me to uninstall a bunch of conflicting packages, most of which had to do with the audio subsystem. I then rebooted and tested and now everything works amazingly well 😎 In the process, I revised the command line for the A/V capture: `ffmpeg -use_wallclock_as_timestamps 1 -f pulse -i $(pactl list short sources | grep "stereo.monitor" | awk '{print $2}') -framerate 60 -f x11grab -i :0.0 -codec:a libopus -codec:v hevc_nvenc -rc constqp -preset:v p1 playing_$(date --iso-8601=seconds).mkv` This command uses FFmpeg for the video and audio capture. Specifically, this command: 1. Uses the wall clock time (i.e., the hardware realtime clock) as the time reference to make sure the audio and video streams are synchronized. 2. Specifies PulseAudio as the input format for the audio. 3. Essentially grabs "alsa_output.pci-0000_0a_00.6.analog-stereo.monitor" as the audio source. The "monitor" source is the outgoing audio of the system (i.e., the game audio). 4. It captures at a constant 60 frames per second 5. Specifies "x11grab" as the input format for the video capture. 6. Specifies the screen as the input video source. 7. Encodes the sound as Opus Audio. 8. Uses Nvidia NVENC hardware encoding for the video, using the HEVC (i.e., H.265) video codec. 9. Specifies the use of the constant quantization parameter rate control method for the video, which uses lots of bitrate for complex areas of the scene and less bitrate for simple areas. 10. Uses the fastest and simplest video preset for realtime capture. It still records in excellent quality, at the expense of more disk space. 11. Saves the video in a Matroska multimedia container with a name that looks something like this: `playing_2024-07-27T13:25:38-05:00.mkv` Here are some notes about this recording method: 1. I record at 60 FPS because that's the maximum frame rate that KZbin supports. 2. I use the constant quantization parameter rate control method because it's efficient at storing video at a high quality while also saving significant amounts of space. Also, the computational complexity of this rate control method is comparable to other methods and it's easy to use and get excellent results. 3. The Matroska multimedia container format is resilient against corruption, including truncation, so if your computer crashes while you're racing and recording, you'll be able to salvage everything that had been written to storage with no trouble. 4. I use a dynamic name for the file so I can easily avoid name collisions so I don't overwrite a recording by accident. The source code of the comparator, in Ruby: ```ruby def grab_first_column(file_path) # Initialize an empty array to store the first column first_column = [] # Open and read the file line by line File.open(file_path, 'r') do |file| file.each_line do |line| # Split the line by whitespace columns = line.split # Append the first column to the array first_column << columns[0] unless columns.empty? end end # Print the resulting array return first_column end production = grab_first_column("Production_installed.txt") test = grab_first_column("Test_installed.txt") puts "Installed in the test environment but not in production:" puts (test - production).map { |x| "pamac info #{x} " } puts "sudo pacman -S " + (test - production).join(" ") puts " " puts "Installed in production but not in the test environment:" puts (production - test).map { |x| "pamac info #{x} " } puts "sudo pacman -R " + (production-test).join(" ") ``` To generate the files: `pamac list --installed > Production_installed.txt`, then do similar inside the test environment. Run this script against the files to see the differences. It'll be different for Ubuntu.

I didn't publish the races from yesterday because the audio on my Manjaro system was busted in some very weird ways so I didn't record the races. Too bad because there were a lot of funny moments and some incredible racing. After analyzing the PulseAudio configuration, I figured the root cause was some sort of software conflict. To find the software that should be installed, I installed a fresh version of Manjaro on another drive and compiled and ran SuperTuxKart from there, then I verified that my A/V capture method worked there. After doing that, I compared the software that was installed in the test environment against my production environment. Specifically, I found the set of software that was installed in the test installation that wasn't installed in the production system. Once I found that set, I issued a command to install that software on the production system: `sudo pacman -S chromaprint gcolor3 gst-plugin-pipewire intel-ucode lensfun lib32-mesa-utils libportal libportal-gtk3 manjaro-gstreamer manjaro-modem manjaro-pipewire manjaro-settings-manager-notifier memtest86+-efi openmp pamac-gtk3 pipewire-alsa pipewire-pulse pipewire-session-manager plymouth plymouth-theme-manjaro xorg-server-devel xorg-util-macros` Pacman then prompted me to uninstall a bunch of conflicting packages, most of which had to do with the audio subsystem. I then rebooted and tested and now everything works amazingly well 😎 In the process, I revised the command line for the A/V capture: `ffmpeg -use_wallclock_as_timestamps 1 -f pulse -i $(pactl list short sources | grep "stereo.monitor" | awk '{print $2}') -framerate 60 -f x11grab -i :0.0 -codec:a libopus -codec:v hevc_nvenc -rc constqp -preset:v p1 playing_$(date --iso-8601=seconds).mkv` This command uses FFmpeg for the video and audio capture. Specifically, this command: 1. Uses the wall clock time (i.e., the hardware realtime clock) as the time reference to make sure the audio and video streams are synchronized. 2. Specifies PulseAudio as the input format for the audio. 3. Essentially grabs "alsa_output.pci-0000_0a_00.6.analog-stereo.monitor" as the audio source. The "monitor" source is the outgoing audio of the system (i.e., the game audio). 4. It captures at a constant 60 frames per second 5. Specifies "x11grab" as the input format for the video capture. 6. Specifies the screen as the input video source. 7. Encodes the sound as Opus Audio. 8. Uses Nvidia NVENC hardware encoding for the video, using the HEVC (i.e., H.265) video codec. 9. Specifies the use of the constant quantization parameter rate control method for the video, which uses lots of bitrate for complex areas of the scene and less bitrate for simple areas. 10. Uses the fastest and simplest video preset for realtime capture. It still records in excellent quality, at the expense of more disk space. 11. Saves the video in a Matroska multimedia container with a name that looks something like this: `playing_2024-07-27T13:25:38-05:00.mkv` Here are some notes about this recording method: 1. I record at 60 FPS because that's the maximum frame rate that KZbin supports. 2. I use the constant quantization parameter rate control method because it's efficient at storing video at a high quality while also saving significant amounts of space. Also, the computational complexity of this rate control method is comparable to other methods and it's easy to use and get excellent results. 3. The Matroska multimedia container format is resilient against corruption, including truncation, so if your computer crashes while you're racing and recording, you'll be able to salvage everything that had been written to storage with no trouble. 4. I use a dynamic name for the file so I can easily avoid name collisions so I don't overwrite a recording by accident. The source code of the comparator, in Ruby: ```ruby def grab_first_column(file_path) # Initialize an empty array to store the first column first_column = [] # Open and read the file line by line File.open(file_path, 'r') do |file| file.each_line do |line| # Split the line by whitespace columns = line.split # Append the first column to the array first_column << columns[0] unless columns.empty? end end # Print the resulting array return first_column end production = grab_first_column("Production_installed.txt") test = grab_first_column("Test_installed.txt") puts "Installed in the test environment but not in production:" puts (test - production).map { |x| "pamac info #{x} " } puts "sudo pacman -S " + (test - production).join(" ") puts " " puts "Installed in production but not in the test environment:" puts (production - test).map { |x| "pamac info #{x} " } puts "sudo pacman -R " + (production-test).join(" ") ``` To generate the files: `pamac list --installed > Production_installed.txt`, then do similar inside the test environment. Run this script against the files to see the differences. It'll be different for Ubuntu.

I didn't publish the races from yesterday because the audio on my Manjaro system was busted in some very weird ways so I didn't record the races. Too bad because there were a lot of funny moments and some incredible racing. After analyzing the PulseAudio configuration, I figured the root cause was some sort of software conflict. To find the software that should be installed, I installed a fresh version of Manjaro on another drive and compiled and ran SuperTuxKart from there, then I verified that my A/V capture method worked there. After doing that, I compared the software that was installed in the test environment against my production environment. Specifically, I found the set of software that was installed in the test installation that wasn't installed in the production system. Once I found that set, I issued a command to install that software on the production system: `sudo pacman -S chromaprint gcolor3 gst-plugin-pipewire intel-ucode lensfun lib32-mesa-utils libportal libportal-gtk3 manjaro-gstreamer manjaro-modem manjaro-pipewire manjaro-settings-manager-notifier memtest86+-efi openmp pamac-gtk3 pipewire-alsa pipewire-pulse pipewire-session-manager plymouth plymouth-theme-manjaro xorg-server-devel xorg-util-macros` Pacman then prompted me to uninstall a bunch of conflicting packages, most of which had to do with the audio subsystem. I then rebooted and tested and now everything works amazingly well 😎 In the process, I revised the command line for the A/V capture: `ffmpeg -use_wallclock_as_timestamps 1 -f pulse -i $(pactl list short sources | grep "stereo.monitor" | awk '{print $2}') -framerate 60 -f x11grab -i :0.0 -codec:a libopus -codec:v hevc_nvenc -rc constqp -preset:v p1 playing_$(date --iso-8601=seconds).mkv` This command uses FFmpeg for the video and audio capture. Specifically, this command: 1. Uses the wall clock time (i.e., the hardware realtime clock) as the time reference to make sure the audio and video streams are synchronized. 2. Specifies PulseAudio as the input format for the audio. 3. Essentially grabs "alsa_output.pci-0000_0a_00.6.analog-stereo.monitor" as the audio source. The "monitor" source is the outgoing audio of the system (i.e., the game audio). 4. It captures at a constant 60 frames per second 5. Specifies "x11grab" as the input format for the video capture. 6. Specifies the screen as the input video source. 7. Encodes the sound as Opus Audio. 8. Uses Nvidia NVENC hardware encoding for the video, using the HEVC (i.e., H.265) video codec. 9. Specifies the use of the constant quantization parameter rate control method for the video, which uses lots of bitrate for complex areas of the scene and less bitrate for simple areas. 10. Uses the fastest and simplest video preset for realtime capture. It still records in excellent quality, at the expense of more disk space. 11. Saves the video in a Matroska multimedia container with a name that looks something like this: `playing_2024-07-27T13:25:38-05:00.mkv` Here are some notes about this recording method: 1. I record at 60 FPS because that's the maximum frame rate that KZbin supports. 2. I use the constant quantization parameter rate control method because it's efficient at storing video at a high quality while also saving significant amounts of space. Also, the computational complexity of this rate control method is comparable to other methods and it's easy to use and get excellent results. 3. The Matroska multimedia container format is resilient against corruption, including truncation, so if your computer crashes while you're racing and recording, you'll be able to salvage everything that had been written to storage with no trouble. 4. I use a dynamic name for the file so I can easily avoid name collisions so I don't overwrite a recording by accident. The source code of the comparator, in Ruby: ```ruby def grab_first_column(file_path) # Initialize an empty array to store the first column first_column = [] # Open and read the file line by line File.open(file_path, 'r') do |file| file.each_line do |line| # Split the line by whitespace columns = line.split # Append the first column to the array first_column << columns[0] unless columns.empty? end end # Print the resulting array return first_column end production = grab_first_column("Production_installed.txt") test = grab_first_column("Test_installed.txt") puts "Installed in the test environment but not in production:" puts (test - production).map { |x| "pamac info #{x} " } puts "sudo pacman -S " + (test - production).join(" ") puts " " puts "Installed in production but not in the test environment:" puts (production - test).map { |x| "pamac info #{x} " } puts "sudo pacman -R " + (production-test).join(" ") ``` To generate the files: `pamac list --installed > Production_installed.txt`, then do similar inside the test environment. Run this script against the files to see the differences. It'll be different for Ubuntu.

RowdyJoe is win nimeye two hecksel is three

Download link?

Had a fun time racing with you today! Maybe next time I’ll turn on “show other karts held powerups” lol

Nice.. Shall join next time again.. It's 1.30am in my timezone 😅

only one Godette...

Only one Godette

11:25 Thanks for uploading uncle 😂