Search Results for 'Ice Age 2'

[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]

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

[namine207]

Hey guys! So after a lot of messing with emulators to get VorpX working, I decided to write a quick guide for anyone who wants to play emulated games in the Rift! So far, I’ve only managed to get three emulators working, but if anyone finds out how to do another emulator, I’ll gladly add it to this post and give them credit!

Alrighty, here we go!

Nintendo 64 (Via Project64, many thanks to Ralf on this one!):

1. Download Project64 1.6. For some reason, 2.0 doesn’t seem to like VorpX.
2. Download Rice’s Video Plugin from here (http://files.emulation64.fr/Plugins/VID_Mudlord_RiceVideoSetup_6-1-4.zip)
3. Extract the files inside to the [Project64 1.6 Installation]/Plugin/ folder.
4. Run Project64 with VorpX control open and set Mudlord’s Rice Video Build 6.1.3 – DX9 as your graphics plugin. Feel free to make any changes in the plugin’s configuration (1280 x 800 resolution, etc, etc.)
5. Run the desired rom! You will get a warning sometime during this guide that tracking isn’t functioning. This is true, and for now, all you’ll have is that awesome Oculus vision! However, in the next VorpX update, we’ll have KeyMapping, so you can very easily map head movements to keys, like Up, Down, Left, and Right!

Note: If it still doesn’t work, you may have to put BGMlib.dll into the same directory as Project64.exe. I used the BGMlib.dll from the 2.0 installation, inside plugins/gfx/, but I don’t think it should matter.

PS2 (Via PCSX2):

1. Install PCSX2 0.9.6.
2. Download any roms, bios files, etc. to get the emulator working properly, and run it with VorpX control open.
3. Set the graphics plugin to GSdx 890 (MSVC 15.00, [Whatever type of SSE your processor is. SSE2 is probably the safest if you don’t know, but test it out and see.])
4. Open the configuration and change the following things:
Resolution: 1280×800 60Hz
Renderer: Direct3D9 (Software)
Shader: Pixel Shader 3.0 (2.0 probably works as well, haven’t tested it yet)
Interlacing: None
5. Click okay and run the iso! Same deal as with PJ64, it won’t head track, but with keymapping coming soon, we’ll be able to map head movements to keys!

NOTE: This setup is for 0.9.6, but theoretically, you can apply it to any later version. You just have to take the 0.9.6 graphics plugins and put them into the plugins folders for 0.9.7, 8, and most likely 1.0. It seems the later versions took out a lot of the options that help VorpX recognize the emulated game.

Gamecube (Via Dolphin, with help from Ralf and Marulu):

1. Download and install Dolphin 4.0
2. Edit the video plugin configuration so that it’s using the Direct3D9 backend. (Tested it with Direct3D 11, but it didn’t take.)
3. Change fullscreen resolution to 1280 x 800, v-sync, hide mouse cursor, use fullscreen. Under enhancements, scaled EFB copy, widescreen hack, and under advanced, freelook.
4. Start the iso! If you want to look around without keymapping, you do have the freelook feature enabled, which will allow you to look around by right clicking, and then looking around with the rift. But based on past experience, it moves really fast and doesn’t line up with your head movements particularly well, so it’s kind of meh…

So that’s it! If you have any problems setting these up, let me know, and I’ll give you suggestions to fix them! I hope to see more emulators with rift support soon, as they definitely can help fill the rift library with new VR Classics. :3

[Helvie]

Hi all,

I got my registration key yesterday and tried to activate this driver. Unfortunately I can’t do this. Even if I try to do so, I receive an Error which says that my registration information could not be validated (See Screenshot: . For me it seems that the tool can’t connect to any Server.

I tried the following to solve this Issue but without success:
– Deactivated the AntiVirus (AntiVir, deactivated the service of it too)
– Added the exeption for the whole folder of VorpX
– Software Firewall is deactivated anyway
– Tried to start the tool with administrator permissions
– I do copy the whole Name inclusive email from the registration mail

Because of the Error-Message, for me it seems that there is no problem with the key but with the connection to the server. Does anybody of you have an Idea how to solve this Issue? By the way, which Port is it using? Maybe I have to configure a port forwarding on my HW-Firewall?

Many thanks in advance!

Helvie

[LazloTheGreat]

Works fine on one my machines (older, running Windows 7), but I get the 30 sec crash on the other (newer, running Windows 8).

Perhaps it’s worth noting that even though BI starts through Steam on both machines, it does work fine on the one through which I initially installed from the DVD-ROMs (Windows 7), but does NOT work on the 2nd machine (Windows 8) through which I merely duplicate installed directly from my Steam online account without the DVD-ROMS.

This second to-be-installed-on Windows 8 machine was actually the first one I tried with vorpX as it was the newer faster one. As luck would have it, my DVD-ROMS have been damaged so unfortunately I can’t try re-installing from them on the Windows 8 non-working machine to see if it makes a difference.

Specs:

Non-Working Windows 8 Machine, BI duplicate digital installation directly from Steam

Operating System: Windows 8 Pro, 64-bit
DirectX version: 11.0
GPU processor: GeForce GT 750M
Driver version: 320.78
Direct3D API version: 11.1
Direct3D feature level: 11_0
CUDA Cores: 384
Core clock: 941 MHz
Memory data rate: 5000 MHz
Memory interface: 128-bit
Memory bandwidth: 80.00 GB/s
Total available graphics memory: 4096 MB
Dedicated video memory: 2048 MB GDDR5
System video memory: 0 MB
Shared system memory: 2048 MB
Video BIOS version: 80.07.88.00.15
IRQ: 16
Bus: PCI Express x16 Gen3

Working Windows 7 Machine, BI DVD-ROM installed

Operating System: Windows 7 Home Premium, 64-bit (Service Pack 1)
DirectX version: 11.0
GPU processor: GeForce GTX 460M
Driver version: 266.86
DirectX support: 11
CUDA Cores: 192
Core clock: 675 MHz
Shader clock: 1350 MHz
Memory clock: 1250 MHz (2500 MHz data rate)
Memory interface: 192-bit
Total available graphics memory: 4095 MB
Dedicated video memory: 1536 MB GDDR5
System video memory: 0 MB
Shared system memory: 2559 MB
Video BIOS version: 70.06.25.00.07
IRQ: 16
Bus: PCI Express x16 Gen2

[Ralf]

There are three things that you need to take care of once for each game:

1. Enhancing the field of view (FOV), otherwise the image will appear zoomed in.
2. Adjusting the head tracking sensitivy in the vorpX ingame menu.
3. Choosing the optimal 3D mode dpending on your PC’s performance.

1. Field Of View

Setting up the FOV correctly is crucial with the Play Style option set to Full VR. With a wrong FOV in Full VR mode the image looks zoomed in and/or warped. For many games vorpX can handle that automatically, either by auto-adjusting game settings or with the DirectVR memory scanner.

If vorpX cannot handle FOV automatically for a game, the ideal options are:

• Setting the FOV in the game options if possible. The right value usually is 112° horizontically or 96° vertically. Some games however use arbitrary numbers, so these values aren’t always right!
• Setting the FOV with a tool like Flawless Widescreen or by tweaking a game’s config files. The PC Gaming Wiki is a great source of information in this regard.

If the actual game FOV cannot be set high enough or changed at all, the following workarounds exist. You can combine them for the best possible result.

• Use one of the letterbox aspect ratio modes in the vorpX ingame menu and/or the Image Zoom setting to compensate for a low FOV.
• Check whether 4:3 or 16:9 resolutions work better. Depending on the game one may be better than the other in regard to FOV.
• Use the 3D FOV Enhancement in the vorpX ingame menu (availabe in Geometry 3D games).

Should you encounter a game where it is not possible to get a good a result with the methods above, you can set the Play Style in the vorpX menu to Immersive Screen Mode or Virtual Cinema Mode, which don’t require a perfectly tuned FOV.

2. Head Tracking

If a game does not support DirectVR head tracking, vorpX handles head tracking relative to your individual mouse sensitivity in a game, so it might need some tweaking. If the view rotates either too fast or too slow while turning your head, adjust the Sensitivity on the Head Tracking Settings page of the in-game menu.

A good way to calibrate mouse based head tracking is placing yourself directly in front of a wall in the game and then rotate your (real) head 90° degrees. Check how far your ingame view rotated while doing that and lower/raise the sensitivity if necessary. Doing this two or three times should usually suffice to get solid tracking.

3. 3D-Mode

vorpX uses two very different approaches for creating Stereo 3D. All supported games have Z-Buffer 3D, many of them Geometry 3D. Geometry 3D offers the most lifelike 3D experience, while Z-Buffer 3D is about twice as fast (but has ‘less 3D’). Especially in resource hungry games you should consider the Z-Buffer mode. A high framerate is very important for a great VR experience, often more important than perfect Stereo 3D.

[Valez]

TLDR:
Mycommerce support is a joke. It seems that I have to wait till next week until I hear from them again. Don’t worry Ralf, I am still patient and can wait until you are less busy.

———————

After another 24 hours I got this mail:

Thank you for contacting RegNow.

We apologize for the inconvenience. Unfortunately, we are unable to determine the cause of the issue with the information provided. Please reply with additional information so that we may assist you. If you are receiving an error message, please include the message or message number. If you do not have this information, please try to place a new order.

To attempt a new order, start by going to the vendors website.

Before attempting a new order, please try to delete your cookies and browsing history for your better assistance of your online purchase.

Add the product(s) you wish to purchase to the shopping cart. Once you have the items you wish to purchase in the shopping cart click on “Checkout”. We recommend when placing an order that you enter your billing information as it appears on your credit card billing statement.
Please note that your order is not complete until you press the “Submit Order” button at the bottom of the Order Confirmation Page.

If you would like to place an order over the phone we can definitely assist you. Your may dial this number 1-877-353-7297 to reach our order placement department and customer service.

Thank you for your patience.

Giving me a Washington phone number when I live in Germany is really brilliant.
After another 24 hours they finally seem to realise I’m not too stupid to click some buttons and write my name, but they still seem worried I may be not clever enough to receive emails:

Thank you for contacting RegNow.

We are sorry for the inconvenience.

We have forwarded your concern regarding order placement issue through online purchase to our escalation department to further investigate this issue. You will be notified with our team via email within 2-3 business days and please monitor your email folders such as spam or junk mails.

Your ticket number: XXX
Order number: XXX

Thank you for your patience.

[Dudesre89]

@AledB

Try the things I list below.

1) Try Rift in another Usb port that is connected to you motherboard.
2) remove all other Usb devices apart form mouse and rift.

