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
Well that is very concerning!
I will indeed update this shortly, though I've been running with it since 1.26 with 0 issues other than the new units not being resized, so I can't help but suspect some sort of more serious issue, because no mod has the power to mess with an EU4 installation.
In any case, I was going to get an update out as soon as possible regardless, and we'll see if that at least improves the issue.
Yes, naturally!
I'm doubtful that this mod could actually do what you're describing, it is just a tiny little thing a couple lines away from being ironman compatible, but I suppose some sort of perfect storm mix of an outdated file reference with the wrong driver with the wrong security software with the wrong computer hardware might do it?
In any case, it should be updated now, so hopefully that will at least help. If you continue to have issues, do let me know and I'll try to make sure they're not on my end!
Think nothing of it, I've been at the "What is happening to my computer?!" point as well, so I understand. I hope it resolves itself, and I'm glad it appears this mod had nothing to do with it.
Thanks for the report! I was going to update within a few days, which will hopefully resolve the issue. If after the update you still have issue, please do let me know & I'll keep looking for this error (heard 2-3 reports of it, but many others (> dozen) are unable replicate the issue, including me, so it is a bit hard to track down the cause).