Aces High Bulletin Board
General Forums => Open Beta Test => Topic started by: 68ZooM on July 26, 2015, 06:28:33 PM
-
is there a high res download for the alpha?
-
Nope. Just increase the texture size in the video settings pop up.
-
UrSelf,
Have you tried creating your own SLI profile for the alpha to run your two GTX260?
http://www.nvidia.in/object/slizone-appprofile-in.html
-
I am working on that but I can't figure out how to link them both together so that the game recognizes more video card memory
-
I read some blogs and a common theme is some games only see the memory from one of the cards. Have you tried profiles for other games?
-
It doesn't work that way. The memory is mirrored instead of doubled. That way each GPU has its own memory to draw from and can render alternate frames without drawing on the other card for help, and potentially slowing down the whole operation.
-
been in the nvidia control panel would I change it to force alternating frame 2 or force alternating frame 1
-
The only reason to change the setting is if you have the same problem MADe has where SLI doesn't appear to be working. The only difference between 1, or 2 is which card does odd number frames, and which does even frames.
-
Better question is, chalenge do you actually know how to make SLI work with the alpha and Self is gonna go 20 questions with you rather than you just give him an itemized list of things to do? Do games see a combined single amount of ram equal to the RAM on both cards if the profile is setup correctly?
I was looking at profile editing and it looks like you are addressing register level machine addressing info directly that the OS will then use as fact even if it's spoofing the identity of the two cards in the bus.
On some sites players talk about spoofing the PC into seeing a different card ID for the cards you are running to fool a game into working with your cards. Here from NVIDIA using coolbits they walk through modifying existing profiles.
http://www.nvidia.co.uk/object/nzone_sli_appprofile_uk.html
The SLI Profile Tool lets you see the register level and modify it. Reminds me of programing I\O functions in assembler.
http://www.geeks3d.com/20100528/manage-your-sli-profiles-with-nvidia-geforce-sli-profile-tool/
-
You mean in cases where it has never worked? Sometimes you can rotate the SLI bridge and it will be working, or otherwise look for a new bridge. Other times just adjusting the bridge will work.
No, games will not report the sum of the two cards.
My question for Self is how many lanes (physical slots on the MB) is he using? What model MB are we talking about? Are you using a CPU that has only 16 lanes and yet trying to use x8/x8/x4? or worse? Power down, remove everything else, and try it with just the two GPUs.
EDIT: Just to remove any doubts; it is possible for you to completely populate the slots of your motherboard and still get SLI. However, if all present devices (or enough of them) are pushing maximum throughput, then the multiplexing that the motherboard uses to provide additional lanes will not work. When you are sitting idle and checking SLI everything appears to be working. Once you are in the game and other requests fly down the pipe then the SLI function can become unavailable. Normally, if the second GPU can always maintain at least x4, then it will continue to function in SLI. If it ever goes x8/x2 then you are out of SLI goodness. Depending on the devices that are installed it is quite possible for everything to check out at idle, and then completely fail once a game starts up and then the system will fall back to a single GPU. Even then you are in SLI mode, and it will continue to mirror memory as it can, but on one GPU there is no benefit.
When I read about the stuttering that was reported this is what came to mind.
-
Chalenge it's a Asus m7ne sli MB(I'm in my semi truck now so I can't check it for sure) but it has two dedicated video card slots that's why I bought it if you run just one video card in it then it functions as pci-e x16 if you run dual video cards then it's splits to x8 instead 16 has onboard audio the only 2 pci slot that I'm using even though there's two more of them available.
-
Hold up, pump the brakes :old: No matter what we do with SLI, we cannot get the game to recognize the second card as additional memory. Am I correct in that statement?
From what I learned here (thanks Bustr and Challenge) is that the second card will mirror the data received and then alternates / splits the processing of frames (one card then the next). The bump in speed comes from each card not having to wait to complete rendering the next frame as it's partner has that job, so it only has to render every other frame. Am I correct in that statement?
The problem that Zoom and I may have with the motherboard, reduces the number of channels by half, and therefore lose the benefit of the additional card in many cases (so far, Aces High fitting that description). If I am correct with that statement, are you saying that there IS something that can be done that will increase speed even with the loss of half of the channels?
-
Okay, thanks to you all for making me actually test it. I can confirm SLI is NOT working in the Alpha. That is, UNTIL you chose Force alternate frame rendering 1, or 2, as outlined earlier.
You can test SLI for any game by pulling up Nvidia Control Panel and on the top menu bar go into the 3D Settings and clicking on "Show SLI Visual Indicator."
SLI is working in AH2, but is NOT working in the Alpha version until FORCED ON. This means that anyone with an SLI setup will not only have to add the Alpha to their NVCP 3D setting, but also force SLI on.
If you still need help with this I will add a thread to show how it is accomplished.
-
Chalenge it's a Asus m7ne sli MB(I'm in my semi truck now so I can't check it for sure) but it has two dedicated video card slots that's why I bought it if you run just one video card in it then it functions as pci-e x16 if you run dual video cards then it's splits to x8 instead 16 has onboard audio the only 2 pci slot that I'm using even though there's two more of them available.
I went looking for your MB and cannot find a listing for it. I seem to remember it from the past, but I cannot find it. Do you have a DXdiag that lists your CPU? Otherwise, I am going to need help locating the MB manual.
-
I posted on our web site so I went there and copied and pasted it here you go I really appreciate this
Machine name: BLACKSUN
Operating System: Windows XP Professional x64 Edition (5.2, Build 3790) Service Pack 2 (3790.srv03_sp2_gdr.130306-1435)
Language: English (Regional Setting: English)
System Manufacturer: System manufacturer
System Model: System Product Name
BIOS: Default System BIOS
Processor: AMD Phenom(tm) 9950 Quad-Core Processor (4 CPUs), ~2.6GHz
Memory: 8190MB RAM
Page File: 794MB used, 9012MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
DxDiag Version: 5.03.3790.3959 64bit Unicode
------------
DxDiag Notes
------------
DirectX Files Tab: No problems found.
Display Tab 1: The file nv4_disp.dll is not digitally signed, which means that it has not been tested by Microsoft's Windows Hardware Quality Labs (WHQL). You may be able to get a WHQL logo'd driver from the hardware manufacturer.
Sound Tab 1: No problems found.
Music Tab: No problems found.
Input Tab: No problems found.
Network Tab: No problems found.
--------------------
DirectX Debug Levels
--------------------
Direct3D: 0/4 (n/a)
DirectDraw: 0/4 (retail)
DirectInput: 0/5 (n/a)
DirectMusic: 0/5 (n/a)
DirectPlay: 0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow: 0/6 (retail)
---------------
Display Devices
---------------
Card name: NVIDIA GeForce GTX 260
Manufacturer: NVIDIA
Chip type: GeForce GTX 260
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_05E2&SUBSYS_23931682&REV_A1
Display Memory: 896.0 MB
Current Mode: 1920 x 1080 (32 bit) (60Hz)
Monitor: Plug and Play Monitor
Monitor Max Res: 1600,1200
Driver Name: nv4_disp.dll
Driver Version: 6.14.0013.3504 (English)
DDI Version: 9 (or higher)
Driver Attributes: Final Retail
Driver Date/Size: 2/23/2014 00:24:23, 12928640 bytes
WHQL Logo'd: No
WHQL Date Stamp: None
VDD: n/a
Mini VDD: nv4_mini.sys
Mini VDD Date: 2/23/2014 00:24:23, 11537864 bytes
Device Identifier: {D7B71E3E-46A2-11CF-8278-9E0300C2CB35}
Vendor ID: 0x10DE
Device ID: 0x05E2
SubSys ID: 0x23931682
Revision ID: 0x00A1
Revision ID: 0x00A1
Video Accel: ModeMPEG2_C ModeMPEG2_D
Deinterlace Caps: {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
Registry: OK
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled
DDraw Test Result: Not run
D3D7 Test Result: Not run
D3D8 Test Result: Not run
D3D9 Test Result: Not run
-------------
Sound Devices
-------------
Description: HD Audio rear output
Default Sound Playback: Yes
Default Voice Playback: Yes
Hardware ID: HDAUDIO\FUNC_01&VEN_1106&DEV_0397&SUBSYS_1043836C&REV_1000
Manufacturer ID: 1
Product ID: 100
Type: WDM
Driver Name: viahduaa.sys
Driver Version: 6.00.0001.7031 (English)
Driver Attributes: Final Retail
WHQL Logo'd: Yes
Date and Size: 3/14/2014 18:24:22, 1228288 bytes
Other Files:
Driver Provider: VIA Technologies, Inc.
HW Accel Level: Full
Cap Flags: 0xB5B
Min/Max Sample Rate: 44100, 192000
Static/Strm HW Mix Bufs: 1, 0
Static/Strm HW 3D Bufs: 0, 0
HW Memory: 0
Voice Management: No
EAX(tm) 2.0 Listen/Src: No, No
I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No
Registry: OK
Sound Test Result: Not run
---------------------
Sound Capture Devices
---------------------
Description: HD Audio rear input
Default Sound Capture: Yes
Default Voice Capture: Yes
Driver Name: viahduaa.sys
Driver Version: 6.00.0001.7031 (English)
Driver Attributes: Final Retail
Date and Size: 3/14/2014 18:24:22, 1228288 bytes
Cap Flags: 0x41
Format Flags: 0xCC0
-------------------
DirectInput Devices
-------------------
Device Name: Mouse
Attached: 1
Controller ID: n/a
Vendor/Product ID: n/a
FF Driver: n/a
Device Name: Keyboard
Attached: 1
Controller ID: n/a
-
Having run AH on SLI with my 680s, 970s, and now 980s, when I've tried disabling SLI and going to just single card with AH, I noticed absolutely NO difference in performance.
Since nVidia never made a decent profile for AH, I doubt they'll be in a rush to make one for AH2.
What I'm interested to know in this thread, is there someone able to create one that works well enough to see an actual benefit and boost in performance? Chal/Bustr/etc, is it possible using the tools provided to make something worth the time in your opinions?
-
@Gman I was about to answer on that when I got into helping Self here. Yes, it is possible to see significant scaling in the Alpha, and AH2 both. I have been creating profiles all along not realizing Skuzzy was unaware that it needed to be done. The SLI hacking tool that Bustr posted should be able to export the profile, but it has not been updated in so long I don't trust it to work with current drivers. I will post my settings if you need, but I can already tell you that you will probably have to tweak on your own anyway. I think I said yesterday that the SLI profile that works best for the Alpha (for me at least) is "Force alternate frame rendering 2" where I get something like 60% scaling. Not great, but compared to the "rendering 1" option of just 5% I think it is clearly the way to go.
@Self It looks like you meant that you have an ASUS M2N-E? I cannot find an M7N-E. If it is the M2N-E that you have, then it is a poor SLI board. Otherwise it looks like the PCIe lane scheme on AMD boards is so different (compared with Intel) that knowing your board specifications is critical to ironing out SLI issues. If it really is an M2N-E then the specifications I found indicate that it operates at X16/x4 for SLI, which would explain the problem, but I would want to know for sure which MB you have before giving up.
-
I'll be home in a few hours I'll look inside the machine and get the right numbers
-
When you do let's move this into Hardware Support so we can get out of everyone's hair.
-
Thank you very much for helping my squad mate Chalenge.
-
Chalenge I posted in the hardware section