Search Results for 'Ice Age 3'

[gustavor38]

After reading roadtovr article about compatibility with skyrim in DK2 i ran to buy your product.
Now I find that really they are reviewing a not public version, right?. I think that this is not a good policy.
When i try to use the product i find that no head movement is detected by vorpx, not the camera (i know i must wait for the update), the rift alone. When I turn the head the image turns with me, i can´t look around is as i have a monitor glued to my head.
I tested it with fallout3, i tried stopping and starting the oculus service, the program opens ok in the dk2 forcing it with vorpx control. I tried using system config but the problem is the same.

Am I doing anything wrong?

Excuse my english, it isn´t my native language.

[JackDT]

doc wrote:

Ralf, from one developer to another: small, timely updates keep the community interest in your software high.

We should all be here to talk about how awesome VorpX is, but instead, it’s been 9 months since we had even a minor update, and we’re all on the spectrum of impatient and pissed off.

it’s not just DK2 support people are impatient for – it’s all of the small features and everything that has been promised. You’re bundling too many features into each update. From what I’m reading, this update will include DK2 support, DX11 geometry support, lots of setting changes, fixed shaders in Skyrim, an automated licensing solution, and probably more that you haven’t mentioned. That is just NUTS. Hell, I’d be happy with the letterbox rendering changes only, which were supposedly resolved 4 months ago. Why do I have to wait for DK2 support for that fix? You’re trying to be Internet Explorer when you should be Chrome. Change your dev cycle to release small features silently and very often. It minimizes risk for you, keeps your community engaged and happy, and shows that you are constantly working on our investment.

I’m looking at purchasing VorpX and the fact that the last update was so long ago was what made me hold off. A history of updates on a steady tic is totally what inspired confidence in a purchase — even if the updates are very small.

Alternatively an unstable branch that showed changes over time would have probably sufficed.

This probably makes your development life a tiny bit more complicated in that you’d maintain a separate branch for the biggest changes, but as someone who started doing that in my own stuff I’ve found that the extra discipline and organization this imposes is actually improving the final output of my work.

[dmortensen1]

Ralf wrote:

@ dmortensen: For unsupported games vorpX duplicates the monoscopic output image instead of creating a 3d image from two ‘eyes’. Everything else works just fine, even if a game is not supported. The experience is similar to closing one eye in reality. You are still fully immersed in the world, just the stereo 3d is missing.

Thanks Ralf for the info ;) however i was also wondering about another thing :) can you make it possible for the owners of the software to actually try VorpX without the Rift needed to be plugged in… it is because i have a license on VorpX but in order to get a small taste of what it can deliver (i own several of the officially supported games!) i either have to view youtube videos (which get a little annoying after a while because many youtube videos are with people who don’t have the same charm like Pewdiepie or emart or Jacksepticeye (to mention those i have subscribed to see rift videos!)) or else i have to use Tridef 3D so i can test if my computer can even run those games VorpX also supports in at least 60Hz fluently… i love what i have seen on many youtube videos so far showing the power of VorpX but i would like to be able to test it myself the way that i see it on youtube (those that show both eyes :) ) thank you for your time to read this :) i hope you’ll think about it…

[Ralf]

DK2 will be supported. There are a few challenges, mainly positional tracking and the way the image is rendered with the DK2, but this is being worked on already as far as possible without an actual device.

Generally vorpX tries to hook into all DX9-DX11 games. Those that aren’t on the support list usually don’t have Stereo 3D, but do work otherwise. Image duplication, head tracking, all extra features like EdgePeek etc, work fine even with most unsupported games. There are exceptions, of course.

[jshipley]

I’m trying to get Mass Effect 3 working with vorpx and the oculus rift.

I have the game on origin, and I am running it in offline mode.

Here are the issues I’m running into:

1. While in the ME3 game I can not hit the Delete key to bring up the in game vorpx controls.

2. The menus are extremely hard to use.
– I do not see a mouse cursor, and it constantly resets it’s position.
– If I manage to get lucky and find a button with the hidden mouse cursor before it resets its position, I can click it to navigate the menu. But some of them are extremely hard to find (the confirm dialogs are near impossible for me).
– I can use the arrow keys to navigate (the game doesn’t seem to support keyboard ability to select an option though).

