|
Post by Jared on Feb 21, 2016 18:55:22 GMT -5
I think I average 110-ish FPS on most courses on high detail (but low tree draw distance) with my 980 Ti at 1080p. I've seen that number drop to below 45 on some of the courses, at which point I just go to medium settings and hold a constant 144 fps. Honestly I'm fine as long as the fps doesn't dip below 60 fps, at which point it becomes really noticeable. Great for other games, but I don't think TGC is optimized enough to warrant the GPU alone. With regards to the question asked in the title, 64-bit has given me problems again recently (crash on load screen) so I just end up staying on 32-bit. There was one course in particular that would always crash on 64-bit. I can't remember which PGA course it was. I'm curious about that. Can you post the specific settings (Detail, HD Trees, Tree Distance) you use? Yeah, sure. Any course in particular you want me to use? I tend to change my graphics settings depending on the course. A few courses really destroy the framerate after like 2000/500 on high, especially since I'm still seemingly forced to use 32-bit.
|
|
|
Post by Andrea on Feb 21, 2016 19:00:22 GMT -5
I'm curious about that. Can you post the specific settings (Detail, HD Trees, Tree Distance) you use? Yeah, sure. Any course in particular you want me to use? I tend to change my graphics settings depending on the course. A few courses really destroy the framerate after like 2000/500 on high, especially since I'm still seemingly forced to use 32-bit. I'm giving you three - but generally I was curious about the margins you work with. Anyways: Magnolia 2016 (Sunday), Spectacle Island (FRI) and Bethpage Black (the new BoomBomm's one) Thanks mate
|
|
|
Post by Brighttail on Feb 21, 2016 19:15:16 GMT -5
Just tried it again with a previous and most current version of the NVIDIA driver. I get to the "click enter' click it and boom .. crash.
So disappointing.
|
|
|
Post by Jared on Feb 21, 2016 23:25:46 GMT -5
Yeah, sure. Any course in particular you want me to use? I tend to change my graphics settings depending on the course. A few courses really destroy the framerate after like 2000/500 on high, especially since I'm still seemingly forced to use 32-bit. I'm giving you three - but generally I was curious about the margins you work with. Anyways: Magnolia 2016 (Sunday), Spectacle Island (FRI) and Bethpage Black (the new BoomBomm's one) Thanks mate Alright. Using EVGA GTX 980 Ti SuperClocked+ ACX 2.0+. OC'ing the GPU (stable at +150 MHz GPU/+450 MHz Memory, no extra voltage) increases the framerate by 5 fps at most. CPU is an i7-4790k @ 4.0 GHz (not OC'ed currently) and shouldn't be a bottleneck. High quality setting from the load menu, object detail 3, tree count 2000, tree distance 500 (I want to see the rig that can do 1080p 20k tree count without dropping below 60 Hz, lol. I remember brighttail mentioning that SLI doesn't help too much with TGC). G-sync is on and it's at full screen 1080p. 32 bit because TGC still continually has issues with 64-bit and NVidia drivers. Just sitting at the first tee. Magnolia: 70 fps Spectacle Island: 85 fps Bethpage: 60 fps Lowering the object detail to 2 raises the fps by 20-25 fps. Also, fps increases by about 10-15 while using the scout's cam. Generally hits 130-144 fps tracking the shot itself (even at bethpage). I normally play at 900p in windowed mode since I use my other monitor to do things while playing rounds. But every once in a while it's nice to full screen. Even at "low" object detail (2), the game looks pretty nice. From what I remember, with the "medium" load settings, I can push the game pretty hard before losing the stable 144 Hz.
|
|
|
Post by Brighttail on Feb 21, 2016 23:53:21 GMT -5
I have two 980 GTX in SLI with a i7 5930k. Both are overclocked with the CPU at 4.7GHz. On my old Asus Swift monitor I was constantly getting 120-140FPS. With the Acer Predator x34 I'm getting 70-90FPS. Honestly I really can't tell the difference tween the two except the new monitor is much wider. I play at full windowed resolution 3440 x 1440. I have left the game at the original HIGH settings and I think there has only been two courses where I have gotten some frame stutter. Don't remember which ones but it was minor.
I'm running the game on two Samsung 950 Pro m.2 256GB drives running in raid 0. I've run the game using a RAM drive and it is about the same speed. Sadly my internet connection is only about 10MBs so ... meh. Overall it flies.
Never thought about lowering the object detail.
|
|
|
Post by Andrea on Feb 22, 2016 1:12:49 GMT -5
I'm giving you three - but generally I was curious about the margins you work with. Anyways: Magnolia 2016 (Sunday), Spectacle Island (FRI) and Bethpage Black (the new BoomBomm's one) Thanks mate Alright. Using EVGA GTX 980 Ti SuperClocked+ ACX 2.0+. OC'ing the GPU (stable at +150 MHz GPU/+450 MHz Memory, no extra voltage) increases the framerate by 5 fps at most. CPU is an i7-4790k @ 4.0 GHz (not OC'ed currently) and shouldn't be a bottleneck. High quality setting from the load menu, object detail 3, tree count 2000, tree distance 500 (I want to see the rig that can do 1080p 20k tree count without dropping below 60 Hz, lol. I remember brighttail mentioning that SLI doesn't help too much with TGC). G-sync is on and it's at full screen 1080p. 32 bit because TGC still continually has issues with 64-bit and NVidia drivers. Just sitting at the first tee. Magnolia: 70 fps Spectacle Island: 85 fps Bethpage: 60 fps Lowering the object detail to 2 raises the fps by 20-25 fps. Also, fps increases by about 10-15 while using the scout's cam. Generally hits 130-144 fps tracking the shot itself (even at bethpage). I normally play at 900p in windowed mode since I use my other monitor to do things while playing rounds. But every once in a while it's nice to full screen. Even at "low" object detail (2), the game looks pretty nice. From what I remember, with the "medium" load settings, I can push the game pretty hard before losing the stable 144 Hz. That's a great report Thanks!
|
|
|
Post by kireishoujo on Feb 22, 2016 1:28:04 GMT -5
I just really need the AMD issue fixed.. It's been long enough.
|
|