Crashes when I click on Settings Thread — S.T.A.L.K.E.R. Anomaly mod for S.T.A.L.K.E.R.: Call of Pripyat
S.T.A.L.K.E.R. Anomaly
S.T.A.L.K.E.R.: Call of Pripyat mod | Released 2018
The stand-alone mod S.T.A.L.K.E.R. Anomaly aims to be the most stable and customizable experience for fans of the S.T.A.L.K.E.R. games. It’s powered by the Monolith 64-bit engine, a custom fork of the X-Ray engine.
I just downloaded and installed anomaly, I can start a new game without problems (DX11) but I just cant open the settings, any idea ? thanks
here is the log:
* Detected CPU: Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz [GenuineIntel], F6/M14/S9, 2809.00 mhz, 20-clk ‘rdtsc’
* CPU features: RDTSC, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, HTT
* CPU cores/threads: 4/8
Found commandline file!
Initializing File System.
using fs-ltx fsgame.ltx
File System Ready.
FS: 51339 files cached 66 archives, 9507Kb memory used.
Init FileSystem 0.568795 sec
‘xrCore’ build 8028, Jan 29 2021
——loading d:/stalker anomalygamedataconfigssystem.ltx [2]
Initializing Engine.
Starting INPUT device.
Loading DLL: xrRender_R3.dll
refCount:m_pAdapter 1
Available render modes[1]:
[renderer_r3]
command line «d:stalker anomalybinanomalydx10avx.exe» -smap2048
Executing config-script «user.ltx».
Invalid syntax in call to ‘renderer’
Valid arguments: renderer_r3
[d:/stalker anomalyappdatauser.ltx] successfully loaded.
Loading DLL: xrRender_R3.dll
Loading DLL: xrGame.dll
* [x-ray]: Full Memory Stats
* [win32]: free[137434503212 K], reserved[4275796 K], committed[174400 K]
* [ D3D ]: textures[0 K]
* [x-ray]: process heap[41184 K]
* [x-ray]: economy: strings[29469 K], smem[0 K]
SOUND: OpenAL: enumerate devices.
SOUND: OpenAL: EnumerationExtension Present
dir[1]=D:STALKER Anomaly
dir[2]=D:STALKER Anomalybin
dir[3]=C:WINDOWSsystem32
CleanDeviceSpecifierList
CleanDeviceSpecifierList OpenAL Soft
devices OpenAL Soft
SOUND: OpenAL: system default SndDevice name is
SOUND: OpenAL: All available devices:
1. OpenAL Soft, Spec Version 1.1 eax[0] efx[no] xram[no]
Executing config-script «d:/stalker anomalygamedataconfigsdefault_controls.ltx».
! Unknown command: g_old_aim
! Unknown command: input_exclusive_mode
[d:/stalker anomalygamedataconfigsdefault_controls.ltx] successfully loaded.
Executing config-script «user.ltx».
Executing config-script «d:/stalker anomalygamedataconfigsrspec_default.ltx».
[d:/stalker anomalygamedataconfigsrspec_default.ltx] successfully loaded.
Executing config-script «d:/stalker anomalygamedataconfigsdefault_controls.ltx».
! Unknown command: g_old_aim
! Unknown command: input_exclusive_mode
[d:/stalker anomalygamedataconfigsdefault_controls.ltx] successfully loaded.
! Unknown command: g_end_modif
! Unknown command: g_firepos
! Unknown command: g_god
! Unknown command: g_unlimitedammo
! Unknown command: log_missing_ini
! Unknown command: ph_gravity
Invalid syntax in call to ‘renderer’
Valid arguments: renderer_r3
! Unknown command: time_factor
! Unknown command: rs_borderless
! Unknown command: rs_fullscreen
! Unknown command: rs_borderless
! Unknown command: rs_fullscreen
[d:/stalker anomalyappdatauser.ltx] successfully loaded.
SOUND: Selected device is OpenAL Soft
* sound: EAX 2.0 extension: absent
* sound: EAX 2.0 deferred: absent
* sound : cache: 524296 kb, 38848 lines, 13820 bpl
Starting RENDER device.
* GPU [vendor:10DE]-[device:1C20]: NVIDIA GeForce GTX 1060
* CREATE: DeviceREF: 3
* Texture memory: 6052 M
* GPU shading: vs(0/4.0/40), ps(0/4.0/40)
* GPU vertex cache: unrecognized, 24
* NVidia MGPU: Logical(1), Physical(1)
* Starting rendering as 2-GPU.
* DVB created: 4096K
* DIB created: 512K
* HWDST/PCF supported and used
* Managed textures disabled
[Discord RPC] Failed to create Discord RPC
* [x-ray]: Starting Main Loop
Starting engine.
intro_start intro_logo
intro_delete ::update_logo_intro
* [x-ray]: Full Memory Stats
* [win32]: free[137432952452 K], reserved[4371544 K], committed[1629412 K]
* [ D3D ]: textures[16 K]
* [x-ray]: process heap[672785 K]
* [x-ray]: economy: strings[29361 K], smem[0 K]
! [SCRIPT ERROR]: d:/stalker anomalygamedatascriptsui_options.script:802: attempt to perform arithmetic on local ‘w’ (a nil value)
[error]Expression :
[error]Function : CScriptEngine::lua_error
[error]File : ..xrServerEntitiesscript_engine.cpp
[error]Line : 191
[error]Description : fatal error
[error]Arguments : LUA error: d:/stalker anomalygamedatascriptsui_options.script:802: attempt to perform arithmetic on local ‘w’ (a nil value)
ok I just tested on DirectX 9 it works, not above.
Источник
CTD when trying to complete tasks Thread — S.T.A.L.K.E.R. Anomaly mod for S.T.A.L.K.E.R.: Call of Pripyat
S.T.A.L.K.E.R. Anomaly
S.T.A.L.K.E.R.: Call of Pripyat mod | Released 2018
The stand-alone mod S.T.A.L.K.E.R. Anomaly aims to be the most stable and customizable experience for fans of the S.T.A.L.K.E.R. games. It’s powered by the Monolith 64-bit engine, a custom fork of the X-Ray engine.
| Posts | |
|---|---|
| Crashes when I click on Settings (Games : S.T.A.L.K.E.R.: Call of Pripyat : Mods : S.T.A.L.K.E.R. Anomaly : Forum : Support : Crashes when I click on Settings) | Locked |
| Thread Options | |
Scenario: Playing as an Ecologist, I was in the Clear Sky base and I had upgraded a merc outfit and forgot to tear off the patch after. Saw the green bar and went to a building and removed the patch, but I don’t remember seeing the notice that I was regarded as an Ecologist. Took 2 tasks and both cause a CTD with the following error.
pick_section_from_condlist xr_effects fail! obj=actor functor=drx_sl_reward_stash
! [SCRIPT ERROR]: c:/games/anomalygamedatascriptsxr_logic.script:491: attempt to call a nil value
[error]Expression :
[error]Function : CScriptEngine::lua_error
[error]File : ..xrServerEntitiesscript_engine.cpp
[error]Line : 191
[error]Description : fatal error
[error]Arguments : LUA error: c:/games/anomalygamedatascriptsxr_logic.script:491: attempt to call a nil value
Any help in finishing these tasks would be greatly appreciated.
Huh, are you up to date and can you upload your entire log along with your save game please? (Might want to try google drive or something)
Hi Tim, yes my game is up to date. I can’t upload the save or log as I was playing Ironman mode and died stupidly. again :/
I tested attaching and removing patches in and around the Clear Sky Base and found that the message will only show at the broken fence before you enter the base. Looking at the code in xr_logic.script I’m pretty sure the error was caused by my character not being recognized in a faction because of the disguise system.
Anyway, problem solved by starting new game.
I have this very similiar error when trying to turn in a drugmaking kit for a task from professor Kalancha. However, I havent been using the disguise system (and im playing as Clear sky). Could it be caused by one of the hotfixes or something? Here’s my part of the log, just in case:
pick_section_from_condlist xr_effects fail! obj=actor functor=drx_sl_reward_stash
! [LUA] SCRIPT RUNTIME ERROR
! [LUA] . anomaly/1.5.0 beta 3.0gamedatascriptsxr_logic.script:491: attempt to call a nil value
! [SCRIPT ERROR]: . anomaly/1.5.0 beta 3.0gamedatascriptsxr_logic.script:491: attempt to call a nil value
[error]Expression :
[error]Function : CScriptEngine::lua_error
[error]File : ..xrServerEntitiesscript_engine.cpp
[error]Line : 191
[error]Description : fatal error
[error]Arguments : LUA error: . anomaly/1.5.0 beta 3.0gamedatascriptsxr_logic.script:491: attempt to call a nil value
EDIT: Im running hotfix 8
Okay, do either of you have any addons by chance? looking at a similar error, according to tdef:
«You are using some mods that edits tasks and tried to use deprecate function «drx_sl_reward_stash» which was removed»
Well, i tried the temporary fix ([Fix — Update 4] Addressing death_manager/npc_pda crash) to solve random crashes in the swamps. I had this temporary fix removed after these task-CTD’s, but it made no difference?
That crash is unrelated to whatever error this is. Is that the only addon/mod you have/had?
Yup, no other addons. I started a new game, il see if it pops up again later
Having the same error, been working on tracking it down. So far, it only has occurred in the Clear Sky base, both with the Doctor (specifically, giving him the drug-making kit; others didn’t crash) and with Cold (all tasks crashed, including the chimera-hunting one). The drx_sl_reward_stash function seems to occur throughout the task configs of the regular game, based on a search of my unpack (configsmisctasktm_marsh.ltx, . tm_military.ltx, etc.), so I don’t think it’s the problem, but I could be wrong.
I’m creating a fresh, clean install and updating to U8 + PDA fix now.
Initial testing did not reproduce the error, so that’s a thing. Hmm! Re-introducing the mods — specifically, copy+pasting the gamedata folder over — also failed to re-introduce the error. As did copy+pasting the save files. Testing some more things, looking for differences, etc.
AAAAAAAAND I only just went and solved it! At least on my end, & hopefully on yours. In your Anomaly/db/updates folder, look for anything that doesn’t belong. For me, it was a set of five hotfix .db0 files, one of which presumably contained the offending content. Probably WAS that deprecated script being called after all, I reckon. Ha! Deleting those in my original install completely solved the problem for me. A correct clean install doesn’t have these files, so worst comes to worst I think you can clean install and port over everything you modded in, then copy your saves over and resume from there. Hope this helps!
Yup, you fixed it for me too mercplan. I had this CTD the other day with a new save, but this time with Cold and turning in banditpatches. Now i tried removing these 5 hotfix.db0 files quickly like you said and it worked immediately !! Are they leftovers from a old hotfix or something? Good find and thanks for the share !!
Merc, your a legend fixed my issue right away as well thanks man.
Источник
Справочник вылетов (Line 101 — Line 200)
Questions
Причина :
Возникает ТОЛЬКО при загрузке сохранений. А вылетает из-за несоответствие конфигов с версией игры. Такое точно случается, если подсунуть шестому патчу system.ltx от четвёртого, получается ли данный вылет с другими конфигами или нет я не знаю.
Правда, на просторах встечал этот же вылет, только в описании были явно указаны или .ogg или .ltx файл — в данном случае ничего сказать не могу.
Лечение :
Причина :
Причиной вылета служит неправильный путь для проигрывания партикла (пример: аномалия в Х-18, она двигается по зацикленному пути из .anm файла).
Лечение :
Либо удалить глючную аномалию (в частном случае партикл), либо исправить проблему.
Причина :
Не найдена трёхмерная OGF-модель, в данном случае mesh.ogf из папки meshesphysics.
Лечение :
Проверяйте наличие файла, правильность написания пути и имени файла.
Причина :
Лечение :
Причина :Игра не находит id какого-то профиля. или диалога. или квеста. В общем указанный id в .xml файле.
Лечение :
Проверяйте правильность написания идентификатора, либо добавьте его, если таковой отсутсвует.
Причина :
game.graph не соответствует кросс-таблице одной из локаций.
Лечение :
Скорее всего — забыли закинуть в геймдату level.gct после правки в СДК и компиляции AI. Помните, level.gct нужно обновить для всех локаций, а не только для тех, которые подвергались правке.
Причина :
Происходит при попытке загрузки сохранения, которое было сделано не другом «наборе» gamedata.
Лечение :
Если делали какие-то изменения собственноручно, то верните папку gamedata в первоначальный вид. В противном случае следуйте совету — удалите сохранение.
Причина :
Странно, но данный вылет происходит только в моде Lost World Trops Of Doom с патчами ниже 3.5.2. Причиной этому якобы большой вес ноги псевдогиганта (inv_weight = 20.0).
Лечение :
Уменьшить вес ноги до 12.
Причина:
Отображение и сокрытие съемных аддонов на оружии в сталкере осуществляется при помощи отображения и сокрытия меша, привязанного к определенной кости в моделе. Существует три таких кости: wpn_scope, wpn_silencer и wpn_launcher. В данном случае мы попытались прописать оружию съемный прицел, но указанный худовый визуал не содержит кости wpn_scope.
Лечение:
Сделать аддон несъемным (либо отключить его вообще) путем редактирования конфига либо добавить в худовую модель указанную кость.
Причина :
game.graph и файл level.ai одной из локаций не соответствуют друг другу.
Лечение :
Вероятно также, что и у предыдущего вылета.
Причина :Одна из моделей на локации зафиксирована (посредством параметра fixed_bones в all.spawn) за неизвестную кость.
Лечение :
Найти и исправить ошибку.
Причина :
Вылет из-за железа, а точнее — оптимизации ОС. Скорее всего проблема с драйверами.
Лечение :
Обновите драйвера на видеокарту. Снизьте графические настройки.
Причина :
Игра не находит идентификатор указанной погоды, в данном случае boloto, в файле environment.ltx.
Лечение :
Варианта два:
1. Поменять погоду прописанную одной из локаций в файле game_maps_single.ltx;
2. Добавить идентификатор погоды в секцию weathers, файле environment.ltx.
Причина :
Данная ошибка, как правило указывает на «криворучие» при создании меню игры. Например: ползунок который увеличивает опции меню при прокрутке задран очень высоко. И в большей степени относится к изменениям худа.
Лечение :
Смотри, где, что наковыряли и исправляйте.
Причина :Игра не нашла в какой-то модели анимацию с именем waunded_1_idle_0.
Лечение :
В первую очередь проверьте правильность написания имени анимации. Если в названием всё впорядке, тогда либо заменить/удалить модель, либо добавить/переименовать анимацию.
Причина :
В диалоге, в данном случае это esc_dialog, нет доступной для отображения фразы (например все заткнуты инфопоршенами и не одно из условий не выполнилось).
Лечение :
Убедиться в том, чтобы хотябы одна из фраз диалога будет доступна.
Причина :
В файле game_relations.ltx допущена ошибка. Вероятнее всего для параметра communities заданы неправильные значения.
Лечение :
Проверить данный файл на ошибки.
Причина :
Для какого-то оружия не верно прописан тип нанoсимого урона.
Лечение :
Найти и исправить ошибку.
Причина :Какая то вершина (вейпоинт) пути sniper_3_walk стоит в неположенном месте (например не на аи-сетке). Объект stalker_0002 (в данном случае сталкер), который якобы двигался по пути sniper_3_walk, попал на эту точку, а заодно ушёл за аи-сетку. Этого движок не терпит.
Тоже самое произойдет если координаты(вейпоинт) пути sniper_3_walk совпадет с координатами места? где нпс запрещено находится будь то рестриктор или аномалия в схеме обхода аномалий. Также этот вылет наблюдается при попытке отправить нпс за пределы места работ параметр out_rest = «имя_рестриктора», в файле загрузки работ гулага. Попробуйте любого сталкера из лагеря новичков отправить допустим к остановке получите этот самый вылет.
Лечение :
Найти и исправить ошибку.
Причина :
Лечение :
Говорят от него помогает установка третьего сервис пака на ХР.
ТЧ, 1,0004. + Луа-расширение RvP. Такая необычная реакция на неправильно указанное имя текстуры в xml-описателе.
См. также справку по вылетy Line 764
Причина :
Судя по логу — проблемы с видео памятью. Причины не известны.
— Неверная установка мода.
— Проблемы с драйверами видеокарты или Direct X.
— Проблемы с операционной системой и прочее.
Лечение :
Причина :
Игра не находит указанного файла.
Лечение :
Либо добавить файл, либо убрать регистрацию этого файла в конфигах, зачастую это либо system.ltx, либо localization.ltx.
Причина :
В игре даже пропатченной до версии 1.0005 всё ещё есть проблемы с маршрутами.
Лечение :
Обычно достаточно просто загрузить последний сейв и не сохраняться рядом с местами, где происходят такие вылеты.
Дополнительное обсуждение и информация — в этом и этом постах.
Причина :
Игра не может найти указанный файл по указанному пути.
Лечение :
Либо находите в .ltx файлах строку #include «prefetchprefetch.ltx» и удаляйте, либо добавляйте сам файл.
Причина :
all.spawn не соответствует game.graph. Когда компилировали AI, видно, забыли пересобрать спавн.
Лечение :
Привести all.spawn и game.graph в соответствие.
Причина :
Вылет говорит о том, что объект попал в вертекс (96), которого нет на данной карте.
Лечение :
Если загрузка последнего сохранения не помагает, то можете попробовать уменьшить радиус A-Life, посредством параметра switch_distance, пройти проблемный участок, а затем вернуть первоначальное значение параметра.
Возникает при попытке взять имя уровня по его ID c помощью вызова alife():level_name(level_id), если число level_id не соответствует ни одному из существующих уровней.
Причина :
Игра не находит в каком-то .xml файле указанный элемент.
Лечение :
Найти и исправить ошибку.
Причина :
Продублирована указанная секция в .ltx файлах.
Лечение :
Найти и исправить ошибку.
Причина:
Вы присвоили какому-то объекту визуал, у которого забыли сгенерировать шейпы. Как вариант — случайно были перепутаны мировая и худовая модели оружия. Имя объекта и сбойный визуал указаны в строке description
Лечение:
Есть несколько вариантов:
а) Сгенерировать у указанной модели шейпы, используя Actor Editor (AE) из состава СДКб)заменить указанную модель на «заведомо рабочую»
B) Найти, где в конфиге прописан неверный визуал, и исправить параметр на другой
Добавил новую модель (ПДА заменил). Запускаю игру, ловлю вылет: Все было проставлено правильно, СДК не бунтовал при экспорте. Делал на основе кости старого ПДА АПД.
Все, спасибо, разобрался. Нужно было в СДК во вкладке Object поставить make progressive
Причина :
Игра определила повторяющиеся id в .xml файле, чего быть не должно.
Лечение :
Найти и исправить ошибку.
Причина :
Либо не найден файл шейдера deffer_impl_flat.vs, либо проблема вся в том, что неправильно закомпилился шейдер, при компиляции уровня на качестве, более высоком чем Draft. Для ЗП (ЧН) это может ещё быть из-за отсутствия thm’ок для текстур терраина уровня.
Лечение :
В первом случае — проверить наличие файла. Во втором — нужно скачивать исправление шейдеров от товарища Haron.
Источник
Adblock
detector
| Posts | |
|---|---|
| CTD when trying to complete tasks (Games : S.T.A.L.K.E.R.: Call of Pripyat : Mods : S.T.A.L.K.E.R. Anomaly : Forum : Support : CTD when trying to complete tasks) | Locked |
| Thread Options | |
Scenario: Playing as an Ecologist, I was in the Clear Sky base and I had upgraded a merc outfit and forgot to tear off the patch after. Saw the green bar and went to a building and removed the patch, but I don’t remember seeing the notice that I was regarded as an Ecologist. Took 2 tasks and both cause a CTD with the following error.
pick_section_from_condlist xr_effects fail! obj=actor functor=drx_sl_reward_stash
! [SCRIPT ERROR]: c:/games/anomalygamedatascriptsxr_logic.script:491: attempt to call a nil value
FATAL ERROR
[error]Expression : <no expression>
[error]Function : CScriptEngine::lua_error
[error]File : ..xrServerEntitiesscript_engine.cpp
[error]Line : 191
[error]Description : fatal error
[error]Arguments : LUA error: c:/games/anomalygamedatascriptsxr_logic.script:491: attempt to call a nil value
Any help in finishing these tasks would be greatly appreciated.
Huh, are you up to date and can you upload your entire log along with your save game please? (Might want to try google drive or something)
Hi Tim, yes my game is up to date. I can’t upload the save or log as I was playing Ironman mode and died stupidly… again :/
I tested attaching and removing patches in and around the Clear Sky Base and found that the message will only show at the broken fence before you enter the base. Looking at the code in xr_logic.script I’m pretty sure the error was caused by my character not being recognized in a faction because of the disguise system.
Anyway, problem solved by starting new game.
I have this very similiar error when trying to turn in a drugmaking kit for a task from professor Kalancha. However, I havent been using the disguise system (and im playing as Clear sky). Could it be caused by one of the hotfixes or something? Here’s my part of the log, just in case:
pick_section_from_condlist xr_effects fail! obj=actor functor=drx_sl_reward_stash
! [LUA] SCRIPT RUNTIME ERROR
! [LUA] … anomaly/1.5.0 beta 3.0gamedatascriptsxr_logic.script:491: attempt to call a nil value
! [SCRIPT ERROR]: … anomaly/1.5.0 beta 3.0gamedatascriptsxr_logic.script:491: attempt to call a nil value
FATAL ERROR
[error]Expression :
[error]Function : CScriptEngine::lua_error
[error]File : ..xrServerEntitiesscript_engine.cpp
[error]Line : 191
[error]Description : fatal error
[error]Arguments : LUA error: … anomaly/1.5.0 beta 3.0gamedatascriptsxr_logic.script:491: attempt to call a nil value
stack trace:
EDIT: Im running hotfix 8
Edited by: Vengeance19
Okay, do either of you have any addons by chance? looking at a similar error, according to tdef:
«You are using some mods that edits tasks and tried to use deprecate function «drx_sl_reward_stash» which was removed»
Well, i tried the temporary fix ([Fix — Update 4] Addressing death_manager/npc_pda crash) to solve random crashes in the swamps. I had this temporary fix removed after these task-CTD’s, but it made no difference?
That crash is unrelated to whatever error this is. Is that the only addon/mod you have/had?
Yup, no other addons. I started a new game, il see if it pops up again later
Having the same error, been working on tracking it down. So far, it only has occurred in the Clear Sky base, both with the Doctor (specifically, giving him the drug-making kit; others didn’t crash) and with Cold (all tasks crashed, including the chimera-hunting one). The drx_sl_reward_stash function seems to occur throughout the task configs of the regular game, based on a search of my unpack (configsmisctasktm_marsh.ltx, …tm_military.ltx, etc.), so I don’t think it’s the problem, but I could be wrong.
I’m creating a fresh, clean install and updating to U8 + PDA fix now…
Initial testing did not reproduce the error, so that’s a thing. Hmm! Re-introducing the mods — specifically, copy+pasting the gamedata folder over — also failed to re-introduce the error. As did copy+pasting the save files. Testing some more things, looking for differences, etc…
AAAAAAAAND I only just went and solved it! At least on my end, & hopefully on yours. In your Anomaly/db/updates folder, look for anything that doesn’t belong. For me, it was a set of five hotfix .db0 files, one of which presumably contained the offending content. Probably WAS that deprecated script being called after all, I reckon. Ha! Deleting those in my original install completely solved the problem for me. A correct clean install doesn’t have these files, so worst comes to worst I think you can clean install and port over everything you modded in, then copy your saves over and resume from there. Hope this helps!
Yup, you fixed it for me too mercplan. I had this CTD the other day with a new save, but this time with Cold and turning in banditpatches. Now i tried removing these 5 hotfix.db0 files quickly like you said and it worked immediately !! Are they leftovers from a old hotfix or something? Good find and thanks for the share !!
Merc, your a legend fixed my issue right away as well thanks man.
 |
