[p2035]

@HB_Paul - Can you please comment upon the recent v0.4 alteration which affected random tree locations in the course creator?   Or if not, can you please ask somebody else (Anthony maybe?) to look into it?

v0.4 altered the random tree distribution/location without any input or change from me. 

Before the v0.4 update all 18 holes on my fantasy course had a clear line of sight which was not obstructed by any trees.   I spent a lot of time getting rid of stray trees that were blocking the line of sight to the pin on every hole.  It's a fantasy course with lines of sight that don't always cross over the fairway so random trees must be manually removed by me to clear these lines of sight. 

It's time consuming since it means adding small bunkers or ponds over the stray trees to get rid of them, or sometimes I must move the pin to solve the issue.

But then after the v0.4 update nearly every single hole had 'new' trees blocking the line of sight (which I had to manually remove again, which is very time consuming).    I've never changed the tree slider so it's not even possible that I changed the trees.

I'm really hoping that it was just a one time thing.   Please confirm if that's the case.

Here's my question though: 

Is it possible for courses already published to be affected by this type of bug which alters random trees?   

In other words, does the DNA of published courses contain the exact position of random trees or does it rely on referencing an algorithm or external database which can get altered by bugs when you update the software?

What I'm afraid of is that after I publish my course (and you guys update the software again) then my published course will have new trees inserted which block the line of sight for certain holes.  And since I can't edit a published course there's nothing I can do about it.  My course would be unplayable and broken.

If the DNA of an unpublished course can have random trees altered then why wouldn't it be equally possible for a published course to be affected in the same way?   This is very concerning. 

Most course designers wouldn't have noticed this bug which is probably why I'm the first one mentioning it, since most designers have lines of sight going over the fairway (where no random trees are inserted).   

But for those of us who make fantasy courses (with risk/reward shots that must leave the strict path of the fairway) things are different and it affects us more.

[HB_Paul]

I'll take a look into this or pass this along to someone who can.  Our updates shouldn't effect what happens to the trees/hills etc from already published courses but something may have happened. 

[HB_Paul]

Just a quick question, what theme did you have for the course where you saw this? 

[p2035]

Just a quick question, what theme did you have for the course where you saw this?

Alpine theme.

Tree Slider is set to about 40% full (just short of midway).

[p2035]

I appreciate it.

Oh...  If you have any trouble replicating this problem I have daily backup copies of my ".course" files for the course in question, going back for 10 days. 

So if necessary, I could send you copies of my .course files that were saved in v0.3 plus copies of the same files saved in v0.4.   You could then load my v0.3 files into versions 0.3 and 0.4 to see the changes yourself.  But hopefully you'll be able to replicate without these files. 

[guitardude_324]

I had the same issue, glad to hear I'm not the only one.  I ended up just removing the trees by planting the smallest possible bunkers.  Take the circle brush and make it as small as possible and place the bunker at the base of the tree and in most cases, the tree will disappear.  That's what I did to get around the issue.

[p2035]

I had the same issue, glad to hear I'm not the only one.  I ended up just removing the trees by planting the smallest possible bunkers.  Take the circle brush and make it as small as possible and place the bunker at the base of the tree and in most cases, the tree will disappear.  That's what I did to get around the issue.

Excellent tip.  That's a great way to remove trees.

I just 'hope' this doesn't happen to courses after they're published. 

Can you imagine how frustrating it will be if trees are added to your course after being published? 

It sounds to me like published courses and unpublished courses both use the same tree rendering algorithm for showing random trees (they really have to, since they both render the same set of random trees from very tiny files).  The files are too small to hold actual tree locations. 

It's a scary thought if HB can't replicate this issue and prevent it from happening again in the future.

[p2035]

@guitardude_324: Sometime yesterday I had a few more random trees inserted into my course without any input from me (mostly around greens and fairway edges).   This is odd since it's the 2nd time during the v0.4 update that this has happened.

It's even odder since there was no update yesterday.  So I don't know how it could have switched my trees again yesterday.   

Can you please check your recently published course to verify if 'published' courses are being affected by this tree bug?   

I'm hoping that published courses aren't affected so if you could verify that your course is unaffected I'd greatly appreciate it. 

[guitardude_324]

Sorry for the very late reply.  It has not affected my course after publishing, thankfully.

[Evabar]

metformin

[Evabar]

metformin