@razazel any ETA ? Cheers

If its is regarding only KOTH you have to contact either the Author or the Hoster of the server/mission. KOTH is a usermade mission.

The FCS is a direct Sight method. The Range is calculated from the point you are aiming at. The real FCS is the right side where you put in your elevation.
What you actually want are range tables, maybe BI can provide some.

This is still an issue, and very annoying. Fills my logs with information we don't need to see.

Artillery FCS. The artillery sight does not allow manual selection of the range of distance RNG, TRV and REL. ELV should receive automatically, depending on the choice of the trajectory HIGH and LOW. Or highlight REL = true when the angle of the barrel for HIGH and LOW is manually selected correctly.
This is necessary for a shot beyond the visible range when the ballistic computer is off.

Please save my eyes from this problem. It's like before, it's hard to read the chat.

This works as before. AT launcher can be picked up only after unintentional choice of laser target designator (range finder).

In T123164#1570076, @Alwin wrote:

Hi,
There are still not all localizations finished. (in 1.67)

Thanks for report.

Thank you, close the ticket.

I get this as well when I use APEX chars in missions.

Ai is fired when they see the geometric center of the target. Ai never shoot at any visible part of the target.
https://youtu.be/DSevNn5OKFo
Give the AI ​​a wide range for selection.

Works like a charm so far---we can close this thread. thanks Wiz.

+1, the AT launcher was a way to compensate for the enemys quantity through your own quality / skill. At least improve missile speed or make a switch between top and direct mode.

On the video in this ticket everything looks interesting. But I think this issue could be partially solved without changing the animation.
Add an icon to the center of the grenade throw view, with the loading forces division in a circle, similar to this

In T126258#1634204, @ceeeb wrote:

Related to assigned T64247.

Thanks, I could not find it.

I repeated myself here https://feedback.bistudio.com/T126258
More details. The optical sight is jammed at maximum resolution. Occurs with some optical sights on turrets and cars, where there is a smooth zoom.
https://youtu.be/6_G95da1n_c
This happens when the 3D view is turned on + the "temporary zoom" key is clamped and the "optics" key is pressed.
After the optical sight is stuck at maximum magnification, it is impossible to return the functionality of changing the multiplicity on the optical sight, in the equipment where it happened.

+1

{F71735}So, i did some file digging and it appears the gun depression is actually correct in the files but somehow in game it's bugged...

Related to assigned T64247.

Changing the angle on the artillery, up and down, stops - when the free view turns on.
https://youtu.be/mVYljLTQuvg

I am surprised. This was to be decided on May 8, 2013.

Hi dude, i have also find out one good template website
<a href="http://www.templateonweb.com/">
Download Free Template</a>

i see alot of people on other sites saying it a logitech issue but i have a corsair void rgb and i receive it too. dont know what that means.

I think it may also be an AMD issue

I have a GTX680 4gb what do you suggest I have my voltage set to on MSI afterburner? I have the fan set to 63% right now nothing else tweaked at the moment. It does not matter if I underclock all the way or overclock slightly. Fan 100% or auto it will still artifact or crash to black screen resulting me to ctrl alt del and ending process. Last time it crashed I was playing king of the hill and I was ejecting out of the hummingbird before the parachute deploys and it crashed to black screen and then artifacts shortly after the game is closed. I seen improvements of my card not crashing often after trying different fixes but it still occurs. I included updated .rpt and log files. Will report back if running dxsetup did anything.

Hey i managed to fix this issue by reinstalling DX in the arma files:

Hey i managed to fix this issue by reinstalling DX in the arma files:

In T74907#1633828, @nigel wrote:

https://community.bistudio.com/wiki/setTerrainGrid
You can force these settings for your mission if it is a highly competetive PVP mission.

It's a good offer. But most players do not control the server, and do not create a mission and most likely will not try to solve these issues with the server administrator. Those who do missions and control the server do not care about it.
But all players are forced to face a not fair game. To establish the fact of violation of prohibitions is impossible, everything can be explained by chance and other reasons.
The reputation of the game can suffer - nobody likes fraud, and does not want to face it.
How many servers have a lock, this setting?
On servers only block the maximum range of visibility.
For this reason, I have the opinion that the server in principle should not have the setting below:
-Very High = 6.25
-Ultra = 3.125
This is not one problem that reduces the impression of Arma3. If attention to these problems does not change, it makes no sense to continue the dialogue. Or this problem should be, in some way or another, transferred to server administrators as a desirable configuration guide.

This can not affect the problem. I can not keep my stels position, because I do not control the position of the players settings. I can open someone's stels position, it does not control my settings.

