Hi there mybe anyone has already investigated this issue and has a clue why this happens to random clients at random times?
Is there any way that is suggested to find route cause of this ? All crashes point to this code snippet
static void DrawModelGeometryHook(grmShaderFx* shader, int a2, void* a3, int a4, bool a5)
{
if (shader->program && shader->program->vertexPrograms.GetSize() && shader->program->vertexPrograms[0].name && strstr(shader->program->vertexPrograms[0].name, "_batch:") != nullptr)
{
return;
}
g_origDrawModelGeometry(shader, a2, a3, a4, a5);
}
It would probably be better if you provide crash reports as we can’t guess as to why something is crashing there 
You think dmp will also be usefull ?
No provide the entire file you get with “Save Information”
Do these crashes happen if you don’t run with graphic mods?
No these are 4 different people and 1 has Maxed out settings, NVE, one is NVE without NBE, and two are complete stock
Yes, also just received new log
CfxCrashDump_2023_10_08_09_17_55.zip (1.6 MB)
With absoloutely no graphic mods
Do you have any streamed files running? Attempt stopping those to verify the issue doesn’t lie in the streamed asset.
Ok it will take some time to go trough everything, but will try to do batch disabled over restarts, and report back whats what. Thanks for the advice
If it happens consistently enough I would ask clients to try to keep track of where they are when it happens. If they are all near the same location then its probably a map, if they are not then the issue could potentially be a vehicle, or clothes maybe. It isn’t even guaranteed that the issue is a streamed asset, but its good to close all doors before deciding there is an issue with the main area, and IF DrawModelGeometryHook is what’s crashing them I imagine that would have to be related to some incorrect data passed from a model.
L1CKS
13
What @JiminyKroket said is absolutely correct. The crashes are probably caused by the “broken” assets you are streaming (hint: the tens of broken poly edge messages in the log). I personally fix these issues with an older version of ymap-ybn-mover (the newest version doesn’t seem to have this feature)