reported earlier Different lighting when hitting fly again

[scampaboy]

Hi

Its something of nothing but I noticed last night when using fly again to re enter a mission the lighting is different almost as though the time stayed the same after you ejected/crashed/spilt tea on your lap. 
I will try and make a video but I don’t have any screen capture software available, it would have to be via telephone camera. 
So I start a mission at 6am it’s dark and the sun is just sparking over the horizon fly for 40 mins crash and hit escape by this time it’s light and all street lights have turned off. I use the option to fly again and the time stays the same when the mission reloads. It’s not game breaking by any means just means a restart of the mission from editor etc. is it normal behaviour ? Is this why we are seeing high ram usage because the textures from the previous flight are still there ? 
Or is it something like what my mum would say “ well don’t crash then!!!” 

[Flappie]

I've just done the test and I cannot reproduce your issue.

[scampaboy]

I’ll have another go later this evening and make a video. 

[Agim]

It happens to me sometimes too, but its very rare ... hard to repro.

[scampaboy]

On 10/22/2021 at 8:22 AM, Agim said:

It happens to me sometimes too, but its very rare ... hard to repro.

I’ve been trying unsuccessfully since I posted 

[Svend_Dellepude]

From time to time here as well. Usually if I've been shot down and the screen goes black, before i respawn.

[dorianR666]

same

[Flappie]

Both in SP and MP?

[scampaboy]

On 10/25/2021 at 9:41 AM, Flappie said:

Both in SP and MP?

Sp only for me it’s one of those hard to reproduce when you need to jobs, because it’s split over two mission starts a track isn’t possible and unless I record every mission start with my phone it would be hard to catch. 
 

[Enduro14]

good one to witness this is f16 mission Dawn Raiders Persian gulf.  When i was testing cloud presets the stock settings for that mission lighting is completely different than when you do a preset,  even one with very very low cloud cover.  posted pics on discord

 

Crom

[rossmum]

I've been experiencing this for a while, most recent time was about a week ago. For everyone else it was a full moon with reasonably bright ground. For me, the moon was invisible, the ground was very dark, but the Persian Gulf was reflecting so much light that the water was physically painful to look at and objects like buildings, helicopters, my own cockpit, etc. were very bright. Example (screenshot from Tats who experienced the same issue on the same mission) -

I have also experienced this in the past, going back maybe a year or more. It is extremely rare and virtually impossible to reproduce intentionally, and it can usually be fixed by reconnecting to the server, let alone restarting the game. I don't recall if I've experienced it in SP but that is probably because I do not play SP very much. I am nearly 100% sure the issue is connected to time of day and specifically the way the game handles the handoff between "night" and "day" states - every time this bug has happened, it's been within 30 mins of sunrise/sunset. The issue is extra annoying, because sometimes the "day" cockpit lighting behavior is active and so your instruments are nearly completely invisible in the darkness.

For another example, here's my view in a mission earlier in the year - here's a video from when I streamed it (timestamped to mission start) and then some screenshots to compare it against -

These screenshots were taken from the trackfile, where the lighting functioned as intended. This is also what the other players in that mission saw.

As you can see, the ambient lighting level is substantially different, and heavily impacted my ability to play the mission. I could only see my HUD, not even my instruments.

The only way I can think to reproduce this issue is to just load up a mission set around dawn/dusk and restart it until the issue occurs, but I have no idea how many attempts that will take. It may also be connected to a very subtle, but noticeable, 'flicker' between two slightly different colour temperatures during certain lighting conditions - I don't know how to describe it, but every few seconds the game scene will tint slightly green, then back to blue, and repeat constantly. Something to do with GI?

[Flappie]

I recognize the sea made of light and the black sky. I believe this bug was happening more often when the initial 2.7 came out. I had it a few times, but I thought it was extinct.

It was brought back to mymemory not so long ago in another thread. Since it is rare, it will be a tough one to fix. But maybe there's a trace in the dcs.log file. If it happens again to any of you, please immediately attach your dcs.log file so devs can look at it.

To others: is that the bug you are all talking about? I thought it was seomething else.

[scampaboy]

On 10/29/2021 at 11:33 PM, Flappie said:

I recognize the sea made of light and the black sky. I believe this bug was happening more often when the initial 2.7 came out. I had it a few times, but I thought it was extinct.

