I still cannot play certain servers because of the PBO Error
- Queries
- Arma 3 Activity
- All Stories
- Search
- Advanced Search
Arma 3 Activity
Aug 8 2019
Aug 7 2019
Hi,
it's caused by new Steam update. https://twitter.com/Arma3official/status/1159116450860347392
As requested, here's the video:
https://www.youtube.com/watch?v=lHszHlJnkwU&feature=youtu.be
Hi,
I am able to connect and play on roleplay.co.uk server without issues. Do you have this issue in latest version of Arma (1.94.145977)?
It seems that you have corrupted one pbo file.
Hi,
could you please try?
- Delete a3.pbo file and 3den.pbo file from ....\steamapps\common\Arma 3\Addons\
- Verify game data through Steam https://support.steampowered.com/kb_article.php?ref=2037-QEUH-3335 , it should be download these files again
- Try host server again
Hi,
thanks for the report. We will look on it.
Cool. thanks for confirmation that last fix has solved your issues with arsenal loadouts.
@Astaroth It is working again. Both saving and loading works as before so our community is happy again.
Hi,
it seems be ok on my pc. Could you please make video with this issue and add here? Thank you.
Hi i try many time use the post to fix it but i just don't seem to work
I would suggest the launcher query the server mod list on its own rather than the steam APIs, querying only once the "mods" button is pressed.
Aug 6 2019
Hi,
thx for the report. We will look on it.
I was helping Flix on Discord, we tried the usual culprits like ensuring drivers are up to date, verifying game integrity, etc.
Hi,
crashdump wasn't create in your case so I am not able to find what was wrong. Could you please attach another logs if issue happens again?
Hi,
servers are not updated to latest version so you can't connect with client with newer data. We are working on update of our Official servers now. I am sorry for troubles.
Hi,
your logs are empty becuase you use nologs parameter. Could you please attach new logs without nologs parameter if you have this issue again? Thanks
Hi,
your logs are without crashdumps. It seems that crashdumps weren't create during crash. I am not able to find what is wrong without crashdumps because this error is very generic. More info is on this page:
https://community.bistudio.com/wiki/Arma_3_Unusual_process_exit#0xC0000005_-_ACCESS_VIOLATION
Same Here, all multiplayer servers...
Same issue here I dont think is fixable any more the, try everything that the support have given. any one have a way to fix it?
Aug 5 2019
Thanks it working with greyed out loadouts again
Hi,
it should be fixed in today's update of RC. Arsenal should load loadouts which are greyed out just without missing things. Could you please try if it solves your issues? I am sorry for troubles.
RC access code is: Arma3Hotfix194RC
https://community.bistudio.com/wiki/Arma_3_Steam_Branches
Aug 4 2019
This is the single biggest hassle for server managers that both use and don't use the steam workshop.
Aug 3 2019
In T127954#1922700, @Manzarek wrote:you are probably using some mods
you are probably using some mods
up ?
@kajschak that's what we did with the ACE Arsenal. We are going to run a VANILLA server though that will still support usage of TFAR so this needs to be fixed, or reverted to the old system for that to work. We also want to use the 3CB uniforms etc. so we need to be able to use BI Arsenal to load our loadouts.
Aug 2 2019
You also get them with certain faces by RHS. This issue is related to a certain radio item. Even when you safe newly made loadout, the issue appears in the current release. You had to remove the radio item manually in the exported loadouts from the 192 Release Version.
We have quite a few custom loadouts made by all our members, so having to re-create them is something we really don't feel like doing. Instead, would it be possible to make it so that for now loadouts with missing items can be loaded again? The mod creators than have time to fix the issues with their mods.
The fix is working. But it is still not allowing me to load loadouts that miss an item. Previously the arsenal would ignore the item and leave it blank. Thanks for the fix! Looking forward for it to be released.
Hi,
it should be fixed in latest devbranch and in RC build on Steam. RC access code is: Arma3Hotfix194RC
https://community.bistudio.com/wiki/Arma_3_Steam_Branches
Thanks. I will check it later today.
Hi,
it should be fixed in latest devbranch and in RC build on Steam. RC access code is: Arma3Hotfix194RC
https://community.bistudio.com/wiki/Arma_3_Steam_Branches
Hi,
it should be fixed in latest devbranch and in RC build on Steam. RC access code is: Arma3Hotfix194RC
https://community.bistudio.com/wiki/Arma_3_Steam_Branches
Hi,
it should be fixed in latest devbranch and in RC build on Steam. RC access code is: Arma3Hotfix194RC
https://community.bistudio.com/wiki/Arma_3_Steam_Branches
Sorry, meant to add that it was opening the MAP screen that instigated the crash.
Aug 1 2019
This is a problem I experience as well. I've found that if you remote control a unit then release it, it will have reloaded the zeus interface and this problem stops until you do the search bug again.
I am hoping that what you mean, is the selection for OPFOR/BLUFOR/indep disappears.
I've tested this with other objects as well. Putting down pier sections (Land_Pier_F) do the same thing. When aircraft taxi over the seam, they take damage. They also take unrealistic damage, like anti-torque failure or engine damage.
Has anything come of this? I've been trying to create a place able airfield using Land_AirstripPlatform_01_F. It doesn't seam to matter how close I get them, they still cause damage to aircraft that taxi or land on them.
Same exact problem here i did everything but nothing fixed it reinstalled the game and that didnt fix it i really dont know what to do anymore.
Jul 31 2019
I also am experiencing the same issue on the second mission. Logs attached.
Windows 10 however.
I think it has something to do with our configuration files. I'm crediting, rightly or wrongly, my deleting Arma3 including Arma 3 and Arma3 profiles in my documents. Then down loading arma3 and starting over. Anyway my Virtual Arsenal is working fine now.