Any advice?

[Ralf]

That looks, well, interesting…

Can’t replicate the issue unfortunately (using the Steam version of ME). So all I have are a few general things:

– Disable (or better uninstall, then restart Windows) the MSI Gaming App and Shadowplay (GeForce Experience). Both programs probably hook into DirectX similar to vorpX, which might cause a conflict.
– Try to switch from Z-Buffer to Geometry 3D or vice versa and restart the game. This might help.
– Try another graphics driver version. The card itself can be ruled out, I think. The main dev machines have a GTX770 here ATM, but maybe it’s an issue with a specific driver version.
– In case your old machine had an nVidia graphics card too (and you still have it), please check whether any graphics driver settings are different than before.
– if nothing helps, please send me a screenshot of your task manager showing all running processes to support |at| vorpx com . Maybe I can spot something else that possibly interferes with vorpX.
(- Just in case you haven’t done so already: please check the trouble shooting guide above.)

[sucaj]

ok! I did a great deal more troubleshooting and tweaking, and have basically reduced the effect to be unnoticeable. However, how I did so is totally unreasonable. Here are my findings.

– Ralf, you’ve suggested that VorpX works best at resolutions of 4:3 or 5:4. Although these resolutions certainly reduced the fisheye effect, and reduced the appearance of everything being stretched vertically, at 1280×1024 (5:4) the distortion was still present and greatly noticeable. However, a combination of carefully tweaking the image zoom, the game’s FOV, setting the “simple” aspect ratio correction, and tweaking the eye offset resulted in a greatly reduced fisheye effect. To me, this indicates that the distortion shader is not scaled or changed properly based on VorpX’s settings… unlike Vireio, Tridef and other stereo solutions out there.

– Although a 4:3 resolution of 5:4 is suggested, I noticed that 5:4 was still less stretched and better than 4:3. This indicated that the more square the resolution, the better VorpX hadles it. Confirming my suspicion, I was able to add a custom GPU-scaled square resolution of 1280×1280 (1:1), which successfully eliminated the effect entirely. Hmmmm.

Ralf, I urge you to please reconsider how you are implementing your image projection and applying your distortion shader. Neither Tridef nor Vireio have such issues with aspect ratio or image distortion. Neither Tridef nor Vireio require any sort of aspect ratio correction, and both work fine with not only 16:9 resolutions, but ANY resolution that you throw at them. The distortion shader is scaled properly no matter how the image is zoomed, what your FOV is, or what your stereo separation settings are. Requiring users to use 4:3 or 5:4 resolutions within a very thin margin of ‘correct’ stereo settings is a clear indicator that something is horribly broken in VorpX’s rendering. Since Vireio is open source, I really hope you can take a look at it’s implementation and apply your findings to VorpX. You clearly have a better sense of polish and product than Vireio… but despite the fact that I paid for it, I unfortunately find myself using Vireio more often simply because the rendering is vastly superior.

[itxtutor]

In arma 2 it works really nice. But it says in arma 3 not supported game… But on the webpage it says it´s supported. Maybe we have to wait for the new update. Does it work for anyone ?

[robottesla]

Hi Ralf/everyone.

I recently got left 4 dead 2 on the steam sale, but Vorpx does not seem to work with it. When I start Left 4 dead 2, it starts normally without vorpx turning the screen stereo. When I exit the game I then notice vorpx is no longer running. I’ve double and tripple checked this. Turn on Vorpx via Vorpx Control shortcut, verify its running in task manager and in the side tray, run left 4 dead 2, exit left 4 dead 2, and vorpx is no longer running.

The other two games I have recently ran with Vorpx is BF4 and Dirt 3, no isses with either of them. Vorpx is still running when I exit either of them.

Any ideas? My setup is:

– Windows 7 Ultimate (64bit).
– 16 Gig Ram
– intel i7-4770 3.40GHz
– Asus GTX 770 Nvidia GeForce DirectCU II OC 2GB GDDR5 Graphics Card

[jeffw773]

