anyone?

In T123657#1599747, @razazel wrote:

Hello,

may I ask whether latest updates or profiling branch changes have had any impact?

Duh, I swear I searched before posting.

I can answer this real quickly for you this isn't a bug but this is more of how Landing strips are made. AI program to land in one direction of the Airfield and take off in another never the opposite. with this the ilS only shows when you're coming in from The Landing side of the Airfield not the takeoff. in conclusion runaways are like a one-way Street and the ILS will not show up unless you were coming and in their correct direction. hope this helped

I agree. Just found out that it's impossible to use any kind of TI with ppEffects.

Same problem here. I've got a Logitech G430 (7.1 Surround). If I'm inside a vehicle or in a building the sound is "multiplying" itself. Inside a vehicle (especially in a chopper) the game starts shuttering, FPS drops down to 3 until the game crashes.

may I ask whether latest updates or profiling branch changes have had any impact?

new logs since perf branch update:

It seems that the picked random texture for the goats / sheeps are not set globaly, only the machine that spawn the unit sees it.

Having same problem with my multiplayer framework

I can confirm that I am experiencing similar issues with this command, as well as canAddToUniform, canAddToVest, and canAddToBackpack. I am unsure of the cause, and I can confirm that it is not only an issue with the Bergen backpack. It seems to report inaccurate results for other clothing items as well. I read another feedback ticket regarding a similar issue as well, which you can see here: https://feedback.bistudio.com/T85789. I hope that there will be an update to this issue sometime soon as I would love to be able to use these commands.

Hello Shmurda,
could you please upload your Launcher logs here? Here's how you can gather them manually: http://arma.jiripolasek.com/howtos.html

Hello kitfox,
we're still trying to make some sense out of the error, but unfortunately it points to the core of .NET Framework (so deep that we can't reverse engineer it to see what could possible go wrong) and we haven't been able to find out any similar issues anywhere on the internet.

In T124490#1599576, @hvymtal wrote:

+1
Severity is major, this basically makes the carrier useless after four launches, and it makes landing on it impossible after launching from cat 3. This would be accurately described as "game breaking"

So any reason why you haven't replied in a week. pls I want to be able to play arma on this computer again.

still an issue

Updated images, all at low altitude on official map with laser designator selected (no gun cross)

@ocf Negative, I was definitely using nose indicators. Besides, at low altitude over ocean even on lower view distance settings the horizon line should be on the... horizon. Perhaps a bit above it given arma's relatively short view distances. This is easy to see for yourself. Perhaps the shikra isn't as off as I think it is (edit nvm it is) but the gryphon and wasp DEFINITELY are off.
Updated ticket with proper images

+1
Severity is major, this basically makes the carrier useless after four launches, and it makes landing on it impossible after launching from cat 3. This would be accurately described as "game breaking"

Very much like to see these updated too.
Especially enticing as the 45 pistol appears to be getting a new flash-light attachment.
It would look great in a little black dress! ;)

And no more range data...

I will add video on this problem UCAV.
https://youtu.be/9PEwhvBfvI0
But what occurs in practice, the bomb defines a laser point there where watches a tourist's fir-tree.

The rocket does capture of the purpose, but the purpose isn't locked in the lock.

Why do we need two identical functions with different names?

similar real world use the catapult

Do you get also a windows error message direct after the crash or only that from Arma 3 Launcher?

Two problems:

• iron bushes;
• AI looking at targets through vegetation/smoke.

You can use two commands:
allowCrewInImmobile
canUnloadInCombat

Launcher version: 1.5.141155

I have the same problem -_-

thank you for the feedback.

tooltip for both is the same afair, so most likely it the same function and was left over from a legacy version...

Problem is solving when i setting "Interface size" from "small" to "large".

The problem has appeared with release 1.67-1.68. There are problems not only in a marking of poles. Try to change in video settings of a game a raziyer of HUD - small or very small.

Note that there are Drones and the Remote Designator too.