Wireless Adapter on Vive Pro - blurry resolution and performance impact

SteveCole
Pioneer

Wireless Adapter on Vive Pro - blurry resolution and performance impact

Hi, I just got my Vive Pro and Wireless Adapter and set it up with my base station and controller 1.0. I thoroughly tested wired vs wireless for consistency. I noticed a significant loss of resolution on Vive Pro by going wireless. This can be compensated by applying enough supersampling in SteamVR. However, the performance is significantly impacted as a result with more reprojection and lower framerates. Everything else works as expected, no tracking issues even at 400% supersampling, no choppy performance, no connection loss or blackouts and wireless connection strength is always at full bars. Is this normal behaviour or am I missing something.

As an example, Fallout 4 VR looks pretty sharp with wired Vive Pro with SteamVR 100% supersampling. In wireless image is very blurry at same supersampling and similar performance. I have to increase supersampling to at least 200% to get a similar image quality but of course at a lower performance. Anyone else experiencing issues with Vive Pro? I'm reading customer reviews on Amazon that people are having similar problems with Vive Pro and Wireless Adapter.

My specs:
Asus Rampage VI Extreme X299
CoreX i7 7820X
Asus Strix 1080ti OC
32GB Corsair DDR4 3200
Samsung SSD 960 Pro 1TB
EVGA 1200watt PSU

WiGig card is inserted in the only 4X slot available. I can't use the PCI-E16_2 as it's covered by dual slot GPU. Due to CPU limitations I only have another PCI-E16 at 8X speed available, and I don't think it will make a difference either.
I have made relevant changes to BIOS and all lanes are set at Gen 3.0.

Any ideas how to fix it? Thanks.
RedRising
Contributor

Re: Wireless Adapter on Vive Pro - blurry resolution and performance impact

Facing the exact same issue as you.

I have almost identical specs to yours and I did try to use the PCIEX16 slot, not difference

 

My specs:
CoreX i7 7700K
Nvidia GTX 1080ti FE
32GB Corsair DDR4 3200
Samsung SSD 960 Pro 1TB
EVGA 1200watt PSU

 

Very frustrating. I have tried the three channeles on the wireless - no change.

Testing the issue in Arizona Sunshine - Horde Mode. no lagging but the background is completly pixilated on wireless. Interestingly though, I dont see the pixilation on the screen mirror on my desktop monitor, only in the HMD itself. Even adjusting game specific supersampling doesnt help the pixilation... 

 

Doing research on the web ... so far nothing valuable...

Re: Wireless Adapter on Vive Pro - blurry resolution and performance impact

Can you post some output text from the log files located at C:\Program Files\VIVE Wireless\ConnectionUtility\Log
It may help someone diagnose your issue.

The reason you do not see pixelation on the monitor is because the compression is being done by the PCI-e card before it is sent to the HMD, and is not affecting the output to your monitor, I believe.

SteveCole
Pioneer

Re: Wireless Adapter on Vive Pro - blurry resolution and performance impact

I will post the log tonight so hopefully it can shed some light. I did some further testing last night and had some interesting findings.

This issue seems to be affecting Fallout 4 VR which is a power hungry game. I tested The Lab (robot repair and other mini games) and resolution was just as sharp as wired with same supersampling. The Lab has no difference wired vs wireless.

I'm not sure if Vive Wireless Adapter goes blurry based on how demanding a game is or is it a game specific bug. The strange thing is that applying supersampling brings Fallout 4 VR back to normal but at a performance loss. I have Fallout 4 VR at supersampling of 1.7 (in game through ini tweak) and now it looks pretty sharp. Can anyone test if their issue can me mitigated by applying supersampling? Or do you guys always have blury image regardless of supersampling amount?

