[Bug][Critical] Silent Crash After Booting Up "eternity.exe" (V4.04.00-Win64)

[JohnMason1986]

After attempting to launch "Eternity Engine" V4.04.00 (64x on Windows 10). a console window is appearing and then closing. At the end, I have no error log that can be sent here, because that crash isn't generating an output error logging file at all.

[FozzeY]

Could you try launching it through the Command Prompt so it doesn't close right away?

[JohnMason1986]

Could you try launching it through the Command Prompt so it doesn't close right away?

After attempting to launch "eternity.exe" via "cmd.exe", I can see a "sand clock" icon near pointer that is appearing only for few milliseconds and then nothing happens.

[ioan-chera]

Just to be clear, did you try starting it from a fresh extraction from the archive? Try starting Eternity from its own folder, instead of merging it with other Doom ports and possibly affecting the DLLs.

I wonder if it's possible you didn't install the Visual C++ runtime. Not totally sure it's that, since Windows usually tells you if a DLL is missing.

Does the same thing happen with development builds? https://devbuilds.drdteam.org/eternity/

[JohnMason1986]

Just to be clear, did you try starting it from a fresh extraction from the archive? Try starting Eternity from its own folder, instead of merging it with other Doom ports and possibly affecting the DLLs.

Even fresh instance not launching for me at all.

I wonder if it's possible you didn't install the Visual C++ runtime. Not totally sure it's that, since Windows usually tells you if a DLL is missing.

I have "Visual C++ Redist" of 2005, 2008, 2010, 2012, 2013 and even 2015-2022.

Does the same thing happen with development builds? https://devbuilds.drdteam.org/eternity/

Sadly, even "V4.03.00 Pre-1428", "V4.03.00 Pre-1409", "V4.03.00 Pre-1408" and "V4.03.00 Pre-1399" is not launching on my PC. I've used some dev-build before, but I can't remember number of that version.

[JohnMason1986]

I am able to launch "Eternity Engine" from archive "Eternity-x86-4.04.00.7z" (and game's window says that it is 4.03.00 for some reasons). I don't know why I am able to launch x86 version, but not x64 one...

[ioan-chera]

Is your computer capable of starting other "x64" programs? Do you have both "Program Files" and "Program Files (x64)" under C:\?

Does the 4.04.00-win32 release work for you?

[JohnMason1986]

Is your computer capable of starting other "x64" programs? Do you have both "Program Files" and "Program Files (x64)" under C:?

Yes, my "Windows 10" is 64x, for sure and other 64x apps working just fine.

Does the 4.04.00-win32 release work for you?

As I mentioned before, V4.04.00 (84x) works just fine and it is written on the top of the window that it is a V4.03.00...

[FozzeY]

Could it be an antivirus blocking the execution? It is rather unusual that there is no error message of any kind.

[JohnMason1986]

I've added "Eternity Engine's" folder and its executable to the "Windows Defender's" whitelist and I still can't get newest version to boot up. Now it is showing up an empty console window and then it is closing fast w/o any sounds.

[ioan-chera]

Let's check the DLL dependencies. To try it, you can download the Dependencies program from https://github.com/lucasg/Dependencies and (as described in the README there), run DependenciesGui.exe and open Eternity.exe with it. You will see a list of DLLs. Try and check if you have all of them (some of them come bundled with Eternity, others are expected in C:\Windows\System32).

[ioan-chera]

Do you have both VCRUNTIME140.dll and VCRUNTIME140_1.dll in C:\Windows\System32? I see that the 32-bit version doesn't depend on VCRUNTIME140_1.dll from C:\Windows\SysWOW64.

[JohnMason1986]

Try and check if you have all of them (some of them come bundled with Eternity, others are expected in C:\Windows\System32).

I have these results:

[JohnMason1986]

Do you have both VCRUNTIME140.dll and VCRUNTIME140_1.dll in C:\Windows\System32?

I have these libraries inside of "System32" folder:

[JohnMason1986]

I've checked out V4.04.01 (32x) and it is launching just fine, but I still can't launch V4.04.01 (64x) and I don't know why. I had 0 problems with 64x software before and were able to launch any app easily...

[ioan-chera]

That warning sign looks suspicious and doesn't appear when checking the same file on my computers. Do you see it when opening DependenciesGui on the 32-bit executable?

Are the file sizes of the 4.04.01 eternity.exe the following (in Explorer right-click eternity.exe and click Properties)?

• 32-bit eternity.exe: 3 267 584 B
• 64-bit eternity.exe: 4 324 864 B

Until we figure out the cause of the problem, can you still play Eternity from the 32-bit executable in the meantime, without any problems?

[JohnMason1986]

That warning sign looks suspicious and doesn't appear when checking the same file on my computers. Do you see it when opening DependenciesGui on the 32-bit executable?

Not sure what was that (app said something about "zero module" that is "not on disk anymore, so press F5"), but repeated check after few hours showed this:

Are the file sizes of the 4.04.01 eternity.exe the following (in Explorer right-click eternity.exe and click Properties)?

• 32-bit eternity.exe: 3 267 584 B
• 64-bit eternity.exe: 4 324 864 B

32x executable is "3,11 МБ (3 267 584 байт)". 64x executable is "4,12 МБ (4 324 864 байт)". I am afraid that we have no clues here either...

Until we figure out the cause of the problem, can you still play Eternity from the 32-bit executable in the meantime, without any problems?

I think so, since it is, at the very least, is able to launch on my machine. After few minutes spent in the first "Doom" game I didn't experienced any bugs/stutters/lag spikes or something like this.