Nainstalovat Steam
přihlásit se
|
jazyk
简体中文 (Zjednodušená čínština)
繁體中文 (Tradiční čínština)
日本語 (Japonština)
한국어 (Korejština)
ไทย (Thajština)
български (Bulharština)
Dansk (Dánština)
Deutsch (Němčina)
English (Angličtina)
Español-España (Evropská španělština)
Español-Latinoamérica (Latin. španělština)
Ελληνικά (Řečtina)
Français (Francouzština)
Italiano (Italština)
Bahasa Indonesia (Indonéština)
Magyar (Maďarština)
Nederlands (Nizozemština)
Norsk (Norština)
Polski (Polština)
Português (Evropská portugalština)
Português-Brasil (Brazilská portugalština)
Română (Rumunština)
Русский (Ruština)
Suomi (Finština)
Svenska (Švédština)
Türkçe (Turečtina)
Tiếng Việt (Vietnamština)
Українська (Ukrajinština)
Nahlásit problém s překladem
Desperados has a nifty file where it logs errors - it should be found at Windows 10: C:\Users\*USERNAME*\AppData\LocalLow\Mimimi\Desperados III
File Name is: output_log.txt
You can look through the log and see if anything pops out at you. Note the last entries.
This is a long shot but it can't hurt.
Edit: Oh, and some people in their forum have had crashes during cutscenes when G-sync was turned on.
should not happend and its seen before.
https://www.memtest86.com/
Thanks, this might really be helpful!
This is the lower part of that log file, from where errors start to happen:
@Iceira
I do have:
- VC++ 2005
- VC++ 2010
- VC++ 2012
- VC++ 2013
- VC++ 2015-2022
Every one of thos both in x64 and x86.
Another dev had a suggestion on a quick workaround. Now, this might not work, but it's worth a try. The worse this can do is crash instantly, run slowly or crash in the same place:
Go to your Steam Library.
Find the game and right-click it, then select "Properties"
Under the General Tab, click "Set Launch Options" and a dialog box will appear.
Type in "-force-d3d9" (without the quotes) and click "OK"
Close the Properties window.
You can also try "-force-glcore".
I might have something else to try, but I want to test it on my own version of XCom 2 first. It's taking its fair time to install though.
Edit: Sorry, I should've said, you're basically forcing the game to start in Dx9 and you could even try DX10. You should be able to change it in-game as well.
you even sure thisa is not a game that need to run in dx9 as lowest setings.
@Bee
I tried with "-force-d3d9" but it crashes in the same spot.
I tried with "-force-glcore" but it won't even start.
if fresh driver install dont work , you might want to contact Nvidia support.
I'll look around more and hammer my copy of XCom 2 for a bit.
@Iceira
I'll try as soon as I can.
feel free to test , things like shadow play off and steams preshader cache off vulkan driver to off.
other then that still a nvidia problem, steam and game devs do not make GPU Driver fix or its settings,
in old games you could see option like bloom effect and how to use diffrent setup, but you problem is it crash along the way or never startup, besure its not antivirus app that block own game from startup, maybe its a game never started thats not samethings as game did start and have issue with crash in a game, and yes there is a diffrence in every step, even seen what game devs call splash screen effect crash.
dl nvida game rdy Driver use advance install and make fresh install then checkbox is there. if that dont help ask Nvidia support they might want to look at it.
as bee said other seem to have unity games issue, but as i see it still nvidia that might look at it, either say problem is not here but with that game engine, and i doubt that will happend require pretty good proof from nvidia.
################# from error log ###################################
Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak
d3d11: failed to create buffer (target 0x1 mode 1 size 82944) [0x887A0005]
d3d11: failed to create buffer (target 0x2 mode 1 size 5748) [0x887A0005]
d3d11: attempt to lock null buffer
d3d11: attempt to lock null buffer
D3D11: Failed to create RenderTexture (1920 x 1080 fmt 9 aa 1), error 0x887a0005
#############################################################
this is a GPU / VC+++
Try launch the game from steam install location ((( game.exe name ) and see if it trigger a popup crash message.
im try to figure if this is a corrupted VC+++ file in the system
ps.
feel free to uninstall all VC+++ in the system
run as admin and DL all-in-one VC+++
and see if newest VC+++ might help you
https://www.techpowerup.com/download/visual-c-redistributable-runtime-package-all-in-one/
they are all signed by MS
rest is part of the Nvidia support and if you read own log you can see its from pre-shader to vulkan driver and somehow effect that game.
check system for vulkan driver, should apply again with reinstall of nvidia driver today.
thats my point you might want to uninstall it as test with it and without it.
all this is still Nvidia support job to help you better or they have to deal with it.
and now you get why i was on the VC+++ issue if that judge your system not have newest as techpower do even newer then MS own support page. ( go figure , its like they know even newer files. Ms offcial dont give at own support page. )
according to log 4 frames might not be seen as much ( but reduce gpu power , can be seen as exatly as that.) this is a known old debat, and many dont do that on newest gpu card, its more then you are in other end and need every gpu power cycle, or typical laptop user mistake.