7 replies to this topic

[Armand]

I'm wondering what might cause this behavior in the map/top view in PG?  It seems there is a hurricane brewing or something in the overhead map.  I've seen this in more than one course, both PP and user-designed courses.

 

 

 

My computer specs are as follows:

Radeon Software Version - 16.10.1
Radeon Software Edition - Crimson
Graphics Chipset - AMD Radeon ™ R9 200 Series
Memory Size - 2048 MB
Memory Type - GDDR5
Core Clock - 925 MHz
Windows Version - Windows 10 (64 bit)
System Memory - 24 GB
CPU Type - Intel® Core™ i7-4790 CPU @ 3.60GHz
 

 

[SirGrassCutter]

Depending on the time of day you choose you will get skies that look this way.  It is normal.

[SirGrassCutter]

Oops.  I thought you meant the sky and not the map, me bad.  

[Buck]

You mean the billboard trees?

[IanK]

I think it's if you have the time of day set to around midday. It's just the shadows going in a circular pattern.

[Kablammo11]

T'is not the shadow, imho. Buck is right: The top view is "filmed" by a separate, automatically placed camera same as your golfer cam. And from a far distance, most likely on long par 4's and 5's, that camera hovers so high up to capture the entire hole from tee to green that the Speedtree LOD kicks in and reduces the tree details until there are only billboards left.

(All the more since many trees not close to the playing surface are low-res models or other low-poly trees to save performance).

Note how they align concentrically around the center of the map (the camera axis). You will get a lot less tornado trees on a short par 3 or for your second shots into the green, because for these the camera is placed closer to the ground.

 

Perhaps an isometric top cam would be less revealing? Anyway, it's not a bug and it's not a mistake by the designer - it's something that is absolutely logical when it happens. Though it might be nice if it didn't. 

[Armand]

Thanks, all, especially K11 for the detailed explanation (Buck's "billboard trees" didn't really mean much to me, I'm afraid!).  It doesn't bother me much, but since I've seen it a few times on various courses, I thought I'd ask if it was something to do with my video card.  I'm glad it isn't.  I'll try to take note of the hole length when it occurs and if I happen to come to a conclusion of when it does and doesn't occur, I'll post back.

[Buck]

Thanks, all, especially K11 for the detailed explanation (Buck's "billboard trees" didn't really mean much to me, I'm afraid!).  It doesn't bother me much, but since I've seen it a few times on various courses, I thought I'd ask if it was something to do with my video card.  I'm glad it isn't.  I'll try to take note of the hole length when it occurs and if I happen to come to a conclusion of when it does and doesn't occur, I'll post back.

As K nicely articulated. It's the LOD setting.
Nothing wrong at all. Working as intended to reduce detail far away from players physical location and lower the rendering workload.