Yup I got it! Thank you so much! :D
I have a quick question about how to use VorpX with some games though…
I am trying to get DiRT 3 to be able to drive with my xbox gamepad but while also being able to look around the interior of the car with the oculus but for some reason I can’t get it to work….I would appreciate any advice or help you can offer me :)

And jjordan12 I think you should be able to go into your email and find the email about your purchase and it should have the link to your download in there. :)

[Ralf]

Hi kosmo,

Instaead of disabling head tracking completely, set the Head Tracking Sensitivity to 0.0. This way you can disable the tracking, but EdgePeek stays functional.

Scaling the scene can be achieved by raising the Eye Separation in vorpX (main page of the in-game menu). BF4 only only supports Z-Buffer 3D currently, so the effect is somewhat limited though.

Another thing that affects the perceived scale is the field of view set in a game. Please make sure to set it to something like 95-100 in the game options. Unfortunately this works only in multiplayer, in the campaign this value is ignored. The reason for this is only known to DICE…

[Ralf]

The top/bottom distortion is an artifact of the ‘Smart’ aspect ratio mode. You can get rid of it completely by selecting another aspect ratio mode (display page of the in-game menu).

The solution I prefer though is choosing a 5:4 or 4:3 screen res (1280×1024 or 1600×1200), which makes life much easier for the ‘Smart’ mode, resulting in less top/bottom distortion. 16:9 modes are clearly the worst choice in this regard. Depending on graphics card and driver settings there is a certain chance though that only 16:10 modes are displayed fullscreen on your Rift.

[Ralf]

“Scaling” the world can be done by changing the ‘Eye Distance’ in the in-game menu, which does essentially the same, this works best in Geometry 3D, in Z-Buffer 3D the effect is limited for various reasons.

There are two methods for changing the FOV: the ‘3D-FOV-Enhancement’ for Geometry 3D, which does what you know from other drivers, and the ‘2D-FOV-Enhancement’ that works in all modes, even without any Stereo 3D. As you already noticed the latter is a matter of taste though, since it introduces some image distortion, especially when set too high.

Hope that hepls.

[jasonatokc]

disabled steam overlay reset to defaults on my radeon 7970 and now I am getting the following message right after I press play in the menu

The direct3d 11 device has been removed or has crashed. This requires the game to exit. please ensure you have the latest drivers for your graphics device and restart the game. the sound still plays in the background until I clear the message

[jasonatokc]

starts level headtracking works and 3d works crashes about 20 – 30 secs after that with no error.

Binaries
CPU-Z version 1.61

Processors
Number of processors 1
Number of threads 8

APICs
Processor 0
— Core 0
— Thread 0 0
— Core 1
— Thread 0 1
— Core 2
— Thread 0 2
— Core 3
— Thread 0 3
— Core 4
— Thread 0 4
— Core 5
— Thread 0 5
— Core 6
— Thread 0 6
— Core 7
— Thread 0 7

Processors Information
Processor 1 ID = 0
Number of cores 8 (max 8)
Number of threads 8 (max 8)
Name AMD FX-8350
Codename Zambezi
Specification AMD FX(tm)-8350 Eight-Core Processor
Package Socket AM3+ (942)
CPUID F.2.0
Extended CPUID 15.2
Core Stepping OR-C0
Technology 32 nm
TDP Limit 125 Watts
Core Speed 1404.8 MHz
Multiplier x FSB 7.0 x 200.7 MHz
Rated Bus speed 2608.8 MHz
Stock frequency 4000 MHz
Instructions sets MMX (+), SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, SSE4A, x86-64, AMD-V, AES, AVX, XOP, FMA
L1 Data cache 8 x 16 KBytes, 4-way set associative, 64-byte line size
L1 Instruction cache 4 x 64 KBytes, 2-way set associative, 64-byte line size
L2 cache 4 x 2048 KBytes, 16-way set associative, 64-byte line size
L3 cache 8 MBytes, 64-way set associative, 64-byte line size
FID/VID Control yes
Min FID 7.0x
# of P-States 7
P-State FID 0x1A – VID 0x0A – IDD 13 (21.00x – 1.425 V)
P-State FID 0x19 – VID 0x0B – IDD 13 (20.50x – 1.412 V)
P-State FID 0x18 – VID 0x11 – IDD 12 (20.00x – 1.337 V)
P-State FID 0x12 – VID 0x19 – IDD 10 (17.00x – 1.237 V)
P-State FID 0xC – VID 0x21 – IDD 8 (14.00x – 1.137 V)
P-State FID 0x5 – VID 0x2B – IDD 5 (10.50x – 1.012 V)
P-State FID 0x10C – VID 0x35 – IDD 4 (7.00x – 0.887 V)

