Loading...
0 files liked
2 comments
0 videos
0 uploads
0 followers
  • Default

    @kabwto The .ini file is in the scripts folder. In the beginning, there is no .ini file. You only have the .dll file and the .pdb file (you place them in the scripts folder). Once you start the game (with the .dll and .pdb files in the scripts folder), the .ini file is created and placed in the scripts folder. The problem is, the .ini file is created EVERY time you restart GTA V, replacing the older .ini file. This means that you can't really change anything in the .ini file because it will just be replaced the next time you open the game. This is a major problem because it means that you can't change the activation key of the mod in the .ini file, and the activation key that's written by default can't work because it doesn't use GTA V's virtual key coding or windows virtual key coding.

    Mércores 9 de Agosto de 2017
  • Default

    I know how to fix the problem! The mod is programmed to create a .ini file every time the game loads up. I tried to change the Mod Menu Key by replacing "F10" with "121" (This number is F10 in GTA V Virtual Key Coding. See for yourself: https://www.gta-modding.com/iv/tutorials/virtual_key_codes.html), but the file would just be replaced with the automatically generated one that comes back when the game starts. That's why F10 won't open the Menu. If you change the automatically generated .ini file and change "F10" to "121", I'm sure it will fix the problem! I've seen this problem way too many times and it takes merely a few seconds to fix. The problem here is that I CAN'T fix it because the original file generates back and replaces the one I edited, making my effort useless. Just replace the "F10" with "121" in the automatically generated .ini file and the problem will be solved. Please take this into consideration because I can tell you put A LOT of effort into this mod and it would be a shame if half of the people can't play it because of some tiny problem.

    Domingo 6 de Agosto de 2017