Recent Posts

I am proud to finally release my latest UT99 Movie I have been working on for the past 2 months! I hope you guys enjoy it as much as I enjoyed making it!

This movie features World Record runs from the Summer Rush competition, which is hosted every year by the UTBT community. The game we play is Unreal Tournament and the mod is called "Bunny Track" or "BT" for short. The goal of BT is to play and finish maps, which include obstacle courses with puzzle elements. This mod has been around since a very long time, 2003 to be exact. We welcome everyone to come and give BT a try!

Feel free to join the official UTBT Discord here: https://utbt.net


Special thanks to @VegasKill for his RypelCam Updates!




(Make sure to watch it with the highest quality)

Nice! Can't believe people still create new UT content. Great video!

I am proud to finally release my latest UT99 Movie I have been working on for the past 2 months! I hope you guys enjoy it as much as I enjoyed making it!

This movie features World Record runs from the Summer Rush competition, which is hosted every year by the UTBT community. The game we play is Unreal Tournament and the mod is called "Bunny Track" or "BT" for short. The goal of BT is to play and finish maps, which include obstacle courses with puzzle elements. This mod has been around since a very long time, 2003 to be exact. We welcome everyone to come and give BT a try!

Feel free to join the official UTBT Discord here: https://utbt.net


Special thanks to @VegasKill for his RypelCam Updates!




(Make sure to watch it with the highest quality)

UT99 RypelCam 1.3.2 - Changelog

- removed pre-set camera path that would load in case of missing RypelCam.ini
- faster paced camera timer for smoother camera movement
- camera speed controls operate at 25 instead of 30 FPS

Let me know if you can reproduce this or if it's just me. The issue is not present when I use older versions like 1.3

I see, I can reproduce this problem.
If RypelCam.ini is not removed before compiling, Unreal Engine 1 will write it into the compiled RypelCam and use it for default values.

You can either open RypelCam.ini and set the cam point count to 0 (value "z=0"), or wait for an updated RypelCam, that will follow soon.


Edit: released UT99 RCam 1.3.2 fixes this issue.

Glad it works out for you.

Thank you for your work again! I have discovered a bug with RypelCam.ini on both new versions (1.3.1 and 1.3.1 FPS_Timer_Fix). If you delete RypelCam.ini and load rypelcam in UT, you will notice RypelCam loads 20 flags which are already placed around the map, they were not placed by me. They seem to be hardcoded too and I can't get rid of them even when there is no RypelCam.ini. This makes new RypelCam paths impossible to make. Could you reproduce this?

1. Delete RypelCam.ini
2. Load RypelCam with DemoManager.
3. There are 20 placed flags around the map. Open RypelCam properties to see them, or spectate them with viewclass CamControl.

Let me know if you can reproduce this or if it's just me. The issue is not present when I use older versions like 1.3

Glad it works out for you.

Controlling RCam over timers caused this problem, among others.
Increasing the timer speed stabilizes the camera speed for moderately higher frame rates. I'm not sure if that causes problems on some other place, though. So if you want to switch to the version with the faster timer, I'll just attach it here to this post.


UT99 Rcam with its dependence on udemo and UT99 specific code is just too different from the UT3 version to simply copy over all the code. Some updates made in the UT3 RCam sure would be a huge improvement in UT99 or UT2k4 as well. Just alone the unreleased code commits to the UT3 RCam...

Uploaded as RCam 1.3.1.

Excellent work, this fixed the biggest issues I had with RypelCam! The camera speed is now much more consistent and it does not go blazing fast when you play it back at higher FPS.

For some reason the camera slows down a bit more than required at increasing FPS. Very drastic frame drops could still have a somewhat noticeable effect on the camera speed...

Yes, I have noticed that as well. Camera speed seems to be fine if you work within the range of 30 FPS to 180 FPS. If we compare 30 FPS against 180 FPS, the camera slowdown is so small that it's basically unnoticeable. It only starts to get noticeable if you reach 250 FPS and beyond. I wouldn't say this is a big deal, it's miles better than before. I'd rather have the camera slower like this when working with really high FPS, before the camera speed used to be so fast that it finished the RypelCam path in one second.

- default keybinds for "PageUp" and "PageDown" change the command from "Cam.softlyquicker" and ""Cam.softlyslower" to the new introduced "Cam.softlyquicker2" and "Cam.softlyslower2", thus no longer causing 20% camera speed changes, but a customizable value (10% by default, configure "cam_speed_change_perc" in RypelCam.ini, default value 10.0 changes playback speed by 10%)

Great new feature and new binds, I did not notice any issues. Customizable speed works just as expected.

Overall, it's a really good update, great work!

Uploaded as RCam 1.3.1.
In the hud you can see by how much the camera speed was reduced, depending on the FPS.
Speed controls work as if the game runs @ 30FPS, so rather smaller changes compared to the previous RCam.

For some reason the camera slows down a bit more than required at increasing FPS. Very drastic frame drops could still have a somewhat noticeable effect on the camera speed...

UT99 RypelCam 1.3.1 changelog:

- camera speed no longer increases significantly at higher frame rates
- speed controls can be operated as if the game were running at a maximum of 30 FPS
- default keybinds for "PageUp" and "PageDown" change the command from "Cam.softlyquicker" and ""Cam.softlyslower" to the new introduced "Cam.softlyquicker2" and "Cam.softlyslower2", thus no longer causing 20% camera speed changes, but a customizable value (10% by default, configure "cam_speed_change_perc" in RypelCam.ini, default value 10.0 changes playback speed by 10%)
- keybinds for "soft" camera speed changes now use reverse percentages, allowing to easily change back to the previous or original speed values
- keybind to activate timed path (default key: "5=summon Cam.btimetrigger") now also allows to disable the timed path

I see. Frame based playback automatically limits the fps to the demo tick rate and does no further time interpolation. If you use slowmotion 0.25 the demo playback changes from 120 FPS to 30 FPS and massive stutters occur.

Time based playback on the other hand does not change the FPS when using slowmotion.
Limiting the FPS rate to the demo tick rate seems to work fine at the first look: no noticeable stutters, similar to the frame based playback.
Although limiting the FPS rate in the graphics settings gives some fluctuations of +-10 FPS, while frame based playback is basically fixed 120 FPS.


Did some tests on the camera speed:
Modifying the RCam camera speed based on the current frame rate seems to give usable results. I'll give it another look and upload it later today so you can test it.