I'd be down with RTA no loads as the final solution, if possible. An "FPS" variable similar to how RE1R handles FPS differences would probably be sufficient for those concerned with the differential of hardware. The differential here is pretty minimal so I'm not sure it's worth the stink, especially since mechanically no runner is at a disadvantage.
[quote]Isn't RE1R mixed 120 and 60 fps ? It's the game that make me start speedrunning few weeks ago, played it 120 cause the game doesn't really need huge config but it seems that was 60fps run on the board (Carci for example)[/quote]
As far as I'm aware the max FPS in RE1R is 120, even on Variable. The game's framerate will not natively go past that without external tools/mods to 'break' the cap. Which isn't the case here.
60 is allowed as it is in the game, as is Variable. They just aren't tracked as separate categories there, as in, there is no competition solely for 60, or solely for Variable framerate, it's one competitive category, and runners just utilize whatever framerate option is possible for them on their setup.
That said, my opinion would be based around potentially just dropping IGT in favour of another solution. Either manual RTA no-loads (and considering how few load screens RE3R has, this may be feasible) or performed through an RTA script that cuts out loads automatically. Unlike the older Resident Evil games, which had benefits to using IGTs (such as loads not being counted), there doesn't appear to be any such programming here, and it is just a flawed RTA timer with this revelation being brought into light.
In RE2R it was more complicated, because framerate directly affected the gameplay in relation to the knife, whereas here it's just the IGT, I presume?
Hey gang, I was up really late last night digging more into an RTA loadless solution. I thought I had a break through and had @hazeblade test, but it lead to a similar problem.
I still have a bunch of ideas to try, and I'm still digging and will report back. It's good to see people like the idea of RTA loadless. I'll see what I can do :)
Btw, @NuZ -- I'm not a mod. :P
I have played re3r on Xbox 1x and my base console. It feels the same and I have started my speedrun attempts. The menu is just terrible for the game and feels the same on both consoles. I haven't tried ps4 or pro yet. Will update as soon as I get that copy.
@CursedToast haha i know and i think i have never said that, sorry if i did 😊 Nice! Good work! Yeah RTA is common in speedrunning so.
I would vote for a fixed 60fps cap for all cats. Makes it easier to organize everything and can be even more competitive, maybe bring more ppl that didnt play RE2 to the board. Understand its better to play on higher fps and it looks better on streams, but i believe rules should be about whats better for everyone (or most ppl).
I also think the cap should be 60fps. And my PC can easily do 120fps but I know that not everyone's PC can.
I found a solution to this problem. I've contacted the mods for testing. Behaves the same on 60 and 150 FPS in my testing.
@Chris_Hylands -- I'm pretty sure there's talk about separating console and PC anyway.
@NuZ right back at ya :P
Update, hour 16 of working on this today: I think we're pretty damn close to a full bug-free solution to this.
Thanks to @hazeblade and @maxylobes for testing -- I'll work on this more after I get some rest, as its not quite perfect yet. >_<
It might be a stupid question, but how can i setup 120fps when there is no such a option in game ?
C'mon Capcom, employ this man to fix your bugs :D @CursedToast
Awesome work! Really appreciate it, thanks for putting in so much effort :) !
I wanted to drop in with an update on the plans for the frame rate situation. As @CursedToast has posted already, he has come up with a Livesplit solution that effectively gets rid of the issue for PC. While there are a couple of bugs currently being worked out, it will give us consistency for people running on high end and low end PC’s. This will take the basic principals behind the auto-splitter where it is looking at memory in the game but it will track the time separate from the actual in game timer so that frame rate will not cause an issue during cutscenes. The Livesplit timer will be displaying a time that is different from what you will see on the end of game statistics screen. That is entirely the point. The games in game timer is flawed, so identical runs for a PC at 30fps and at 240fps will show different times on the end of game stat screen, where this solution would show the same time for both.
What this changes in the plans is that we will NOT be using the actual in game timer on PC because of it being flawed, though the end of the game statistics screen will still be required to be in your VOD’s for submissions. This also means that there will NOT be a cap on FPS. CursedToast’s Livesplit script will effectively be creating its own version of IGT directly from in game events that are being read from memory. This will mean that displaying Livesplit WILL be required for all submissions on PC and the time displayed on Livesplit is the official time you will use for your submissions, we’ll get to console towards the end of this post. If you don’t care about individual splits, you can simply have Livesplit displayed on screen with just the timer, which is very simple to setup in OBS and similar programs.
The way this script is being implemented will cause a change in the behavior of the clock compared to the game IGT. The Radio calls with Carlos will no longer cause the timer to stop. Using the games in game timer, these calls stopped the clock which caused a situation where moving slower by listening to them fully or until you reached a door or item you needed would take less time than skipping them from the start and moving at full speed. It will now save time to actually skip those calls and move at full speed. The timer will still stop during cutscenes and on the pause screen.
At the time of writing this, the script has not been released publicly since it is getting the last few bugs worked out of it. It is currently being tested by some runners who are bug hunting to make sure everything will be 100% before public release. As soon as it is ready to go it will be available and I will make another update here to let everyone know.
Now to talk about Console. The frame rate issue is at its worst the lower your frame rate is. The difference between 240fps and 120fps is approximately 4 seconds, the difference between 30fps and 60fps is approximately 20 seconds. The Xbox One X and PS4 Pro run the game north of 50fps, neither running 60fps at all times. The other versions of these consoles run in the mid to low 30fps area. Because console can not utilize livesplit, and because of the significant disparity between these consoles, we will be splitting console into two categories. One category for Xbox One X and PS4 Pro and one category for Xbox One S, Xbox One Day One Edition and Standard/Slim PS4, both categories will continue to use IGT.
We believe these options for PC and Console are the best way to make things fair for everyone. It puts all PC runs on the same time, and gives consoles the ability to compete fairly against similarly capable machines. We appreciate all of the feedback we’ve received and again look forward to any feedback or thoughts.
That's so awesome! Seriously.. so many ppl will be excited to hear this! Cheers sir toast!
That's some real good news. I don't really understand how livesplits works but it seems that you guys are doing some hard work. I'm really impressed, many thanks to yo guys
