Instalar Steam
iniciar sesión
|
idioma
简体中文 (chino simplificado)
繁體中文 (chino tradicional)
日本語 (japonés)
한국어 (coreano)
ไทย (tailandés)
Български (búlgaro)
Čeština (checo)
Dansk (danés)
Deutsch (alemán)
English (inglés)
Español de Hispanoamérica
Ελληνικά (griego)
Français (francés)
Italiano
Bahasa Indonesia (indonesio)
Magyar (húngaro)
Nederlands (holandés)
Norsk (noruego)
Polski (polaco)
Português (Portugués de Portugal)
Português-Brasil (portugués de Brasil)
Română (rumano)
Русский (ruso)
Suomi (finés)
Svenska (sueco)
Türkçe (turco)
Tiếng Việt (vietnamita)
Українська (ucraniano)
Comunicar un error de traducción
nothing at all, when I launch the game and it closes immediatly, it seems not to log anything in the event log
there should be. Its a applocation error and it should say ys8.exe in the details.
nothing related to that in the log :(
try loading the game, then under windows logs/application try to see anything that appears. Make sure its sorted by date with todays date being up top.
There are other files that could not be working right.
Try uninstalling all of the visual C++ stuff and redownloading them off the microsfot website you need both x86 and x64. There are multiple differen ones like 2010 2012 13 15 17 etc
there is more than 2013 like 2015 2017
I'm not sure if this would help, but could you try the Preview branch that we've uploaded earlier today?
https://steamcommunity.com/app/579180/discussions/2/3288067088112098881/
We'll keep working together to find a solution for your launch issue.
Best,
Sean
I tried launching it directly with y8.exe (admin mode) located in the game root directory.
This time i get an error message : The application was unable to start correctly 0xc000007b.
I've replaced some .dll files in system32 and syswow64, nothing changed.
Also in the Windows event log/Application, the 2 ESENT errors always appear after i try to launch the game :
DllHost (14388,G,0) The beta feature EseDiskFlushConsistency is enabled in ESENT due to the beta site mode settings 0x800000
svchost (12504,G,0) The beta feature EseDiskFlushConsistency is enabled in ESENT due to the beta site mode settings 0x800000
That's a receipt for disaster. Run CMD in admin mode and execute a "sfc /scannow" right now, to ensure that you do not have any corruption or incorrect system files.
What logs do you actually get related to the game in Windows' Event Viewer? You should have an "Application Error" as well as an "Windows Error Reporting" right besides each others from when the game crashed. Both of these include some description about what caused the crash, in what module it occured, what the exception code was, etc.
The most commonly seems to be 0xc0000005, and simply means that /something/ in the process tried to access invalid memory. Either memory that did not exist, or memory that it did not have access to.
This is not related to the game. It's something new in Windows 10 v1709 that Microsoft have enabled. That log comes on all systems every now and then.
Thank you for your answers.
Unfortunatly, Windows logs absolutly nothing in the Event log. The only way to have an error message is to launch directly ys8.exe from the root directory, a popup appears telling me the "application couldn't start, error 0xc000007b, click ok to close" and that's it. After that, nothing else appears in the Windows event log, as if nothing crashed, except the Application popup line to notify me i just had a popup error, but without any more information.
I tried sfc /scannow, it found some error and said it repaired them. The game still won't launch tho :(
Thank you to everyone who took the time to answer, Aemony, gstommylee001, and many others.
In case this happens to anyone else, here is what i did :
- downloaded Depends22 tool, to know what ys8.exe needed to work. It showed some dll were actually installed, but showed in red. I guess it means they were corrupted. Even if i reinstalled VC++ 2010 and 2013 many times during my attempts the last few days, it didn't seem to delete the corrupted dlls. I removed them manually from system32 and syswow64, making myself the owner of some of them in order to delete them.
- uninstalled all the Visual C++ libraries (2005, 2008 2010 2012 2013 2015... all coming with "additionnal" or "minimum" addons, i think i had them all...)
- uninstalled .Net Framework and running the .Net cleanup tool (dotnetfx_cleanup_tool, easy to find)
- downloaded a Visual C++ Package, which contained 18 packages. It installs all of them at once.
- .Net framework came back clean (from windows update i guess)
I hope it helps^^