Thank you, we are aware of this problem and it is being looked into.
Regards,
Geez

Thank you for the report MrDonaldDuck.
This has been reported previously and we are working on it.
Regards,
Geez

Haven't built one of these in forever,
Players on my server are complaining about the stone oven despawning.
There is no types for this asset to configure the persistence.

GG

In T180098#2652522, @Steniboy wrote:

Hi @Geez

I was testing bit on 1.26 Exp and I saw that the restock timer in types.xml has been fixed. It seems to be working again.

However the parameters in globals.xml that I pointed above are still not working. Just wanted to let you know.

Mainly talking about these 2:
<var name="RespawnLimit"
<var name="RespawnTypes"

Cheers,
Sten

Thanks for your time.

Thank you for the clarification. This is normal behaviour when zooming in. Unfortunately not much we can do about this at the moment.

This is the latest one I could generate, the mdmp did not pop up with this

Sure thing, here are both the video and the dxdiag file.

AMD is also aware of this but no fix yet...

In T175252#2557604, @Geez wrote:

In T175252#2557259, @Jordi435 wrote:

In T175252#2522674, @Geez wrote:

Resolved for the 1.24 update.

@Geez

I tested this again and unfortunately it's not (completely) fixed:

>> VIDEO <<

As you can see in my video the color of the skirt is now fixed in the inventory screen (this wasn't the case before) but unfortunately not in first or third person view...

Thank you, forwarded to the QA

@Geez We have made a new instance, which is where this file was pulled from, which is a copy of the previous server. Do you think if we deleted the prior instance and let the new one run, you think that may help? This issue has been a pain in the ass. The server "nukes" at random times, its never consistent. Could run for 5 min before crash, or 5 hours. It has started right after 1.25.xxxxxx. Any help is appreciated, If you need more of the mdmps, and rpts, I have plenty

Hello oPoz.
Could you possibly record a video of the issue? Also can you upload your dxdiag file?

Thank you for the report.
We will investigate with BattlEye.
Regards,
Geez

Thank you for the report.
We will investigate with BattlEye.
Regards,
Geez

Hello, I am reaching out about some issues that have started happening
within the last few weeks that are affecting a ton of servers, quite
literally. There are communities shutting down due to this issue. We
run on a dedicated server, on our end we run OHV cloud, I personally
use GTX. Anyway what is happening is that the entire Dayz servers are
shutting down and closing shop due to this issue. Dayz is completely
closing for no reason. It does generate any crash logs below is the
entire log unfortunately I did not translate it because I am afraid it
will change the file and become useless. . We have traced this issue
back to one of your patch notes..., Any help would be much
appreciated, Below will be a translation into Czech which I do believe
you guys speak. The issue started during the update 1.25.

@LydHosting Это происходит рандомно во время работы сервера

The current DayZ web application is implemented as a Single Page Application (SPA), which primarily relies on client-side rendering. Due to this setup, dynamically generating OG (Open Graph) meta fields in real-time isn't feasible. For dynamic OG meta field generation, the application would need to run in server-side rendering mode.

Resolved for 1.26 stable.

Resolved for 1.26 stable.

In T183640#2653115, @Huntbach wrote:

In T183640#2652726, @Martinucho5000 wrote:

Buddy, u need to delete the dayz folder in documents. If u can't need to go to the task manager, and close onedrive. Then u gonna try again to erase that folder. And the next is try to open the game. This was a solution for me (sorry if i typed something wrong, im a spanish user) greetings from Uruguay.

Thanks for the reply but unfortunately that did not work for me.

In T183640#2652726, @Martinucho5000 wrote:

Buddy, u need to delete the dayz folder in documents. If u can't need to go to the task manager, and close onedrive. Then u gonna try again to erase that folder. And the next is try to open the game. This was a solution for me (sorry if i typed something wrong, im a spanish user) greetings from Uruguay.

bug still exists in latest experimental 1.26.158551

I forgot to mention that the cylinder for the magnum is also not re-texturable, the rest of the gun does work.

Maybe this year?

Confirmed.

Maybe worry more about the fact that cars and trucks in DayZ only seem to have 1 spark or glow plug, Or the fact that there's only one type of fuel (gasoline) around and trucks and humvees magically seem to be running fine on it...

That doesn't make a lot of sense. You think people who abandon their car would drain out the oil first?

In T158378#2652858, @freerider3434 wrote:

@Geez I unfortunately have to report, that the bug is still present as of experimental game version 1.26.158551, so I'm asking you to please reopen this ticket. Steps to reproduce are as follows:

1. Login to the server and equip a gun with attached magazine that you have at least another magazine for in your inventory.
2. Hold R and note that the reload does not occurr and the hotbar does it's 'flashing' thing.
3. Workaround I: Attempt to drag a magazine from your inventory onto the gun, which does reload and occassionally 'uncurses' the mag that was in the gun upon logging in, meaning cycling through mags via holding R is possible afterwards.
4. Workaround II: Drag the magazine out of your gun into the vicinity and click 'attach', while looking at the magazine on the ground with your gun in your hands. Has always worked 100% and still does.
   
   Best regards

@Geez I unfortunately have to report, that the bug is still present as of experimental game version 1.26.158551, so I'm asking you to please reopen this ticket. Steps to reproduce are as follows:

@Geez, can you forward this to the responsible team?

@XiKKA Hello. I've been able to work on a number of servers with this error. I've come to the conclusion that the latest update is not at fault and that the error itself is irrelevant, as it is systematically caused by a mod that crashes the server. However, it's difficult to identify the mod with this error alone: I'd advise you to ignore this error and look among your mods for what might be causing the crash. If it happens systematically during startup, it should be fairly easy to find. Otherwise, you'll need to be patient and persistent.

holding the item isn't correct

Hello everyone.
These messages can appear if an item does not have many spawnpoints in the world and Central Economy is having a hard time finding them, or the item does not have any spawnpoints available at all.

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

Здравствуйте, имею две таких проблемы после переустановки OmegaManager одна проблема ушла и появилась новая.

Дання проблема ушла после переустановки OmegaManager, список модификаций не менялся.
Crash-Log #1:
Program: C:\Dayz-Server\OmegaManager\servers\0\DayZServer_x64.exe
Reason: Access violation. Illegal read by 0x7ff68c213c9f at 0xffffffffffffffff

Buddy, u need to delete the dayz folder in documents. If u can't need to go to the task manager, and close onedrive. Then u gonna try again to erase that folder. And the next is try to open the game. This was a solution for me (sorry if i typed something wrong, im a spanish user) greetings from Uruguay.

Also, This is on the normal Stable DayZ Launcher and weirdly I can still use the Experimental Launcher but not the Stable one.

KNOWN ISSUES

I was testing bit on 1.26 Exp and I saw that the restock timer in types.xml has been fixed. It seems to be working again.

I wish there was more lore behind the bombings, maybe a radio broadcast over the PA system before a strike "Evacuate the area Immediately! Protocol Z has been initiated"

In T183624#2652486, @Traqu wrote:

DMR is DEloot

Not in 1.26

DMR is DEloot

Is this not happening during the first launch after a wipe?
And after is, seldomly

"It was the biggest stability update up to that point. There were like 4 pages of fixes and good changes. but for some reason people got stuck on "masks"." The "masks" is just because the only new content were masks, but it was forced and advetised like it was 2nd Dambog bunker on chernarus. It was a good update in tearms of bug fixing in theory, but realization was not the best. Radio "known" frequency is a good idea, it'll make radio used for something finally. Alarm over the speakers in every place where it falls - this is zombie apocalypse, don't think they have some kind of sensors that can do that automatically, plus how long the battary would last for that thing? As far as I know such systems work along with humans. So either them all be controlled remotely from some place (which should be 2nd bunker somwhere on Livonia), or they just stopped working long time ago as all the operators are looking for some fresh brain now. Besides they already have visual alarm - red light. I don't even know why this ticket was opened. Livonia is too big, lets remore part of the map :)

almost six years and no answer from bohemia! thanks!!!!!

Hello Jordi435.
This was an intentional change by the devs. Vehicles are no longer supposed to act as a heat source.

okay I'll give it a try

In T179537#2652026, @MilesDownshur wrote:

Are you nuts people? "The whole "toxic" update was the worst one ever." LOL, did you forget about 1.14 Mime masks??? You guys act like you have billions of $$$, tried everything in this life and bored as heck, don't know what to do so you decide "let's remove this". Relax, dynamic toxic zones are fine, they add spice when you loot some location and then you have to quick delta out of there.

I like the dynamic gas zones. But there should be a siren sound in the spot where it's landing IMO like seconds prior to impact, through PA system speakers. That would be super immersive imo.

In T182498#2647909, @Geez wrote:

In T182498#2647621, @intenso2891 wrote:

@

In T182498#2638413, @Geez wrote:

We would also suggest to not rename the server executable

https://feedback.bistudio.com/T182498
can you please check and help me? please

Currently this is awaiting a check from the devs, however, due to the current priorities it might take more time as the devs need to focus on the prioritised issues.

AMD is also aware of this but no fix yet...