10 replies to this topic

[DoGgs]

Help!  take a look at this screen and please tell me what i have done or not done, it appears that my bunkers are not snapping to the terrain, in CF it all appears fine, it's only when i build the course then play test it that this rears it's ugly head...i'm at a loss 

[pingzing]

Hi Dogz - looks like you chose quick sand for the bunker mate, you might need to add some rope around the bunker so we can pull him out, good way to fix up your opponent.

 

Very clever and sneaky of you to do that -  LOL

 

Wish i could help but my problems are bigger than yours with C/F- High elevations are causing me problems with the mesh, 

 

Good luck mate

[Kablammo11]

It looks like you did not enclose your fairway and bunker with a semi-rough or rough layer. What you see is what you get - what you don't see is what you haven't added. 

 

Rule Nr. 124b: ALWAYS, ALWAYS, ALWAYS, ALWAYS, ALWAYS, ALWAYS enclose your meshes with a rough or deep rough mesh. Sounds a bit nit-picky, I know, but now you can see why that is.

Looks nice, though. Good job!

[highfade]

It also looks like you clicked the bunker preview button and then had your course build.

[Kablammo11]

Don't think so, Adriaan. Leaving the preview on or off should in no way influence the build of the course. This lowering of the terrain underneath the bunkers is always done automatically when building a course. The preview button in CF is showing you in advance what the build will do to the terrain. And here, it was lowered below the bunkers to avoid the base terrain sticking out. Of course you can't see this in most builds, because this part is supposed to be covered by rough.

[DoGgs]

Kablammo11, on 03 Aug 2015 - 08:02 AM, said:

It looks like you did not enclose your fairway and bunker with a semi-rough or rough layer. What you see is what you get - what you don't see is what you haven't added. 

 

Rule Nr. 124b: ALWAYS, ALWAYS, ALWAYS, ALWAYS, ALWAYS, ALWAYS enclose your meshes with a rough or deep rough mesh. Sounds a bit nit-picky, I know, but now you can see why that is.

Looks nice, though. Good job!

I think you may be right about the enclosing...going in to test now!   ty

[DoGgs]

yes! forgot to enclose, thanks kablamo   i can finally move on to the next hole....love this designer, have enjoyed the golf club's creator but this is amazing....so much fun!

[Kablammo11]

Where's that BEST ANSWER button coming from? Never seen that before.

Your enjoyment is plainly visible in your image, DoGgz... Keep having fun - and we all will.

[highfade]

Kablammo11, on 03 Aug 2015 - 09:30 AM, said:

Don't think so, Adriaan. Leaving the preview on or off should in no way influence the build of the course. This lowering of the terrain underneath the bunkers is always done automatically when building a course. The preview button in CF is showing you in advance what the build will do to the terrain. And here, it was lowered below the bunkers to avoid the base terrain sticking out. Of course you can't see this in most builds, because this part is supposed to be covered by rough.

My bad,  looks like I'm still a bit rusted.

[Mike Jones]

Yeah I'm thinking of removing the preview mesh icon as basically it can cause issues. It really doesn't serve too much of a purpose now you can just load up the course in game and play it.

[Kablammo11]

I don't know, I like to use it for reassurance when certain deep bunkers show portions of the base terrain. If you excavate them deep enough, the terrain will always protrude and I still need to see the finished bunker to assess its viability. Also, the mesh preview is always helpful for making screen shots to show to the general public, as it makes sure of clean bunkers instead of showing, well, ungodly visual messes.

No idea if this might also come in handy on that fine day when we get POT BUNKERS!

Seems also a bit facile to get rid of something just because it's partially defective, rather than to try and make it work. Making a build and loading up the game to go check on bunkers? Surely there ought to be a less complicated way!

 

So I would recommend leaving it in. To avoid certain nasty side-effects, how about programming it in a way that the moment another icon is being activated (or CF is switching to the Unity terrain engine) it automatically toggles off?