PStateReg 0x80000186-0x0000141A
PStateReg 0x80000186-0x00001619
PStateReg 0x80000177-0x00002218
PStateReg 0x8000015F-0x00003212
PStateReg 0x8000014B-0x0000420C
PStateReg 0x80000136-0x00005605
PStateReg 0x80000124-0x00006A4C
PStateReg 0x00000000-0x00000000

Package Type 0x1
Model 00
String 1 0x0
String 2 0x0
Page 0x0
CmpCap 7
Base TDP 6 Watts
Boosted P-States 2
Max non-turbo ratio 20.00x
Max turbo ratio 21.00x
Attached device PCI device at bus 0, device 24, function 0
Attached device PCI device at bus 0, device 24, function 1
Attached device PCI device at bus 0, device 24, function 2
Attached device PCI device at bus 0, device 24, function 3
Attached device PCI device at bus 0, device 24, function 4
Attached device PCI device at bus 0, device 24, function 5

Chipset
Northbridge AMD RD9x0 rev. 02
Southbridge AMD SB950 rev. 40
Graphic Interface PCI-Express
PCI-E Link Width x16
PCI-E Max Link Width x16
Memory Type DDR3
Memory Size 16384 MBytes
Channels Dual
Memory Frequency 668.9 MHz (3:10)
CAS# latency (CL) 9.0
RAS# to CAS# delay (tRCD) 9
RAS# Precharge (tRP) 9
Cycle Time (tRAS) 24
Bank Cycle Time (tRC) 33
Uncore Frequency 2207.5 MHz

Memory SPD
DIMM # 1
SMBus address 0x52
Memory type DDR3
Module format UDIMM
Manufacturer (ID) G.Skill (7F7F7F7FCD000000)
Size 8192 MBytes
Max bandwidth PC3-10700 (667 MHz)
Part number F3-1866C9-8GXM
Number of banks 8
Nominal Voltage 1.50 Volts
EPP no
XMP yes
XMP revision 1.3
JEDEC timings table CL-tRCD-tRP-tRAS-tRC @ frequency
JEDEC #1 5.0-5-5-14-19 @ 380 MHz
JEDEC #2 6.0-6-6-17-23 @ 457 MHz
JEDEC #3 7.0-7-7-20-27 @ 533 MHz
JEDEC #4 8.0-8-8-22-30 @ 609 MHz
JEDEC #5 9.0-9-9-25-34 @ 685 MHz
JEDEC #6 10.0-10-10-28-38 @ 761 MHz
XMP profile XMP-1778
Specification PC3-14200
Voltage level 1.500 Volts
Min Cycle time 1.125 ns (889 MHz)
Min tRP 9.25 ns
Min tRCD 10.25 ns
Min tWR 14.88 ns
Min tRAS 29.50 ns
Min tRC 39.25 ns
Min tRFC 260.00 ns
Min tRTP 7.50 ns
Min tRRD 5.00 ns
Command Rate 2T
XMP timings table CL-tRCD-tRP-tRAS-tRC-CR @ frequency (voltage)
XMP #1 9.0-10-9-29-39-2T @ 972 MHz (1.500 Volts)
XMP profile XMP-1600
Specification PC3-12800
Voltage level 1.500 Volts
Min Cycle time 1.250 ns (800 MHz)
Min tRP 10.88 ns
Min tRCD 12.13 ns
Min tWR 17.50 ns
Min tRAS 34.63 ns
Min tRC 45.88 ns
Min tRFC 303.63 ns
Min tRTP 8.75 ns
Min tRRD 5.75 ns
Command Rate 2T
XMP timings table CL-tRCD-tRP-tRAS-tRC-CR @ frequency (voltage)
XMP #1 9.0-11-9-29-38-2T @ 827 MHz (1.500 Volts)

