Details
- Panel Type
- Query Panel
- Editable By
- ElbertMurphy (Elbert Murphy)
- Appears On
- ElbertMurphy's Dashboard
Fixed in Dev build 151781.
Thanks for your information. Keep posting.
Resolved for 1.26 update.
Thank you for your extensive report MilesDownshur.
I will forward this to the devs for consideration.
Regards,
Geez
Resolved for 1.26 update.
Thank you, we will investigate with BattlEye.
Regards,
Geez
Thank you Turnvater.
We are aware of this problem and it is scheduled for a fix.
Regards,
Geez
Complete triumph! Among the various papers on the subject, this is probably the most compelling. Outstanding information! With my significant knowledge in this industry, I completely understand the efforts you are doing. I'd like to offer my heartfelt gratitude for the amazing service you've provided.
play capybara clicker game
I just wanted to add: thank you and huge respect for all that you've done, for the ambient music, for upcomming winter map - this is more that a lot oh ppl could dream about. Still plese don't close your eyes on the problems that are left. I know no time, all are extremely busy, maybe not for now, but for the future at least note this for yourself. Dayz is a great game, but with long range sniping it will be much better (like it just became with the new ambient that a lot of folks were asking to add for a very long time)
He's on right now shooting through walls in my base
Failnot was able to fix this on the W.C.S servers. Rank is cancelled if someone attempts to load a vehicle while it is currently being unloaded. To my understanding the driver needs to get in and drive the vehicle to reset this. Long story short it's been fixed on our end. Still needs to be resolved in the base game.
@Geez the new map looks amazing! Hope it will also come with a new anti-cheat :3
OMFG now I understand why it takes so long to fix a bug.. Just click the delete user button with admin privileges....
If sand bags became destructible from an explosive blast from a rocket or explosive charge, that would be a good way to counter this without removing the ability to build around structures.
someone made this great mod to fix this issue (thanks to cyborgmatt for linking me): https://reforger.armaplatform.com/workshop/614F73C7E71E1480-Allrankslockable
There are reports that this can also happen when the unit does a gesture partway through a reload. (See: Arma Discord > arma3_feedback_tracker)
In T180461#2603092, @Gramps wrote:Any update on this?
Server absolutely ubearable again right now. My car is destroyed
Hello trunkmonkey98695.
Has an error message popped up? Were you able to save the report and if so, can you upload the generated archive here?
In T126046#2602464, @NikkoJT wrote:I think you need to read a bit more carefully.
KK added a revision number (i.e. the change number for the problem being fixed) and changed the task status to Feedback, as in "waiting for feedback on whether the fix worked".
Hello Mccc2.
Please include the following information:
Hello again.
Can you also upload the ArmaReforgerSteam_2024-05-05_23-30-42.mdmp file please?
@Geez I’m having this same issue, along with massive stuttering.
In T180574#2602736, @Kurbstomp4 wrote:I have encountered other problems with bases not being capturable when they should be or not being able to spawn in them despite having antenna and supplies. I think these problems may all be related. Trying to figure out how to replicate the problem.
Any update on this? Ive spent hours and weeks trying to figure this out...
I've also posted a few times in the discord about it and never get an answer.
Every time I try to remove the Request Vehicle action it gets auto added back to the prefab, canceling out the old method of spawning vehicles and it's soooo frustrating!!!
Please fix the lag switch
We need a fix ASAP
I tested addMagazineCargo, addItemCargo and addMagazineAmmoCargo, all are fixed. Tyvm!
next dev/prof
The submunition being spawned multiple times is actually normal.
Every shot has a local-only copy on every player. But they should be flagged as being local and not cause effects like that.
Works for me
getAttackTarget isn't well defined.
So it returning the "target the unit is told to attack" seems correct.
We're switching from "the target that was last shot at" to "the target we are going to shoot at". I think that fits.