Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
You'll still need to do dinput8.dll removal (and any other .dll that battleye may halt on). If you are using a 'mods' folder for openIV (hopefully you are) - you should only need to remove dinput8.dll -for that-. And of course, 're-allow' battleye by putting the checkmark back in R* launcher / settings - or by removing -nobattleye from launch options (or commandline.txt) - if you 'skipped' battleye that way.
Reshade, sweetfx and all that - you'll have to look into/test most likely. I haven't bothered 'yet' myself. Maybe tomorrow, if I have the time.
/goodluck
Thank you very much for your helpful reply here. Yeah I have all my mods in a separate folder for OpenIV since I like to keep my installation well organized. I used a combination of OpenIV and Codewalker RPF Explorer This must be what it meant then since iirc it did throw the error on a dll file. I am assuming this also means no change to the fact one cannot use cosmetic mods while in GTA Online. It's very sad some modders just cannot play nicely and have to use the creative freedom modding provides as a way to cheat and compromise fair competition.