Jump to content
DayZ Forums

dublea

Members
 View Profile  See their activity

  • Content Count

    32

  • Joined

  • Last visited

Posts posted by dublea

  5. Posted

    Two hardware tests I would perform. Test the HDD that the game is installed on and your system's memory. As far as your HDD, find the manufacturers diagnostic tools. And, for memory, run memtest86. If you want a easy way of doing either, look for a ISO called hiren's. I think they are at v15.2.

    Verify that game and mod install too. Depending on where you obtained the game will depend on what options you have with that.

  12. Posted

    I have GPU_MaxFramesAhead=1; GPU_DetectedFramesAhead=1; I I was playing around with the video settings and it really doesn't change the fps count by changing anything. I will try editing the core/thread count to see if it changes anything but I don't see how lowering my vram will change anthing. With the ingame setting on default I should be using all of my vram.

    ? Lowering vram? Set it to the amount you have on your video card. As far as the -maxMem it is locked to 2047mb

  15. Posted

    I got an i7 and get ~65+ on avg. It only drops when there are more zeds/players than norm. Though I don't have antialiasing set that high. You are missing some things I would add to your launch parameters though.

    Here is mine: -cpuCount=4 -exThreads=7 -nosplash -nopause -maxMem=2047 -maxVRAM=1024

    You may not be utilizing all of your cores or threads by not setting it.

  16. Posted

    This did not work for me...I wonder why

    See the list of services that fail? Check your Software and Event Log in Windows Event Viewer and see what is failing when you disconnect. Be sure that you actually set it to disabled as the service will start again if it stays set to automatic.

  20. Posted · Edited by dublea

    When you drop to DX9 from DX10, it doesn't use the same versions of shadders, AA, etc. You will always gain an FPS increase from doing it. Minor SLI load balancing is still there when not forcing it into DX9. I only gained about 3-5fps from doing it.

  21. Posted

    in dayz commander settings

    set additional launch parameter

    -winxp

    this enables crossfire/sli and i also believe it forces arma 2 to run in directx9 .

    To my knowledge, the only way to enable SLI is to make sure you have the correct drivers/patch such as the EVGA SLI Patch. But, even when it is working, it only offers minor load ballancing as Arma 2 / OA is not optimized for SLI/CF. '-winxp' enforces DX9 and compatibility with older GPU drivers. That's about as much as that command does. I've only seen one other who suggested it, but when I tried it I never saw a noticable difference as compaired to DX10 while having SLI enabled. I later found this list of commands and what they actually do

  22. Posted · Edited by dublea

    I have your solution here. Currently have an open ticket with BattlEye.

    this happend to a freind of mine, are you using dayz commander?

    It happens on lower ends computers with bad internet connections

    Possibly true, but it would happen even while playing. As it is happening when he closes the game, it's probably the PCA service being killed by BattlEye.

  23. Posted

    Have you set any addition launch parameters? That will make a huge difference in FPS. As an SLI users, Arma 2 does not benefit from it in any way. The game is just not optimized for it. So don't think another 680 will help. Here is are my launch parameters I have configured into dayz commander that gave me a 15-20fps increase:

    -cpuCount=3 -nosplash -nopause -maxMem=2047 -maxVRAM=1024 -exThreads=7

    I have a core i7 w/ 12GB of ram and 2 GTX 580 SSC cards in SLI. I only get ~45-75fps with high settings with or without SLI. The game just isn't optimized that well but there are ways to improve it.

  24. Posted

    what are his pc specs,

    it may be an issue with sli or crossfire (if he has multiple gpu)

    if running amd cpu, it may be a bios poo poo, update bios

    I agree. It would still cause the BSOD, and some happen so fast people don't see them. To pin-point it, we can look at the error it created. I find it can be easier to get the info from the BSOD msg than having someone look through their Event Viewer. Either would work though. We just need to find out what is being logged, if anything, as the point of failure. I always disable that feature for machines I build due to how fast newer systems reboot after dumping the info.

    So, I would suggest he do both, provide system specs and disable the auto restart w/ testing to see if he gets a BSOD.

    • Like 1

  25. Posted · Edited by dublea

    Ok, you are probably getting a BSOD but the reboot is happening so fast you are not seeing it. To verify this we need to disabel automatic restart on system failure. Click the start menu, Right-click on Computer, and select Properties. If this is Vista or above, click on Advanced System Settings in the menu on the left. Under Startup and Recovery, there is a Settings button, click that. Under System Failure, uncheck the Automatically Restart. Hit OK and apply to all windows. Get him to play and see if it stops on a BSOD when the system fails.

    • Like 2
×