Could you please verify that you have
Few other tips
I was not able to experience any issues on Apple MB110. What type of KB do you have?
It is not available or is it not working when bound to the "Optics Mode" action?
Could you please attach a screenshot of your settings? (similar to https://www.dropbox.com/s/t1mtd76oif6imst/Arma3Int_DX11%202014-07-07%2018-07-37-46.png )
I've reset controls config to default - nothing.
My keyboard model is 'Apple MB110 Wired Keyboard'.
Maybe it's not a keyboard issue?
It is not working when bound to the "Optics Mode" action.
Screen:
https://www.dropbox.com/s/w98koxdetoql1pr/arma3%202014-07-07%2023-09-27-852.png
Video:
http://www.youtube.com/watch?v=EgIJp52ylzY&feature=youtu.be
In the binding menu you should see a column on the right side of the window with available combinations. Look for Left Ctrl+Sec. Mouse Btn. and drag it over to the keys already assigned to the action.
I did. It doesn't work for me.
This is an issue with the ARCO optic attachment. See here:
Closing according to ViperMaul
Aah thanks AD2001 Yes I was using CBA...
Tested without and they didn't explode :-)
BUT some AI still hit the ground too hard and die on impact. even with the wind set to zero :-s
Yeah just tested it with giving AI a way point and they just slam into the ground at full speed; killing themselves.
Are you using CBA? It used to cause this bug.
I tried reproducing this but couldn't.
I opened the editor on Altis, created a paratrooper as the player, elevation of 600, and also made the wind and gust speed North heading full. Starting the preview I dive forward to gain speed, open the parachute at 200m, reaching speeds of 84km/h when chute is opened fully and still travelling forward. Upon hitting the ground is instant death, but no explosion.
This was done over Almyra.
I have re-worded the issue removing the explosion part (caused by @CBA mod)
They are simply dying on impact.
Thanks to AD2001 for the info :-)
There are pre-configured things like Checkpoints and FOB's. The ability to create and save small structures like these would be a great improvement. Things like better checkpoints, generic FOB's, depots, and mission assets could then be pre-configured beforehand and deployed quickly during setup, vastly improving the pre-preparation mission masters can put towards their zues missions.
-maxmem is automatically limited to what the game can handle.
If supported maxmem is 2047 you could even put 9001 but the game would reset that back to 2047.
Anyway i haven't followed dev log in the last few days but they said they removed it last weekend so if it doesn't work they haven't added it yet.
They said they're still working on it in the dev branch log yesterday or a couple days ago. It's gonna take some more time i guess.
I don't have installed the test branch at the moment, so I ask you, have you tried the startparameter "-maxMem=3072"? If it is not working maybe you could open a ticket with the request that this patch is deactivated until the problem is resolved, but can be activated with the "-maxMem" parameter.
Closing as duplicate.
Duplicate of #96, and #12578
mousewheel should be fixes first, think much more people uses mice than touchpads
AD2001 I use ' [ ' and ' ] ' keys!
But some of us use touchpad :(
Agree to your suggestion. It sucks hard not beeing able to adjust zoom of scopes and other stuff with the wheel
How do you use the scroll menu on a touchpad?
I really want stance adjustment on the scroll wheel, current stance keybinding is cumbersome and not effecient (the new sub-stances).
Fixed for a while.
Mass closing tickets marked as resolved more than 1 month ago.
If the issue is in fact not resolved, please create a new ticket referencing this one and ask for it to be re-opened.
Thank you for the info! We sent the dumps to analysing.
Hello,
would it be possible to upload three more crashdumps?
Thank you very much!
Sorry, but i can´t. Played the mission 10 times and it doesn´t crash anymore.
Tested on both, the "dev_branch" and the "rc"
Mass closing tickets marked as resolved more than 1 month ago.
If the issue is in fact not resolved, please create a new ticket referencing this one and ask for it to be re-opened.
Not all uniforms have a weapon holder, but the person always holds a pistol in his hands ;)
Mass closing tickets marked as resolved more than 1 month ago.
If the issue is in fact not resolved, please create a new ticket referencing this one and ask for it to be re-opened.
Double-click on the item when selecting it.
Automatic switch would be too annoying and wouldn't work when the time is stopped.
Hello,
thank you for uploading the ticket. Your crashdumps were sent to analysis, we'll let you know, thank you very much.
Fixed.
Please close the ticket, because the problem seems to be resolved (Why can't I close my own ticket?).
Duplicates fixed and the pool of uniforms made consistent in both editor and Virtual arsenal.
Rgr - will try and again without mods/params - haven't had a crash for a couple of days but will try to replicate.
Hello,
would it be possible to upload dumps without any mods activated and without parameters as well?
Thank you.
As author said, Thanks a lot for intel!
After the latest dev-branch update to 1.25.125903 I can still see the entries in the VR Arsenal.
I attached pictures of all the entries.
@Moricky/Pettka
I found out, what the problem is.
I trusted Steam, for downloading all updates the correct way. I verified the integrity of game cache and Steam found several false files (19). After downloading 335 MB of data through Steam I started the game again.
Now I cannot see these entries anymore. It seems, that the thread can be closed.
Sorry guys and I am pretty embarrassed :(
I'm currently not seeing them, but that's not to say that there are a lot of missing/confusing entries in the gear config still.
Just as an interesting side note, you should look up the wiki entry for Kabeiroi or Cabeiri, a remenant of 'what could have been'? ;)