FIxed in Dev build 151757.

We suggest to try disabling one mod at once to try to find the one that is faulty.

in this case, how can I find the cause of the server crashes? they weren't there, then they appeared. Perhaps there are some tools or ways to identify the cause?

¨Hello GluttenFreeVapes.
Is this still an issue at the moment?

Hello! I attached a video. Is this the result of a change in the collision of trees and will they remain so in the future?

https://community.bistudio.com/wiki/createSoundSourceLocal

Hello everyone.
Currently we do not plan to provide the unbinarized models. This might possibly change in the future.

This would be awesome

It has been almost 5 months since the ticket has been made. Asking for an update close to half of year is not unreasonable.
I am trying to open a discussion between DayZ devs and modders.

I am very pesimistic with this ticket. It will open pandora's box if will be not refused. And honestly making pressure for answer is not good way in my opinion.

Sure, but they already do that with proper cheats bypassing SQF and creating own shot messages. Is it really *that* much worse than creating shots with createVehicle and createVehicleLocal? You can already do a lot of mess with {createVehicleLocal ["HelicopterExploBig", getPos player, [], 0, ""]} forEach allPlayers and its not even logged in createvehicle.log. (Censor this if needed)

Hello Helkhiana.
Unfortunately no new information I can share.

Everything have limits, for example 8bit computers can have 65536 bytes of memory. RV engine have limits you met with that model/skeleton. I am not dayz developer, so i dont know which limits you reach. Its life, nothing is unlimited.

Hello Romanof7.
Can you please try the following?

@Hunterz What do you mean by saying reached limits? Which exactly limits? And no, one of them hasn't reached any limits and works fine. That is what I am talking about. Two pretty similar models and the first works, but the second doesn't

Thank you, we will investigate with BattlEye.
Regards,
Geez

Ref https://feedback.bistudio.com/T180805
Chains of skippable addons are not supported

It is what I mentioned here
https://feedback.bistudio.com/T172179#2447268

Those models just reached limits of old RV engine.

It would be so nice if people from BI would say "Guys do not do it this way, make sure you've clicked on that button and check if you ... bla-bla-bla" :)

@Hunterz as I wrote above definitely the issue persists because of something, and I agree that it can be related to RV implementation. But for me as a developer, some aspects are still unclear. Why do those two models have different behaviors, what exactly causes it, and how can I avoid them? I mean understanding the problem is half the way to solving it

This seems it would just make it easier for cheaters to post bullets impersonating other players.

Won't do.

Please follow https://feedback.bistudio.com/w/ft_a3_howto/gamecrash/

Same crash, fixed in todays profiling branch update

Just read something about history of dayz and arma. RV is name Real Virtuality engine which was used in arma2, arma3 and his artifacts are still in dayz. Dayz is mix of both engines. Issue you have is coming from old RV engine and his limitations. Thats why are all fine in anim editor, which use enfusion only.

I just googled that RV is old Real Virtuality Bohemia's engine, but it still doesn't explain anything) I understand if something works and something does not there is some difference between the two. But I can't find it and want to know what exactly we have to do to avoid this issue

Hi @Hunterz I am not sure what exactly RV means. Also about any limitations, what exactly can cause those limits? I have 2 very similar models (the first is broken, the second is fine) they use the same skeleton, same xob, same anims, same selections, same bones, their names, and their amounts. The difference between them is the 3D mesh and vertex weights. The broken one even has fewer polygons and vertices. For me, it doesn't look like I reached any limitations but the issue still persists

DayZ is mix of old RV engine and new Enfusion engine. This is problem of artifacts of old RV and his limitations.

I have posted my concerns about this as well and feel it still needs refinement. One issue is that FIA counts as enemies, this in theory is fine, the issue is that FIA can often get stuck in odd positions. A good example is the St. Pierre Coastal point. FIA can get stuck in the water or under the map and this prevents the point from being able to be built on.
"Enemy in the area" does work both ways, one tactic that the defenders use now is to often check build privilege as a sort of radar to know if someone is hiding or nearby. I really don't think this mechanic is all that much better than the previous solutions and both present their own issues.

Hello @Geez Sorry for chasing this. It would be nice to get an update on where we are with this request.

For official servers*

Would also like to bump this, and add in that players are still building ovens on the middle of ladders which makes it impossible for players to climb past it, and therefore making apartment bases impossible to raid. I imagine removing the physical hitbox would fix both these issues.

UI to texture rendering failed. The rendertarget didn't exist. I don't know how that happened I never saw that before. I added a safety check, won't happen again after tomorrows profiling branch

Resolved internaly for the stable version.
Regards,
Geez

Hello intenso2891.
These crashes are related to the modded content you are running. Unfortunately there is no other information we can decipher from the dumps.
Regards,
Geez

Thank you Krypton.
This seems like it is related to one of the mods you are running.
Regards,
Geez

Hello ignorshik.
The crash dump points towards nvppex.dll file, indicating a problem with your GPU drivers. Please do a clean installation and check your OS for any corrupted installations/files. Also make sure your system is up to date.
Disabling HWAA in the game might resolve the issue but the root cause is somewhere on your system.
There is also a chance that if you are running Nvidia app instead of Ge-force experience that that is the cause of the problem.
Regards,
Geez

Hello micro310.
The crash dump points towards nvppex.dll file, indicating a problem with your GPU drivers. Please do a clean installation and check your OS for any corrupted installations/files. Also make sure your system is up to date.
Disabling HWAA in the game might resolve the issue but the root cause is somewhere on your system.
There is also a chance that if you are running Nvidia app instead of Ge-force experience that that is the cause of the problem.
Regards,
Geez

Hello belbich.
Can you please try the following?

Hello tarkules.
This will be rebalanced for the 1.26 update.
Regards,
Geez

Hello EyeAgent.
We have tested this thoroughly on our end but we were unable to reproduce the issue.
Regards,
Geez

Hello Traqu.
The issue will be resolved for the 1.26 update of the game.
Regards,
Geez

In T180795#2599475, @Damca wrote:

Sorry to bother you again, but if I may ask, what do you mean by investigating with BattlEye exactly? Every time there's a cheater reported you apparently do so (which is a good thing of course), but what is it exactly that you do? Write an email to BattlEye? Check the logs? And what does happen after that, does the cheater just simply get banned or will the cheating software itself get flagged (and all it's users banned globally)? Thanks in advance

Sorry to bother you again, but if I may ask, what do you mean by investigating with BattlEye exactly? Every time there's a cheater reported you apparently do so (which is a good thing of course), but what is it exactly that you do? Write an email to BattlEye? Check the logs? And what does happen after that, does the cheater just simply get banned or will the cheating software itself get flagged (and all it's users banned globally)? Thanks in advance

Thank you XcuzMyFrench.
This is a known error and it is scheduled for a fix.
Regards,
Geez