Obviously more testing is needed as I didn't have time to test other games. In Fallout 4 - Diamond City, there's a shop with robot in the middle, and right behind the robot there's a sign that reads "All employees must wash hands...". I use that particular spot for testing image sharpness. At SteamVR 100% supersampling the sign is not legible, but at 200% you can read it. Can anyone test it with wired to see if the sign is legible at 100% supersampling?

A major hurdle in testing is switching the cables and opening the headset, especially with the flimsy compartment cover that is worst design and easily breakable. I wish HTC could sell a female-female adapter so we could quickly change cables if we decided to go wired sometimes.

SteveCole
Pioneer

Re: Wireless Adapter on Vive Pro - blurry resolution and performance impact

Update:

I did some further testing and I'm happy to report everything else runs exactly as wired. As I kept scratching my head wondering why Fallout 4 VR looks blurry and thinking back, I realized my mistake. I had set in-game supersampling of Fallout 4 VR at 1.6 through ini tweak. When I installed my Vive Pro last week, it was still at 1.6 so everything looked sharp when I tested Vive Pro. Then just before installing Wireless Adapter I removed the supersampling tweak to avoid issues and forgot about it. A simple forgetfullness led to so much troubleshooting. Fallout 4 VR is not optimized for Vive Pro, so with OG Vive it looks fine, but with Vive Pro the lower resolution textures become apparent.

 

Overall I'm very happy with the Wireless Adapter. I have none of the issues people are reporting. No tracking loss, no lag, no disconnects, no choppiness, no loss of sharpness, and no heat issues, even at much higher supersampling values and long play sessions. Eveything works exactly as advertised, cameras, mic, etc. I guess I consider myself lucky or an oddity here. My Wireless Adapter preorder was delayed and that perhaps gave me plenty of time to read about other people's impressions and technical issues, so I kinda had a good idea of what to expect and how to troubleshoot. TBH when I first fired up Wireless Adapter to test I was pretty nervous not knowing what to expect after spending so much. I'll share some of the considerations and steps I took before and after installing the adapter to ensure a smooth experience:

 

My system specs are in my above post but I'll add that my Windows 10 version is 1709.

  • First, make sure you consult your motherboard manual and CPU model thoroughly and learn it's PCI-E slot limitations like total lanes, lane sharing with GPU slot, and Gen 2/3, and decide which slot is your best fit.
  • Use the slot closest to CPU provided it has the lanes and speed you need. NEVER go cheap on motherboad; buy the best out there as you'll regret it some day otherwise.
  • Apply proper BIOS settings to ensure your PCI-E slot runs at Gen 3 and don't just leave things in "auto". I set the lane speed manually at Gen 3 before installing WiGig card.
  • I have installed the Wireless Linkbox much higher than recommended monitor height, about 2.5 meters above ground as my case is sitting on desk. This way it always has a line of sight no matter which way I turn.
  • Before installing Wireless Adapter make sure you update all firmware (headset, controllers, base stations etc), update Steam, SteamVR, and clean install latest NVIDIA drivers.
  • IMPORTANT - make sure you disconnect the displayport cable from GPU to wired link box. Leave link box connected through USB as you'll need it to update and power manage your base stations through bluetooth.
  • Change your WiFi to 5G only, and turn off 2.4G. I did this before installing the adapter.
  • After installing the wireless software make sure to restart the system.
  • I usually start with turning on wired link box, wireless software, then run Steam and SteamVR. After play session, I close SteamVR and Steam then wireless software then power off link box.

 

Hope these help anyone having issues. I guess these steps that I proactively took and my system specs can be used as a reference of what works and what doesn't. Obviously meeting advertised system requirements doesn't guarantee that it will work. HTC has missed a lot in there. For a lot of people making the adapter work as advertised with no issues is a hit or miss with too many variables and unknowns in between. Majority of issues are arising from motherboard limitations I guess. Cheers.

RedRising
Contributor

Re: Wireless Adapter on Vive Pro - blurry resolution and performance impact

Here is an output from the log file.. let me know if you see anything strange

