ArgentinaA few months ago i saw a post on the official EA page of a guy talking about how broken the in-game timer in the Crazy Targets Range was (the same that is used on Zomburger Delivery, Chomper’s Pizza Delivery, etc) depending on how many FPS you play the game. After some tests with different frames per second values by comparing 1 minute in real time, the results that he got are actually insane:
2560x1440 (144Hz) Maxed out graphics -> 90-95 FPS = 44 seconds! 1280x720 Maxed out graphics -> 144 FPS = 68 seconds! 1920x1080 Maxed out graphics -> 144 FPS = 68 seconds
Then I've used Riva tuner to limit my FPS (2560x1440 - Maxed out graphics). 1 minute in real time is (standing still at the start, not moving): 30 FPS = 56-57 seconds 45 FPS = 63-64 seconds 60 FPS = 56-57 seconds 75 FPS = 70-71 seconds 90 FPS = 42-43 seconds!!!
- Original post here: https://answers.ea.com/t5/Technical-Issues/Crazy-Targets-Time-affected-by-FPS-A-lot-Gamebreaking-Bug/m-p/5184971#U5184971
As we all can tell, EA has never fixed this bug, and the main reason for this post is that we are currently using this IGT in 4 different categories (all of them from the individual levels). In order to fix this, i think we have 2 options:
-
Remove the IGT and start running the leaderboards by the RT just like what we are doing with all the other categories.
-
Keep the IGT on the runs like something secondary that people can put if they want, because runs are only going to be verified by the real time.
The Big Mama problem: At this point we have over 40 submissions with this timer, and that means we have to re-time all those runs and change them to RT because this is something that MUST be fixed.
P.S: If you ask me what happens with the levels that we can shot gnomes to freeze the time, i think the best option is just ignore them and simply use the real time in the whole run, because if we are going to calculate how long the time was freezed for ich target that he shot, at the end, the final time is more like an approximation.
People dont even upload his times on YouTube. Back in 2017-18 i was the only how was doing that, but then people star heting better and after some months all my privious records were beaten, but not a single one was on YT. So my question is: should i take my runs as a world record beause they have video proof? or put my rank on the title? should i keep with the "no vid no did" argument?
No problem man. I came up with this idea because at this point all the 16 leaderboards have been completely broken due to cheats. It's now that I realize the work it would take 16 ils for something that it's not that special. Sorry if I was rude at some point on this forum, I would not like to have a bad relationship with people that I personally admire.
In-game leaderboards that include videos of each runs are the ones that wouldn't make sens to be on speedrun.com. The crazy targets boards can easily be manipulated, the pc ones are full of hackers, on ps4 people can get times under 2 seconds without even hacking: https://photos.app.goo.gl/ph7DM6w5HEmyFLJU7 , or 1st in the Pirate boards without using the character: https://photos.app.goo.gl/Nk182PhbnmfhWgbT9 But I am not here to fight, I love and respect how this speedrun.com site was designed, but ils for crazy targets is reasonable in order to know what the real WRs are.
Basically it's called crazy targest, and it's a speedruning course that has in-game leaderboards for each character. A few years ago I got 8/16 1st's, my channel exploded, I got 12K total views (it blew my mind). The years passed and now the runs are very perfected, but none is proven on video; so It would be a good idea if you guys make crazy targets as a misc or ILs category with leaderboars for each character. The rules would be: -Runs assisted by more than one person are not allowed since it's a course to be done by one person and apart from the leaderboards as well. -IGT is used for runs. -Any glitch is allowed as long as it's done by a single person, without the help of someone else.
Yeah, definitely. If there are ils for Goat% why not for Chomper%?
