Steam 설치
로그인
|
언어
简体中文(중국어 간체)
繁體中文(중국어 번체)
日本語(일본어)
ไทย(태국어)
Български(불가리아어)
Čeština(체코어)
Dansk(덴마크어)
Deutsch(독일어)
English(영어)
Español - España(스페인어 - 스페인)
Español - Latinoamérica(스페인어 - 중남미)
Ελληνικά(그리스어)
Français(프랑스어)
Italiano(이탈리아어)
Bahasa Indonesia(인도네시아어)
Magyar(헝가리어)
Nederlands(네덜란드어)
Norsk(노르웨이어)
Polski(폴란드어)
Português(포르투갈어 - 포르투갈)
Português - Brasil(포르투갈어 - 브라질)
Română(루마니아어)
Русский(러시아어)
Suomi(핀란드어)
Svenska(스웨덴어)
Türkçe(튀르키예어)
Tiếng Việt(베트남어)
Українська(우크라이나어)
번역 관련 문제 보고
It hapened 3 times right now
Go to the game folder, look for the alife.ltx file located in gamedata/configs folder.
Open it and you should have a line like this:
switch_distance = 550 ; 600 ; 850 metres
the first number is the actual switch distance used, default is 350 i think, change it to something small like 30 (just enough to be able to see Yar) and save the changes.
Start the game and now Yar should be calm.
Dont forget to change switch distance back to whatever it was, you can only do that when out of the game.
Actuly the error info from the log is what is needed, like this example below...
FATAL ERROR
[error]Expression : fatal error
[error]Function : CInifile::r_section
[error]File : E:\stalker\sources\trunk\xrCore\Xr_ini.cpp
[error]Line : 342
[error]Description : <no expression>
[error]Arguments : Can't open section 'wpn_pm'
This example shows that this crash was by this ltx file that I renamed to make this example crash. It can't find it, so it stopped and gave a reason why. This is the part that I or anyone else that understands the system would need to see.
If you only have this to show for...
stack trace:
Then its a memory dump.
This is at the very bottom of your crash log txt. Pending on your system, after a bug crash, you can get away with just pasteing in note pad off the back after. So if it just crash, now is the time to get it. Because it writes a new log everytime you start the game.
X-Ray Engine
Exception reason:
xrEngine.exe caused BREAKPOINT in module "C:\Program Files\Steam\steamapps\common\Stalker Call of Pripyat\bin\xrCore.dll" at 001B:0058E12E, xrDebug::backend()+174 byte(s)
Registers:
EAX=4D395F00 EBX=00000000 ECX=4D395F08 EDX=4D395FDD
ESI=005B88C8 EDI=1D980B00 FLG=00200212
EBP=0012F884 ESP=0012E878 EIP=0058E12E
CS=001B DS=0023 SS=0023 ES=0023 FS=003B GS=0000
Stack trace:
001B:0058E12E xrDebug::backend()+174 byte(s)
001B:0058ED3D xrDebug::fatal()+2557 byte(s)
001B:4E68D160
001B:09035FB0 CDialogHolder::CleanInternals()+487600 byte(s)
001B:D5E85708
001B:7A1F0A80
Stack trace:
001B:0058E12E xrDebug::backend()+174 byte(s)
001B:0058ED3D xrDebug::fatal()+2557 byte(s)
001B:09035FB0 CDialogHolder::CleanInternals()+487600 byte(s)
When it crashes, look at the bug trap, should say on the right a box says "Preview"
Click on that should show like 3 files in a box on top, find the one that says "log txt" or something like that. Usally is the second file in the list, click on that and scroll down to the "ERROR" report, it look like this...
FATAL ERROR
[error]Expression : fatal error
[error]Function : CInifile::r_section
[error]File : E:\stalker\sources\trunk\xrCore\Xr_ini.cpp
[error]Line : 342
[error]Description : <no expression>
[error]Arguments : (why the crash)
Your getting close, I can see it is gonna be some kind of dialog issue. But I need the error report please..
If you have XP it is in...
Shared Documents\S.T.A.L.K.E.R. - Call of Pripyat\logs\xray_crash.log
FATAL ERROR
[error]Expression : error handler is invoked!
[error]Function : handler_base
[error]File : D:\prog_repository\sources\trunk\xrCore\xrDebugNew.cpp
[error]Line : 764
[error]Description : pure virtual function call
I found it at C:\Program Files\Steam\SteamApps\common\Stalker Call of Pripyat\_appdata_\logs\xray_masterwiky.log
(I have no xp on this)