Still not Working

1) uninstall Usb devices and then re-install under device manager.
2) make sure Trackir is not running if you have it
3) Type msconfig in the run box and make sure to disable the programs you don’t want running.
4) Make sure your Rift’s head tracking is still enabled when you run these games by pressing on the Oculus config utility, it just might be that it is been disabled.
5) do you have Logitech wireless mouse or any other wireless mouse you are using? Try a wired one and disable the wireless one.

[Valez]

Got an answer from mycommerce after almost 24 hours, and it doesn’t help at all:

Dear X
Thank you for contacting MyCommerce.

We apologize for the inconvenience. Unfortunately, no complete orders were found under your information. Please try to place a new order.

To attempt a new order, start by going to the vendors website.

Add the product(s) you wish to purchase to the shopping cart. Once you have the items you wish to purchase in the shopping cart click on “Checkout”. We recommend when placing an order that you enter your billing information as it appears on your credit card billing statement.
Please note that your order is not complete until you press the “Submit Order” button at the bottom of the Order Confirmation Page.

Sincerely,
Carol G.
MyCommerce
Customer Service
ordersupport@mycommerce.com
http://www.mycommerce.com/faq
Email ID: 26786397

What a shitty service (I mean mycommerce)!
It seems they don’t even know their own system.

I already send you an email Ralf. If there is an alternate way of purchasing vorpX for me, I would be very happy.

[museumsteve]

Susu986 wrote:

museumsteve: I got your point, and you are also right. But I’m not asking much, isn’t it??? And yeah, RFactor 2 would be nice!

Of course I’m with you all the way :) I’m just very mellow in my old age ;)

[Jademalo]

brad wrote:

I am very excited about your driver. A few questions if I could. You mention your stereo driver’s technique only adds ~10% overhead. I am not clear if you mean 10% over a single eye’s resolution (640×800) if you were to simply output that to a monoscopic screen or if you mean 10% over what would be the horsepower needed to output the resolution (1280×800) taken up by both eyes. In other words should I expect performance equal to a 10% hit to my favorite game played at 640×800 on a regular screen or that same game at 1280×800?

 

By overhead, he means performance. As in, to generate a stereoscopic image, it only takes 10% more GPU power to run at the same speed as without 3D. Standard methods render the image twice, so take nearly double the power.