DIMM # 2
SMBus address 0x53
Memory type DDR3
Module format UDIMM
Manufacturer (ID) G.Skill (7F7F7F7FCD000000)
Size 8192 MBytes
Max bandwidth PC3-10700 (667 MHz)
Part number F3-1866C9-8GXM
Number of banks 8
Nominal Voltage 1.50 Volts
EPP no
XMP yes
XMP revision 1.3
JEDEC timings table CL-tRCD-tRP-tRAS-tRC @ frequency
JEDEC #1 5.0-5-5-14-19 @ 380 MHz
JEDEC #2 6.0-6-6-17-23 @ 457 MHz
JEDEC #3 7.0-7-7-20-27 @ 533 MHz
JEDEC #4 8.0-8-8-22-30 @ 609 MHz
JEDEC #5 9.0-9-9-25-34 @ 685 MHz
JEDEC #6 10.0-10-10-28-38 @ 761 MHz
XMP profile XMP-1778
Specification PC3-14200
Voltage level 1.500 Volts
Min Cycle time 1.125 ns (889 MHz)
Min tRP 9.25 ns
Min tRCD 10.25 ns
Min tWR 14.88 ns
Min tRAS 29.50 ns
Min tRC 39.25 ns
Min tRFC 260.00 ns
Min tRTP 7.50 ns
Min tRRD 5.00 ns
Command Rate 2T
XMP timings table CL-tRCD-tRP-tRAS-tRC-CR @ frequency (voltage)
XMP #1 9.0-10-9-29-39-2T @ 972 MHz (1.500 Volts)
XMP profile XMP-1600
Specification PC3-12800
Voltage level 1.500 Volts
Min Cycle time 1.250 ns (800 MHz)
Min tRP 10.88 ns
Min tRCD 12.13 ns
Min tWR 17.50 ns
Min tRAS 34.63 ns
Min tRC 45.88 ns
Min tRFC 303.63 ns
Min tRTP 8.75 ns
Min tRRD 5.75 ns
Command Rate 2T
XMP timings table CL-tRCD-tRP-tRAS-tRC-CR @ frequency (voltage)
XMP #1 9.0-11-9-29-38-2T @ 827 MHz (1.500 Volts)

Monitoring
Mainboard Model SABERTOOTH 990FX R2.0 (0x0000055D – 0x1EDE55C0)

LPCIO
LPCIO Vendor ITE
LPCIO Model IT8721
LPCIO Vendor ID 0x90
LPCIO Chip ID 0x8721
LPCIO Revision ID 0x1

Hardware Monitors
Hardware monitor ITE IT8721
Voltage 0 11.98 Volts [0xF0] (+12V)
Voltage 1 4.96 Volts [0xEC] (+5V)
Voltage 2 1.19 Volts [0x63] (CPU VCORE)
Voltage 3 1.69 Volts [0x8D] (VIN3)
Voltage 4 0.19 Volts [0x10] (VIN4)
Voltage 5 3.12 Volts [0xD0] (+3.3V)
Voltage 6 0.77 Volts [0x40] (VIN6)
Voltage 7 0.17 Volts [0xE] (VIN7)
Voltage 8 1.67 Volts [0x8B] (VIN8)
Temperature 0 37°C (98°F) [0x25] (CPU)
Temperature 1 30°C (85°F) [0x1E] (Mainboard)
Fan 0 3293 RPM [0xCD] (CPU)
Fan 2 1398 RPM [0x1E3] (FANIN2)
Fan PWM 0 0 pc [0x0] (FANPWM0)
Fan PWM 1 0 pc [0x0] (FANPWM1)
Fan PWM 2 0 pc [0x0] (FANPWM2)

Hardware monitor AMD ADL
Voltage 0 0.85 Volts [0x352] (VIN0)
Temperature 0 33°C (91°F) [0x21] (TMPIN0)

PCI Devices
Description Host Bridge
Location bus 0 (0x00), device 0 (0x00), function 0 (0x00)
Common header
Vendor ID 0x1002
Model ID 0x5A14
Revision ID 0x02

