HTC Vive.First day.

I just got my Vive delivered today, after some fiddling about trying to get the headset to work in Elite Dangerous (I kept getting a grey screen in the headset) I finally managed to get it working. OMG it was amazing the Cobra MKIV cockpit looks huge and my HOTAS set up is roughly the same distance apart as it is in the game so very easy to find.

The only thing that was disconcerting for me when I looked down I found I had boobies which being a man was kind of odd seeing them there. After I resisted the urge to give them a squeeze I tried to focus on the game and fly around a few systems. I even stood up and walked around my cockpit as well and its huge.

I did find the writing to be fuzzy as well as the orbital lines I put this down to some AA problems with the vive? I did find though that if I looked directly at them they did become much clearer.

Running the Vive on a system that is around 4 years on windows 10 running at 60fps with the VR set to high. No problems.

Keep up the good work FD it would be awesome if we could use the Vive controlers in the galaxy map and system map. [up]

Spec.
Operating System: Windows 10 Pro 64-bit (10.0, Build 10586) (10586.th2_release_sec.160422-1850)
Language: English (Regional Setting: English)
System Manufacturer: To be filled by O.E.M.
System Model: To be filled by O.E.M.
BIOS: 1201
Processor: AMD FX(tm)-8350 Eight-Core Processor (8 CPUs), ~4.0GHz
Memory: 16384MB RAM
Available OS Memory: 16284MB RAM
Page File: 5731MB used, 26935MB available
Windows Dir: C:\WINDOWS
DirectX Version: 12
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
Miracast: Available, with HDCP
Microsoft Graphics Hybrid: Not Supported
DxDiag Version: 10.00.10586.0000 64bit Unicode

x2 gfx cards in crossfire.
Card name: AMD Radeon HD 7900 Series
Manufacturer: Advanced Micro Devices, Inc.
Chip type: AMD Radeon Graphics Processor (0x6798)
DAC type: Internal DAC(400MHz)
Device Type: Full Device
Device Key: Enum\PCI\VEN_1002&DEV_6798&SUBSYS_30001002&REV_00
Display Memory: 14248 MB
Dedicated Memory: 6107 MB
Shared Memory: 8141 MB
Current Mode: 1920 x 1080 (32 bit) (60Hz)
Monitor Name: S221HQL (HDMI)
Monitor Model: S221HQL
Monitor Id: ACR01A9
Native Mode: 1920 x 1080(p) (60.000Hz)
Output Type: DVI
 
Congrats - I have just got the OSVR working and am similarly amazed at how good it looks relative to older versions - not to mention 2D!

My CMDR is missing boobies to squeeze though, very disappointed at FDev - filed a bug report - hopefully they'll make it a priority patch for 2.1.03.
 
I just got my Vive delivered today, after some fiddling about trying to get the headset to work in Elite Dangerous (I kept getting a grey screen in the headset) I finally managed to get it working. OMG it was amazing the Cobra MKIV cockpit looks huge and my HOTAS set up is roughly the same distance apart as it is in the game so very easy to find.

The only thing that was disconcerting for me when I looked down I found I had boobies which being a man was kind of odd seeing them there. After I resisted the urge to give them a squeeze I tried to focus on the game and fly around a few systems. I even stood up and walked around my cockpit as well and its huge.

I did find the writing to be fuzzy as well as the orbital lines I put this down to some AA problems with the vive? I did find though that if I looked directly at them they did become much clearer.

Running the Vive on a system that is around 4 years on windows 10 running at 60fps with the VR set to high. No problems.

Keep up the good work FD it would be awesome if we could use the Vive controlers in the galaxy map and system map. [up]

Spec.
Operating System: Windows 10 Pro 64-bit (10.0, Build 10586) (10586.th2_release_sec.160422-1850)
Language: English (Regional Setting: English)
System Manufacturer: To be filled by O.E.M.
System Model: To be filled by O.E.M.
BIOS: 1201
Processor: AMD FX(tm)-8350 Eight-Core Processor (8 CPUs), ~4.0GHz
Memory: 16384MB RAM
Available OS Memory: 16284MB RAM
Page File: 5731MB used, 26935MB available
Windows Dir: C:\WINDOWS
DirectX Version: 12
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
Miracast: Available, with HDCP
Microsoft Graphics Hybrid: Not Supported
DxDiag Version: 10.00.10586.0000 64bit Unicode

x2 gfx cards in crossfire.
Card name: AMD Radeon HD 7900 Series
Manufacturer: Advanced Micro Devices, Inc.
Chip type: AMD Radeon Graphics Processor (0x6798)
DAC type: Internal DAC(400MHz)
Device Type: Full Device
Device Key: Enum\PCI\VEN_1002&DEV_6798&SUBSYS_30001002&REV_00
Display Memory: 14248 MB
Dedicated Memory: 6107 MB
Shared Memory: 8141 MB
Current Mode: 1920 x 1080 (32 bit) (60Hz)
Monitor Name: S221HQL (HDMI)
Monitor Model: S221HQL
Monitor Id: ACR01A9
Native Mode: 1920 x 1080(p) (60.000Hz)
Output Type: DVI


Thank you for sharing the info :) I love my Vive and it is great to see that I'm not alone ;) What I was wondering - is Crossfire supported in VR? If so this would make the RX480 in crossfire quite tempting considering the price range and potential power matching 980ti per card as that should be enough to enjoy VR for a while.. (I currently have 980ti, but I don't feel like splashing out for 1080)
 
Last edited:
No SLI or Crossfire works with VR your only choice to increase performance is get a new graphics card OR reduce settings. There's lots of talk on here about settings but you cannot beat a 1070 or 1080 by the sounds of the quality and figures coming from people on here and Reddit.

I'm with you on the whole experience though. AMAZING
 
Last edited:
No SLI or Crossfire works with VR your only choice to increase performance is get a new graphics card OR reduce settings. There's lots of talk on here about settings but you cannot beat a 1070 or 1080 by the sounds of the quality and figures coming from people on here and Reddit.

I'm with you on the whole experience though. AMAZING


I would pick up the 1080 today if I had certainty that FDev will implement the new VR rendering options in Cobra in somewhat timely manner thus utilize the new architecture as that should in theory allow Ultra settings with 2x SS (only if ;) ), but considering that it has been months now for fixing Vive issue (and still no proper solution on either scaling issue, rendering issue or the text readability) I have small trust issues when it comes to FDev and 20/30% improvement doesn't seem justified to me for the investment just yet.... All my other VR games look awesome with my 980ti and Vive with no huge AA issues or scaling bugs...
 
I did find the writing to be fuzzy as well as the orbital lines I put this down to some AA problems with the vive?
I haven't used the Vive, but I understand that it doesn't have a huge "sweet spot" on the lenses, so there'll be some blurring outside of the centre of the lens.
 
I think there is a setting to turn on and off your two priority patches (male / female)

Dree

Yes if you look in Graphics options there is a setting for male/female avatars. It was put in during late alpha or early closed beta. I had just forgot that I had it set since then to female avatar as I tested the option and forgot about it. *shrugs*

As for new graphics cards on the AMD side I would wait till after June, their new cards will be out and they are going to start at the price of $200 on their new architecture. Looking at the figures they at present out perform Nvidia.
 
Back
Top Bottom