- Queries
- Arma 3 Activity
- All Stories
- Search
- Advanced Search
Advanced Search
Dec 5 2016
Effective firing range 200 m
Maximum firing range ≈920 m (1,000 yd) (self detonates)
https://en.wikipedia.org/wiki/RPG-7
The aim level has a window and a scale with the divisions designated by figures 2, 3, 4, 5.
Figures of a scale designate range of fire in hundreds of meters (200, 300, 400, 500 m).
https://feedback.bistudio.com/T121840
In the editor.
-AI Stationary mortar.
-Artillery support, each order, on any 1-4 volley.
-Always only 1 volley.
Dec 2 2016
All UAV, red, blue, and green fractions.
And further.
Fixed designator, and all, with no pilot - video does not transmit to the PIP.
No Mission.
This editor, selecting drone operator.
I will try in the evening. It was stored in a sample editor, from the past. Maybe this problem.
But it seems I have tried and the new selection.
Enable the PIP screen on the person, always broadcast from the pilot chamber.
I understood. This ticket is not very important. A significant problem in other ticket. It appeared at the same time.
https://feedback.bistudio.com/T121561
What under this ticket? There will be a correction for it. It breaks use of monitoring in the PIP screen. Tactical monitoring in PIP it isn't possible. Monitoring is possible only in the control panel of the UAV or in control of the camera of the UAV.
It breaks a possibility of performance of a task and simultaneous monitoring of a situation.
Dec 1 2016
Nov 30 2016
Changes for release 1.66 will be?
Changes for release 1.66 will be?
Nov 29 2016
In T118532#1537893, @TheMasterofBlubb wrote:Because its WIP (Work in Progress) not sheduled for next Patch.
Why there are no explanations on this type of work of UAV?
Why operation of the camera isn't corrected?
Why operation of the camera isn't corrected?
Why in CR versions appear problems there where there were no problems in DEV of the version?
Why in CR versions appear problems there where there were no problems in DEV of the version?
Nov 28 2016
The problem remained on RC 1.66 of the version.
Nov 25 2016
On version RC 1.66 the problem has remained.
Nov 24 2016
In T86310#1492115, @TheMasterofBlubb wrote:Its not sticking to the head. Its changing the distance to your point of view thats why it seems that the crosshair sticks to the head. Its a optical illusion
Nov 23 2016
I have such ticket.
https://feedback.bistudio.com/T82258
I have repeated it. But the reason of creation of the ticket was in another.
Replace the name on - UAV Darter traveling points don't work.
98% of UAV Darter won't reach in a point.
ArmA 3 RC 1.66
You when solve it UAV Darter?
https://youtu.be/UOQncpTZk9Q
Nov 22 2016
+ 100%
The sound on the wind generator is necessary
https://youtu.be/xnSrdE9uvPU
I do not understand this bug is easy to appear on bespilotnike. I put two drone in the editor, and a detachment of the enemy. During the game in the editor, drone revolves around the point and can not take the appointed position.
Is there no time to fix it?
Video
https://youtu.be/Vk_Rjf8liOA
for Mission Editor.
Use the UAV to detect the enemy.
Nov 21 2016
If there is a ballistic computer on board:
- On board there are semi-automatic ballistics
- Optical sight gunner and tank commander
set up at the site. Lead ballistic barrel in the optical axis zero sight.
- All the other amendments to the optics on the sighting frame with a wide range of scales on the angle correction of sight.
In the first seconds of video - axis offset ballistic computer AI,
for an explosive charge HE, T-100 on. Centre sight arrow above the target. But AI is on target. Keeping sight position, your shot is off target.
Nov 17 2016
Everything happens as before to VR= \> 3200. Time in which I have received - Process page file used 3427 pleases. This time has made 3:40 hours of a game.
The option when Process page file used doesn't exceed = ~ 3200 is possible, and my game will make more time than 4 hours?
But this result, much better than was earlier , 30-40 minutes.
Nov 16 2016
There are options of UAV group of recalculation?
Nov 15 2016
Yesterday in DEV of the version has received some defect. The turn of a tower of the tank reproduced the case of the tank to jump. Change from the driver to the shooter reproduced wheels to sink in soil.
https://youtu.be/RAzF2DVthuI
On DEV it is reproduced, as before.
Nov 12 2016
Nov 11 2016
In T83302#1529009, @Tsnfsdnfkjsdn wrote:Its not a bug. In any modern tank range is not calculated utomaticly, you need to lase the target, THEN range correction is done.
Put infantry of AT on 2500 meters from the tank. Try that that to generate to include AUTO and to shoot.
At you it won't turn out to include AUTO for firing at infantry or at the building. There is no button of inclusion of AUTO. The maximum distance of 1900 meters on the optical center. Everything that further than 1900 meters, to shoot as will turn out.
Groups of UAVs getting to yellow fraction reduce the number of the main group.
It has been noticed from the very beginning. For this reason, I have shown you a problem of groups of UAVs. If in the mixed groups not to use UAVs, with calculation of groups there is no problem.
But in missions UAVs are used, and there is an emergence of a problem, in the form of loss of creation of the main (living) groups.
https://youtu.be/HcOd-O-oWwo
Removal of yellow groups doesn't renew an opportunity to return all 144 living groups.
https://youtu.be/tj8nMN2SpMI
The mission for the editor, is only 1 group.
Nov 10 2016
Mission for the editor
Nobody knows in BIS what parameter in the "client settings" setup of the server causes damages from bushes?
Nov 9 2016
In Dev of the version there is a correction. Thanks.
In Dev of the version there is a correction. Thanks.
In T120533#1518148, @razazel wrote:Are you able to observe same issues on the Development branch?
Nov 8 2016
In Dev of the version the problem isn't reproduced
Close the ticket.
Nov 7 2016
On our server there is DLC Apex objects, weapon and cars as a part of the Altis card.
In the list of the required additions there is DLC Apex.
But as not all have this addition, on the server strict check on MOD is turned off, it allows players to play without DLS on the server. Lack of check is bad for all too, players can use the forbidden MOD.
For players without DLC Apex, the message in a game has to be realized - "you can't use this object....", as it has been made in former DLC.
Lack of such realization, inclusion of strict check of MOD of many causes the necessity. It makes protection of players with DLC Apex from collisions in a game against players without DLC Apex, emergence of problems of Stels vision.
I don't welcome such realization of DLC from BIS as it razedinyat people on players from DLS and players without DLS.
All have to see APEX objects, use them могкт only owners of DLC.
Too I hope that it will be corrected. Otherwise loss of players because of inclusion of strict check on MOD is necessary to us to exclude use of the forbidden MOD.
Why now parameter and a launcher is necessary maxVRAM = 256 - 2049 and maxMem = 256 - 16384 ?
What tasks they carry out, it is more than doubts in their application?
For all that that restriction of maxMem = ~ 1000, about it or less really works.
In a launcher any restriction less than admissible works.
I hope that it is correct. But in the ambassador of the last update, often, completion of work of process of arma3.exe comes to the end with a mistake.
When I press the exit button in the main menu of a game.
The instruction of no anpecy 0x0000000001C7792D has addressed memory of no to the address OxOOOOOOOO7E1CAAC4. Memory can't be written.
http://imgur.com/9bwD8WM
Restriction of maxMem=2048 doesn't work. Process easily goes beyond this restriction through 5-10minut after start.
http://imgur.com/RFiCqWZ
Earlier all Arma3 versions beat with other restrictions - maxVRAM - maxMem.
In a launcher there were other restrictions, it was possible to change values in such limits:
- maxVRAM = 256 - 2049
- maxMem = 256 - 16384
It can be seen in reports.
In reports Arma3 to version 1.64:
- maxVRAM=2049 -maxMem=10241
In reports Arma3 of version 1.64 above:
- maxmem=2047
- maxvram=8196
Sizes of parameters have traded places.
It promoted emergence this ticket.