Description PCI to PCI Bridge
Location bus 0 (0x00), device 2 (0x02), function 0 (0x00)
Common header
Vendor ID 0x1002
Model ID 0x5A16
Revision ID 0x00

Description PCI to PCI Bridge
Location bus 0 (0x00), device 4 (0x04), function 0 (0x00)
Common header
Vendor ID 0x1002
Model ID 0x5A18
Revision ID 0x00

Description PCI to PCI Bridge
Location bus 0 (0x00), device 5 (0x05), function 0 (0x00)
Common header
Vendor ID 0x1002
Model ID 0x5A19
Revision ID 0x00

Description PCI to PCI Bridge
Location bus 0 (0x00), device 9 (0x09), function 0 (0x00)
Common header
Vendor ID 0x1002
Model ID 0x5A1C
Revision ID 0x00

Description PCI to PCI Bridge
Location bus 0 (0x00), device 10 (0x0A), function 0 (0x00)
Common header
Vendor ID 0x1002
Model ID 0x5A1D
Revision ID 0x00

Description PCI to PCI Bridge
Location bus 0 (0x00), device 11 (0x0B), function 0 (0x00)
Common header
Vendor ID 0x1002
Model ID 0x5A1F
Revision ID 0x00

Description PCI to PCI Bridge
Location bus 0 (0x00), device 13 (0x0D), function 0 (0x00)
Common header
Vendor ID 0x1002
Model ID 0x5A1E
Revision ID 0x00

Description Serial ATA Controller
Location bus 0 (0x00), device 17 (0x11), function 0 (0x00)
Common header
Vendor ID 0x1002
Model ID 0x4391
Revision ID 0x40

Description USB Controller (OHCI)
Location bus 0 (0x00), device 18 (0x12), function 0 (0x00)
Common header
Vendor ID 0x1002
Model ID 0x4397
Revision ID 0x00

Description USB 2.0 Controller (EHCI)
Location bus 0 (0x00), device 18 (0x12), function 2 (0x02)
Common header
Vendor ID 0x1002
Model ID 0x4396
Revision ID 0x00

Description USB Controller (OHCI)
Location bus 0 (0x00), device 19 (0x13), function 0 (0x00)
Common header
Vendor ID 0x1002
Model ID 0x4397
Revision ID 0x00

Description USB 2.0 Controller (EHCI)
Location bus 0 (0x00), device 19 (0x13), function 2 (0x02)
Common header
Vendor ID 0x1002
Model ID 0x4396
Revision ID 0x00

Description SMBus Controller
Location bus 0 (0x00), device 20 (0x14), function 0 (0x00)
Common header
Vendor ID 0x1002
Model ID 0x4385
Revision ID 0x42

Description Multimedia device
Location bus 0 (0x00), device 20 (0x14), function 2 (0x02)
Common header
Vendor ID 0x1002
Model ID 0x4383
Revision ID 0x40

Description PCI to ISA Bridge
Location bus 0 (0x00), device 20 (0x14), function 3 (0x03)
Common header
Vendor ID 0x1002
Model ID 0x439D
Revision ID 0x40

Description PCI to PCI Bridge
Location bus 0 (0x00), device 20 (0x14), function 4 (0x04)
Common header
Vendor ID 0x1002
Model ID 0x4384
Revision ID 0x40

Description USB Controller (OHCI)
Location bus 0 (0x00), device 20 (0x14), function 5 (0x05)
Common header
Vendor ID 0x1002
Model ID 0x4399
Revision ID 0x00

Description PCI to PCI Bridge
Location bus 0 (0x00), device 21 (0x15), function 0 (0x00)
Common header
Vendor ID 0x1002
Model ID 0x43A0
Revision ID 0x00

Description PCI to PCI Bridge
Location bus 0 (0x00), device 21 (0x15), function 1 (0x01)
Common header
Vendor ID 0x1002
Model ID 0x43A1
Revision ID 0x00

Description PCI to PCI Bridge
Location bus 0 (0x00), device 21 (0x15), function 2 (0x02)
Common header
Vendor ID 0x1002
Model ID 0x43A2
Revision ID 0x00

