You can use any version released by Rockstar. This list goes from 1.0.0.0 to the latest version of the Complete Edition (which is the Rockstar Launcher version). Running it windowed is also perfectly fine. The downgrade shouldn't work on the Rockstar Launcher version.

As you can see from this video, the framerate seriously impacts the in-game timer. The upper left video completes the race with an in-game time of 3:53 and an RTA time of 4:07. The lower right video gets an in-game time of 3:54 and an RTA time of 4:23. The FPS in the upper left video likely averages around 100 or so while the lower right video averages around 210 or so.

Timing begins when "go" appears in the center of the screen and ends when the race is finished. Runners are not required to have a timer of any kind displayed in the video. Moderators can and will retime races when necessary.

As a new runner, it depends on how seriously you want to take it right out of the gate. Below is a beginner's guide and splits file which will get you through the run. A lot of useful information is found on the resources page. Some additional information can be found on the forum listed below. Downgrading to 1.0.4.0 has become a real mess ever since the game was updated to the 'Complete Edition'. To abide by the rules here and on Discord, we really can't discuss how to downgrade the game as that would involve certain skull & bones tactics. I would recommend doing a search online for a method, or purchase a physical copy of the game. The main reason to downgrade would be to get better performance. Graphically, view/detail distance and shadows have the greatest impact, as is often the case. Lastly, be sure to read the game/category rules.

Beginner's guide - https://docs.google.com/spreadsheets/d/e/2PACX-1vQCp71bXczgsFzghuLUC1t9qIIJzy2c7MKVi1ht6XdfgW_pTog0qhkGnGatp62mOK2tJbsuVOa2P6km/pub?gid=564829700&single=true&output=pdf Beginner's guide splits - https://www.speedrun.com/splits/Grand_Theft_Auto_IV_-_Any_ucuy6.zip Discord - https://discord.com/invite/7gCbWuq Additional resources - https://www.speedrun.com/gtaiv/resources Rules update thread - https://www.speedrun.com/gtaiv/thread/816c6 GTA IV Forum - https://www.speedrun.com/gtaiv/forum

It should also be noted that for any runners with an "artificial loadless time" (-11:00), if you complete a run which beats your current 'with loads' time, but doesn't beat the 'artificial loadless time' currently on the board, please still submit this run so you can have an accurate time on the leaderboard. None of these runners should have trouble beating their 'artificial loadless time' to begin with.

In regards to Any% runs submitted prior to June 3rd, 2020 which lack a loadless time, what I'll be doing to keep these runs fairly ranked, to the best of my ability, is knocking exactly 11:00 off of the "with loads" time and using this as the "without loads" time. The value of 11:00 is the average load to loadless difference of all nine runs with a loadless time on the Any% leaderboard.

For 100% runs, because Stig's load to loadless difference is 18:59, and his is the only submission with a loadless time, the deduction will be 18:59.

For All Pigeons, a 13 second deduction.

