Jump to content

Punisher74

Members
  • Posts

    357
  • Joined

  • Last visited

Everything posted by Punisher74

  1. It's seems to happen just as the FPS dropped while running 2 cards, and I agree no games are running on 8 cores, I just feel that it maybe pulling requests from the CPU pinging anything available to find the fastest route to get the FPS back to normal.
  2. Most definitely sticking to one setting you get the same results no matter the test, but switching it up lets them know at different settings there are still issues just different results. On that image is was 4x msaa and 2x atf. Not everyone has high end cards. On ground warfare 16x ATF and 4x Msaa is stable as long as only one card is activated, 2 cards major dips. When I first saw the pixels issues I thought of the movie pixels. And snapped them.
  3. Not Sure what this is but I found it Over Kutaisi Airport.
  4. Truthfully there are so many threads all with the same issues, FPS drops, micro shutters, crossfire fire not working causes FPS drops, memory leaks, high CPU consumption, etc. I think they know.
  5. It shouldn't matter if the game is installed on a HD or a SSD drive there should be 0 shutters or FPS Drops like others are experiencing.
  6. I understand but a simple reported will stop the multiple reports of the same issue.
  7. I've had flights recently where my CPU had maxed out on all 8 cores. I turned on onscreen display of CPU cores, memory, GPU usage, FPS, etc. and had all 8 cores reading 100% for more then 10 secs. Could be processes running in background or DCS processes, but the devs need to know everything so we get a great simulator.
  8. With a little touch up yes. It's hard to believe the A-10C is straight off the assembly line.
  9. DCS Moderators I've noticed bug that are reported in this forum threads have a [REPORTED] mark in front of them. Why have FPS, and Crossfire/SLI ones haven't been. People are having serious issues with FPS drops with card 100% within the DCS requirements, yet aren't reported or are with no notification. Please keep use informed so we can move forward with other testing. Thank you!!!!!
  10. I noticed that I switched it to monitor capture and it started recording fine with crossfire enabled. If you can please close this out. Thank you.
  11. No the A-10C in DCS 1.5 with lower texture setting is blurry. just look at the record switch on the left of the cockpit, and the HSI at Medium and Low Textures. Actually in DCS 1.5 when you lower the Textures in the options menu the Cockpit's text becomes blurry in DCS 1.5. In DCS 1.2.16 there is a zip file in \Bazar\World\textures\ called CockpitsHDTextures.zip that prevented the lower textures settings from making the text in the cockpits from being blurry.
  12. Yes I turn it off when running afterburner to record videos no change. Has anyone noticed the insane CPU usage? All 8 of my cores were running at 75% or more. RAM started at 6.5 GHz and ramped up to 8+ Ghz. I'm thinking of assigning 1 core straight to DCS to improve performance.
  13. Why does 1280x768 auto start DCS in crossfire mode but HD resolutions don't? Is that a bug?
  14. I was just about to post that. Just flew 2 missions on high 1 day, 1 nightfall was just happening both mission averaged about 75 FPS with msaa 4x and ATF (anisotropic filter) 4x. With 1gpu at full clock speed of 1120 Ghz
  15. It's not my system other games work fine. No serious lagging issues like in DCS. Checked all drivers, CCC drivers, played other games like Arma 3, h1z1, SC, all checked out no lag issues in game. I lowered all the setting in DCS to mediumish settings and was able to lock 60FPs but as per AMD high settings across the board should work in DCS. It's a beta I get that but a card that's mid grade should handle way better. DCS 1.2.16 It was a solid 40 to 50 FPS with slight drops in gun runs and loading. With dx9 & 1 card. Now common sense says if I get that on dx9 I can get like at least 75 to 90 on high settings in DCS with dx11 with 2 cards. When I say high I mean everything but trees. Let's say 3000 trees. Well you saw the results. I'll sometimes load into a mission I make with 120 FPS, taxi drops to 80, takeoff drop to 50. There is a huge memory leak (already reported), that's the issue. ITS A BETA!
  16. Not vsync, there is a setting in nvidia or catalyst where you can lock the FPS. Vsync eats FPS
  17. A temp fix is to lower as much to medium, turn off shadows, DOF keep the terrain textures to high, tree's to 1500, you can also lower the preload distance, lock your frames to a max setting lock ie. 60FPS max, no lens flares. in other words try to keep the plane and weapons systems looking round like in the real world. I was able to get 60FPS with MSAA at 8x and AA at 8X. that with crossfire enabled in the F-15C and close to 30FPS in the A-10C. I was getting better FPS in DCS 1.2.16 which makes no sense since it was out dated DirectX. Anyway I've been running changes to settings all day and that's the best I found. I hope that they fix these issues with FPS, Anti-Aliasing, FLIR FPS Drop, Memory Leaks, etc. soon.
  18. You're not the only one, I think a lot has to do with the GPU handling too much. Before in DCS the graphic rendering was handled by the CPU. Now it's handled by the GPU and unlike the CPU the GPU has 1 or so ghz where as a CPU has 3+ ghz. I think a multi GPU and CPU handling of bothe game performance and rendering will help a lot. But it also could be memory leaks, or just a poor handling of graphics api. But it's a beta so for now we just need to take the good for the bad and trust they will be resolved. Just gather as much proof and post.
  19. so I finished on the A-10C and moved over to the F-15 thinking the performance would be better since there is not FLIR or MAV. While I was seriously wrong, the FPS issues with moving your head, loading of new objects, trigger actions, etc. are insane. I'm talking losses of 120 FPS to 7 FPS with MSAA at 4X, and 50+ FPS to 6 FPS with MSAA 8X Both with CCC Anisotropic 16X just in the parking area. I use Anisotropic Filter in CCC because its doing the calculations on the card and not thru to game to the card faster response thru the card. MSAA is not a option thru the card. Video is Uploading to YouTube and will be added shortly so please check back. Please verify the video is playing at 1080P for best quality!
  20. I basically turned off every setting in CCC to Use App settings, and only tweaking in-game settings. I just uploaded all the Hardware monitoring log file, images of AA issues and more to this post so the devs can see and make adjustments to the memory usage, AA, etc.
  21. For me alt enter will not engage 2nd GPU if using OBS.
  22. I have AMD cards not nvidia.
  23. That not in game settings. It's the cards settings CCC = catalyst control Center
  24. I completely agree, it's a Beta version. There are supposed to be issues to be ironed out. As for my display I'm only running at 1080p on a 55" Samsung 240 Hertz HD TV. But that's only for now. 4K comes next, and higher GPU's. Also with the extreme support behind DCS 1.5 I'm sure the Dev team is overwhelmed with bug reports and I'm certain ED will square away this game by its 2.0 release.
  25. I tried 16x msaa all I saw was a washed out runway, and the jagged edges was still there. A tried 8x msaa and 8x anisotropic and was better but with TGP off and mavs off when I hit the 150,000 preload I also noticed a 50% drop in FPS to load the screen. I think multi GPU and CPU support would fix that. Also the heavy memory usage should fix loading of new objects. CPU has 4.0ghz and GPU has 1120ghz you'd think multi GPU and CPU support would make things much more smooth.
×
×
  • Create New...