Looking for some help with my GC3 / FSX play software. The numbers like carry etc match fine when I use FSX 2020 but when I use FSX play the carry is always a yard or 2 different to what's displayed on the GC3 unit, the launch and ball speed always seem to match but carry and backspin are always a little less on FXS play. Happens on the ranges or courses, i've tried tweaking the weather and temps and make sure the unit it set to barometer along with making sure FSX play is set to Your Altitude. Am i missing something?
Announcement
Collapse
No announcement yet.
GC3 with FSX play, Numbers not matching
Collapse
X
-
I'd be really surprised if the room settings affect ball data, I don't know that it doesn't, but I can't think of why it would. I think the room config tool only alters the way the image is projected on the screen, items such as centerline, depth of field, bottom of image etc. As far as the data discrepancy on spin & carry, are you referring to the data tiles that are shown on FSX Play as compared to the screen on the GC3?
Comment
-
Yes that's right, the data tiles on the bottom of the projected screen from FSX play. They are always less than what's displayed on the GC3 unit. Thanks for your help.Originally posted by MongoOnlyPawn View PostI'd be really surprised if the room settings affect ball data, I don't know that it doesn't, but I can't think of why it would. I think the room config tool only alters the way the image is projected on the screen, items such as centerline, depth of field, bottom of image etc. As far as the data discrepancy on spin & carry, are you referring to the data tiles that are shown on FSX Play as compared to the screen on the GC3?
Comment
-
I recently upgraded to FSX Play and the first thing my friends and I noticed is that the ball seemed to curve a lot more than in the old software. It makes me wonder if they didn't implement spin degradation or have other problems with the model in the new software. Given how many other problems/bugs there are in FSX Play, it wouldn't surprise me if the ball flight model is wrong too.
Comment
-
I whacked some balls, and while there were discrepancies on spin and carry, they were minor, could've just been rounding errors, looks like the screen tiles don't carry out the decimal point on some of the data. Spin was always right on, carry was nearly always within a yard.
Regarding the curving, I agree with sinkingputts, the camera angle/display looks different to me also. If I'm watching ball data on the quad, I'm never significantly more offline when using FSX Play as opposed to FSX 2020 or FSX Pro. I think it might be like the tree discussion/issue on Play vs 2020. I think Play is more accurate on the effect of hitting into a tree, like real life, whereas 2020 cut me a lot of slack sometimes.
Comment
-
I did some additional messing around this morning, and experienced the same thing you were describing, though this time I played a few holes rather than selecting the driving range. The previous shots were done on the Kinsale driving range, today's data was from La Jolla, so now you've got me confused as well. I'll have some time later next week to do a little more in depth comparison, will try to respond on the thread prior to Christmas Eve.
Comment
-
I tried this as well with my quad on a hole not the flat Paris driving range and i see that it was giving me the adjusted number where that carry would have been on the down hill slope of the hole i was playing Home Spy Glass which is like a 50ft drop from the blue tee. The top of the quad was giving me around 280 carry and the FSXplay tile bar said around 305. This was obviously do to the slope. I wanted to ask a follow up question did you test this out at the flat Paris driving range? Was it different on flat ground?
Comment
-
The sidespin on Play is way more than 2020. To the point where I do not even play on FSX Play. Have friends over that are scratch golfers who were hooking into the weeds every drive. Launch FSX 2020 and no issues at all. Any ideas. Foresights support is the worst I have ever tried to deal with. Got a one word answer from support 5 weeks after email was sent!!
Comment
Comment