# Log begin at 2018-10-16 17:59:03.451
[2018-10-16 17:59:03.451 -8 0x27B4 INFO LOG] CU Begin
[2018-10-16 17:59:03.467 -8 0x27B4 INFO LOG] Load languages from : C:\Program Files\VIVE Wireless\ConnectionUtility\Text\Languages.json
[2018-10-16 17:59:03.474 -8 0x27B4 INFO LOG] Load text from : C:\Program Files\VIVE Wireless\ConnectionUtility\Text\en_US.json
[2018-10-16 17:59:03.474 -8 0x27B4 INFO LOG] Load Language Text : en_US
[2018-10-16 17:59:03.474 -8 0x27B4 INFO LOG] Load fonts from : C:\Program Files\VIVE Wireless\ConnectionUtility\Font\Fonts.json
[2018-10-16 17:59:03.478 -8 0x27B4 INFO LOG] Parsed fonts config : C:\Program Files\VIVE Wireless\ConnectionUtility\Font\Fonts.json
[2018-10-16 17:59:03.526 -8 0x2A44 INFO LOG] DisplayLink driver registered.
[2018-10-16 17:59:03.528 -8 0x3DB8 INFO LOG] Known device : 0BB4/030A
[2018-10-16 17:59:03.528 -8 0x3DB8 INFO LOG] Known device : 2BDE/2300
[2018-10-16 17:59:03.528 -8 0x3DB8 INFO LOG] Known device : 0BB4/030C
[2018-10-16 17:59:03.528 -8 0x3DB8 INFO LOG] Known device : 0BB4/030B
[2018-10-16 17:59:03.528 -8 0x3DB8 INFO LOG] Known device : 0BB4/0309
[2018-10-16 17:59:03.528 -8 0x3DB8 INFO LOG] Known device : 2BDE/2101
[2018-10-16 17:59:03.528 -8 0x3DB8 INFO LOG] Known device : 0BB4/2134
[2018-10-16 17:59:03.528 -8 0x3DB8 INFO LOG] Known device : 2BDE/2000
[2018-10-16 17:59:03.528 -8 0x3DB8 INFO LOG] Known device : 0BB4/2C87
[2018-10-16 17:59:03.528 -8 0x3DB8 INFO LOG] Known device : 0D8C/0012
[2018-10-16 17:59:03.528 -8 0x3DB8 INFO LOG] Known device : 0BB4/2C87
[2018-10-16 17:59:03.528 -8 0x3DB8 INFO LOG] Known device : 2BDE/2101
[2018-10-16 17:59:03.528 -8 0x3DB8 INFO LOG] Known device :
[2018-10-16 17:59:04.032 -8 0x470 INFO LOG] (ControlCenter)GetDeviceStatus : SDK_WIGIGFSM_STATE_STOPPED(3), reason = SDK_CURRENT_STATE_REASON_NOT_SCANNING(16)
[2018-10-16 17:59:04.032 -8 0x470 INFO LOG] (ControlCenter)CallbackDeviceStatus : SDK_WIGIGFSM_STATE_STOPPED(3), reason = SDK_CURRENT_STATE_REASON_NOT_SCANNING(16)
[2018-10-16 17:59:04.032 -8 0x470 INFO LOG] (ControlCenter)Intel WiGig SDK DLL Version : 4.0.10371.5
[2018-10-16 17:59:04.032 -8 0x470 INFO LOG] Init OK
[2018-10-16 17:59:04.252 -8 0x470 INFO LOG] (ControlCenter)Set RF ON success.
[2018-10-16 17:59:04.254 -8 0x470 INFO LOG] SteamVR version : 1539100633
[2018-10-16 17:59:04.379 -8 0x3FAC INFO LOG] (ControlCenter)CallbackDeviceStatus : SDK_WIGIGFSM_STATE_STOPPED(3), reason = SDK_CURRENT_STATE_REASON_NOT_SCANNING(16)
[2018-10-16 17:59:04.461 -8 0x3FAC INFO LOG] (ControlCenter)CallbackDeviceStatus : SDK_WIGIGFSM_STATE_SCANNING(4), reason = SDK_CURRENT_STATE_REASON_REQUESTED_BY_APPLICATION(9)
[2018-10-16 17:59:04.465 -8 0x3FAC INFO LOG] (ControlCenter)CallbackDeviceStatus : SDK_WIGIGFSM_STATE_CONNECTING(5), reason = SDK_CURRENT_STATE_REASON_AUTO_PROFILE_FOUND(4)
[2018-10-16 17:59:04.485 -8 0x27B4 INFO LOG] Connection Status set to 2(CONNECTION_STATUS_SCANNING)
[2018-10-16 17:59:04.487 -8 0x27B4 INFO LOG] Connection Status set to 3(CONNECTION_STATUS_CONNECTING)
[2018-10-16 17:59:04.728 -8 0x3FAC INFO LOG] (ControlCenter)CallbackDeviceStatus : SDK_WIGIGFSM_STATE_CONNECTED(7), reason = SDK_CURRENT_STATE_REASON_SUCCEED_TO_CONNECT(13)
[2018-10-16 17:59:04.730 -8 0x3FCC INFO LOG] (ControlCenter)Get dock device name : VIVE-ALON
[2018-10-16 17:59:04.730 -8 0x3FCC INFO LOG] Device Name : VIVE-ALON
[2018-10-16 17:59:04.730 -8 0x2264 INFO LOG] Connection Status set to 7(CONNECTION_STATUS_PREPARING)
[2018-10-16 17:59:04.730 -8 0x2264 INFO LOG] BeginMcuUpdate
[2018-10-16 17:59:04.736 -8 0x3FCC INFO LOG] (ControlCenter)Otp Channel 1
[2018-10-16 17:59:04.736 -8 0x3FCC INFO LOG] (ControlCenter)Otp Channel 2
[2018-10-16 17:59:04.736 -8 0x3FCC INFO LOG] (ControlCenter)Otp Channel 3
[2018-10-16 17:59:04.736 -8 0x3FCC INFO LOG] (ControlCenter)Get dock preferred channel : Channel 3 (Player 2)
[2018-10-16 17:59:04.736 -8 0x3FCC INFO LOG] Preferred Channel : Channel 3 (Player 2)
[2018-10-16 17:59:04.740 -8 0x3FCC INFO LOG] (ControlCenter)CurrentFwVersion : 4.0.10371.5
[2018-10-16 17:59:04.740 -8 0x3FCC INFO LOG] (ControlCenter)FactoryFwVersion : 4.0.10327.19
[2018-10-16 17:59:04.740 -8 0x3FCC INFO LOG] (ControlCenter)NvmVersion : 8.32.2.7
[2018-10-16 17:59:04.740 -8 0x3FCC INFO LOG] (ControlCenter)MacHwVersion : 6577
[2018-10-16 17:59:04.740 -8 0x3FCC INFO LOG] (ControlCenter)RFEM1HwVersion : 8
[2018-10-16 17:59:04.740 -8 0x3FCC INFO LOG] (ControlCenter)RFEM2HwVersion : 8
[2018-10-16 17:59:04.740 -8 0x3FCC INFO LOG] (ControlCenter)ActiveFwVersion : MAIN
[2018-10-16 17:59:04.756 -8 0x2264 INFO LOG] MCU Update Launch OK.
[2018-10-16 17:59:05.696 -8 0x3FAC INFO LOG] (ControlCenter)Link Condition Change : peerSignalQuality = 4, performanceQuality = 3
[2018-10-16 17:59:08.555 -8 0x2264 INFO LOG] MCU Update Closed. Wait for 3 seconds.
[2018-10-16 17:59:11.562 -8 0x2264 INFO LOG] Connection Status set to 5(CONNECTION_STATUS_CONNECTED)
[2018-10-16 17:59:13.525 -8 0x1BEC INFO LOG] CreateProcess : C:\Program Files\VIVE Wireless\Updater\Updater.exe
[2018-10-16 17:59:13.525 -8 0x1BEC INFO LOG] Param : -NoUI MANX -StopWhenBrotherRunning -SkipAdditionTasks
[2018-10-16 17:59:13.525 -8 0x1BEC INFO LOG] Dir : C:\Program Files\VIVE Wireless\Updater
[2018-10-16 17:59:13.638 -8 0x1BEC INFO LOG] CreateProcess OK
[2018-10-16 17:59:14.734 -8 0x27B4 INFO LOG] M_Temperature=31, R_Temperature=27
[2018-10-16 17:59:15.717 -8 0x1BEC INFO LOG] Updater exit 0
[2018-10-16 17:59:15.718 -8 0x1BEC INFO LOG] No new DisplayLink version : 1.1.33748.8682
[2018-10-16 17:59:15.719 -8 0x1BEC INFO LOG] No new IntelWiGig version : 4.0.10371.12G_VR(msi)
[2018-10-16 17:59:15.719 -8 0x1BEC INFO LOG] No new WirelessUpdate version : 1.0.0.12
[2018-10-16 17:59:15.720 -8 0x1BEC INFO LOG] No new CU version : 1.0.0.67
[2018-10-16 17:59:24.730 -8 0x27B4 INFO LOG] M_Temperature=32, R_Temperature=29
[2018-10-16 17:59:34.742 -8 0x27B4 INFO LOG] M_Temperature=33, R_Temperature=31
[2018-10-16 17:59:44.732 -8 0x27B4 INFO LOG] M_Temperature=38, R_Temperature=35
[2018-10-16 17:59:54.731 -8 0x27B4 INFO LOG] M_Temperature=40, R_Temperature=36
[2018-10-16 18:00:04.730 -8 0x27B4 INFO LOG] M_Temperature=41, R_Temperature=39
[2018-10-16 18:00:24.736 -8 0x27B4 INFO LOG] M_Temperature=43, R_Temperature=44
[2018-10-16 18:00:34.734 -8 0x27B4 INFO LOG] M_Temperature=45, R_Temperature=46
[2018-10-16 18:00:54.736 -8 0x27B4 INFO LOG] M_Temperature=47, R_Temperature=42
[2018-10-16 18:01:04.732 -8 0x27B4 INFO LOG] M_Temperature=46, R_Temperature=46
[2018-10-16 18:01:14.731 -8 0x27B4 INFO LOG] M_Temperature=48, R_Temperature=51
[2018-10-16 18:01:24.734 -8 0x27B4 INFO LOG] M_Temperature=49, R_Temperature=45
[2018-10-16 18:01:34.731 -8 0x27B4 INFO LOG] M_Temperature=50, R_Temperature=47
[2018-10-16 18:01:44.735 -8 0x27B4 INFO LOG] M_Temperature=51, R_Temperature=50
[2018-10-16 18:01:54.733 -8 0x27B4 INFO LOG] M_Temperature=49, R_Temperature=50
[2018-10-16 18:02:04.734 -8 0x27B4 INFO LOG] M_Temperature=52, R_Temperature=50
[2018-10-16 18:02:14.735 -8 0x27B4 INFO LOG] M_Temperature=49, R_Temperature=49
[2018-10-16 18:02:24.731 -8 0x27B4 INFO LOG] M_Temperature=55, R_Temperature=52
[2018-10-16 18:02:34.736 -8 0x27B4 INFO LOG] M_Temperature=54, R_Temperature=53
[2018-10-16 18:02:44.733 -8 0x27B4 INFO LOG] M_Temperature=55, R_Temperature=55
[2018-10-16 18:02:54.732 -8 0x27B4 INFO LOG] M_Temperature=56, R_Temperature=57
[2018-10-16 18:03:04.733 -8 0x27B4 INFO LOG] M_Temperature=58, R_Temperature=58
[2018-10-16 18:03:24.735 -8 0x27B4 INFO LOG] M_Temperature=57, R_Temperature=57
[2018-10-16 18:03:44.734 -8 0x27B4 INFO LOG] M_Temperature=59, R_Temperature=50
[2018-10-16 18:03:54.741 -8 0x27B4 INFO LOG] M_Temperature=60, R_Temperature=49
[2018-10-16 18:04:24.733 -8 0x27B4 INFO LOG] M_Temperature=61, R_Temperature=56
[2018-10-16 18:04:44.731 -8 0x27B4 INFO LOG] M_Temperature=62, R_Temperature=58
[2018-10-16 18:04:54.732 -8 0x27B4 INFO LOG] M_Temperature=63, R_Temperature=53
[2018-10-16 18:05:04.734 -8 0x27B4 INFO LOG] M_Temperature=64, R_Temperature=58
[2018-10-16 18:05:44.736 -8 0x27B4 INFO LOG] M_Temperature=67, R_Temperature=56
[2018-10-16 18:05:54.732 -8 0x27B4 INFO LOG] M_Temperature=66, R_Temperature=55
[2018-10-16 18:06:04.738 -8 0x27B4 INFO LOG] M_Temperature=67, R_Temperature=53
[2018-10-16 18:06:34.733 -8 0x27B4 INFO LOG] M_Temperature=68, R_Temperature=54
[2018-10-16 18:06:44.732 -8 0x27B4 INFO LOG] M_Temperature=69, R_Temperature=53
[2018-10-16 18:07:14.730 -8 0x27B4 INFO LOG] M_Temperature=70, R_Temperature=56
[2018-10-16 18:07:34.732 -8 0x27B4 INFO LOG] M_Temperature=71, R_Temperature=62
[2018-10-16 18:07:44.735 -8 0x27B4 INFO LOG] M_Temperature=72, R_Temperature=59
[2018-10-16 18:08:54.730 -8 0x27B4 INFO LOG] M_Temperature=73, R_Temperature=64
[2018-10-16 18:09:24.731 -8 0x27B4 INFO LOG] M_Temperature=71, R_Temperature=63
[2018-10-16 18:09:34.732 -8 0x27B4 INFO LOG] M_Temperature=75, R_Temperature=67
[2018-10-16 18:10:24.738 -8 0x27B4 INFO LOG] M_Temperature=76, R_Temperature=62
[2018-10-16 18:10:31.706 -8 0x3FAC INFO LOG] (ControlCenter)Link Condition Change : peerSignalQuality = 3, performanceQuality = 3
[2018-10-16 18:10:34.706 -8 0x3FAC INFO LOG] (ControlCenter)Link Condition Change : peerSignalQuality = 4, performanceQuality = 3
[2018-10-16 18:10:34.736 -8 0x27B4 INFO LOG] M_Temperature=78, R_Temperature=62
[2018-10-16 18:10:44.735 -8 0x27B4 INFO LOG] M_Temperature=76, R_Temperature=56
[2018-10-16 18:10:54.734 -8 0x27B4 INFO LOG] M_Temperature=71, R_Temperature=52
[2018-10-16 18:11:04.734 -8 0x27B4 INFO LOG] M_Temperature=76, R_Temperature=54
[2018-10-16 18:11:14.736 -8 0x27B4 INFO LOG] M_Temperature=77, R_Temperature=56
[2018-10-16 18:11:24.735 -8 0x27B4 INFO LOG] M_Temperature=78, R_Temperature=61
[2018-10-16 18:11:34.733 -8 0x27B4 INFO LOG] M_Temperature=79, R_Temperature=62
[2018-10-16 18:11:44.734 -8 0x27B4 INFO LOG] M_Temperature=78, R_Temperature=58
[2018-10-16 18:11:46.707 -8 0x3FAC INFO LOG] (ControlCenter)Link Condition Change : peerSignalQuality = 3, performanceQuality = 3
[2018-10-16 18:11:48.706 -8 0x3FAC INFO LOG] (ControlCenter)Link Condition Change : peerSignalQuality = 4, performanceQuality = 3
[2018-10-16 18:12:14.732 -8 0x27B4 INFO LOG] M_Temperature=79, R_Temperature=61
[2018-10-16 18:12:24.737 -8 0x27B4 INFO LOG] M_Temperature=78, R_Temperature=61
[2018-10-16 18:12:34.740 -8 0x27B4 INFO LOG] M_Temperature=80, R_Temperature=55
[2018-10-16 18:12:44.732 -8 0x27B4 INFO LOG] M_Temperature=81, R_Temperature=57
[2018-10-16 18:12:54.734 -8 0x27B4 INFO LOG] M_Temperature=79, R_Temperature=54
[2018-10-16 18:13:04.733 -8 0x27B4 INFO LOG] M_Temperature=80, R_Temperature=53
[2018-10-16 18:13:34.731 -8 0x27B4 INFO LOG] M_Temperature=81, R_Temperature=54
[2018-10-16 18:13:38.708 -8 0x3FAC INFO LOG] (ControlCenter)Link Condition Change : peerSignalQuality = 3, performanceQuality = 3
[2018-10-16 18:13:42.708 -8 0x3FAC INFO LOG] (ControlCenter)Link Condition Change : peerSignalQuality = 4, performanceQuality = 3
[2018-10-16 18:13:44.735 -8 0x27B4 INFO LOG] M_Temperature=83, R_Temperature=57
[2018-10-16 18:13:49.709 -8 0x3FAC INFO LOG] (ControlCenter)Link Condition Change : peerSignalQuality = 3, performanceQuality = 3
[2018-10-16 18:13:50.708 -8 0x3FAC INFO LOG] (ControlCenter)Link Condition Change : peerSignalQuality = 2, performanceQuality = 3
[2018-10-16 18:13:52.709 -8 0x3FAC INFO LOG] (ControlCenter)Link Condition Change : peerSignalQuality = 4, performanceQuality = 3
[2018-10-16 18:13:54.729 -8 0x27B4 INFO LOG] M_Temperature=76, R_Temperature=55
[2018-10-16 18:15:34.731 -8 0x27B4 INFO LOG] M_Temperature=75, R_Temperature=49
[2018-10-16 18:15:44.730 -8 0x27B4 INFO LOG] M_Temperature=76, R_Temperature=48
[2018-10-16 18:16:04.732 -8 0x27B4 INFO LOG] M_Temperature=75, R_Temperature=49
[2018-10-16 18:16:14.735 -8 0x27B4 INFO LOG] M_Temperature=76, R_Temperature=49
[2018-10-16 18:17:04.731 -8 0x27B4 INFO LOG] M_Temperature=77, R_Temperature=44

MrOlsen
Contributor

Re: Wireless Adapter on Vive Pro - blurry resolution and performance impact

Thanks SteveCole for this very deep walkthrough advises. I am trying to follow your advises as I am having som lag problems (blue screen 'loading' very often). I have found slots with Gen3

I am wondering if you really mean Use the slot closest to CPU or Use the slot closest to GPU.

Sorry for my incompetence on this matter.

Thanks in advance for any reply to my question.

Olsen

SteveCole
Pioneer

Re: Wireless Adapter on Vive Pro - blurry resolution and performance impact

Slot closest to CPU, and by that I mean any 1X or 4X slot closest to your CPU. You could try 16X slot as well but depending on your mobo and CPU models and lane limitations you might limit the bandwidth of you GPU to 8 lanes. Just be sure to check your manuals.