New South Wales Golf Club

[dwg]

Sigh,

Bugger, about all I can say that is printable.

I do not see the problem on a Windows system with Nvidia and no wrapper.

I am not seeing it on Linux (2 systems)

Putting dgVoodoo back onto the machine, I do not see it either.

I will post a question to the DDrawCompat wrapper developer to see if he has any ideas, at best I would like to think it could be corrected with a config change.

Des

[Colin Jones]

On a bus touring Tokyo. Excuse any typos!

I gave a heads up about this on the download page. The effect appeared very late in the design. And around the same time I installed the new wrapper. But this may be a coincidence

It’s similar to the effect of an errant overlapping vert. For the life of me I still can’t find one tho.

Colin.

[dwg]

Ahh so that is what the reference is to. I assume then that the 3rd must be adjacent.

Even on that machine it only occurs in some positions, they can be hard to find, seems I have been landing around the same spot.

I am seeing something unusual on that hole on the hill on the right hand side, there is a white square, related perhaps?

FWIW I just get a colour streak across the screen when in certain positions, if I trace it back it would seem to go through that white square.

I get the square on my Nvidia Desktop, have not been able to get the large object though.

[Ian Wells]

When I first saw the image from Des I thought it was a vert that had been unintendedly dragged from it's actual location and felt great sympathy for Colin having to find it with a 2m DEM.

I opened the course on my All in one with AMD graphics card and there was no problem.
On my laptop with the new wrapper I could see the problem clearly.
As Des says it is very position specific. Moving the ball a small distance in any direction changes the graphic.

NSW3_1.jpg (988.42 KiB) Viewed 125 times

NSW3_2.jpg (996.05 KiB) Viewed 125 times

Surely if it was a stray vert it would show on all graphic cards(?), therefore to my simple mind it looks like a problem with the new wrapper.

Good luck.
Ian

[dwg]

I see you are getting that white square as well Ian.

[dwg]

Ian,

Could I get you to try something for me?

Edit the DDrawCompat.ini file. and set VertexFixup = cpu

For example my file has:

# VertexFixup = gpu
VertexFixup = cpu
# ViewportEdgeFix = off

# is the comment character and the entry following it shows the default setting for that setting.

Save it and retest hole 3

Thanks

Des

[Ian Wells]

Des,
Sorry for the delay, I was having lunch.

When I did what you asked I got this message:

DDraw.jpg (100.17 KiB) Viewed 86 times

What next?

Ian

[Ian Wells]

Des,
The white square is a waste bin next to the tee.
I'm off to watch the football, will reply in the morning.

Ian

[dwg]

Ian,

It looks like you have installed Links in the default location in Program Files, hence you get the security message.

The easiest way is to copy the file to an unprotected folder like your document folder, edit it then copy it back, when copying it back Explorer will show a pop up asking for permission but will do it when you agree. I would think you got that pop up when installing any wrapper.

This security is why when installed into the default location you have to start Links with admin privileges since Links itself can and does write files to this folder, when installing courses for one thing, if you choose to place it in the course folder.

Many of us install Links to a folder right underneath the C drive to avoid the hassle.

FWIW I must have spent half an hour or more after making the change then moving the ball around to see if I could get the artifact, but couldn't.

So that is what the white square is, it certainly stands out.

I spent the afternoon watching golf, there was a tournament in Adelaide, you have to watch golf here when you can we do not get much and there is not that much in a decent timezone for me in any case.

Des

[dwg]

For information the developer is taking an interest in the problem, he has been very responsive all the way through with issues on Links, we have had excellent support.

I have uploaded a saved practice round, as he has not been able to reproduce the issue, and requested such. Given how positionally dependent it is I am not surprised he did not see it. I found it as I played the same sort of shot a couple of times and landed in the same general area so saw different effects.

I am still interested Ian in if my change of option resolves the problem for you. It may be a long term fix or could potentially highlight where the problem is in the wrapper.

As it stands he has built a version of the wrapper for Links to resolve some issues and we have used config options for some others.

Once we have an outcome I will look to update or to have updated the discussion on this wrapper, depending on the resolution.

Des