Jump to content

Punisher74

Members
  • Posts

    357
  • Joined

  • Last visited

Everything posted by Punisher74

  1. Also OBS turns off crossfire when using it to record or stream. http://forums.eagle.ru/showthread.php?t=148697
  2. Please show screenshots. So we and the devs can see
  3. I agree it needs to run only once in-mission not in main menu, and no need to press anything. There is nothing I hate more the having to press extra buttons to get performance you should. That's what the SLI & Crossfire enable/disable options are for. And I stated it happens to me as well referring to FPS Drops with FLIR and Maverick
  4. Not for me, with crossfire off I'm seeing 90 FPS, with crossfire on with Both cards GPU rocking 1120 MHz I'm getting 125+ FPS. Read my specs to see my cards specs. I see FPS drops in game with FLIR & Maverick screens running. Never on main menu.
  5. I was attempting to record FPS and anti-aliasing issues using open broadcast, and while recording I noticed the AMD Crossfire logo was missing on upper right. Hit LALT Enter screen reset still no logo. Tried again same. Closed DCS reopened and hit LALT ENTER and sure enough there. Turned recording on same thing again. I'm using the game scene plugin not window. This setting pulls straight from dx11.
  6. And there no difference on too. Just slight drops in FPS.
  7. Another thing I've noticed and the under performance if Anti-Aliasing filters. with MSAA Set on 4x the close lines are jagged, the FPS is very high the distant mountains edges look great, but runways, Power lines, distance bridge outlines all look horrible. I'm not talking major distances on these runways i'm talking with in 75 to 100ft and greater. its the constant flickering of the whit noise within these edges. People may say its your video card, but truth be told its designed for DX 11 and up and well within the means to handle 120 FPS and Greater at MSSA settings of 4x with 0 drops in FPS and not have such shuttering of the edges. as per AMD with MSSA at 4x the lines should be smooth with a mild sharpness and 0 whit noise. In-Game Anisotropic Filter 16x Model Visible Enlarged MSAA 4x CIV Traffic, heat blur off All Shadows off Water Medium Everything else High CCC Settings AA Mode, Samples Use app settings Filter Edge Detect AA Method Super Morphological Filtering on Anisotropic Filter Method, level Use App wait for Vertical Refresh off unless needed by app OpenGl on Tessellation Mode and level AMD Optimized Frame Pacing On Crossfire Default or 1x1 both give same results Please note I've been testing out different settings to find the best performance for both in game and Card workload. Look Thru the HUD Out in the distance passed the taxi way Passed the bridge in the distance In the distance just below the mountains FPS Drops and hardware monitoring files of gameplay.zip
  8. It shouldn't I assume it's a way to preserve the 2nd GPU from not being over used. The LALT + Enter is like a bypass to tell the 2nd GPU to enter high performance mode at all times. As I wrote the FLIR still drops my FPS by 36% 110 FPS to 40 FPS.
  9. It should show a difference, after I was shown the lalt + Enter turned on the 2nd GPU my start up A-10C FPS is 120FPS then I get the A-10C started up FPS drops to about 110fps takeoff and fly to combat area still about 110 FPS as I turn the MFCD to TGP ON FPS DROPS to 40 FPS if lucky. That's with the pit res at 1024 and 512. That a major bug!!!
  10. yes each different position kills FPS in different ways. Center switch is the best out of them all but its harder to find enemies. and that's even Crossfired.
  11. Proof if not working in full screen mode. Well it looks like it's not but it is. Just that it is not setting the clock speed. For example. Gpu 1: 1120 mhz Gpu 2: 300 mhz Mem: 1400 MHz Mem: 150 MHz Should be Gpu 1: 1120 mhz Gpu 2: 1120 mhz Mem: 1400 MHz Mem: 1400 MHz Because that's what the settings are. Now I did notice it runs correctly, but it's loading the game into a mission not while you fly. The bug might be that the high performance mode isn't set on the 2nd GPU like for the primary gpu. The second GPU api in the line code must also reference that setting to match the primary GPU. Or the second GPU will end resting desktop mode.
  12. There's more to it the second gpu runs in OC mode while loading the flight then turns off OC. If DCS is intending to have better graphics performance using multi gpu then OC my de should stay on at all times in simulation and MP Simulation.
  13. My fans always run at 90% in CCC, the test I ran was in afterburner and that one has fans manually set to 73%.
  14. ran some indepth testing today on DCS 1.5 here are my results. with xfire running. I found that xfire does work kind of. The second GPU switches from 300MHz to 1120Mhz in the preload screen only, never in game 1st gpu 1120Mhz with 1400Mhz mem, 2nd GPU 300Mhz with 150MHz Mem. Having both GPU's running with all cylinders is needed most while in game not the preload screens. Now that's on all xfire settings Default, AFR, Optimized 1x1. If both GPU's were firing on all cylinders the FPS would be steady at 90FPS or more on High setting with all AA filters on 8x or more.
  15. I see that the second GPU switches from 300MHz to 1120Mhz in the preload screen only never in game. where it is needed the most. now that's on all xfire settings Default, AFR, Optimized 1x1. the second GPU never turns on in game. If both GPU's were firing on all cylinders the FPS would be steady at 90FPS or more on High setting with all AA filters on 8x or more.
  16. I'm not having those issues and I have 2x R9 270x. Even crossfire disabled. But I mainly run enabled. Same results. Card settings Both cards sent to below: overclocked 1120 MHz, 1400 MHz RAM overclock In game settings msaa 4x, Anisotropic filter level 16x, settings on high, heat bluer off, DOF off, water medium, both shadows off, trees at 4000, pit 512, HDR on, lens dirt+flare, preload radius 12,000: 70 FPS in pit. 3-D application settings in catalyst control Center: AA mode: override AA samples: 12x Filter: edge AA method: super Morphological filtering: on texture filter Anisotropic filter: app settings Anisotropic filter Level: app settings Texture filtering quality: on Surface format optimization: on Frame rate control Wait for vertical refresh: on OpenGL: on Tessellation Tessellation mode: AMD optimized Maximum tessellation level: AMD optimized Crossfire Frame pacing: on AMD crossfire mode: default With those settings I'm able to get 70 FPS in A-10C, F-15-C, BS, HUEY.
  17. You cannot just shut off tree shadows mustang?
  18. Turn off vsync should be better a little.
  19. Look up at the top of the main menu, there will be 3 icon from left to right. 1. Module Manager 2. Options 3. Log out
  20. I turned on msaa to 4x and fps dropped to 75fps in highly populated areas on pit views and 60 on external views with DOF off.
  21. What's your msaa settings, and are you using DOF?
  22. It does with the right MB, because the bridge is thru the MB not a crossfire cable.
  23. Msaa is required now for edge rendering?
  24. Now that DCS 1.5 is out I'm having thoughts about how insane the graphics would be with the new FURYX or a crossfired dual FURYX
  25. Plus the DOF options the first one is in Russian.
×
×
  • Create New...