Добро пожаловать, |
Прохождение мода Stalker Anomaly
(1 чел.) (1) гость
|
Ответить |
Новая тема |
|
|
ПРОХОЖДЕНИЕ МОДА STALKER ANOMALY
S.T.A.L.K.E.R. Anomaly — представлен как модпак построенный на 64-разрядной версии движка Open X-Ray и платформе проекта Last Day 1.3 с множеством дополнений и пользовательскими аддонами. Кроме геймплейных нововведений, измененной графической оболочки и новых игровых систем в Stalker Anomaly добавлен сюжетный режим прохождения Lost to the Zone, состоящий из трех частей.
Режим Story теперь включает сюжетные линии «Lost to the Zone», а также «Mysteries of the Zone» и DRX Questlines. Игрок волен играть в любую из них, когда захочет. Основные квесты не будут даны вам при запуске игры, вам нужно попросить об этом.
|
|
Спасибо сказали: 9im10, FANAT, varikap, Recluse, DoctorChe, D.Rash, DRON, Таня, LAKI, AndreyStep, gazin, zima59, gewa, continent, Сталкер_06, bazilevs, Виктор53, lapa1969, igor4404, viktor19, СтарыйРаста |
ОПИСАНИЕ и ССЫЛКИ НА СКАЧИВАНИЕ
|
Подскажите пожалуйста в чем причина вылета при сдаче Лукашу квеста на уничтожение бтров на Кордоне? Выдаёт вот такой лог вылета:
Логи вылета, большие тексты, картинки и видео — прячь под спойлер. Инструкции.
Спасибо за быстрый ответ)) |
|
|
|
DaniilSki, привет. Информация по вылету Line 12:
|
|
«Эти добрые люди — ничему не учились, и все перепутали, игемон. Я, вообще начинаю опасаться, что путаница эта будет продолжаться ещё очень долгое время…» (М.А. Булгаков) Vae victis!
|
|
Начались постоянные вылеты каждые минуту две на Дикой территории.
|
|
Ребята, подскажите, вылетает игра, в любое время может вылететь, примерно каждые 3-5 минут где то, что за модуля не хватает не знаю, может подскажите :
Заново перекачал игру, установил фиксы, теперь при новой игре или по старым сохранкам вылет:
Сбросил ссылку на оф.сайт в ЛС. |
|
|
|
Господа подскажите , не выключаются Осознание, рычажок «заклинило». |
|
|
|
Подскажите пожалуйста что за вылет на болотах.
Как я понял мне не хватает какого то скрипта №338, хотя может я и не прав |
|
День добрый! |
|
Ребят, а кто знает как выполнить задание LR_300ml x3 Контрабанда? Там надо перевести оружие мимо вояк, но меток — нет. |
|
|
|
Ответить |
Новая тема |
|
https://forums.adobe.com/people/Jeff+A+Wright wrote
Dreamedia, what type of Creative Cloud membership are you using to install and use Adobe XD? I do not see any memberships assigned to the e-mail address you used to post to this public forum.
Are you installing Adobe XD on a computer, and network, that you personally manage, Dreamedia. If so then do you have any questions on how to implement the solutions listed in Error code 191 when installing XD on Windows ?
I do have a Creative Cloud membership attached to this e-mail address and it is currently on the Adobe XD monthly plan. Also I do personally manage the computer and have systematically completed each and every step in the troubleshooting document save for acquiring a Windows developer license or reformatting the computer, neither of which are reasonable «solutions» for a company to suggest with a straight face.
I have also tried running the CC Cleaner Tool to completely remove the Creative Cloud Desktop App and all previous installations of Adobe XD. I then restarted, reinstalled Creative Cloud, and attempted to install Adobe XD again. It resulted in the same error, as expected:
Exit Code: 191
-------------------------------------- Summary --------------------------------------
- 2 fatal error(s), 2 error(s), 0 warnings(s)
FATAL: Error (Code = 191) executing in command 'AddUWPAppxCommand' for package: 'UWPAssets', version:18.0.12.9
FATAL: Error occurred in install of package (Name: UWPAssets Version: 18.0.12.9). Error code: '191'
ERROR: hdhelper exe at C:Program Files (x86)Common FilesAdobeAdobe Desktop CommonHDBoxHDHelper.exe failed to install UWP app with xml
Adobe.CC.XD
C:adobeTempETR8BC9.tmp1SparklerAppSparklerApp.appx
18.0.12.9
x64
CN=Adobe Systems Incorporated, OU=Adobe Systems, O=Adobe Systems Incorporated, L=San Jose, S=California, C=US, SERIALNUMBER=2748129, OID.2.5.4.15=Private Organization, OID.1.3.6.1.4.1.311.60.2.1.2=Delaware, OID.1.3.6.1.4.1.311.60.2.1.3=US
adbxd:
Microsoft.VCLibs.140.00
14.0.25426.0
x64
CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US
C:adobeTempETR8BC9.tmp1SparklerAppDependenciesx64Microsoft.VCLibs.x64.14.00.appx
Microsoft.VCLibs.Desktop.140.00
14.0.25426.0
x64
CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US
C:adobeTempETR8BC9.tmp1SparklerAppDependenciesx64Microsoft.VCLibs.x64.14.00.Desktop.appx
false
with error code 1
ERROR: Failed to install UWP Appx Package
-------------------------------------------------------------------------------------
Hello,
using the gamedata folder available in your repo as of 21st Jan 2023 vanilla anomaly crashes to dektop after trying to launch a game with the error
Expression :
Function : CScriptEngine::lua_pcall_failed
File : ..xrServerEntitiesscript_engine.cpp
Line : 204
Description : fatal error
Arguments : LUA error: …games/anomaly 1.5.2gamedatascriptsarti_jamming.script:990: attempt to index global ‘custom_functor_autoinject’ (a nil value).
I understand that the content might not be suited for release. I was just trying to circumvent conflict of an olde version with ammo maker, found this webpage and since release is currently not working, I tried using directly data in the repo.
Have a nice day, good work with this addon 
Hello,
I might be mistaken, but the latest release seems to contain incorrect files. I would guess weapon and outfit part overhaul got mixed up somehow?
Using Grok Stash overhaul and outfits part overhaul
I believe this may not be an actual bug, but more just something unlucky that can occasionally happen, but I’ve had it happen about four times over a playthrough where I’ll have just left somewhere after fully restoring a weapon at a technician or fully restoring it myself, (3 of the 4 times this happened was with the Saiga «Nerd» variant from BaS, which may be an incompatibility? Not sure) and the first or second shot will cause a weapon jam, even when I’ve turned down the weapon jam chance to 0.5 in MCM.
I feel like there should be a configurable option in MCM where you can set the minimum health a component needs to be to start jamming (e.g. a weapon part other than the barrel needs to be at 90% before a Jam can occur), as it feels evil when you get a weapon jam on the first shot after getting it wholly repaired to new.
Hello, I love your mod, I was using the previous version and after updating to the latest version you posted a couple of hours ago, I got a crash when loading my save file.
I’m not using Gamma, just Anomaly with a bunch of addons.
I do have MCM, and the only addon that was conflicting with yours was Luna’s Master Disassembly List and Parts Fix, which I put behind your addon.
category: processing encyclopedia_addons
article: processing article_opo
article: processing articles_wpo
- TB_Remove_Bugged_Stashes script has already been run in this game.
! Can't find sound 'weapons_gunfiremonovsskvssk_close_distance'
! Can't find sound 'weapons_gunfiremonocloseclose_distance'
! Can't find sound 'weapons_gunfiremonoclosemedium_distancemp153'
! [SCRIPT ERROR]: ...s/anomaly mo2gamedatascriptsa_arti_jamming_mcm.script:66: attempt to concatenate a nil value
* Saving spawns...
* Saving objects...
* 32484 objects are successfully saved
* Game fatal_ctd_save_1.scop is successfully saved to file 'd:/games/anomaly mo2appdatasavedgamesfatal_ctd_save_1.scop'
FATAL ERROR
[error]Expression : <no expression>
[error]Function : CScriptEngine::lua_pcall_failed
[error]File : ..xrServerEntitiesscript_engine.cpp
[error]Line : 204
[error]Description : fatal error
[error]Arguments : LUA error: ...s/anomaly mo2gamedatascriptsa_arti_jamming_mcm.script:66: attempt to concatenate a nil value
stack trace:
The new BaS guns are not supported by this mod
The arti_jamming script’s using_old_ammo function determines if the old ammunition penalties should apply to a weapon by checking if the ammunition’s impair value is greater than 1.
The 9x21mm ammo in BaS has an impair value of 1.1 for some reason. This means WPO treats it as old ammunition even though it isn’t, and with the old ammunition penalties enabled all 9×21 guns jam multiple times a magazine and rapdily lose condition.
Related script/config snippets:
-- returns true if using ammo with impair > 1
function using_old_ammo(wpn)
if wpn:id() ~= cgd.id or not get_config("oldammo") then return false end
local ammo_type = wpn:get_ammo_type() + 1
local ammo = cgd.ammo_data[ammo_type]
if ammo and SYS_GetParam(2, ammo, "impair") > 1 then
return true
else return false
end
end
[ammo_9x21_sp10]:ammo_base ; 165 gr
GroupControlSection = spawn_group
discovery_dependency =
$spawn = "weaponsammoammo_9x21_sp10" ; option for Level Editor
class = AMMO_S
~snip~
k_disp = 0.66
k_hit = 0.77 ; 1.25
k_impulse = 0.8
k_ap = 0.45
impair = 1.1
tracer_color_ID = 0
~snip~
Stumbled upon a bug that crashes the game when i’m trying to disassemble a weapon that doesn’t have a mag inside. Started happening after i updated WPO to the latest version (10.10.22). I use default wuut mags (version from the 18.02.21). Also, before update i used a version of WPO from around october/november of 2021.
weapon_eject_mag_precondition
weapon_eject_mag_precondition1
WeaponGetMagData: (wpn_ppsh41_woodnew) ID: 28136
WeaponGetMagData: (N:no_mag:0:)
WeaponGetMagData: (wpn_ppsh41_woodnew) ID: 28136
WeaponGetMagData: (N:no_mag:0:)
WeaponSetMagData N:no_mag:0:
FATAL ERROR
[error]Expression :
[error]Function : CInifile::r_section
[error]File : Xr_ini.cpp
[error]Line : 544
[error]Description : fatal error
[error]Arguments : Can’t open section ‘no_mag’.
stack trace:
When I attempt to select an item in the repair window to repair I CTD. This is caused by a new line of code in the script «zzzz_arti_jamming_repairs». Using an old version of this mod with a previous script allows me to repair, but I can’t field strip with that one activated. This has forced me to juggle between the mods. Log excerpt below. Please fix.
! [SCRIPT ERROR]: ....5.1.2gamedatascriptszzzz_arti_jamming_repairs.script:851: attempt to index global 'a_repair_override' (a nil value)
FATAL ERROR
[error]Expression : <no expression>
[error]Function : CScriptEngine::lua_pcall_failed
[error]File : ..xrServerEntitiesscript_engine.cpp
[error]Line : 204
[error]Description : fatal error
[error]Arguments : LUA error: ....5.1.2gamedatascriptszzzz_arti_jamming_repairs.script:851: attempt to index global 'a_repair_override' (a nil value)
stack trace:
I installed the mod and when I went to field strip a gun it doesn’t do anything. I clicked on field strip then remove all and nothing happened. Same with individual parts. I am using desolation but idk how they would conflict.
Is it normal that, when my weapon jammed and I press the reload key the actor puts down the weapon and directly pulls it out again? It does not clear the jam and sometimes breaks the unjam key so I have to manually unjam the weapon in my Inventory.
Hard to reproduce, but taking certain actions during the unjam animation (the gun being holstered) freezes the gun in a holstered position. No other gun can be equipped, knife can’t be equipped either, but you can still open your PDA or get RF receiver/Detector.
This does not get fixed in any other way than reloading a save. I’ve tried unequipping, dropping, field stripping, unloading, and all possible inventory actions, along with all keystrokes (interact, reload, change ammunition, change fire mode, etc), and nothing brings back the affected or any other weapon.
Apparent steps:
Double tap F to fix a jam (doesn’t seem to matter which kind)
Make another action — Attempting to swap weapons, draw knife, jump, interact with something via F
Gun is permanently holstered, you lose access to other guns.
Is it possible to re-enable classic repair at technicians as an MCM option so they repair the entire weapon (overall condition and parts)? I run with the Anomaly setting that repairs and upgrades by technicians take time and would like the techs to repair weapon parts while they «work on my weapon(s)».
Addon Version: November 9th, 2021
Modlist: MO2 Modlist 2021.11.11.txt
Heads up man, got another index error:
Checking parts for wpn_knife3
! [SCRIPT ERROR]: ...nomaly/anomaly 1.5.1gamedatascriptsa_wpo_parts.script:25: attempt to index a nil value
FATAL ERROR
[error]Expression : <no expression>
[error]Function : CScriptEngine::lua_error
[error]File : ..xrServerEntitiesscript_engine.cpp
[error]Line : 191
[error]Description : fatal error
[error]Arguments : LUA error: ...nomaly/anomaly 1.5.1gamedatascriptsa_wpo_parts.script:25: attempt to index a nil value
stack trace:
WPO Crash — Full Log 2021.11.11.log
The interesting part is that it only seems to happen when I save and then reload the save in Dead City — anywhere else seems to be safe and sound.
Happening with original Mags (not redux). I suspect it being the addition of magazines potentially block unjam mechanic. At least I couldn’t find anything else that would explain it. Happens only on latest relese from Github.
Why I’m still using Wuut Mags? Because I’m in the middle of another playthrough that I want to finish first.
! [LUA] SCRIPT RUNTIME ERROR
! [LUA] …mes/stalker anomalygamedatascriptsarti_jamming.script:387: attempt to compare number with nil
! [SCRIPT ERROR]: …mes/stalker anomalygamedatascriptsarti_jamming.script:387: attempt to compare number with nil
FATAL ERROR
[error]Expression :
[error]Function : CScriptEngine::lua_error
[error]File : ..xrServerEntitiesscript_engine.cpp
[error]Line : 191
[error]Description : fatal error
[error]Arguments : LUA error: …mes/stalker anomalygamedatascriptsarti_jamming.script:387: attempt to compare number with nil
stack trace:
Apparently barrel_wear is nil when using shotguns because family_shotgun.ltx has two values for barrel_wear (which is interpreted as a table), while it is parsed as a single float in the script at line 285. Changing barrel_wear values inside family_shotgun.ltx to single values (for example, from «barrel_wear = 0.07, 0.12» to «barrel_wear = 0.07») fixes this issue. I believe the second value was intended to be used when the shotguns fired old ammo, but calculate_barrel_wear already just doubles the normal wear if old ammo is used.
! [SCRIPT ERROR]: …nomalygamedatascriptszzzz_arti_jamming_repairs.script:738: attempt to call global ‘math_random’ (a nil value)
FATAL ERROR
[error]Expression :
[error]Function : CScriptEngine::lua_error
[error]File : ..xrServerEntitiesscript_engine.cpp
[error]Line : 191
[error]Description : fatal error
[error]Arguments : LUA error: …nomalygamedatascriptszzzz_arti_jamming_repairs.script:738: attempt to call global ‘math_random’ (a nil value)
stack trace:
Apparently math_random isn’t declared in the script like other math functions.
The Russian translation is not correct. the degree of wear of parts shows with the inscription «st_damage_4»
and in MCM there is no translation, just bare words from the code, even without translation into English.
Addon Version: Latest Release — October 14th
Other Relevant Addons:
- Outfit Parts and Repair Overhaul + WPO patch, using the Github latest release
- Mechanics Can Repair Weapon Parts by anomalu, https://www.moddb.com/mods/stalker-anomaly/addons/mechanics-can-repair-weapon-parts
Encountered Problem: So I may have ran into a possible bug (or incompatibility?) where the weapon’s condition doesn’t adjust accordingly when I replace broken parts from the workbench.
As far as I understand it, weapon condition is the overall cleanliness of the gun, right? And because the gun I was repairing, the TOZ-34 Bizon, was at critical condition with 5% and all of its parts broken, I thought that its condition would go up as I replace its broken parts with clean and refurbished parts (thanks to MCRWP linked above).
However, the shotgun stayed at 5% despite me having replaced all of its broken components at Xenotech’s workbench. I used the shotgun repair kit itself to raise the condition and that’s when more weirder stuff happened. The kit started to, as stated in the mod description, replace the «damaged» parts, even though I just replaced them with fresh ones, and generated two 0% shotgun parts that it had replaced.
I’m hoping you might have some insight into this unless I was interpreting the mod’s functions wrong. And I do apologies for not having any images or videos since I wasn’t doing any recording when I ran into that problem.
EDIT: Forgot to mention that I did load up the addon and the other related addons to active save — after I obtained the near broken TOZ-34 Bizon.
After updating to the newest version (I used 1.11 prior to this) my game crashes when loading a save, and when I make a new game it crashes whenever I fire a weapon. Does it have to do something with that i use BaS?
New game error:
! [LUA] SCRIPT RUNTIME ERROR
! [LUA] …mes/anomaly-1.5.1.2gamedatascriptsarti_jamming.script:253: attempt to index global ‘larp’ (a nil value)
! [SCRIPT ERROR]: …mes/anomaly-1.5.1.2gamedatascriptsarti_jamming.script:253: attempt to index global ‘larp’ (a nil value)
FATAL ERROR
[error]Expression :
[error]Function : CScriptEngine::lua_error
[error]File : ..xrServerEntitiesscript_engine.cpp
[error]Line : 191
[error]Description : fatal error
[error]Arguments : LUA error: …mes/anomaly-1.5.1.2gamedatascriptsarti_jamming.script:253: attempt to index global ‘larp’ (a nil value)
Current save error:
! [SCRIPT ERROR]: c:/games/anomaly-1.5.1.2gamedatascriptswpo_loot.script:70: attempt to index global ‘larp’ (a nil value)
FATAL ERROR
[error]Expression :
[error]Function : CScriptEngine::lua_error
[error]File : ..xrServerEntitiesscript_engine.cpp
[error]Line : 191
[error]Description : fatal error
[error]Arguments : LUA error: c:/games/anomaly-1.5.1.2gamedatascriptswpo_loot.script:70: attempt to index global ‘larp’ (a nil value)