DMX mod 1.3.4 - Traduction Anglaise maintenant Disponible!!

FATAL ERROR

[error]Expression : fatal error
[error]Function : CScriptEngine::lua_error
[error]File : E:\stalker\sources\trunk\xr_3da\xrGame\script_engine.cpp
[error]Line : 73
[error]Description : <no expression>
[error]Arguments : LUA error: ...hadow of chernobyl\gamedata\scripts\state_mgr.script:197: C stack overflow


stack trace:

"C stack overflow"
"C stack overflow" - playing overflow the stack.

In the game runs in series / parallel set of operations. Interim results are entered into a selected region (the stack). The size of the overgrown depends on many factors, and purely on the amount of free RAM at start of game.
Thus if the "old" computer RAM or clogged various stock / residents - the volume can not be 'sufficient' for the assembly in critical conditions.
In the assembly of different modules are added / schemes, whose work, in comparison with the original game, an additional load / game fills the stack. The latest minifiksom added at least two new schemes, and in fact the scheme has not yet been optimized to the end, what and test!

Summary:
- Optimize memory company (the old - it is added, and the rest - unload) at the start of the game;
- Give the stats and look forward to update / optimization.

Depart on a stack overflow happens for two reasons:
- A) 'the curve' code;
- B) 'local splash' - usually an isolated case.

In case a) - to try to change their game / passage, revert to an earlier save.
In case b) - do not use that leads to the departure (eg the "Contact Us" in the PDA) or just continue with the last Seiwa - departures may not be repeated.

Well, if at all 'procedure simply' departures stack - disable the most recently added to the assembly of modules to debug them and / or disabled are not the most interesting for the following modules AI.
As previously explained in stack: a region of memory allocated to the game and which temporarily stores the results of the various functions. If you exceed the amount of results of the selected area overflow on the stack (stack overflow). Filling the stack - is a function of time (!), Ie filling is changed (usually increased, but may decrease) as the playing time at the location. Not to be confused (!) Stack and Storage (storage) of data objects and HS games are remembered not only in RAM.
Simple logic dictates - if the stack periodically emptied (cleared of unclaimed / outdated data) - the overflow can be avoided.
Various (Quick) Save-loady least quite simply completely cleans the stack, because boot (!) any (Quick) Seiwa is reinitializing all modules / variables.
However (!) Is a loss of previously performed audits / computing / counter / ... etc.
- Tolik wounded in the logic is written to "stand and wait 60 seconds after contact with the PC." If after talking to restart Save - trigger a conversation already worked, and the timer time nulled -> Shreds ran home.
- Petrukha report on the implementation of cleanup if the death of all registered in the gulag ATP bandits. Sometimes Petrukha or dies (it should be duplicated report surviving partner), and sometimes counter goes astray, as Do not kill the stalker and / or YY, or a Doctor of monster ... After a reboot - the trigger to work, the bandits live counter is empty, there was no report => report Petruha.
And so on etc. ...
Thus "Treatment podvisshih jobs" restarts it is quite logical, but does not apply to the stack, not counting the trivial complete cleaning.

FATAL ERROR

[error]Expression : assertion failed
[error]Function : _VertexStream::Lock
[error]File : E:\stalker\sources\trunk\xr_3da\R_DStreams.cpp
[error]Line : 44
[error]Description : (bytes_need<=mSize) && vl_Count

.... Entering the ZONE .....
* phase time: 15 ms
* phase cmem: 418458 K
* [win32]: free[2017428 K], reserved[137432 K], committed[2039380 K]
* [ D3D ]: textures[932973 K]
* [x-ray]: crt heap[418456 K], process heap[12111 K], game lua[49405 K], engine lua[234 K], render[0 K]
* [x-ray]: economy: strings[13100 K], smem[26233 K]
[16-9] get_xml_name for[game_tutorials.xml] returns [game_tutorials.xml]
[16-9] get_xml_name for[ui_credits.xml] returns [ui_credits.xml]
[16-9] get_xml_name for[ui_movies.xml] returns [ui_movies.xml]
[16-9] get_xml_name for[maingame_pda_msg.xml] returns [maingame_pda_msg.xml]
[16-9] get_xml_name for[maingame_pda_msg.xml] returns [maingame_pda_msg.xml]
[16-9] get_xml_name for[maingame_pda_msg.xml] returns [maingame_pda_msg.xml]
[16-9] get_xml_name for[maingame_pda_msg.xml] returns [maingame_pda_msg.xml]

FATAL ERROR

[error]Expression : !object->used_ai_locations() || ai().level_graph().valid_vertex_id(object->m_tNodeID)
[error]Function : CALifeSwitchManager::add_online
[error]File : E:\stalker\sources\trunk\xr_3da\xrGame\alife_switch_manager.cpp
[error]Line : 64
[error]Description : Invalid vertex for object
[error]Arguments : wpn_abakan_m143010

Code:

Expression:! Object-> used_ai_locations () | | ai (). Level_graph (). Valid_vertex_id (object-> m_tNodeID)
Function: CALifeSwitchManager:: add_online
File: E: \ stalker \ patch_1_0004 \ xr_3da \ xrGame \ alife_switch _manager.cpp
Line: 64
Description: Invalid vertex for object
Arguments: af_rusty_sea-urchin23058

