fixed Friendly units prevent fog of war unfogging

[bal2o]

Hi,

since update, i see that with fog of war we can't see unit in F10 even with Awacs (for CAP) or MQ9 repear (for ground unit). In this last case, unit is visible 1-2s and disapear after that.

It's a new "correct as is" or bug ? (attach file show 2 screens : first exactly when MQ9 spawn, second somes seconds after

[Flappie]

Please attach a short DCS track.

[bal2o]

2 hours ago, Flappie said:

Please attach a short DCS track.

Hi, see attach file. it's a short in time but it's a large mission .... i don't have other mission for now with reaper spawning on call... But you can see me calling a reaper on ramon Airbase, red ground unit came visible in F10 and 2s after, same unit became invisible.

 

  Hope it's help thanks.

bugFog.trk

[Bobelz]

Yes, same here on our Server's.

[Volator]

Same on Blue Flag servers, this can't be a "feature"...

[Freelancer]

Can you Laser or find a target through the clouds or fog in real live?

[bal2o]

1 hour ago, Freelancer said:

Can you Laser or find a target through the clouds or fog in real live?

it's not the question : no information in change log about changing something in fog of war, so it's a bug. And unit was visible but only 1s after MQ9 spawn, and same for awacs : plane is visible during 1s. So it's not "real live" too...

And some player like this feature. if you don't want seeing unit, there is a option for that.

[Yoshi]

Hello guys,

first of all I apologize if I'm posting in the wrong section, but I'm not actually sure if this is a ME issue or a general DCS one, or if I simply have done something wrong during the editing.

Here's the deal, I select a Tactical Commander slot, start the mission, for a few seconds I can see several enemy ground units in the F10 map, then they suddently disappear from the map, even if they should be visible.

I though it might have been related to the number of units, so i started removing them but it didnt work.

I have also removed all the triggers in the mission, same result.

I'm really out of options here, anyone has any idea why this is happening?

DAY 01_V2.2.miz

[bal2o]

@BIGNEWY possible to check this ? it's a true bug or a problem in server side ? i can try to make more track if needed.

[BIGNEWY]

Hi,

we will check

thanks

[Flappie]

Testing in OB, it works in SP. Checking MP now.

[Flappie]

It works fine in MP as well.

Now, I see that you're talking about MQ-9 spawning. I'll try again with a late activated MQ-9.

EDIT: even with late activation, I cannot reproduce the issue. I'll check your track now, @bal2o.

MQ9-20231024-233130.trk

Edited October 24, 2023 by Flappie

[Flappie]

I do witness the issue in your track, but I just don't understand why I cannot reproduce it in my own missions...

Can you reproduce the problem in a Caucasus mission, please? That would help.

[bal2o]

1 minute ago, Flappie said:

I do witness the issue in your track, but I just don't understand why I cannot reproduce it in my own missions...

Can you reproduce the problem in a Caucasus mission, please? That would help.

I can try of course. probably tomorrow (need time for short mission)

[Flappie]

I'm seeing this:

Are some missing?

[bal2o]

Ok so not possible to reproduce with a simple mission with reaper late activate .... it's not map related because i have same problem on all map, and also with CAP, but don't know why.

I will try to work with this new information to find if something change in scripts/mission params...

 

[bal2o]

And now i try with my script : no problem on clean mission. hard to understand ...

[bal2o]

ok last test : i add a reaper with late activation on mission used in my track => problem. so it's not about script.

so question : is there some red unit that can turn on fog  ?

 

tomorrow i test on other large mission where we have same problem, without script for MQ9 spawn.

Edited October 24, 2023 by bal2o

[Yoshi]

Hi Flappie, yes, if you check the miz in the editor, there's a bunch of sams all around, they should be visible i guess. Additionally, try the radio menu Other -> Start Mortars. It will spawn a group of mortars and an armored column right below the UAV. They will appear briefly on the map, less than a second, and then they will vanish.

[bal2o]

20 hours ago, Flappie said:

I do witness the issue in your track, but I just don't understand why I cannot reproduce it in my own missions...

Can you reproduce the problem in a Caucasus mission, please? That would help.

CG Ticonderoga !!

if you add it on mission, it's remove the "unfog" reaper capacity (and probably same for awacs ? - but not check). And distance matter :

- no problem (aka reaper can show unit) at 260Nm of reaper zone

- problem at 230Nm

 

In attach :

- miz with always FOG because CG too close (REAPER - always FOG.miz) + trk (FROG.trk)

- miz with no problem because CH at more 250Nm (REAPER - FOG ok.miz) + trk (No FROG.trk)

 

Hope it's help. don"t know if also the problem for AWACS and if other unit are the effect.

 

Best,

Edit : may be it's not only this unit that act like this...

 

REAPER - FOG ok.miz No FROG.trk FROG.trk REAPER - always FOG.miz

Edited October 25, 2023 by bal2o

[bal2o]

Ok find problem with other unit : blue Beacon TACAN Portable TTS 3030  block unfog of blue reaper ...

[Flappie]

Nice find!

Maybe all TACAN emitters do this. I'll check.

[Flappie]

@bal2o found out that some nearby units cause this issue. Please join us here:

 

[Flappie]

I can't reproduce the portable TACAN issue so far. How did you do?

Edited October 25, 2023 by Flappie

[Flappie]

Issue reported.

These units cause the bug, but there are probably many others:

• Ticonderoga
• 25 di Mayo
• Pyotr Velikiy
• Moskva
• Kuznetsov
• Nimitz (must be close)
• Arleigh Burke
• La Combattante
• Oliver Perry
• ...

If you can provide me with a track showing the portable TACAN bug, I'll add it in the internal report.

Edited October 25, 2023 by Flappie