Is there any way to do this in Unreal Gold (Unreal Anthology edition)? I liked my old Unreal version where it went a lot slower and a more consistent speed.
slowing down intro castle sequence?
- Thread starter SkaarjMaster
- Start date
-
Two Factor Authentication is now available on BeyondUnreal Forums. To configure it, visit your Profile and look for the "Two Step Verification" option on the left side. We can send codes via email (may be slower) or you can set up any TOTP Authenticator app on your phone (Authy, Google Authenticator, etc) to deliver codes. It is highly recommended that you configure this to keep your account safe.
Err? Open TimeDemo statistics (from Tools I think) and see if your framerate goes over 100. If it does, set your current renderer FrameRateLimit to 100. That will slow everything down to what it should be.
Do I really want this if I'm installing all the high-res S3TC textures for Unreal from the UnrealTextures web site? Right now I only have the UnrealGold and UT-GOTY edition installed from Unreal Anthology and will be working with these for a while. I think I'll be running both in OpenGL with their respective S3TC texture files.
Last edited:
Yes. You want that on all the time. FPS of 200 will make textures animate fastly, FPS of 300 will make time go faster.
Hmm I really should try this. My fractal textures animate way too fast. And VSync is on IIRC.
I dislike VSync, so FrameRateLimit is better for me. Capping frames to refresh rate isn't fair
What exactly is the use to let your graphics card render more FPS than your monitor can display? (Except benchmarking)
Actually, nobody knows if VSync is better to be enabled or not. General rule is to try out both and decide which you like more. Initially VSync was created to stop screen tearing, but I haven't seen any on LCDs yet. And Wikipedia points out that fast games, like FPSs, react better when VSync is off as their timer is usually based on framerate. But as you can see, in Unreal too many frames make the timer collapse (in UT2003 it might be one of the causes of the Negative Deltatime error I think). Yet having tick set at ~150 might make it stable and responsive enough. Compare to FPS of 75 - it has two times less ticks and thus has less chance to react, making it a microsecond slower.