Details
- Panel Type
- Query Panel
- Editable By
- theracersmark (theracersmark)
- Appears On
- theracersmark's Dashboard
Hello xAlbinoBuffalox.
It is possible the collission is blocking you from properly entering the code.
Regards,
Geez
Hello Scooby420.
There is nothing we can do on our end about the vehicle.
Regards,
Geez
Thank you for the report.
This has been resolved for 1.27.
Regards,
Geez
Hello dokerdoker99.
Can you please provide more detailed description of the boat sound issue, containing step by step reproduction steps and a video possibly? thank you!
This is the modern world, having a limit of 128 on anything, especially #defines, is almost archaic. Please add just one more byte so we can have 32K defines...
Resolved for 1.27
Thank you for the report.
This has been reported previously and is being worked on. Closing the ticket as it is a duplicate.
Regards,
Geez
In T186586#2709328, @Seentje wrote:Hi Geez,
Thanks for reply.
The computer has allready a clean install, so thats not the problem. You wrighting about the Nvidia app INSTEAD of Ge-force experience.
The Nvidia app was a free 'upgrade' from Ge-fore experience.In meanwhile I deleted Nvidia app and re-installed the Ge-fore experience again, and that looks it works fine (so far). Whats wrong with the Nvidia app?
Thank you
Resolved for 1.27 update.
Mods that declare multiple 'defines' can work individually without problems, although running them to the server simultaneously leads to a crash when the total limit is reached.
**Increase the limit, or remove the dependency.
Hello DimaSema.
Please use English language only when reporting into the feedback tracker. As for your issue:
The only .mdmp files present are from june and september, which we believe are not related to the current issue you have reported. If there are no recent mdmp files then there is nothing for us to analyse the issue by.
Regards,
Geez
Hello Vertxz.
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 trikesnos.
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 woytishoon.
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 robycutzzz.
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 joel21.
The crash dump points towards nvwgf2umx.dll which is a part of the nvidia drivers. Please try to do a clean install and possibly try an older version of the driver.
Regards,
Geez
Hello Twski.
The crash dump points towards nvwgf2umx.dll which is a part of the nvidia drivers. Please try to do a clean install and make sure to install the latest version of the driver.
Regards,
Geez
Hello Fusstter.
The crash dump points towards nvwgf2umx.dll which is a part of the nvidia drivers. Please try to do a clean install and make sure to install the latest version of the driver.
Regards,
Geez
Hello hawaiiancowboy.
Unfortunately there are no .mdmp files from the occurrence and therefore there is nothing for us to analyse the issue by. We can see through the RPT that you are using mods and these could be the cause, you could try running the vanilla version to see if the issue persists.
Regards,
Geez
Hello SenseiClay.
This seems like an issue with not enough memory being available. Please make sure nothing is consuming copious amounts of your RAM and you have enough allocated memory in the OS. You can also try to delete the dayz Documents folder and then verify the game data throguh Steam (make sure Steam cloud sync is disabled before doing so).
Regards,
Geez
+confirm, the server is crashing =/
Could you fix it pleeease?
Please fix this.
Using the PBO provided, I tested it again on both our dedicated machine and a local instance. The first log is from a local server and the second two are from our dedicated machine. All server launches with the mod on resulted in an immediate crash.
FIx
Please fix this for us. Please and thank you
Needs to be fixed ASAP.
Needs some Fixing.
Attention needed :)
Please fix this!
Please fix
Experienced this issue when my team was creating a new server recently, when adding Terje's new mods. We had this kind of immediate crash when the server launches and the terminal closes when displaying "Dedicated Host Created." We tested the server for several days last week, trying to resolve the issue, but without crash logs it was very difficult. Additionally, since we didn't know of the #defines issue at the time, the crashes would appear and behave inconsistently. We believed there to be certain mod incompatibilities on our server, since we had added new content, but removing and adding mods to the load order never pointed to a definitive compatibility.
Confirming this is an issue on 2 of my servers.
In T186575#2706623, @Leopard20 wrote:If you're using the perf branch, wait for the update or switch to stable.
Yes, the problem persists after disable Steam cloud sync and then delete all the contents of your DayZ Documents folder.
I remember bohemia bragged about cleaning game from hackers...apparently they don't check their own servers and as you can see no response on this topic
This is something we had to deal with alot (as server owners and players).
There are a few known servers that do inflate player count artificially and they end up at the top when searching for servers because they got the most players which is extremely unfair for legit servers that might actually bring or would bring value to the players.
Other people are also reporting this same problem. Not sure if it's Nividia's fault
It should work with setParticleParams, why, it doesnt?
It is just a variable stored on player that the function returns, I will get rid of
ok I see its due my modification, I expected it will suppress camera shake, but it just simply froze complete player body. Is this intended?
Thank you!!
Can someone delete this? I think I posted this on the wrong section.