1st Method

still relevant?

Thank you, we will investigate.

Thank you, we will look into this.

Thank you for your report DaniD11.
These are known issues that have been reported previously and are being worked on.
Regards,
Geez

Resolved for 1.2.0.95 and higher

Maybe it's the if (handle == 0) check that makes it fail? Could a valid (non-NULL) FindFileHandle be implicitly cast to a zero int by this comparison, thus making it fail?

The way I understood FindFileFlags is that it tells FindFile where to find files, not what type of thing (i.e. directory/file) it should find. I'm basing this off the code comments in ensystem.c, so not sure if those are correct w/ regards to intent (it also mentions .pak files which are not a thing in DayZ, probably a leftover from Arma. I haven't checked if FindFileMode.ARCHIVES does attempt to find files in PBOs).

Possibly but would that effect performance if the objects were still there just disabled?

Please do something

Same issue, impossible to play on official servers (have not tried other servers)

bump

bump

bump

S.O.G.: Prairie Fire is a part of the Creator DLC program and is not developed by Bohemia Interactive, that's why it has to be installed and enabled separately, https://arma3.com/dlc/creator#FAQ .

The way BI coded this for the AI is actually not that bad, but the use of the actual suppressor-attached gun sound that does not seem to depend on supersonic or subsonic ammo for the human players is pretty poor.

This request is half right and half wrong. Suppressors have only a few downsides, but they're notable due to the trade-offs that entail. They cause more overheating & jams, and they obviously add mass & extended length inertia to the gun's handling, but that's about it. They conversely act as muzzle brakes, flash hiders, and obviously lower the sound, in addition to some other benefits that aren't relevant to the game. They have very little effect on muzzle velocity.

I think this should be fixed in 1.26 too.
I actually never saw this issue during any of my testing so its a bit confusing.

GET RID OF IT

It has been over 3 months and issue is still the same.
So is this ever going to be fixed? Many servers do depend on logs.

This is still one of the biggest detrimental aspects of the game in Conflict. There is not a night where vote kicking is not blatantly weaponized. As of this writing i am on LA conflict Everon 22:00 PST and the entire night last been nothing but vote kicks and constant accusations and arguments. Recently I have seen some action at times where i will see longer bans and clearly something is happening but it isn't enough. The players that do this are relentless. They will continue until the server is completely disorganized or the game dies. Often changing gamer tags and gas lighting other players.
Having some extra support on this issue would be greatly appreciated, as it's something we the players are experiencing continuously.

@StevieB there's actually a mod for this by Bacon - THIRD PERSON VEHICLE ONLY by ceo_of_bacon

Not any more

The flickering has been back for the last few DayZ updates (currently on 1.25 and it still flickers).

July 27 2024 Happened to me on Xbox can only play a single server

I did the tests and my connection is apparently normal. But no luck with BattlEye yet.

That is good News! Thank you so much for the info @Geez :]

This has been improved a long time ago.

Added

Please assist

Good idea!

How it looks now(1.2.0.98):

the intent here is for squad leaders to have a short range radio to communicate with fire teams, and a long-range radio to communicate with platoon-level leaders. the ability to switch between two radios is obviously of little use in Conflict, but is very important for organized milsim PVE units. in ArmA 3, a different keybind is used to talk on each radio, which is simple and intuitive. Reforger has to work with console controllers, so unfortunately we seem to be stuck with a convoluted and clunky workaround involving multiple key presses and keybinds.

The control seems to sort of work even now, BUT you first need to use the push to talk button and have the short range radio already selected (which it is by default) and then change between short and long range radio, but that cannot be the intended function.

Yes, I see what's going on now, Thank you Veteran29
A user at BIS forums also mentioned this to me, and it fixed the map issue. But what's strange is, why did I have to load Prairie Fire in the DLC menu of the launcher to gain access to the assets, Maps, Object...ect? I've never had to do this with DLC's I've bought in the past - they just installed automatically as default DLCs. Either way, it's working now. Thank you.

Hello, is anyone aware of the progress in developing a solution to this problem? The 2nd month of summer is ending, and it’s still impossible to play... When the server is empty, it’s still tolerable, but standing in a line of 20 people to get kicked after 15 minutes is somehow insulting(