Since the most recent update I haven't been able to make a playable CK3 mod. I am able to complete the conversion but I cannot actually load a new game in CK3 as it will just load indefinitely. I have an Invictus save, if that's relevant.
Wait longer, up to 10 mins. I doubt it will load indefinitely.Since the most recent update I haven't been able to make a playable CK3 mod. I am able to complete the conversion but I cannot actually load a new game in CK3 as it will just load indefinitely. I have an Invictus save, if that's relevant.
Turns out you were correct, so I will have more patience in the future.Wait longer, up to 10 mins. I doubt it will load indefinitely.
It never officially supported these mods, just happened to be compatible enough. I plan to work towards better compatibility sometime next year.Turns out you were correct, so I will have more patience in the future.
Though I will say that the converter no longer seems to be compatible with Fallen Eagle or When the World Stopped Making Sense. I never tested the second mod but Fallen Eagle used to work. Obviously I can't expect you guys to account for that but for now that's the only way to simulate the rise of Islam I think, though I might be wrong.
log.txt is in the same folder as ConverterFrontend.exe.I cannot find the log.txt and I also can't find the reason why my save doesn't convert. Can someone help.
It looks like the conversion is failing instantly. Usually it's caused by an antivirus blocking the converter backend executable.So keep getting this error when trying to convert, the D: drive does not exist on my PC, may have at one point as far I remember Imperator would not have been installed within it
No, maybe when CK3 adds China.I have a fair idea that the answer will be 'no', but asking regardless:
Are there any plans to eventually support Terra Indomita (the Invictus fork that adds East Asia)?
So I tried disabling my AV, it's ESET SMART Premium, still fails immediately when active protection and firewall protection is disabled, I'm running on Windows 11 if that makes a differenceIt looks like the conversion is failing instantly. Usually it's caused by an antivirus blocking the converter backend executable.
Are you using the latest converter version (5.2.13)? Please upload log.txt from that version.So I tried disabling my AV, it's ESET SMART Premium, still fails immediately when active protection and firewall protection is disabled, I'm running on Windows 11 if that makes a difference
It seems to think Imperator and CK3 are installed in an entirely different location than they are. They are installed within the E: drive not the D: driveAre you using the latest converter version (5.2.13)? Please upload log.txt from that version.
The warnings are unrelated (probably some leftover junk in Windows registry), they can't be causing the instant fail.It seems to think Imperator and CK3 are installed in an entirely different location than they are. They are installed within the E: drive not the D: drive
Running and admin doesn't change anything, the ImperatorToCK3Converter.exe flashes up a window for less than a second then nothing, no log file is generated, Added the entire folder as an exception, again, nothingThe warnings are unrelated (probably some leftover junk in Windows registry), they can't be causing the instant fail.
Some things you could try:
- run ConverterFrontend.exe as administrator
- run ImperatorToCK3/ImperatorToCK3Converter.exe and let me know what happens (also upload ImperatorToCK3/log.txt when you do that)
- add the aforementioned executables to ESET exceptions if that's possible or completely disable ESET
This is promising.the ImperatorToCK3Converter.exe flashes up a window for less than a second then nothing
Failed to create CoreCLR, HRESULT: 0x80004005 is what I'm gettingThis is promising.
Can you try running ImperatorToCK3Converter.exe through Windows Terminal? It will also fail, but I think it will at least print the error to console.
So I do think it's the antivirus. Someone had the same problem:Failed to create CoreCLR, HRESULT: 0x80004005 is what I'm getting