Jump to content

Badger

Members
  • Content Count

    142
  • Joined

  • Last visited

Everything posted by Badger

  1. It seems to me we had this issue with amd in the past...and it was fixed....then resurfaced (and if I recall correctly you had said it would be addressed in a future patch(now historic)since we're what?...3 patches in ? I'm just wondering if those legacy fixes have been implemented?Again this was alonggg time ago,so my memory maybe faulty.
  2. if you need too I can easily go to comms and tell ya all thats happened in past sessions...might be easier than form post tag...I'm just sittin here hunting american warships in my akula in coldwaters
  3. I think it also needs to be said that what promted me to do this test was similar issues in multiplayer on all sorts of maps....this tank range map I used cause it was easy to duplicate tests and I knew just where to look.I'm hoping by solving this issue it will apply itself to the game as a whole.(I really thought it was some tree model issue..but now I'm just perplexed)
  4. rgr standby. Its the only "large" panel on the right.Also note that if I pan right further off the panel fps still remains low...which is about the 130 to 200 position on tank clock
  5. looking at the reference panel to the right edge of the gunnery range engagement area gives you 40 fps in the best of cases yes best case...constant 29 on settings with V sync balanced (or max energy saving) power settings (Windows 7) fullscreen mode looking anywhere else in the same scenario gives you around 60 fps, give or take a little yes whenever one or multiple of the following settings are activated, you drop to 29 fps, V sync balanced (or max energy saving) power settings (Windows 7) fullscreen mo
  6. dis regard...brain fart getting tired
  7. checking...just to clariy last....the res changes were not in window mode....the sucessfull 40fps Is in windowed mode drivers up to date 20.8.3 no new up date published in control panel news at this time
  8. yes to all with 1 exception...when I lowered res to 1280...it dropped fps....1152 res doubled fps on target panel(scratching my head on that one) this being in full screen btw not windowed
  9. Just to prove I Ain't lie'n vsync off and windowed with power to performance combo that got me to 40...and this is WITH graphics and terrain settings turned back up including terrain cache At 1680 x 1050 and with aa and ansio and shadows.TrackIR on.GPU Stayed cool 66 Celsius
  10. Power settings no change BUT with vsync off AND in windowed mode putting the sight on the target panel in tank range bounced it to around 35-37 ( it fluctuated) please note panning anywhere else in tank range would go as high as 66fps...its just I wanted to use the same aiming point (the target panel )for reference and its where it falls to half FPS. edit...my mistake...power settings didn't take...retried and got to 41fps. So it did something. So I think I'm at 40 ish on that panel now.gonna do more tests edit 2 DAMNIT NO IT DIDN'T WORK ,TRIED IT BY ITSELF STILL 29
  11. I'm Windows 7 and I'm now going to try those power settings ,it was set to balanced
  12. Tried to override settings in radeon control panel AA,Ansio etc....I "upped everything" so it should have dropped from 29fps...It didn't
  13. going down to 1280 res made it worse 19-20fps but 1100 res hit high 50's
  14. EVERYTHING turned down trackIR off at 1680 x 1050 on tank range target panel 29 fps.Gonna try different resolution now opps wrong res...corrected
  15. I do run trackIr...gpu is around 70-77 Celsius which is in normal ranges,drivers are up to date.I will try it without trackIR. However I also run DCS at high settings and get 30-40 in cockpit higher in external...which says alot. BTW...external view in sb is alot lower than test screenshots FYI which adds insult to injury,
  16. All sliders were minimized too far left in those last few screens...so 4gig of graphic card ram isn't enough?That doesn't seem right. In test 2...those screens were not minimized (cache was set to full)and the difference is only a few frames,6 to be exact(the above shot on the target panel is more as its windowed). Plus the direct above shot is trees also and 52 fps.Doesn't make sense.
  17. Is it the trees??? watch what happens when I look to the left...52fps.BTW thats not a lase to the trees...its the range of a previous tank kill
  18. BTW windowed mode...small change,3fps
  19. Is it possible to swap the trees out for older models??...better yet make it an option...then we could run 4.167 on older machines...just sayin.
  20. So there's something wrong with the trees then...As I was also staring at them in 4.023...and getting 40-50ish vs 6-29ish, maybe you need to do something about optimizing the trees??
  21. Yes I can turn a lot down in different aspects...BUT...the real question is WHY am I only getting 29 fps in a scenario where nothing is really happening on a AMD FX 8350 4.0 Ghz CPU , ATI RX 560 4 gig GPU ,32 gig ram on Win7 64bit,1TB HDD. system under 4.167????...on minimal terrain settings???
  22. There is no senerio...its the tank range in the M1a2. System1 is AMD FX 8350 4.0 Ghz CPU , ATI RX 560 4 gig GPU ,32 gig ram on Win7 64bit,1TB HDD. System2(older) is Amd quadcore 3.6ghz with 8 gigram,radeon 5770 graphics 2gig card, 500mb HDD Remember this test was on 2 different systems.The point being even on the newer system 4.167 runs like a dog.Where as 4.023 runs like a dream on BOTH old and new systems.
  23. This is a screenshot of terrain settings set to minimal on the newer system.It's only 6 frames above 24 frames per second.keep in mind also this is the tank range where there's nothing really going on.
×
×
  • Create New...