Here we have hung the artifact. Most often, these crashes occur in the Old Village location. Although these departures are rare. Treated removal problem object. In this case the object is - af_rusty_sea-urchin23058

And now the most important - remove the problem object.
Removing buggy objects (barrels, skeletons, a restrictor)
Important! Make copies of original files.

With departures from invalid vertex, missing paths in the absence of abuse restrictor object, in other game situations it becomes necessary to remove the "nuisance" object. Propose to use an existing block of code in the script bind_stalker.script.
"Removing buggy objects"
0. Note. Remove objects, being in full confidence that they are no longer needed.

1. In the file gamedata \ scripts \ bind_stalker.script find the commented block of code
Code:

- [[Local bad_object_names = {"wpn_lr30053522", "wpn_lr30058409"} - "wpn_lr30025601", "wpn_lr30028817", "wpn_lr30033589"
local i, se_name, se_obj

for i, se_name in ipairs (bad_object_names) do
se_obj = alife (): object (se_name)
if se_obj then
news_manager.send_tip (db.actor, "was removed buggy trunk:" .. se_name, nil, nil, 1000)
alife (): release (se_obj, true)
end
end]]

2. Remove comments - [[at the beginning before the local and]] at the end after end

3. In bad_object_names instead of these names for example trunks enter the names of objects that there is a need to remove. Each name is "", name, if more than one, should be sent by a comma.

Example 1. Removing the restrictor removal Gray (ATP, mobile merchant)
Code:

local bad_object_names = {"atp_sedoy_delete_restrictor"}
local i, se_name, se_obj

for i, se_name in ipairs (bad_object_names) do
se_obj = alife (): object (se_name)
if se_obj then
news_manager.send_tip (db.actor, "was removed buggy trunk:" .. se_name, nil, nil, 1000)
alife (): release (se_obj, true)
end
end

Example 2. Removing buggy forever zombikov (sarcophagus, for example of 2)
Code:

local bad_object_names = {"sarc_arhara_zombied_respawn_154797", "sarc_arhara_zombied_respawn_149048"}
local i, se_name, se_obj

for i, se_name in ipairs (bad_object_names) do
se_obj = alife (): object (se_name)
if se_obj then
news_manager.send_tip (db.actor, "was removed buggy trunk:" .. se_name, nil, nil, 1000)
alife (): release (se_obj, true)
end
end

3. Save the script and load the desired save. Removal will be done at boot time, the PC receives the message
"Removed buggy trunk: <title>" for each object listed in bad_object_names and existing in the game. A remote object once more time do not delete.

After the successful removal of a better (not critical) to restore the comments in the code - [[at the beginning before the local and]] at the end after end, as required by the game to repeat the operation with claim 1 for the other object (s).

Aesthetes can afford instead of "was removed buggy barrel" in the text of the script to write "was removed buggy object"

Using the method of deleting objects in the function actor_binder: update in light of the availability of the described method is, imho, deprecated.

UPDATE

I have a patch for tonight:

FIXES:
added missing texture for PM quest in Swamp
added mossberg590 to physics group

OPTIONS in modders script:
sleeping bag use anytime except Hellhour and Blowouts
use DMX cars or not

also added mac10 and dual weapons to spawn menu.

Still time to send bugs and requests to stalkersoup@tecnobacon.com
============================================================
QUESTION

I am preparing Patch 5, would like to know what you think my default settings should be in the modders script, they are:
start_collector = true
use_ammo_belt = false
use_DMX_cars = true
Auto_Save = true
unlimited_bolts = true
hide_weapon = true
default_hit = true
use_COP_bloodsuckers = true
use_COP_burers = true
use_COP_psi_dog = true
breath_sounds = true
default_sleep = true
money = 1
money_real = 1
suithud_enable = 1
blurs_enable = 1
blood_enable = 1
bleed_enable = 1
kostri = 0

send your suggestions to stalkersoup@tecnobacon.com, most popular settings will be used.
Eric

une fois avoir accompli les missions, le chef nous donne un endroit pour quitter cette map...?! ou bien s'agit'il d'un petit bug..? je n'arrive pas à la quitter cette map J'ai passé au peigne fin tout la map, j'ai même été faire de la plongée, frappé mon visage contre les rochers je vous posterais les screens à venir

Oui, effectivement le boss des stalkers (sosie de Beard) te montre la sortie après la mission des actéfacts. Cette sortie donne sur la Décharge et se trouve à droite de la map, en plein milieu de la route. Je te poste deux screens pour que tu puisse te repérer. Le premier screen désigne le repaire des bandits, le second, la sortie que tu cherches. Et à droite... ben c'est moi, je suis enfin chez Freedom ! Hé ! Hé !

Je n'ai pas vérifier dans cette version du mod mais avant il éxistait une autre sortie: en bas à droite de la map il y a un empilement de trois rochers, tu monte jusqu'en haut et hop: direction le cordon