Description PCI to PCI Bridge
Location bus 0 (0x00), device 21 (0x15), function 3 (0x03)
Common header
Vendor ID 0x1002
Model ID 0x43A3
Revision ID 0x00

Description USB Controller (OHCI)
Location bus 0 (0x00), device 22 (0x16), function 0 (0x00)
Common header
Vendor ID 0x1002
Model ID 0x4397
Revision ID 0x00

Description USB 2.0 Controller (EHCI)
Location bus 0 (0x00), device 22 (0x16), function 2 (0x02)
Common header
Vendor ID 0x1002
Model ID 0x4396
Revision ID 0x00

Description Host Bridge
Location bus 0 (0x00), device 24 (0x18), function 0 (0x00)
Common header
Vendor ID 0x1022
Model ID 0x1600
Revision ID 0x00

Description Host Bridge
Location bus 0 (0x00), device 24 (0x18), function 1 (0x01)
Common header
Vendor ID 0x1022
Model ID 0x1601
Revision ID 0x00

Description Host Bridge
Location bus 0 (0x00), device 24 (0x18), function 2 (0x02)
Common header
Vendor ID 0x1022
Model ID 0x1602
Revision ID 0x00

Description Host Bridge
Location bus 0 (0x00), device 24 (0x18), function 3 (0x03)
Common header
Vendor ID 0x1022
Model ID 0x1603
Revision ID 0x00

Description Host Bridge
Location bus 0 (0x00), device 24 (0x18), function 4 (0x04)
Common header
Vendor ID 0x1022
Model ID 0x1604
Revision ID 0x00

Description Host Bridge
Location bus 0 (0x00), device 24 (0x18), function 5 (0x05)
Common header
Vendor ID 0x1022
Model ID 0x1605
Revision ID 0x00

Description VGA Controller
Location bus 1 (0x01), device 0 (0x00), function 0 (0x00)
Common header
Vendor ID 0x1002
Model ID 0x6798
Revision ID 0x00

Description Multimedia device
Location bus 1 (0x01), device 0 (0x00), function 1 (0x01)
Common header
Vendor ID 0x1002
Model ID 0xAAA0
Revision ID 0x00

Description Serial ATA Controller
Location bus 2 (0x02), device 0 (0x00), function 0 (0x00)
Common header
Vendor ID 0x1B21
Model ID 0x0612
Revision ID 0x01

Description Serial ATA Controller
Location bus 3 (0x03), device 0 (0x00), function 0 (0x00)
Common header
Vendor ID 0x1B21
Model ID 0x0612
Revision ID 0x01

Description USB Controller
Location bus 4 (0x04), device 0 (0x00), function 0 (0x00)
Common header
Vendor ID 0x1B21
Model ID 0x1042
Revision ID 0x00

Description Ethernet Controller
Location bus 10 (0x0A), device 0 (0x00), function 0 (0x00)
Common header
Vendor ID 0x10EC
Model ID 0x8168
Revision ID 0x09

Description USB Controller
Location bus 11 (0x0B), device 0 (0x00), function 0 (0x00)
Common header
Vendor ID 0x1B21
Model ID 0x1042
Revision ID 0x00

Description USB Controller
Location bus 12 (0x0C), device 0 (0x00), function 0 (0x00)
Common header
Vendor ID 0x1B21
Model ID 0x1042
Revision ID 0x00

DMI
BIOS Type American Megatrends
DMI BIOS
vendor American Megatrends Inc.
version 0906
date 09/17/2012
ROM size 8192 KB

DMI System Information
manufacturer To be filled by O.E.M.
product To be filled by O.E.M.
version To be filled by O.E.M.
serial To be filled by O.E.M.
UUID {BF473820-B850-11DC-B570-50465D6B04BD}

DMI Baseboard
vendor ASUSTeK COMPUTER INC.
model SABERTOOTH 990FX R2.0
revision Rev 1.xx
serial 121003131900208

DMI System Enclosure
manufacturer To Be Filled By O.E.M.
chassis type Desktop
chassis serial To Be Filled By O.E.M.

