A strange shadow appears around the player

I've had this same issue, but much more pronounced. The shadow radius is quite a bit smaller, but much darker.

@Chaton Noir

Thanks for your report. I have seen this before and know exactly what you are talking about, however, I did not see it in V1 b317 or in our testing trunk build. Are you still seeing this in V1 b317?

Edited July 15 by WretchedDollie (see edit history)

13 hours ago, WretchedDollie said:

@Chaton Noir

Thanks for your report. I have seen this before and know exactly what you are talking about, however, I did not see it in V1 b317 or in our testing trunk build. Are you still seeing this in V1 b317?

Checked it out. The problem remains.

OK. Do you mind adding screen grabs of your video settings for me?

On 7/18/2024 at 7:15 PM, WretchedDollie said:

OK. Do you mind adding screen grabs of your video settings for me?

I did a quick test and didn't see this in b326. It looks like it has been fixed.

Thanks. I thought it was less noticeable as well. I'll move this to resolved.

Another possible fix  :   

I encountered the same problem on b333 (if I remember correctly the build we have today 27/7/24 running as default), while upgrading the game from "V0.1-unstable-experimental" (where I had no shadow circle) to the "none beta" option at Steam launching options, using the same save and graphic options I was using before the update.

 

But it seems to have been fixed after I experimented with the graphics options. : 

It looks like that after deactivating the "multithreaded on" option at the game launcher screen (before starting the game), running the game, and then shutting down the game, and re-launching while setting "multithreaded" back to active (I had FPS drops without it), the player-shadow-cycle that was annoyingly noticeable on the street now is almost invisible.  Looks to still be there, but it I have to look for it to realize it.   

Note-1: When I had the problem, the circle was visible at Low, Mid and Far shadow distance setting, just at three different radiuses.

Note-2: The above might not be a fix, because after re-launching the game-weather was different. Not such a major change though, so I think that my shadow-cyrcle problem is now fixed.

 

(I am posting only to maybe be helpful to someone. I need no reply or support. Please devs, dont waste your time on my post 🙂 .  Keep on the good work of expanding the game for us 🙂  )

UPDATE:   Bummer....  the below post of mine is a false-fix... The circle is still visibly here ... Will live with it. It is not game-braking because it is not visible on grass or indoors or when facing the sun etc.

 

Another possible fix  :   

I encountered the same problem on b333 (if I remember correctly the build we have today 27/7/24 running as default), while upgrading the game from "V0.1-unstable-experimental" (where I had no shadow circle) to the "none beta" option at Steam launching options, using the same save and graphic options I was using before the update.

 

But it seems to have been fixed after I experimented with the graphics options. : 

It looks like that after deactivating the "multithreaded on" option at the game launcher screen (before starting the game), running the game, and then shutting down the game, and re-launching while setting "multithreaded" back to active (I had FPS drops without it), the player-shadow-cycle that was annoyingly noticeable on the street now is almost invisible.  Looks to still be there, but it I have to look for it to realize it.   

Note-1: When I had the problem, the circle was visible at Low, Mid and Far shadow distance setting, just at three different radiuses.

Note-2: The above might not be a fix, because after re-launching the game-weather was different. Not such a major change though, so I think that my shadow-cyrcle problem is now fixed.

 

(I am posting only to maybe be helpful to someone. I need no reply or support. Please devs, dont waste your time on my post 🙂 .  Keep on the good work of expanding the game for us 🙂  )

I see this problem again in b333.

@WretchedDollie, I had this problem again in 1.1, and before that I saw it in b333.