Type that into google and you'll get solutions
- Queries
- Arma 3 Activity
- All Stories
- Search
- Advanced Search
Arma 3 Activity
Nov 15 2021
Arma launcher only handles the !Workshop folder and links in there.
Steam handles its own folder.
Maybe we need to poke steam to actually delete stuff, don't know if we can do that
It will only fire where the AI is local, that should be fine right?
We will someday evaluate if and what we can port from Argo, there is no ETA for it.
You are loading a outdated ACE compat mod. Remove all your ace compats that are not official ones.
Alternatively, it would be nice to enable "AI remote control" where the player would be able to continue to use freelook, but AI would handle pathfinding and movement
that is already possible. I think switchCamera?
I know I've done this in the past, but more as accident than deliberately, I was able to transfer my camera into a AI's head, without the AI loosing control of its body.
Won't do.
AMD graphics driver bug, they fixed it already.
We are aware, don't need a FT ticket for this
Try verifying your game files via steam, or reinstalling the game.
If it still doesn't work, please upload your RPT log (see https://feedback.bistudio.com/w/ft_a3_howto/gamecrash/)
I have this reproduced, on v2.06 (current stable) and with both the -debug & -filePatching set and not set, so it doesn't seem to be related to either of those.
Fix coming to dev branch this week (I think there will be one this week) and profiling branch
No, too much work too little gain
did you increase steamProtocolMaxDataSize in your server.cfg? Does it solve it if you increase that?
Need logs and crashdump.
See https://feedback.bistudio.com/w/ft_a3_howto/gamecrash/
Please attach your RPT
Nov 14 2021
To the devs:
Doing this seems like a good solution to me:
Use the shortcuts[] property to show the keybinds next to commanding menu items, but also add the assigned keys from shortcutsAction to this array.
E.g. in RscMenuMove we have:
shortcuts[] = {2}; shortcutsAction = "CommandingMenu1";
if the user is using Numpad1 for "CommandingMenu1", you just add it next to the shortcuts[] array before creating the menu (in this example, shortcuts[] = {2, 79}; should be used before creating the menu).
I have tested this with custom commanding menus and it works perfectly fine.
Looks like Linux (x64) Dedicated server problem, as the mod is correctly recognized when I use the same mod in Windows x64 dedicated server.
Nov 13 2021
Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.
Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.
Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.
Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.
Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.
Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.
Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.
I've noticed that behaviour too, but never clued into the difference in player position before.
I'd always assumed it was bad mod interaction. Great insight!
Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.
Looks like OS problem. you installed GPS enabled phone and now it can’t work without it.
we are happy to see that you were able to resolve your issue, so we will close this ticket.
In the unfortunate event that (part of) the issue persists, please open a new ticket and include a link to this one.
Hello Nivek,
Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.
Hello Nivek,
Hello Nivek,
Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.
Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.
Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.
rev 148485
Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.
due to insufficient information and/or our team not being able to reproduce this issue, we will close this ticket.
If you have additional information and/or in the unfortunate event that (part of) the issue persists, please open a new ticket and include a link to this one.
Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.
Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.
Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.
Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.
Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.
Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.
Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.
Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.
Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.
Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.
We've picked up your issue and the fix has been implemented in the latest S.O.G. update. Thanks for helping us making the game better!
In the unfortunate event that (part of) the issue persists, please open a new ticket and include a link to this one.
Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.
Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.
Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.
We've picked up your issue and the fix has been implemented in the latest S.O.G. update. Thanks for helping us making the game better!
In the unfortunate event that (part of) the issue persists, please open a new ticket and include a link to this one.
Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.
Thank you for your feedback! It will now be reviewed by a specialist in our internal QA system.
Sorry, didn't mean to upset you with my question, was simply trying to find out if there is a bug that changes default settings one way or another without user involvement
Your question implies that the fault lies with the player for changing parameters freely given to them.
“Vehicles only” is not a default setting, why it is on during campaign?
Nov 12 2021
rev 148481
Alright, so I got back around to testing this and I see my mistake about assuming the EH handled the occupants as well. If I disable damage on the crew then shooting the RPG does nothing.
I believe this to be a duplicate of T75410, which has been resolved.
Nov 11 2021
Thank you for reporting the issue, I've passed it on to a programmer.
We will see what we can do.
should be fixed in rev.148471
Nov 10 2021
The mission includes some comments with testing instructions. I guess I'll write them out here as well....?
how do you test that it doesn’t work