I updated my QED tonight and it is estimating ball spin on every shot that is under 20mph ball speed. Is this happening to anybody else?
Announcement
Collapse
No announcement yet.
Uneekor update estimating spin on every shot under 20mph ball speed
Collapse
X
-
Yep, someone else posted on this as well. Apparently this issue has actually been in several versions. From the the other post on the same topic, it seems the last version not to have this issue at all was the one from August of 2020.
- Likes 1
-
Originally posted by myrison View PostYep, someone else posted on this as well. Apparently this issue has actually been in several versions. From the the other post on the same topic, it seems the last version not to have this issue at all was the one from August of 2020.
Comment
-
I can only get a few shots to register correctly, then it starts missing shots like crazy. I rolled back to August for Ignite, seemed to work fine, but I don't think it helped with the Swing Optix version of Ignite (Orange Icon). Anyone know how to roll it back?
Comment
-
For others reading this and curious about the new software, the new version seems to be working ok for me. The chips without spin don’t affect my game a lot so that’s not a big drawback. The issue with the club face camera not recording shots does seem to be resolved which is a huge improvement of a big annoyance that has been persistent at least since December.
Comment
-
Updated this morning, and didn’t see any estimated spins...EXCEPT the first shot with each “new club”
But the camera worked for the entire 100 ball session.
- Likes 1
Comment
-
I emailed Uneekor support about the issue I was having and they got me fixed up with a new Z3CamCore file that fixed the problem. After testing it for about 10 minutes, the only shot with an estimated spin was the first one, similar to what 968Cab mentioned. Kudos to Uneekor for getting it squared away for me.
Comment
-
I want to give an update, in case anyone else is running into issues with this. I ended up reverting back to the August 2020 update again after I received the Z3CamCore file due to random misreads and focus problems with the ball view. However, I was on TeamViewer today discussing the issue with Scott, and he said that my CPU was just below the minimum specs and thought that may be my problem. As we were on the phone though, he decided to clean up some files on my C drive as I had the different versions of the software in there so I could roll back in case I was having an issue. Anyways, he moved the old versions to a new, separate folder and everything is working great now. I know this may be a specific quirk, but it is worth looking at if you are running into problems.
Comment
-
I’ll be interested to see if the “fix” holds as it sounds a bit like he’s guessing at the solution. Earlier when I was having problems with the club shot recording starting too late (which was a bug they later fixed), Scott told me my CPU was also likely the culprit (even though it never went above 50% while playing and recording shots).
That’s not to say this couldn’t be the fix and I hope it is, but it sounds a bit like how they assessed my problem as well. In the end which files did you have to clean out of which folder ? It’s worth others of us checking to help verify a real fix if anyone else is in the same situation.
-
You would be surprised on how important clock speed is to CPU calculations. We run into this a lot in eSports gaming titles where professional gamers are looking for that edge of very high FPS and refresh rates above 240hz. It gets to be a real problem when people buy large core count CPUs that do not have the clock speed to meet requests. Task manager is basically reading which cores are running a calculations which isn’t a very accurate representation if processes are being completed on time.
-
I had been following the instructions in post #47 of this thread: https://golfsimulatorforum.com/forum...-sticker/page4. I had the QED_Ignite and Z3CAMsensor files renamed, but still on the C drive with the QED_Ignite and Z3CAMsensor files that were currently being used. Scott took them off the C drive and made a folder on my desktop, and also showed me that the August 2020 update would overwrite all files without needing to do the command prompt stuff.
-
Comment