|
My pc have the following specs:
Ram: 4 GB
CPU: Pentium Dual-core E5800 @ 3.20 GHz
VGA: NVIDIA GT 710 2GB
Windows 10
And the launcher of the game doesn't open, nothing happens, only a log with these info:
[04:59:36.397] [CLIENT] Exe module file: C:\Creative Destruction\client.exe
[04:59:36.397] [CLIENT] Current directory: C:\Creative Destruction
[04:59:36.397] [CLIENT] Initializing client....
[04:59:36.397] [CLIENT] Init utils.dll (1063838562)
[04:59:36.414] M Succeeded to create FileLoader, opener sys, loader indexed_discrete, root C:\Creative Destruction\Documents\res, depth 0
[04:59:36.414] M Succeeded to create FileLoader, opener sys, loader npk, root C:\Creative Destruction\Documents\res, depth 0
[04:59:36.452] M Package C:\Creative Destruction\res.npk under opener sys is loaded.
[04:59:36.452] M Succeeded to create FileLoader, opener sys, loader npk, root C:\Creative Destruction\res, depth 1
[04:59:36.453] M Succeeded to create FileLoader, opener sys, loader discrete, root C:\Creative Destruction\Documents\res, depth 0
[04:59:36.453] M Succeeded to create FileLoader, opener sys, loader zip, root C:\Creative Destruction\Documents\zip, depth 1
[04:59:36.453] M Succeeded to create FileLoader, opener sys, loader discrete, root C:\Creative Destruction\Documents\script, depth 0
[04:59:36.454] M Succeeded to create FileLoader, opener sys, loader npk, root C:\Creative Destruction\Documents\script, depth 0
[04:59:36.455] M Package C:\Creative Destruction\script.npk under opener sys is loaded.
[04:59:36.455] M Succeeded to create FileLoader, opener sys, loader npk, root C:\Creative Destruction\script, depth 0
[04:59:36.455] M Start log.dll
[04:59:36.455] M Start utils.dll
[04:59:36.456] M [UTILS] Init render.dll (1202430036)
[04:59:36.456] M [UTILS] CPU Name Pentium(R) Dual-Core CPU E5800 @ 3.20GHz, core count of this device is: 2
[04:59:36.456] M [UTILS] device model is pc
and other with this:
appkey:ad5879ce5450789fdcb5cd5065972dd3-client_v:3.0.0.11-error_type:WINDOWS_NATIVE_ERROR-os_type:windesktop-project:g91na
For now, I'll stay waiting for News, I expect this error be fix soon. |
|