Fixed next week dev branch and profiling branch, BUT not in 2.12
Too risky to change AI behaviour here, we'll leave this dev/prof only till 2.14

What a rabbit hole did you sent me into here uff.
There are two problems.

1. The sensor takes radarTargetSize into account like you wrote. However that only applies to a signal being sent out, bouncing off an object and then coming back to the sender. Here it should be the pure sending range, we don't care about any bounce back. This had cut the range from 16km down to 12.8km
2. Even if any sensor detects a target, if its out of visual range, all sensor results are ignored. This will be the main bug. Even if radar gets through fog and is received by passive sensor, the results are ignored because fog is blocking eyesight of the target.

My Assignment Help is a very helpful website. I have used this website for my Python Tutors help and they have helped me in my project before the deadline.

There is another useful use case for an isDirect flag.

We talked about this in Discord and I'm just summarising it here for posterity.

groupId alternative syntax thanks to @dedmen!

dev next week

This seems to be ntentional. I don't know why. Someone a long time ago notd "strange issues" when we delete them. So we'll leave it be.

drop [  
 [(getModelInfo player)#1, 1, 0, 1],  
 "",  
 "SpaceObject",  
 1, 10,  
 [0, 0, 1.85],  
 [0, 0, 0],  
 0,  
 1, 0.785, 0,  
 [1],  
 [[1, 1, 1, 1]],  
 [1],  
 0, 0,  
 "", "",  
 quad,  
 0,  
 false, -1, [], [vectorDir quad vectorMultiply -1, vectorUp quad] 
];

next dev branch

Hand grenade hit is direct, fall damage isn't. I guess that's right
dev-branch

dev branch this week

Added "direction" source to Weapon, please report if it works, I'm not testing it.
Dev-branch this week

The wiki is wrong, "direction" is only compatible with "Transport" vehicles. The wiki description also says "The orientation of the vehicle", a weapon is not a vehicle.
How it returns a steadily increasing value I don't understand, it shouldn't exist at all.

A towing vehicle doesn't know its towing anyone, and it also could be towing multiple, so there returning one towed vehicle wouldn't make sense.
getTowParent only works on the towed vehicle

in the this config Cfg3DEN >> Group >> AttributeCategories >> Callsign >> expression
replacing _this setGroupID [_value]; to _this setGroupIdGlobal [_value]; would be a great tweak

awesome!

fixed in next dev probably

fixed in next dev probably

fixed in next dev probably

Thank you for requesting the feature.
Due to the current phase of Live Ops development in Arma 3, we cannot commit to any new features,
though we will try to consider them.

Thank you for requesting the feature.
However you might have found a bug instead, we will look into it.

Thank you for requesting the feature.
Due to the current phase of Live Ops development in Arma 3, we cannot commit to any new features,
though we will try to consider them.

Thank you for requesting the feature.
Due to the current phase of Live Ops development in Arma 3, we cannot commit to any new features,
though we will try to consider them.

Hello, could you try these steps?
https://community.bistudio.com/wiki/Arma_3:_Unusual_Process_Exit#0xC0000135_-_STATUS_DLL_NOT_FOUND

Ahh right, in that case it would be best to contact the GeForce Support.

Hello @captaincullen, sorry to hear about your issue.
To be able to check what the cause might be and to fix it you would need access to the "system files".
Maybe GeForce support can help you out?

this problem is more than 2 years old, but no one cares

rev 150215

This issue occurred again on my end. IS there any way to fix it?

created a YT video for repro https://youtu.be/Yyt0fK5wBkg the "2d" tire sound is continuous if these cars reversing
Apparently this problem persists if you are 580 meters from the Strider or 700 meters from the Ifrit
[? related issue type as in T167073 ?]

https://community.bistudio.com/wiki/insideBuilding rev 150214

In my opinion, don't log anything for any command at all, and instead add a new command line arg for that, so only if someone's interested in debugging would get them in log.

Thats what the error says, no points, and the error is correct

The selection does exist, it just doesn't have any points in it.
It's a selection in the model that has no vertices assigned to it, its empty, its invalid.
Thats what the error says, no points, and the error is correct, there are no points and the returned position is also 0,0,0

We will trim whitespace on preset creation, so you cannot create ones that end with whitespace anymore.
And also fix that deletion thing in case you somehow manually create one :D
dev branch next week

Step 3 "restart" launcher is important, if launcher is not restarted after creating the preset, then deleting works fine.
test space preset.preset2 no repro
test space .preset2 repro

Nevermind I thought I fixed it but didn't.
But I cannot reproduce this with JIP

would have been very handy and cheap way to detect i you are in a building :|

Currently experiencing this problem as well.
I'm using Nvidia GeForce Now to run steam to run Arma 3, so I don't have access to system files.
I've tried verifying game files through steam menus, to no avail.

I'll install the latest prof branch and give feedback in 2 days.

would have been very handy and cheap way to detect i you are in a building :|

Although the MRAWS launcher uses the same sounds sets

they don't

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 have looked into your issue and what you experienced is intended behaviour.
Unfortunately there are technical limitations.
Hence we will close this ticket.

we have looked into your issue and what you experienced is intended behaviour.
Hence we will close this ticket.

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.

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.