In T192202#2817264, @Surreal419 wrote:

Turn "Environment Quality" to low for a workaround

It depends on the height of the viewing angle.

In T192160#2813117, @kasparhzr wrote:

This is kinda known bug as far as i can tell. So there is a workaround for now - try to hold ALT in case your view movement is locked.

In T192018#2810413, @Ciberdead wrote:

Its not realistic but fun. ^^

Being able to troll a bit with the enemy when you are downed is funny.

if its unwanted, add a server setting to enable/disable it.

In T191984#2810031, @Geez wrote:

Hello Ponezun.
This is not a bug. According to the team this working as designed.
Regards,
Geez

In T187674#2805782, @Geez wrote:

Hello Ponezun.
This should be adjustable with user settings such as Aim sensitivity curve. These are can be set up separately for mouse, gamepad and gyro.
Default is 100% which means linear reduction with magnification.
Is it possible you have set it to zero? As that would disable the input scaling with FOV.

I'm pretty sure it's 100%. In some version of 1.2-1.3 this problem existed. In the current version the aiming sensitivity is correctly reduced with magnification but it's still too high for me, in some mods there are some sights that are fixed and some that change with magnification I don't know if it's a mod problem or yours, shouldn't this setting be mandatory for all sights? I also think that the default sensitivity setting is not enough, shouldn't you separate the sensitivity settings for mechanical and magnification scopes (or PIP scopes for that matter)? Also it should be possible to set the scale of the aimer's magnification change yourself, for me it's too fast sensitivity at high magnification (4x+) and then I'll reduce the sensitivity at high magnification!

We need a quick removal of debris, either by blasting with C4 or removing it with some tools

Really well thought out and good advice, I totally agree!

In T191395#2799691, @Geez wrote:

According to the dev team, it is normal behavior because the character is turning his head with the free camera.

In T191395#2799622, @Geez wrote:

Hello Ponezun.
Our testing did not reveal any problems and the current state is intended.
Regards,
Geez

In T189237#2799229, @byNautiic wrote:

Well cars normally use vacuum from the engine running, to power the brakes (brake servo/booster)
So that is probably intended

In T189237#2798853, @lwing wrote:

Additional related bug found after further testing:

vehicles lose almost all braking power if engine is turned off, either by purposefully turning it off or by running out of fuel.

1. spawn veh at top of hill, give it 1% fuel
2. drive it down the hill
3. When fuel empties (or when you turn off the engine manually) note that braking does not work, regardless of if you shift to N or drive gears

I'm more inclined to think it's a bug, as there's nothing wrong with the function of the brake itself you just need more power to use it

The same thing happens with grenades as long as they are close enough to still kill the occupants of the vehicle, and it looks like the in-game blast damage doesn't have an additional attenuation with armor

In T190827#2787832, @Geez wrote:

Hello Ponezun.
Please always include the following when creating the ticket:
Game Version number:
Modded?: (Yes/No)
If modded, please list the mods:
Issue Description:
reproduction steps

In T190760#2787734, @PR9INICHEK wrote:

In T190760#2787677, @Ponezun wrote:

I think it would be better if both the carrier repair point and the armory provided corresponding ammo supplies, and it makes sense that the armory would provide all ammo supplies, and it makes sense that the carrier repair point would only provide ammo supplies for all carriers. It's always better to have more options, isn't it?

For now, I still suggest simplifying the contents of armory so that players don't get confused in it.

I think it would be better if both the carrier repair point and the armory provided corresponding ammo supplies, and it makes sense that the armory would provide all ammo supplies, and it makes sense that the carrier repair point would only provide ammo supplies for all carriers. It's always better to have more options, isn't it?

In T189729#2766196, @Geez wrote:

Hello Ponezun.
Please always include the following information when creating the ticket:

Game Version number:
Modded?: (Yes/No)
If modded, please list the mods:

Issue Description:
Repro steps

In T189394#2760042, @Geez wrote:

Hello Ponezun.
Please always include the following in the ticket:

Game Version number:
Modded?: (Yes/No)
If modded, please list the mods:

Issue Description:

reproduction steps

The speed of maneuvering while aiming should be reduced while the left and right movements should not be as sensitive.

The current weapon restrictions are just too harsh, it would be better if they were adjusted downward by 1 or 2 levels, if possible I would like to introduce a troop system to limit the available weaponry if possible it would be better if it was an optional for the server to freely choose whether to turn it on or not

In T187206#2736937, @Geez wrote:

Thank you.
According to the dev team, this is as designed due to the new control change from version 1.2.1
You can find more info here: https://reforger.armaplatform.com/news/new-controls-explained