It was brought back to mymemory not so long ago in another thread. Since it is rare, it will be a tough one to fix. But maybe there's a trace in the dcs.log file. If it happens again to any of you, please immediately attach your dcs.log file so devs can look at it.

To others: is that the bug you are all talking about? I thought it was seomething else.

If it happens again I’ll pull the dcs log. 
 

[Gryzor]

This bug happens IF:

1-. Start a mission with any cloud preset.

2-. Atart a second mission with NO CLOUDS. Then the bug happens!!! completely sea in fire!

You MUST do point 1 and 2. If you start for the first time some mission with NO CLOUDS, there is no graphical corruction.

Edited November 1, 2021 by Gryzor

[Flappie]

1 hour ago, Gryzor said:

This bug happens IF:

1-. Start a mission with any cloud preset.

2-. Atart a second mission with NO CLOUDS. Then the bug happens!!! completely sea in fire!

You MUST do point 1 and 2. If you start for the first time some mission with NO CLOUDS, there is no graphical corruction.

I tried but I'm unable to replicate the issue in current OB. I first loaded "Scattered7_preset" then "No_clouds" (see attached miz). Can you reproduce the issue with my miz files? If not, please attach yours.

 

Scattered 7:

Then no clouds:

No_clouds.miz Scattered7_preset.miz

[Sharkku]

I have this issue as well. Seems like it always happens if starting a night mission after a daytime mission. Not entirely sure about that though.

Sky becomes black, sea becomes very bright with reflections. Moon invisible.

GTX 1080 Ti

Core i9 10900K

[dorianR666]

41 minutes ago, Sharkku said:

Seems like it always happens if starting a night mission after a daytime mission.

correct, the texture isnt cleared from previous runs. therefore affects even day-day combinations.

 

 

[Flappie]

Can you please attach two missions which trigger this bug when we play them one after the other? I'm unable to reproduce the bug so far.

[dorianR666]

44 minutes ago, Flappie said:

Can you please attach two missions which trigger this bug when we play them one after the other? I'm unable to reproduce the bug so far.

have you tried the two missions i mention in the link above? works for me every time

[Flappie]

I've just tried the following and I couldn't see the bug:

• mission 04 (then I skipped)
• mission 05 (then I skipped
• mission 06

They were all day missions.

[Sharkku]

This time when it happened for me was when playing mission 5 "A matter of mine over water" right after playing mission number 4 "Hammers and nails" in campaign "Rise of the Persian Lion".

[Taz1004]

2 hours ago, Flappie said:

Can you please attach two missions which trigger this bug when we play them one after the other? I'm unable to reproduce the bug so far.

I can reproduce it repeatedly as well by starting Supercarrier Case 1 Recovery Persian Gulf single player mission.  And then starting Case 3 Recovery Persian Gulf.  Doesn't happen on Caucasus.

Starting PG Case1 and then Starting PG Case3

Starting PG Case3 straight from restart.

Below are the DCS log files when the bug happens (dcs_Bug.log) and when the bug doesn't happen (dcs_NoBug.log)

dcs_Bug.log

dcs_NoBug.log

 

All mods were uninstalled during this test.  Mission files are all default files that came with the game.

Edited November 2, 2021 by Taz1004

[Taz1004]

Testing further, it seems like it has to be combination of starting day first PLUS clouds.  I was investigating why it would happen on PG and not on Caucasus Case3.  Difference was PG Case3 had no clouds and Caucasus Case3 had clouds.

So I put clouds in PG Case3 and the problem didn't happen.  Then I removed clouds from Caucasus Case3 and problem did occur.

But in both cases, they had correct lighting even without clouds if I didn't start day mission first.

[Gryzor]

22 hours ago, Flappie said:

I tried but I'm unable to replicate the issue in current OB. I first loaded "Scattered7_preset" then "No_clouds" (see attached miz). Can you reproduce the issue with my miz files? If not, please attach yours.

 

Scattered 7:

Then no clouds:

No_clouds.miz 26.14 kB · 0 downloads Scattered7_preset.miz 26.16 kB · 1 download

Always happens if starting a night mission after a daytime mission. If I start those missions uploaded by you, NIGHT after NIGHT, everything is fine.

[Flappie]

OK, I'm able to replicate the issue on purpose, now. Thank you gents!