#Those Two Console Vars Are Essential
Eric you wrote:
“The Dynamic Shadow Distance setting appears to be working as intended and the limit you are seeing is based on the size of your object to the distance from the camera”
“most of the people in this thread have been talking about an RTS which has the camera at a isometric angle to the playing space. This means that you are not measuring the straight downward vector for distance, but the hypotenuse vector and this amplifies the problem as now the items further back in the scene (which you would not have in the top down method) are actually further back and take up less screen space then the items in the foreground closer to the camera.”
“I know we all have had issues with setting these variables and this area is one in which I am still testing to make sure they are working as intended in 4.4.0.”
r.Shadow.FadeResolution - which says at which shadowmap resolution the fade begins
r.Shadow.MinResolution - which says at what resolution the fade ends
#My Analysis
So if we can get the two above variable to work, when dynamically set during runtime via the console,
Shouldn’t everything be just fine, I can change those values to enable smaller objects to have shadows at greater distances?
My ability to make an RTS without having to change maps just because I zoomed out from 2x to 3x view distance depends on these two console variables actually working properly!
#Between You and Me
Just so you know Eric I understand this issue is quite a large one and that you are just one person addressing this, so personally, thank you for looking into this and know that I am not expecting you to figure this out all by yourself!
I am however expecting Epic to address this issue since I am aware of many people who are making RTS projects and I am personally working on two different paid projects that are RTS 