Resolved for 1.21 stable.

In T172082#2445064, @sileed wrote:

Still not working for me. Have used the same method since 1.0 was released. The account used does not own DayZ. I get everything except the 'mpmissions' folder

//update DayZ EXP Server
@ShutdownOnFailedCommand 1
@NoPromptForPassword 1
force_install_dir C:\DayZ\Servers\EXP\DayZServer
login <redacted>
app_update 1042420 validate
quit
Did the console in a steam client. Is shows "No active license found for appID 104420"

Thank you.
Unfortunately we do not have any more suggestions for now as we cannot produce the issue on our end. If you come across any other info which could help us produce the issue and be able to analyse it further, please let us know.

As mentioned in my previous comment, we are working on fixing the issue.
Spamming identical messages of "please fix this bug" will not speed up the process in any way.

Hello everyone.
We really thank you for the feedback. While the change does bring an improvement to the configs (which was the reason we did it in first place), it ultimately does not fix any issue, only breaks things. Remember, not all creators are active anymore and we always strive to ensure we affect those creations as little as possible.

pls fix this bug

Bitte Bi beheben sie diesen Fehler

Thank you for your time! Please note that I've updated all drivers and verified files thru steam

That's so weird, you changed stuff in the past what REALLY breaks a lot of mods, and now this 🥴

You guys asked for feedback and got feedback. I count 16 people who literally begged you to not revert the change.
For some reason, you decided to ignore the feedback you asked for.
Please consider changing it back.

Changed: Reverted clothing mid classes change as it was breaking vanilla clothing balancing mods

You have several major modders in here asking for it NOT to be reverted back...yet you did it anyway. Can we please just realize that the modding community is what is keeping this game thriving and perhaps we should listen to them more often? They want the change. They took it upon themselves to ready their mods for it. Leave it alone. Put it back in the change list for the patch notes.

Please BI fix this bug :(

Hello everyone.
We are aware of the problem and we are looking into a possible fix.

Please BI fix this bug

Please BI fix this bug :(

Che tu preferisca suonerie strumentali, citazioni di film o i successi più recenti, le suonerie gratis ti offrono infinite possibilità per creare un'esperienza audio unica. Non perdere l'opportunità di rendere il tuo telefono unico e riflettere la tua personalità con suonerie gratis che puoi scaricare e impostare in pochi semplici passaggi.

Very important.
Pls fix

I will add that the addition of many sighting options for crossbows will make the laser rangefinder more in demand and valuable for players.

Plz fix this bug, BI

@Geez DUPLICATE of T171745

Conducted repeated tests, which confirmed: the possibility of changing sighting at different distances (by pressing "PageUp" and "PageDown") for sights mounted on a crossbow is not provided. I propose to add for the crossbow the possibility of shooting at least at 10, 20, 30, 40, 50 and 60 meters: such values will be close to real hunting distances and will make the crossbow a truly convenient tool for hunting, including night hunting.

Hope that BI can fix this Bug fast :)

This is really urgent - please fix this bug.
Thank you, guys!

There doesn't seem to be any sensitivity settings other than activation threshold

Hey @Geez , I've just tried with activation threshold etc - there is no indication that a microphone is working or present. I've double checked that the correct mic is being used under the volume properties.

Please, BI, we need a fix for this, thanks!

Please BI, fix this bug!

BI we need this fixed ASAP!

Hi BI

Pls fix this Bug ,BI!!!

Please fix!

Please BI fix this bug :(

Hello HazzardezPlant.
This is caused by the modded content you have installed and in such case there is nothing we can do on our end.

Hello, the issue is most likely related to @RetroCollectibles mod and in such case there is nothing we can do as the mod creator has to fix the problem.

Hello andula.
Please make sure your video drivers are up to date and do not contain any corrupted dll files (clean install of video drivers would be advised).
If the issue persists upon doing so, please try to verify the game data through Steam.

Thank you akula692009.
We are aware of this problem which is on the Valve's side and they are working on fixing this.

In T171948#2445429, @Pirate_454 wrote:

@Geez @Nate_LapT

I downloaded experimental and don't seem to see any in-game mic settings I'm afraid.

Also I'm assuming the bug still exists, there is no indication that the mic is working through voice activation or push to talk.

I downloaded experimental and don't seem to see any in-game mic settings I'm afraid.

Resolved for 1.21 stable.

Resolved for stable 1.21.

@Geez I'll download experimental and update shortly.

DayZ 1.21.1.21.156165

If it helps, I have found the workaround for this seems to be to drop the plastic explosive and arm it, instead of placing it.

Doesn't exactly inspire confidence. I'm new to the game and the actions of this hacker have made me question if I want to continue.

has this always been too high off the map floor, or is Tisy getting updates..

oh nice. Missed the notes.

It happens to me as well, not always but sometimes (even on the latest experimental update).
@Geez: When it happens, I keep trying to arm the explosive multiple times (from different positions), usually I can arm the explosive this way but it may take up to 50 tries.

Still not working for me. Have used the same method since 1.0 was released. The account used does not own DayZ. I get everything except the 'mpmissions' folder

The devs already know this, they even mentioned it in the patchnotes.

Resolved in stable 1.21.

Resolved for stable 1.21.

Uploaded the dxdiag file but it's disappearing from the post after it finishes. Let me know if you received it.

Hello bakersmb.
Can you please upload your dxdiag file? also, are all your software drivers (especially video drivers) up to date?