GTA5 911 Help and Checklist - What to do when Mods make you Mad
This is a series of hopefully simple videos aimed to help you troubleshoot Mod issues. We won't cover how to install basic mods such as Open IV or ScripthookV, nor will we address mod specific issues because there are just too many mods to cover. Instead we give you the nuts and bolts of getting a modded system to run properly. Mod specific issues should be posted in the Installation Help & Troubleshooting section of the forum, in their own thread.
Tip: to search these forums, use this syntax in your browser search bar. As an example, enter the following if searching for the file vehicles.meta.
Part 1.The Absolute Basics.
First video is just to confirm you have installed the right files in the right folders to run Mods. View full screen on YouTube at 1080P for best readability.
Part 2. Where lies the Problem.
In this next part for absolute beginners, we cover a very general overview of where the problem or problems you encounter might reside.
Part 3.Two very important files: gameconfig.xml and dlclist.xml.
We take a look at where these two files should be installed, warn the beginner against trying to modify gameconfig.xml, and provide a simple tip on how to edit dlclist.xml to avoid syntax errors which would result in invalid models or other errors.
Part 4.The Mods Folder From Windows.
In part 4 of our series we verify the correct structure of the critical user Mods folder as seen from Windows Explorer. YouTube at 1080P for best readability.
Part 5.The Mods Folder From Open IV
In part 5 of our series we verify the correct structure of the critical user Mods folder again, but this time from Open IV. YouTube at 1080P for best readability.
Part 6. Mods or Game not working! An Overview
In part 6 of our series we take a 30,000 foot view of what can go wrong and why along with the first step in a proven methodology that will definitely get your game fixed unless the cause is demonic possession.
Part 7. Mods or Game not working! Root and Scripts Folder
In part 7 of our series, another 30,000 foot view of what can go wrong, this time in the root and scripts folder.
Part 8. Top Ten Modding Mistakes.
In part 8 of our series, a look at the most common mistakes that can occur when installing mods.
GTA5 911 Help Desk. Recover from a broken game.
Part of the How To Playlist.
How to backup and restore game problems resulting from corrupt or damaged or overwritten game files.
Also how to prepare game to continue playing after an update.
The New to Modding Checklist.
1. What should I have installed for modding GTA5 Single Player?
The two following files are the absolute essentials if you are going to add mods. Do not download from other links to ensure you have the current versions.
2. Where do I install Script Hook V?
Script Hook V does not have an installer, you simply copy the 2 files below (from the extracted package) to the same folder as your GTA5.exe. You can call this your game folder, or installation folder, or root folder.
When you unzip or extract the downloaded Script Hook package you will see a bin folder. That's the only folder you want. There are 3 files in the bin folder of the Script Hook V download. You only need two of them: ScriptHookV.dll and dinput8.dll. Both copied in the game folder. You don't copy the bin folder, just those 2 files. You don't need NativeTrainer.asi.
3. Where do I install Open IV?
Open IV, pronounced Open Four, has an installer. Just accept the default path for the installation and follow the instructions. Open IV will ask you if you want to install three different files. Say yes to all of them. They are: ASI Loader, OpenIV.asi, and openCamera. ASI loader is exactly the same as dinput8.dll from ScriptHook V but that's ok. openCamera will be useful if you use the R* editor. OpenIV.asi is a must.
4. How do I know my files are properly installed?
If you followed the instructions carefully for OpenIV then the program itself will be installed in a hidden windows folder called AppData, however you will be able to see at the very least these key files : OpenIV.asi, ScriptHookV.dll and dinput8.dll in the same folder as GTA5.exe. Like this:
Always verify that you scripthook v is properly updated and only download it from the official Alexander Blade site. Remember it should be in the same folder as GTA5.exe. You can check the version numbers by right clicking GTA5. exe, the same with scripthookv.dll, to ensure they are current. At time of writing, this is what it looks like. Of course version numbers will change with time.
Which gameconfig and heap adjuster are the best? No simple answer. Try any of these combinations.
Option 4 is the only one that works for me after Tuner Update. Nothing else works. And for the very first time, i had to install the packfile mod as well.
Game Failures - Common Causes
There are so many factors or combinations of factors which is why patience and a step by step approach is required. The following is a list of common issues, however this list is in no way complete as there are too many different setups out there involving PC hardware, software, game settings, installed mods, mod settings, etc.
PC hardware (GPU, CPU, System RAM, available storage/HDD) may not be powerful enough to meet requirements for modding. Particularly true for laptops. For example, if you are running Windows 7 on a laptop with integrated graphics go real easy on the type and quantity of mods you install. If you can't upgrade your components or the PC itself, again add mods one by one and see if you can handle them before adding others.
PC Software such as video or other PC drivers. Make sure drivers are up to date, particularly if you are experiencing texture issues like flickering, tearing, texture losses, or low FPS. Set graphic settings to default or lower if necessary. DirectX versions can cause issues as well.
GTA5 Version (Steam, Epic, Retail) not updated or using warez version. GTA5 should be uncracked and kept updated with most recent mods when available. Support for cracked versions is not available here.
Scripthook V (latest version) not properly installed. Must be installed in root folder with GTA5.exe (same location for asi mods). Extract the package, remove ScriptHookV.dll and dinput8.dll from the bin folder, and place them in the root folder. You don't need and don't want the trainer file. Don't confuse scripthook with scripthook dot net. See point 8.
OpenIV not properly installed, use its default settings and you shouldn't have any issues.
Gameconfig.xml missing or improperly installed. You need OpenIV to install it. Use base settings to start. Don't modify this file based on some random post you read. It should work fine even with 300+ cars or peds installed right out of the box.
Heap and packfile limit adjusters. Use the Heap mod recommended for your gameconfig to start, keep default settings. These files go in root folder with GTA5.exe
Script Hook V .NET, NativeUI, and LemonUI. These important and often required mods could be missing or not installed properly. Follow mod instructions carefully. These are not required by all mods. The dot net files go in the root folder but most .dll files go in the scripts folder.
Mod File Structure. Ensure all folders are correctly implemented. There are YT videos which actually have the wrong structure. For example update.rpf in wrong folder. You also may need to set folder permissions given many mods will write or save information on your PC. Watch the videos in this thread if unsure or to confirm proper setup.
Dlclist.xml. New addons must be added to this file, with the correct folder names and correct syntax. Best to copy a working entry and edit it. Make sure you have opening and closing tags etc.
Improper installation of mods in the wrong folder/wrong path, or missing mod requirements. Note: OIVs are better installed manually. Caution is required for replace mods as they often involve more than one path/location. Always use a Mods folder. The root folder is where your .asi and many .dll files are installed (e.g. dinput8.dll, ScriptHookV.dll) but generally speaking the .dll from script mods will be in the scripts folder. Proper Installation of Tools and Script Mods
Quantity. Too many mods installed, particularly high polygon count vehicles or massive maps/MLOs. GTA5 was not designed for modding. Push too far, too much and you will crash. You can mitigate issues with properly configured gameconfig, visual settings, and the proper hardware.
Currency. Outdated or defective mods may no longer work with new versions of GTA5 or other mods. Old mods do die.
Corrupt or missing game files. This may happen with or without meaningful error messages. The save game file may also be corrupted, particularly if autosaving during a crash. A verify integrity (or reinstall) will fix most issues, but not corrupt save files, so backup. If necessary start a new game.
Customizing mods. As you are more experienced, you will likely customize yourself. Making edits to files such as handling.meta, converting replace vehicles to addons, adding or replacing textures, renaming files, and consolidating dlcs into one rpf. All of these actions require attention to detail. Mistakes will lead to possible issues which is why keeping track of changes will help troubleshoot if something goes wrong.
Reinstalling. Doing a complete reinstall rather than a verify integrity is not usually necessary. Many users are under the wrong impression that this will fix broken mods as well. A reinstall only impacts GTA5 files, it does nothing to your saved games or mod files. Which is why a clean reinstall is the way to go when all esle fails. This means uninstalling and then manually deleting any remaining files and folders in documents as if game never existed.
The following suggestions will give you a great starting point for troubleshooting a GTA5 game that was working but no longer works. If your game never worked properly in the first place, start at the top of this post and read it entirely or just the sections that apply to you. Most importantly, make sure your folder structure is correct and the installations are in the right folders and paths.
If your game is now suddenly broken (crash, hangs, etc):
Step 1. Run the game without mods. You want to rule out any hardware, PC software, or game file issues and ensure your game runs stably in vanilla mode - without any mods - no scripts, no addons, no trainers. You don't need to uninstall anything at this point.
Instructions: Simply rename dinput8.dll which you will find in your root folder (where GTA5.exe is) to dinput8.bak and start your game. If your game nows runs properly without mods and without incident, move to the next step. You now know your game itself is fine. If it doesn't run, start with a Verify Integrity, and worst case a complete reinstall with a new saved game file as well.
Step 2. Disable your scripts folder. You want to rule out script or script conflict issues.
Instructions: First ensure dinput8.dll has been renamed to its original name, then rename your scripts folder to Xscripts (or whatever you want). Again start your game. If your game runs stably with the scripts folder disabled, you know the problem is with one or a combination of scripts. Uninstall them, one or in small groups, and reinstall until you find the problem. If your game still doesn't run while all your scripts are disabled, you can now suspect the Mods Folder.
Step 3. Disable your mods folder. You want to rule out addon mod or mod conflict issues. The mods folder includes key files such as dlclist.xml, gameconfig.xml, and your Dlcpacks folder with addon peds, vehicles, etc.
Instructions: First rename the scripts folder back to its original name, then rename the Mods folder to XMods (or whatever you want).
You do not need to edit dlclist.xml. Just start your game. If your game runs with the mods folder disabled, you have an issue with one or a combination of mods. Once more, uninstall them, one or in small groups, and reinstall until you find the problem. Ensure you do not have any syntax errors in dlclist.xml and that your gameconfig is installed and updated along with heap and pack adjuster mods.
Step 4. Disable your asi mods. The last step is to ensure it is not a trainer or other asi file that is causing issues. It is less likely to be your trainer, but it could be an .asi mod that is outdated, conflicting, or just not right for you system . Use the same process of renaming the mods, but go one by one. Don't rename OpenIV, it's not necessary. Also make sure to change .asi extension to something like .bak, if you keep the extension as .asi it will still try to be loaded by dinput8.dll and could cause issues.
If none of the above works, read the section entitled Game Failures - Common Causes
Proper Installation of Tools and Script Mods
It's always important to read the instructions that come with any mods. Here we examine two very common mod types.
The asi filetype we're talking about here is a library specific to GTA5. These files are loaded by a file called dinput8.dll, also aptly know as the asi loader. This file is packaged with Scripthook V and with Open IV. ASI files are installed in the root folder where GTA5.exe is found.
Examples: ScriptHookDotNet.asi, Menyo.asi, PackfileLimitAdjuster.asi, OpenIV.asi, TrainerV.asi, NoBoundaryLimits.asi, and your Heap or Heap Limit Adjuster.
These files, dynamic link libraries, generally go in your Scripts folder. Most script mods will be installed in that folder. We won't list them because there are too many but here are some.
Examples: NativeUI.dll, LemonUI.dll, LemonUI.SHVDN3.dll, NAudio.dll, and all the scripts that you create yourself using an IDE or compiler such as Visual Studio.
While the overwhelming majority of script dll mods go in the Scripts folder, there are some important file exceptions that go in root folder:
Steam and GTA5 game dlls, dinput8.dll, the ScriptHookV and ScriptHookVDotNet dlls - all to be installed in root with GTA5.exe.
Are my files loading
To verify if your asi files are loading properly, open asiloader.log in a text editor. Do the same with ScriptHookV.log.
More about key modding files
From the author, Alexander Blade: "Script Hook V is the library that allows to use GTA V script native functions in custom ASI plugins. Note that it doesn't work in GTA Online, script hook closes GTA V when player goes in multiplayer". This is the file that allows modders to create asi mods such as Trainers. Scripthook V is packaged with the Asi Loader (aka dinput8.dll). Mods will not run without Scripthook V.
Installation: manual, destination is root folder. Two files should be installed of the 3 packaged: ScriptHookV.dll and dinput8.dll, the trainer file is not required nor recommended.
Many GTA V files, like the dlc.rpf files (downloadable content/rage package file) are archives - very much like zip files/packages. However, you can't extract them. You can't open them to view the contents with common apps such as winzip, or 7-Zip, or Winrar. That's because rpf files are protected, they are encrypted.
OpenIV was developed by the community as "a multi-purpose editor and archive manager for PC version of Grand Theft Auto IV and Episodes from Liberty city". So essentially, back in the day, Open IV allowed you to open GTA IV rpf files, hence its name. Later it was updated for GTA V and other titles.
So OpenIV is the toolset to edit and manage all the GTA V mod files you will install and those you will modify. You won't be able to load any addons such as car mods without OpenIV. Open IV will also install the Asi Loader as an option.
Installation: Installer with some options. Program is installed in C:\Users\YourName\AppData\Local\New Technology Studio. OpenIV.asi in root folder.
Community Script Hook V .NET
As per the author "This is an ASI plugin for Grand Theft Auto V, based on the C++ ScriptHook by Alexander Blade, which allows running scripts written in any .NET language in-game." This plugin and associated dll files allow the creation of script mods and user developed scripts. These files are not mandatory for all mods but are highly recommended as most if not all scripts (missions etc.) require them.
Installation: manual, destination is root folder
When properly installed, the loader will appear in your root folder as dinput8.dll. This file loads all your asi plugins. You can't run mods without it. It is packaged, as referenced above by both Scripthook V and OpenIV.
Installation: manual if in ScriptHook V package. As an installer option with OpenIV. Destination is root folder
NativeUI (no longer supported) and LemonUI are dll files allowing you to create GTA V like Menus. They are used along with all the Script Hook V .Net files.
Installation: manual. Destination is user created scripts folder
Now that I got your attention, hopefully there aren't any dangerous mods on this site, but there are definitely some mods you should avoid and some instructions which are just plain stupid - as are the modders who created them. More reasons to backup!
Mods installed in games folder
Older mods, particularly those circa 2016, often instruct the user to install in the games folder. That's because mods folders weren't as common then or the creators just didn't care. Always install in your mods folder. If you mistakenly don't and have an issue, a verify integrity should fix the problem.
Mods which include dlclist.xml
Some mods will package a plain vanilla dlclist.xml file, which might date back to 2016, with just their mod added and instructions to replace yours with theirs. This means overwriting any and all addons you've added since you started modding. Don't install a mod's dlclist.xml. Instead, edit your own file.
Mods which include gameconfig.xml
Similar to mods which contain dlclist.xml, this one is even worse - mods which have their own version of gameconfig.xml, some dating back once more to 2016. This is likely a recipe for an instant game crash - particularly and ironically if your game is properly updated because you can't use an old gameconfig with a new updated game. Never install an old gameconfig.xml. Worst case reinstall a current one from this site.
Beware - the OIV Automatic Installers
The OIV method of installing is wonderful for anyone new and/or lazy. It does everything for you and will not make any installation mistakes if properly written and tested. Unfortunately, you don't know what the mod is doing. Some of them will overwrite files you have already modified. Others will replace your gameconfig.xml and/or your dlclist.xml as described above.
So don't use automatic installers unless you know for sure they are safe. An OIV is essentially an archive, so you can unzip them. Inside you will find a file called assembly.xml which will tell you exactly what goes where. You will also see a content folder that includes all the files that will be installed. If you want you can install the mod manually yourself by considering the assembly.xml file as your instructions.
If you don't feel comfortable doing a manual install, at least look at the content folder and if you see gameconfig and dlclist in there, backup your own files and then restore them (overwrite the mod ones) after the installation. Same logic applies for any other files where you want to keep your own versions but you see the mod might overwrite them by looking at the contents folder or assembly.xml.