Sand Wedge Sailing

[Maverick]

So, did this work for you?

[derekney]

I installed the latest beta (k29) and tried with my current settings and it worked the same.

I then tried the settings you suggested here (Pitching_use_clubspeed=True, pitching distance 100, lob wedge selected, etc.) and unfortunately the same problem happens. I get some (few) anomalous hits where the club speed is in the nineties and ball speed is over a hundred. The rest of the hits are more normal with 50s and 70s.

See attached with interface screen with super long hit.

[ProTee Dennis]

What might happen here is that your club is passing the balltrack sensors in front way before the ball does.

Your lobwedge follow thru especially with a very open face will give a very fast speed when going low over the sensors. The system expects a ball high in the air but finds the club low on the floor.

[derekney]

Well that could be the case, but don't other people have the same problem? I thought this was what zmax was getting at with the pitching distance and such.

[derekney]

Some more information (grasping at straws here)...

1. About once or twice in a round, I drive off the tee and often hit a very nice feeling drive and... nothing happens. It just did not register the swing at all. Is this normal? I just take another swing and it works fine (of course it is almost always a worse swing :*().

2. I did have a problem with the location of the settings.pgs file. I have this installed on a Windows 7 system. It seems that my settings.pgs is in this folder:

C:\Users\Golfer\AppData\Local\VirtualStore\Program Files (x86)\ProTeeGolf Interface

I determined this by looking at modification time and the contents of the file after it gets edited. Note that the username for my login is "Golfer".

But there is also another one in "C:\ProTeeGolf Interface" and also in "C:\Program Files (x86)\ProTeeGolf Interface". But those do not seem to get changed when I edit with Alt-E from the interface program.

Actually, I am curious about the "C:\ProTeeGolf Interfac

[ProTee Dennis]

To be able to control the pitching distance is not related to what I see on the analysis screen you posted.

This really depends on your swing and how you address the ball. The system can handle high angle lobwegde shots fine and you can control the distance with the latest updates that zmax is referring too.

For example If your hands are too much in front of the ball its very likely that the club will pass the sensors before the ball. This is because the ball track is very close to the ball. Some people do not have this at all and some have it on some shots only.

Lobwedges and the way they are played, wide open faces and shanks are a simulators worse nightmare.

[Maverick]

This is why I wanted to remote in. Having multiple settings file is bad. Damn Windows.

[ProTee Dennis]

Derek,

You should use the integrated settings file editor. Do not edit the settings files manually.

Your windows security system has created a virtual file store where it holds the active version of the settings file for each user. In the past this system was set off by default. Windows has turned this all on by default due to the amount of security issues they have with their OS. You know need to grant access to almost anything you want to change on your own PC.

The integrated settings editor bypasses these security issues.

[derekney]

I see what you are saying. But what I am having trouble with are not really what I consider "flop shots". I am giving a full swing on my sand wedge. I am not opening the club face at all. I expect a 60-65 yard ball flight.

[Maverick]

I can remote in now.

[Maverick]

I did two remote sessions with Derek. I deleted the extra settings file and got the cameras looking good. All the settings also looked good. But this is one strange problem.

The pitching settings do work but 1 out of every 4-5 shot will go too far. Analysis screen/interface screen will show a very high LW club speed(90mph) and very high ball speed(100mph).

Lets get Protee to remote in.

[Maverick]

Derek,

What kind of light did you say you had above the hitting sensor?

[derekney]

I checked. It is a 75W halogen with a 20-25 degree spread. It is up higher than normal (11' 8").

[psace]

I am using a 50w light over my hitting sensor from the same height as you and a 75w 25 degree bulb over the putting sensor. It works great for me. The height of the light does seem to make a difference. Just something different for you to try.

[psace]

[quote="Derek Ney" post=1799]Thanks all for your comments. To answer some specific questions:

No, there is no debris on my sensors.
I do not have two shadows, just one nice and crisp one.

The problem is still happening. It seems I can reproduce it with some consistency by doing this:

Start Practice mode, chose Monterey Beach course.
Move ball position to 90 yards from first hole pin.
Choose Sand Wedge from Club menu
Hit normal sand wedge shot.
It almost always will sail 95 to 105 yards with a club speed in the 70's or above.

If I then hit some more sand wedges it will do the same for a few shots sometimes
and then more or less settle down to more normal shots and club speeds.
I am leaning towards this being a software bug or a hardware problem with my sensor mat
or maybe the peripheral interfaces.

I did try an experiment. Set things up with the step by step above but on my first
shot I went to the interface window and brought up the Debug window. I used my
sand