Regards,
Geez

When you're in the car, the map compass shows the direction you were facing moments before you got in the car.
I've given feedback before.
T183143

I think this is a serious problem that needs to be fixed badly.Honestly I think the whole networking code of the game sucks and needs to be fixed properly

Carrier driving backtracking and flashing issues as well as transients caused by being out of sync near obstacles，I honestly would have thought that BI was aware of these issues, but apparently not

In T187513#2724186, @Wetzer wrote:

In T187513#2723849, @Yamachinu wrote:

This has been posted on before, but it's one of those small QoL issues that would be nice to not have to think about. if I'm quickly trying to take mags or rearm off a body/vehicle i suddenly pick up extra things i don't want because the item position in the inventory moves on it's own while i am looting. Why?

In my eyes this is not only a "small QoL issue". This is a missing essential functionality of the engine itself. The presentation of items in the inventory has to be some kind of sorted to prevent it from "jumping".
And it is an inventory thing: The player interacts every session with it and in looting situations it has to be happen quickly and the player shouldn't have to fight against the interface then.

In T187206#2722155, @Geez wrote:

In T187206#2721874, @Ponezun wrote:

In T187206#2721785, @Geez wrote:

Hello Ponezun.
Please try to go to C:\Users\...\Documents\My Games\ArmaReforger\profile\.save\app..._user...\settings and delete InputUserSettings.conf.
We have tested this on our end and we were unable to reproduce the issue.

I found the problem, you can't raise or lower your stance while aiming if you switch the aiming settings to the old keystrokes which is Ctrl+Right Mouse Button.
By the way did you guys test the bug that you can only switch scopes when you're aiming?
Honestly the new version has too many button bugs

Can you please specify in more detail? Possibly provide step by step what we have to do in order to produce the issue?

Changed the toggle scope key to ctrl+right mouse button (this was the old version of the key setup),
ok now you can't raise or lower your stance while aiming!

In T187206#2721785, @Geez wrote:

Hello Ponezun.
Please try to go to C:\Users\...\Documents\My Games\ArmaReforger\profile\.save\app..._user...\settings and delete InputUserSettings.conf.
We have tested this on our end and we were unable to reproduce the issue.

I also had this problem my non-functioning keys were the vertical mouse movement and the down arrow key, I solved the problem by resetting all the keys

In T187199#2719185, @kawalec wrote:

Yes it is like that in A3.
I also don't like many changes BI is making in every update. Some of those changes are for the changes' sake only - look at 1.3 on Experimental.

In T187199#2719183, @kawalec wrote:

OK. I though that after the update you have a problem with switching optics in general.
And yes, now it's not possible to change it when not aiming.
It makes sense, it's more realistic. IRL you need to aim to choose between looking through irons sights or optics.

In T187199#2719164, @kawalec wrote:

Try LALT+NUM7 or LCTRL+NUM7. Just to be sure it's not assigned anywhere else. And assign it temporarily to any mouse key, so you will be sure that keys are pressed simultaneously.
For me it works like that:
https://www.youtube.com/watch?v=NA4rggDCQcE

BTW, have you checked if you don't have any mods enabled in mod manager?

I'm talking about switching Optics in the off-aim state, not in the on-aim state

In T187199#2719147, @kawalec wrote:

@Ponezun
Paste a screenshot of your key bindings here, please.

In T187199#2718865, @kawalec wrote:

OK. Look at the screenshot below. I assigned my "Switch weapon optics" to M5 (mouse button number 5). And I am sure that it's the only key bindings for this button. It is possible that the same combination of keys you are using at the moment for "Switch weapon optics" is used by some other action. So assign some unique combination like LALT+LCTRL+LSHIFT+9 to "Switch weapon optics" and see if it works. If it does, it means you had the same keys binded with different actions. If id doesn't work, problem may be elsewhere.

In T187199#2718467, @kawalec wrote:

So there is the same key/key combination assigned to two different actions. Check it all.

In T187199#2718232, @kawalec wrote:

Check the key bindings, there are some changes, so maybe that's the cause. For me it works exactly as previously.

This video gives a better idea of this issue, recorded on version 1.2.1.169. My fps is around 30 or so

In T184897#2676719, @Geez wrote:

Can you please explain what does mean that the instruments will fail?

In T184897#2676653, @Geez wrote:

Also please provide the following:

Game Version number:
Modded?: (Yes/No)
If modded, please list the mods:

This bug still exists and has not been fixed in the latest version.1.2.0.124

This bug still exists in the latest version 1.2.0.98