DMI Processor
manufacturer AMD
model AMD FX(tm)-8350 Eight-Core Processor
clock speed 4000.0 MHz
FSB speed 200.0 MHz
multiplier 20.0x

DMI Port Connector
designation KBC (internal)
designation Keyboard (external)
port type Keyboard Port
connector PS/2

DMI Port Connector
designation USB78 (internal)
designation USB78 (external)
port type USB
connector Access Bus (USB)

DMI Port Connector
designation SPDIF_O (internal)
designation SPDIF_O2 (external)
port type Audio Port

DMI Port Connector
designation USB3_12 (internal)
designation USB3_12 (external)
port type USB
connector Access Bus (USB)

DMI Port Connector
designation ESATA6G (internal)
designation ESATA6G (external)

DMI Port Connector
designation USB34 (internal)
designation USB34 (external)
port type USB
connector Access Bus (USB)

DMI Port Connector
designation USB56 (internal)
designation USB56 (external)
port type USB
connector Access Bus (USB)

DMI Port Connector
designation USB3_34 (internal)
designation USB3_34 (external)
port type USB
connector Access Bus (USB)

DMI Port Connector
designation LAN1 (internal)
designation LAN1 (external)
port type Network Port
connector RJ-45

DMI Port Connector
designation USB12 (internal)
designation USB12 (external)
port type USB
connector Access Bus (USB)

DMI Port Connector
designation AUDIO (internal)
designation AUDIO (external)
port type Audio Port

DMI Port Connector
designation SATA6G_12 (internal)

DMI Port Connector
designation SATA6G_34 (internal)

DMI Port Connector
designation SATA6G_56 (internal)

DMI Port Connector
designation SATA6G_E12 (internal)

DMI Port Connector
designation USB3_56 (internal)

DMI Port Connector
designation USB1112 (internal)

DMI Port Connector
designation USB1314 (internal)

DMI Port Connector
designation COM port (internal)

DMI Port Connector
designation TPM (internal)

DMI Port Connector
designation SPDIF_OUT (internal)

DMI Port Connector
designation AAFP (internal)

DMI Port Connector
designation CPU_FAN (internal)

DMI Port Connector
designation CPU_OPT_FAN (internal)

DMI Port Connector
designation CHA_FAN1 (internal)

DMI Port Connector
designation CHA_FAN2 (internal)

DMI Port Connector
designation CHA_FAN3 (internal)

DMI Port Connector
designation CHA_FAN4 (internal)

DMI Extension Slot
designation PCIE16_1
type A5
populated yes

DMI Extension Slot
designation PCIE1_1
type A5
populated no

DMI Extension Slot
designation PCIE16_2
type A5
populated no

DMI Extension Slot
designation PCIE16_3
type A5
populated no

DMI Extension Slot
designation PCI1
type PCI
width 32 bits
populated no

DMI Extension Slot
designation PCIE16_4
type A5
populated no

DMI OEM Strings
string[0] To Be Filled By O.E.M.
string[1] To Be Filled By O.E.M.
string[2] To Be Filled By O.E.M.
string[3] To Be Filled By O.E.M.

DMI Physical Memory Array
location Motherboard
usage System Memory
correction None
max capacity 32768 MBytes
max# of devices 4

DMI Memory Device
designation DIMM0
format DIMM
type unknown
data width 64 bits

DMI Memory Device
designation DIMM1
format DIMM
type unknown
total width 64 bits
data width 64 bits
size 8192 MBytes

DMI Memory Device
designation DIMM2
format DIMM
type unknown
data width 64 bits

DMI Memory Device
designation DIMM3
format DIMM
type unknown
total width 64 bits
data width 64 bits
size 8192 MBytes

Graphics
Number of adapters 1

Graphic APIs
API ATI I/O
API ADL SDK

Display Adapters
Display adapter 0
Name AMD Radeon HD 7900 Series
Memory size 1024 MB
GPU ref clock 27000
PCI device bus 1 (0x1), device 0 (0x0), function 0 (0x0)
Vendor ID 0x1002 (0x1787)
Model ID 0x6798 (0x2317)
Performance Level 0

Software
Windows Version Microsoft Windows 8 (6.2) 64-bit (Build 9200)
DirectX Version 11.0