Oh how silly of myself. Completly forgot that they had that ahaha. Thank you :D

I guess you've been lucky then because z-fighting has been always happening to everyone else who has ever played this game.

I have been playing the game for months now and i can assure you 100% it was not always like that. It started 2 weeks ago and i can see it after 400 meters. it can be seen everywhere on the maps of altis, stratis modded or vanilla. There is a video on youtube that describes my problem: https://www.youtube.com/watch?v=wzdMIKAnFHE mine is just more intense

I'm sure this has always happened to you, just like it has to everyone else. You only just now noticed it.

In T123668#1581373, @greenfist wrote:

This is a phenomenon called "z-fighting". It has always happened is certain condititions, and there's no way for you to avoid it.

thank you for your feedback.

Logs from the RC branch should do just fine for now :)

This is a phenomenon called "z-fighting". It has always happened is certain condititions, and there's no way for you to avoid it.

Your color is incorrectly defined.
https://community.bistudio.com/wiki/Color

Are you experiencing same issues when running the game without mods?

Does this happen during a specific MP mission?

Hello,
thank you for reporting the issue. We know about the issue, but unfortunately it can't be fixed. The issue is caused by a limit amount of data transferred from the server to clients, and as the data are transfer is handled by Steam libraries, we can't change it.

I , as before, lose the distance of total visibility. There is no way to bypass the problem, or restore the distance of visibility. Only a restart of the mission-restores the previous distance visibility.
Video DEV 1.69.0.140753
https://youtu.be/YjPToeSSg9M

https://forums.bistudio.com/topic/202603-tanks-fire-control-system/

We are really sorry about not making it into 1.68 update in the end :( And we apologise for the inconveniences caused by delaying the change to the 1.70 patch.

@smp1991 Perhaps there is serial communication. But this time, when the UAV cannot reach the route point, assigned to the UAV keeps height. It looks
as loss of coordination in movement.

Can confirm this. I find that it only happens when you set the altitude of the Darter. If you create a waypoint it will move to the waypoint just fine. If you assign it an altitude it will trip out hard, every few hundred meters.

Perhaps, BI could ask something to Steam... I can't imagine there is no clever link between BI and Steam teams... as far as Steam seems mandatory to run Arma....

Yep, agreed 100% I wrote about that on Jet DLC project.... Not sure to be heard. It's absolutely boring to get half throttle pad. The workaround binding both increase/decrease sides of the stick for power doesn't work.

There is also a remaining damage problem along with used caliber and vehicle type. Go directly to 2min10 of this video: https://www.youtube.com/watch?v=kd6ui-dRCto (One of my firsts, sorry).

ok onPlayerDiconnected do the job buthope bis fix that

really 1.66 here everything just fine just tested on 1.66

This problem is similar to the action menu for commanding an AI to grab a weapon or jump into a vehicle. You're not supposed to know every vehicle or weaponholder/crate places but AI does.

Agreed. Not so much differences with a "Move" waypoint. The AI should patrol in range of the completion radius (for example, if not set to zero or minimum depending on type of units.).

It seems the same in 1.66, and for all disconnections. I use "onPlayerDiconnected" EH for deleting the abandoned AI.

In T123238#1578329, @Lex wrote:

Someone can try and check it. I have disconnected BIOS Intel Virtualization Technology, result:

• FPS in a game is stabilized better
• It is less friezes
• The fragmentary sounds characteristic to FPS falling don't appear in a game
• In a game on the server, with MOD, 30 players, about 3 hours a game lasted - hasn't seen a problem 3FPS
  

Yeah ffs Bohemia please mute this useless garbage once and for all, it provides no relevant information whatsoever to end users, all it does is clog I/O and make everything else harder to analyze.

I had this message 18,221 times in 4 hours for this object and it is like this every reboot.

10:01:41 Can't change owner from 0 to 2
10:01:41 Server: Object info 2:6182 not found.
10:01:41 Can't change owner from 0 to 2
10:01:41 Server: Object info 2:6182 not found.
10:01:41 Can't change owner from 0 to 2
10:01:41 Server: Object info 2:6182 not found.
10:01:41 Can't change owner from 0 to 2
10:01:41 Server: Object info 2:6182 not found.

how can i help?

Any news ? Thanks in advance

In T123456#1580371, @JiriWainar wrote:

Hi there. Thanks for the repro mission, I checked it. The script commands you are using there provide basic functionality over simpleTasks. It is absolutely OK, if you use them directly. This way you get full control over your tasks, but also full responsibility over everything else, like is synchronization in MP or the above mentioned automated handling of child tasks according parent task state.

The script commands for simple tasks needs to state generic. Such quality of life improvement could help one guy but at the same time could create a nightmare for another.

If you want semi-intelligent behavior I suggest using the scripted task framework. It does what you need - when parent task is completed (fails, succeeds, is canceled) then all uncompleted tasks are set to state of the parent task. The task framework also handles quite efficiently MP synchronization.

If you need some special handling for several child tasks I suggest setting their task states before you set the parent task state or if even this is not acceptable for you for some reason, just script it yourself. The script commands give you full control over the tasks...

There are some links you might find useful (in case you are not familiar with them):
https://community.bistudio.com/wiki/Arma_3_Task_Framework
https://community.bistudio.com/wiki/Arma_3_Tasks_Overhaul

Note: Regarding the details about available functions and their parameters I strongly suggest to use the in-game Functions Manager. The information there will be most up-to-date and is easy to read - should be properly formatted.

@Alwin if not then i thank you a lot for your efforts but please unassign so that other members and hopefully a developer may notice the thread and know that it is unresolved :)

:(

I posted a new one

still get it on RC branch

So far I could encounter this issue only once. Therefore I could not reproduce it in a game session without mods. What looks like the same symptoms have been confirmed by two other persons but also since then it looks like no one encountered this again. I do not have hard feelings about this so if you say it can not be fixed if it is not reproducible I am fine with you closing the ticket.

Hi there. Thanks for the repro mission, I checked it. The script commands you are using there provide basic functionality over simpleTasks. It is absolutely OK, if you use them directly. This way you get full control over your tasks, but also full responsibility over everything else, like is synchronization in MP or the above mentioned automated handling of child tasks according parent task state.

Ok so now after many hours im getting a different crash bug.

Hmm i agree, the lock should break if the thermal signature is covered.

thank you for the feedback, we will look into this.