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
Here is what happened:
RED4ext 1.26.1 wasn't working when the 2.2 update came out, and I saw a user on Nexus saying to update to the 1.26.0 instead. That worked. Then when it came time to update CET, the devs didn't publish it on Nexus, so I got the 1.34.0 update from their Github. That worked too.
Turns out that on the 13th the CET devs worked out their issue with Nexus and posted a CET 1.34.1 which I didn't have. So I updated that and RED4ext and to my surprise the game launched just fine with all mods working, including the REDmod mods!
Crazy thing is, according to their Nexus page, RED4ext does not require CET to work, neither does the REDmod mods require anything else other than REDmod itself. Maybe it's just something beyond my understanding of how these mods interact with each other, but I just lost a whole day trying to fix this (I'm unemployed)
You can set the game back to previous update under betas everything should work then.