semi/ auto fire reset problem

when you switch your weapon like AT, or handgun. and then return to main gun ( like assault rifles )
the semi/auto fire setting became reset.

(MXM for semi auto by default, and spar-16s for auto by default.)

it's really awful when you using guns for immediate situation.
need to fixed (to follow gunner's previous settings.)

Any weapon that you remove on your back (or holster) - turns on the fuse. That is, the rate of fire is reset.

BIS please correct this shamefull sragdoll

I think TheMasterofBlubb has a point. It makes sense that a USB headset relies on CPU. Too bad nobody makes a soundcard for wireless headsets so the load could be transferred. Not that I'm aware of anyway.

thx razazel

In T74907#1633658, @nigel wrote:

You are playing on low terrain settings. Play on ultra settings. This is used to reduce the amount of triangles used to render terrain. It's what keeps lower end PCs in the game.

This can not affect the problem. I can not keep my stels position, because I do not control the position of the players settings. I can open someone's stels position, it does not control my settings.
The problem is not how the landscape looks. The problem is transparency, which should not be.
You can find the player where it should not be viewed by changing the settings.
https://youtu.be/jGBH7n_K2dk

You are playing on low terrain settings. Play on ultra settings. This is used to reduce the amount of triangles used to render terrain. It's what keeps lower end PCs in the game.

Happens for me only on the right side of the carrier, not on the left side. And did also happen on the big airport of Malden 2035.

3den Arsenal I mean loadout editor. sorry cuz Im playing at japanese laungage. but friends are using english laungage for repro.

issue has been resolved in yesterdays devbranch:
https://forums.bistudio.com/forums/topic/140837-development-branch-changelog/?do=findComment&comment=3214237

Could you please try switching Arma 3 to the Development branch on Steam?

Can confirm. It's a race condition between the scripted eventhandler that executes the expression line and the module script deleting the wreck. The scripted eventhandler is spawned and therefore executed at least one frame too late.

thx razazel, cant wait for the fix :)

Fix is in progress, do not worry about that.

Same issue for me, recently installed a Corsair VOID RGB Wireless 7.1 headset and immediately began having same issue. Game rev 1.72. Only occurs when in 1st person in vehicles.

Please! any update would be much appreciated

been almost 2 months with broken JIP MP can we get an update @razazel

This is still, continues to interfere with playing on the server. BIS !!!!!!!!!!!!!!!!!!!

BIS_fnc_relPos - DONE (getRelPos)
BIS_fnc_relativeDirTo - DONE (getRelDir)
BIS_fnc_inTrigger DONE (inArea)
BIS_fnc_isInsideArea DONE (inArea)
BIS_fnc_enemyTargets DONE (targets)
BIS_fnc_addStackedEventHandler DONE (mission EHs)
BIS_fnc_removeStackedEventHandler DONE (mission EHs)
BIS_fnc_conditionalSelect DONE (select alt syntax)

@razazel Is there any more information on this problem?

This is fixed at least with 1.70 but I guess some versions before.
could be closed...

push.

Great, that is good to hear.

Sorry about not getting back to you quickly.

I really cannot understand why this wasn't added yet. It feels so necessary. +1

Hello oukej, after trying the launcher for a few times on DEV i've came up with 2 problems, but before i go there, i want to say that maneuverability was indeed improved, so short range is not a problem anymore. But now onto the problems, first problem is the view distance, after the missile is launched, its perfect, particles come up, rocket is visible, as soon as it gets ~1.2km away, the rocket particle dissapears, making it invisible for the soldier to see where its going, this is a really big problem if target is more than 1.2km away AND if is moving at the same time its very hard to hit the target, this problem does not occur in Mi-48 Kajman the SCALPEL ATGM missiles, aswell as in AH-99 Blackfoot DAGR missiles. 2nd problem is the speed, iam not saying it should be reverted back to what it was, but making it slightly more faster would make it more viable when shooting in long ranges as the target is moving, when target is static thats a different case scenario. In this video i represent the view distance problem, video: https://www.youtube.com/watch?v=f53NxSF1GIE&feature=youtu.be timestamps:
0:00 - Missile is launched, particles are visible. (No thermals)
0:07- Missile is still flying, particles are gone, very hard to predict the missile.
0:42 - Missile is launched, particles are visible. (Black Hot Mode)
0:49 - Missile is still flying, particles are gone, very hard to predict the missile.
Keep in mind that this is happening on short range(1.7km). I think that 11seconds for 1.7km is too slow,as i said just a little increase on speed, would make it much more better. But view distance is a must.