For All Stunt Jumps, an 18 second deduction (hoxi's run has a 1:56 difference, this will not be considered due to it being a major outlier).

For Classic, a deduction of 5:27 because that's the difference in hoxi's run, the only run on that leaderboard with a loadless time.

Stig: For Most Wanted, a deduction of 3 seconds of loads + 2 seconds for each death.

Stig: For Sweatshirt, deducted Rave's loads time from all Sweatshirt times, and added ms to non-ms submissions.

Runs submitted before June 3rd, 2020 are grandfathered in under the ruleset which existed prior to these new additions.

The run will be considered invalid if

• A save file from a previous speedrun/playthrough/instance of the game is loaded at any point during the attempt ------The runner is permitted to create save files during the run through autosaving and/or saving at the various apartments (These save files can be loaded at any point during the run in which they were created)
• There isn't adequate video/audio proof of the attempt ------The run must be contained in a single upload (no multipart uploads or missing sections) [LOCALLY RECORD!] ------In-game sound effects are audible on the video and are not delayed ------Video resolution is at least 360p ------The video is not too dark or too bright to see the run clearly ------Video is in full color (no black and white, other than when killed/busted) ------Video file framerate is at least 25 FPS with no excessive stuttering or frame drops for extended periods of time ------The video begins prior to the first black frame and ends after the first frame of the final cutscene (Include at least a few frames of the first/final white splash screen and at least a few of the final cutscene) ------Everything the runner was able to see in-game during the run must be visible in the submission video (no cropping of the game feed in post)
• A cheat is entered
• A banned memory monitoring tool was used ------Memory monitoring tools are outright banned (minus the exceptions). If you're using a tool which monitors the game's memory to provide you some sort of information, you're breaking the rules. EXCEPTIONS: Auto-splitters (splitting on mission start/end, objective complete only) and loadless timers
• The submission video has been tampered with (cuts, splices, sped-up, etc.)
• A modification is present in the game's files (Xliveless & downgrading the game/in-game radio is allowed)

Runs use the “Time Without Loads” (loadless) timing convention, which means it measures the real time that has passed from start to finish, minus loading times. Acquiring this time is accomplished by using the load time removal tool which is integrated with LiveSplit. You will need to use this tool in order to have an accurate time for the “Time without loads” column on the leaderboard. You can find the “Alternate Timing Method” here - https://livesplit.org/components/. Once properly installed, it can be added to your layout just like any other component. It’s found under “Information” in the layout editor. This timer must be clearly visible at all times during the broadcast and submitted proof video.

• If the moderators cannot verify the run’s loadless time for whatever reason, the run’s RTA time will fill both “Time without loads” and “Time with loads” on the leaderboard

The in-game FPS limit is 250 frames per second. The game literally speeds up when you go beyond this value. You must limit your framerate to, at most, 250 frames per second.

• An FPS monitor must run while the speedrun is taking place and this same FPS monitor must be clearly visible at all times during the broadcast and submitted proof video
• The FPS monitor must be of appropriate size and color
• If you give your FPS monitor its own background (text background), make sure the font color contrasts well with this background
• If the FPS monitor is not shown, even for a few seconds, at any point during the video, moderators will take a closer look to determine if measures should be taken in regards to the legitimacy of the proof video
• As long as the FPS achieved does not go beyond the limit of 250, any and all tactics used to achieve a higher/lower frame rate are allowed to be used prior to the run beginning, as well as during the run (hotkey toggling on/off the following: overclocking, underclocking, frame limiting, resource intensive processes (example: toggling on the recording feature in your streaming software, which will record at an extremely high quality, thus reducing your FPS for the duration of the recording), etc.), as long as the game's files are not modified in the process
• You are allowed to have multiple FPS limiting tools running at once (i.e., you can have a program like RivaTuner limiting the FPS to 250, while also having a program like Bandicam prepared to lock the FPS to a lesser value when needed)

The run must begin on a Wednesday (in-game).

• This is the day the game is designed to begin on when a player starts from a fresh install. If you clear your saved games folder, you'll always start on a Wednesday
• Vehicle/pedestrian spawns are partially controlled by whether it's a weekday or the weekend, and some are controlled by specific day(s) of the week
• The day of the current session will carry over when the player starts a new game from the pause menu (e.g., You’re halfway through an Any% attempt and decide to reset. The current day is Friday. You pause and select ‘New’ within the menu. When you gain control of Roman’s Taxi at the start of the new game, the current day will be Friday). This is not allowed. If the current day is Wednesday when the player decides to start a new attempt, the game will begin on Wednesday. This is allowed.

This small community is already in agreement that this type of advantage is not allowed and any runs submitted in the future which include the effect being discussed in this thread, will be rejected. We won't be adding a 'rule' until we see concrete evidence of this effect in action; Preferably a multi minute segment of the Any% speedrun.

Needed to see for myself.

Jumping animation...from the starting frame of the animation to the final frame of the animation; FPS: 25 (locked) to about exactly 250 (unlocked) Frames: 130 frames Time: 0:00:02.167

Conclusion - no difference in the time it takes to complete a jump with FPS in the range of 25 to 250

In the video (vertical jumps); FPS - Frames - Time 150 - 128 frames - 2.133 260 - 126 frames - 2.100 280 - 123 frames - 2.050 400 - 96 frames - 1.600 400+ - 75 frames - 1.250, again at 74 or 75 frames, and a third time that was virtually the same

Here are some of my findings from June, 2017 -- Rate of fire MICRO SMG 10 - 443 - 0:00:07.383 20 - 293 - 0:00:04.883 30 - 294 - 0:00:04.900 40 - 294 - 0:00:04.900 50 - 294 - 0:00:04.900 60 - 279 - 0:00:04.650 70 - 251 - 0:00:04.183 80 - 256 - 0:00:04.267 90 - 261 - 0:00:04.350 100 - 264 - 0:00:04.400 120 - 259 - 0:00:04.317 140 - 252 - 0:00:04.200 160 - 256 - 0:00:04.267 180 - 253 - 0:00:04.217 200 - 249 - 0:00:04.150 250 - 247 - 0:00:04.117

Liftoff - from entering until 30 MPH liftoff speed is reached MAVERICK 10 - 1481 - 0:00:24.683 25 - 995 - 0:00:16.583 40 - 983 - 0:00:16.383 60 - 989 - 0:00:16.483 80 - 988 - 0:00:16.467 100 - 983 - 0:00:16.383 150 - 982 - 0:00:16.367 200 - 982 - 0:00:16.367

Boat Speed - From 2 to 30 MPH - boat (I was never holding Ctrl) SQUALO 10 - 305 - 0:00:05.083 25 - 179 - 0:00:02.983 50 - 207 - 0:00:03.450 100 - 208 - 0:00:03.467 150 - 191 - 0:00:03.183 200 - 227 - 0:00:03.783 250 - 200 - 0:00:03.333 *Holding CTRL will lower the time it takes to get from 0-50 by about 5 seconds (If you didn't know)

Driving Times - Straight line (to about the best of my ability), from line A to line B, on the runway, running over the bumps (lights) along the way which line the center of the runway BANSHEE 30 - 1476 - 0:00:24.600 - 95.676 MPH 60 - 1461 - 0:00:24.350 - 95.712 MPH ~120 - 1458 - 0:00:24.300 - 96.979 MPH

ROMAN'S TAXI 30 - 1700 - 0:00:28.333 - 85.373 MPH 60 - 1753 - 0:00:29.217 - 80.838 MPH ~120 - 1739 - 0:00:28.983 - 82.344 MPH

Breaking - From just about 90 MPH to virtually 0 - breaking on the runway (dry surface) BANSHEE 30 - 88.921 MPH - 0.024 MPH = 200 (frames) - 0:00:03.333 ~120 - 87.613 MPH - 0.083 MPH = 218 (frames) - 0:00:03.633

**The Any% splits can be found under the splits section of this resource page: ** https://www.speedrun.com/gtaiv/resources

Only missions are included and the route is taken straight from the guide. Additional information, what you see in the red, light red, blue and black boxes within the starter route/guide, is not included. The additional information will have to be added by the user. Some people prefer for additional info to be included within mission splits, while others prefer entirely separate splits, sub splits, etc., and then there are those who will add absolutely nothing to these splits and will have the route document open, alongside the splits.

If you're new to the IV Any% speedrun or just aren't so sure your current plan will get you through the run without issue, don't fret. I've created a guide that should basically get anyone through the IV Any% run, no matter what their pace is. With this guide, every single player should be able to get through the run without issue. I've uploaded it on my Google Drive. Link below.

PDF: https://docs.google.com/spreadsheets/d/1YzVsHxqDSXIY-LgjX_iZi8fgg7TCmfn7gNiFZF0n7Lo/export?gid=564829700&exportFormat=pdf&format=pdf&portrait=true&single=true&fitw=true

[small]Updated the route on 4/17 at 11:00 PM EDT[/small]

In an attempt to include as many people as possible, the race will officially take place on:

[big]Saturday, April 28th, with a starting time of 12:00 EDT (this time is subject to change).[/big]

Something, something... Sunday somewhere in the world! gtaCoolStory

If you're planning on joining, please check out the first reply which includes information on an Any% starter route/guide

Check what time the race begins for your timezone with this link: https://www.timeanddate.com/worldclock/fixedtime.html?msg=%22What+are+you+doing+for+GTA+IV%27s+10th+anniversary%3F%22+Any%25+Race&iso=20180428T12&p1=179&ah=12

[small]and a countdown - http://a.chronus.eu/183CF60 - Thank you, Josh[/small]

Nearly every streamer lowers their FPS to some degree using streaming software due to the hit it takes on the CPU. FPS limiters should be allowed. We allow it in IV for this very reason. What's stopping someone from preparing an extremely high quality recording, toggled on and off by a hotkey, to drop their FPS down to around 15-30 for the time being? If you allow people to stream/record their runs, you should allow this as well, as it pretty much serves the same purpose/produces the same effect.

This reasoning has nothing to do with the old, "You can't detect they're using it (memory monitoring software is a good example), so it shouldn't be banned" excuse, which I don't agree with. If I want to record my 'Scouting the Port' crate section with settings which I know will drop my FPS to ~15, am I not allowed to?

This is now the best route, but you didn't read that here.

A voters: (Total-23: nearly every last one is very active in GTA speedrunning) Patrick_: SA Any% runner Bosz: SA Any% runner Nagenowa: SA Any% runner Odyssic: SA Any% runner overcooler: SA Any% runner Shadow_Dog: SA Any% runner hoXiu: SA Any% runner guywith: runs many 3D GTA games ryedawg: runs many GTA games Earleys: runs VC Zachoholic: runs many GTA games Anti: runs many GTA games english_ben: GTA runner, practicing SA at the moment D0moTheRussian: runs VC blacklev: runs GTA III agjents: runs many GTA games Powdinet: runs many GTA games Kyle: runs HD era GTA games, was active in SA in the past Nick007J: Zero runs on the lb, but is extremely active in the GTA speedrunning code-monkey scene Bourne: runs SA All Tags crazycharlieh: runs III and V Gustrb: zero runs

B voters: (Total-20: some are very active in GTA speedrunning, the majority have never ran a single game) lelreset: SA Any% runner Kamiks: SA Any% runner BackmadeJay: SA Any% runner derek: SA Any% runner KeeperRavager (Christera): SA Any% runner LukeKlutz: 1 Big Smoke IL run, 1 III 69HP run Steelrodeo: SA IL runner Mehmet79: 3D GTA extension runner Mackdanny: zero runs of anything, claims to be practicing SA Vinny: zero runs finesta: zero runs ReaperActualXV: zero runs Bender: zero runs Chaossy: zero GTA runs TheBroadster: zero runs EricaBby: zero runs spikepsych: zero runs quiltie: zero runs PoorMillionaire: zero runs Joannathegirlgamer3: zero runs

A. I have wan, I am a wanner, please believe me, I (heart) BIG SMOKE!

Try launching it via a shortcut with the following in the target field (your path may differ): "C:\Program Files (x86)\Steam\SteamApps\common\Grand Theft Auto IV\GTAIV\LaunchGTAIV.exe" -noprecache -nomemrestrict -norestrictions

1 ( http://www.speedrunslive.com/races/result/#!/179892 )

ffzLookAtDis!!!