NVIDIA GeForce NOW Beta Update 5

I’ve been playing Destiny 2 using NVIDIA GeForce NOW for MacOS (in beta) during my trip to Denver. The client was recently updated – this post focuses on the addition of Advanced Streaming Settings.

Here’s a little introduction about how I came across NVIDIA GeForce NOW, in case you missed it:

NVIDIA GeForce NOW Mac Beta

“New Ultra Streaming Mode and Direct Mouse Input can reduce lag by 30%” (NVIDIA GeForce NOW for Mac Forum)

Test Setup

Machine

Alice’s Late-2013 MacBook Pro Retina 13″ (MacBookPro11,1)
Intel Core i5-4258U 2.4GHz (Dual Core)
4GB DDR3-1600
Intel Iris 5100
Built-In Retina LCD (2560 x 1600 Retina)

Network

CenturyLink DSL Connection (35 Mbps Download / 5 Mbps Upload)
Hardwired to LAN using USB 3.0 Gigabit Ethernet Hub (the one I recently ordered)

I noted the video settings that NVIDIA GeForce NOW selected within Destiny 2:

Ultra Streaming Mode Off On
Video Settings
VRAM Usage 2579 MB / 24370 MB 1330 MB / 24370 MB
Resolution 1280 x 800
Vsync Off
Advanced Video
Graphics Quality Custom
Anti-Aliasing SMAA FXAA
Screen Space Ambient Occlusion 3D HDAO
Texture Anisotropy 16x 4x
Texture Quality Highest Medium
Shadow Quality Highest Medium
Depth of Field Highest High
Environment Detail Distance High
Character Detail Distance High
Foliage Detail Distance High Medium
Foliage Shadows Distance Highest High
Light Shafts High
Motion Blur On
Wind Impulse On
Additional Video
Render Resolution 100%
HDR Off
Chromatic Aberration On
Film Grain On

I also tested on my mid-2011 MacBook Air:

Mid-2011 MacBook Air (MacBookAir4,1)
Intel Core i7-2677M 1.8 GHz (Dual Core)
4 GB DDR3-1333
Intel HD Graphics 3000 (384 MB)
Color LCD (1366 x 768)

The only difference was the video resolution, which defaulted to 1280 x 720 instead of 1280 x 800.

Input delay was noticeably reduced with both Ultra Steaming Mode and Direct Mouse Input enabled, though it felt like the network was too slow to keep up with demands. I will have to test in greater depth at home, when we can remove the network as bottleneck. When the network cooperated, I was able to challenge with a lot more confidence than previously, making for a better experience overall.

Order Placed: JSVER Unibody Aluminum USB 3.0 Gigabit Ethernet Hub

The full product name on Amazon.com is a little longer: JSVER Unibody Aluminum 3 Ports USB 3.0 Hub and RJ45 10/100/1000 Gigabit Ethernet Hub Converter with Built-in 1ft Cable (Amazon.com), but I think I’ve captured the important parts.

I bought this hub so that I could hardwire my mid-2011 MacBook Air to my LAN. Its aluminum body should complement my MacBook Air well should I take it on the road. Although my mid-2011 MacBook Air only has USB 2.0 ports, this USB 3.0 hub will still work, albeit at USB 2.0 speeds.

NVIDIA GeForce NOW Mac Beta

I was on the phone with Alice last night when I decided to check out the NVIDIA GeForce NOW beta for MacOS. I’d seen it in a promoted post on Facebook when I was going through my feeds earlier in the day, and was immediately interested.

I installed the beta and fired up Diablo III. I proclaimed “The future is here!” as I made my way past the login screen, which I’d last seen as far back as 2013. My mid-2011 MacBook Air ran the game at all low settings when it first came out, but I was now looking at it in its full glory, made possible by GPUs in the cloud.

I set out to see how I might tie my Mac into my streaming setup. I grabbed the mini-DisplayPort to HDMI adapter that I had left laying around ever since I began leveraging DLNA, and used it to connect my MacBook Air to my AVerMedia Live Gamer HD. OBS displayed “HDCP,” but passthrough functionality was unaffected.

I played Fortnite, a title I knew that my workstation could run passably at low settings at 1280×720. The image was obviously being scaled up from whatever GeForce NOW decided was suitable for my MacBook Air. I noticed occasional input lag, which I am assuming is because I was running off of WiFi. It would be nice to tie my MacBook Air more neatly into my workstation setup through a Thunderbolt hub (Amazon.com), but most importantly, I need to hardwire it to my LAN. While a USB ethernet adapter (Amazon.com) would do the trick, I would be better served by a combination USB hub ethernet adapter (Amazon.com).

What really turns me on to NVIDIA GeForce NOW’s technology:

  • It allows users to prioritize investments into infrastructure over amassing local processing power. Investments into infrastructure are long-lasting, whereas Moore’s Law makes keeping up with the latest processors costly.
    • Reduces barriers to entry for modern AAA titles, allowing in users on long upgrade cycles

Next steps:
Before I make the investment into bypassing HDCP (either on the AVerMedia Live Gamer HD or before the signal hits it), I would like to learn how to force NVIDIA GeForce NOW to output to the external display at its native resolution instead of selecting the optimal resolution for my MacBook Air’s display.

Build Log: OCEANBLUe Upgrade

I laid hands on OCEANBLUe for the first time since it traveled with my parents to Moscow, Russia. I did get the opportunity to perform some work on it remotely, but performance remained sluggish. Maybe it was time to give the hardware a rest.

After my parents came back to the United States, my father expressed an interest in upgrading OCEANBLUe. I ordered parts.

Order Placed: OCEANBLUe Upgrade

I livestreamed much of the initial build, stopping when it was time to sit down to dinner.

A couple of notes from the build process:

Plastic brackets for HSF needed to be removed, but I didn’t need to remove the motherboard from the tray to get at the metal bracket underneath

Orientation of the AMD Wraith cooler is important – AMD logo protrudes, making the RAM slot closest to the CPU inaccessible

Houston, we have a problem

My first attempt to power on the system was unsuccessful – the system did not POST successfully, and the board indicated that the CPU was at fault. Symptoms were as follows:

The LED strip lights up briefly, then goes dark. With CPU HSF spinning, the CPU status LED remains lit

CPU orientation is foolproof, but I double-checked to be sure.

I decided that the CPU probably was not getting enough power: OCEANBLUe’s existing PSU had a 4-pin ATX 12V power connector, whereas the motherboard takes an 8-pin connector.

I wanted to get the machine up and running ASAP, so I made the decision to purchase a new power supply unit instead of taking a gamble with a four pin to eight pin adapter, even though I would have liked to have gone the latter route. I selected an EVGA 450 BT (Amazon.com) over a slightly cheaper power supply that lacked the 80 Plus efficiency rating.

When I received shipment of the new power supply on July 9, I resumed work on the build. With the new power supply installed, the system still failed to POST. No change in status.

Diving deeper into the GIGABYTE GA-AB350-Gaming 3 motherboard’s documentation showed that support for AMD Ryzen 5 processors was introduced in BIOS revision F6. Is it possible that the motherboard I received shipped with BIOS revision F3? If that’s the case, my options are either to ship the motherboard back to Gigabyte for an upgrade, or to borrow an AMD Ryzen 7 processor for the sole purpose of flashing the BIOS (I did this before when building my DIY FreeNAS server).

Feedback online suggested that the GIGABYTE GA-AB350-Gaming 3 should support Ryzen 5 out of the box, regardless of BIOS version. Some posters wrote about long first boot times, anywhere from five minutes to two and a half hours. These seemed unreasonable to me.

In any event, I submitted a ticket through GIGABYTE’s eSupport ticketing system. Unfortunately, I’d set my profile to indicate that I was in the UK. I corrected my profile and submitted a new ticket.

While waiting for a response, I phoned in to GIGABYTE’s technical support line. A pre-recorded message advised me that all of their technical support representatives were busy helping other customers, but I could leave my number and my call would be returned.

I followed troubleshooting guidelines and powered up the board with the RAM installed in each of the board’s four slots, clearing the CMOS between attempts. Still no change in status.

I received a call back from Robert, a GIGABYTE technical support representative, and asked if they could check to see which BIOS revision the board had gone out with. He placed me on a brief hold, and informed me that his supervisor had stated that the board should POST regardless of BIOS revision. I asked if he could run the serial number of the board to be sure, and was told that I could expect a call back soon.

Robert called back to state once more that it should POST with any AMD Ryzen CPU – perhaps there were bent pins on the motherboard? I told him that I’d checked and found nothing out of place. He suggested returning the board to the retailer.

I phoned back in to GIGABYTE technical support again later. I had managed to find a speaker to wire up to the motherboard. No matter what, the motherboard wouldn’t issue any beep codes. I didn’t think polarity was important, but I verified anyway. The GIGABYTE technical support representative had me try powering on the system without the CMOS battery inserted. I jumpered the CMOS reset pins on the board. Still no change in status. Maybe, just maybe I’d managed to foul up the CPU installation. I put the probability of this occurring at zero, but checked anyway.

Later, I tested the speaker by plugging it into my workstation. It beeped.

And so begin the RMAs

By this point I was beyond frustrated. I started the RMA process on July 11 by going to Newegg. The box that I received from them had taken quite the hit, so it seemed like the logical place to start.

FedEx came to pick up the motherboard on July 12, and Newegg sent out a replacement motherboard on July 18.

I received shipment of the replacement motherboard on Thursday, July 20. I remembered the GIGABYTE technical support representative’s advice to test outside of the case. With only the CPU + CPU HSF installed, the board’s CPU status LED lit up to indicate that the CPU was faulty.

SuperBiiz approved my RMA request on July 21 and issued a return label for me on that same day. I cleaned the AMD Ryzen 5 1600, placed it back within its packaging, and dropped it off at a nearby UPS Store on Saturday, July 22.

Meanwhile, my father indicated to me that he would be interested in driving a couple of ultrawide displays from this new workstation. The NVIDIA GeForce 9800 GT has a maximum digital resolution of 2560×1600. The NVIDIA GeForce GT 1030 (specifications) may fit the bill nicely: it’s also available in a passively-cooled configuration. Unfortunately, it doesn’t support NVIDIA G-Sync. I’m also considering the Radeon RX 550 to stay under the AMD umbrella.

I phoned in to SuperBiiz on Monday, July 31, to see if there was any update on my order. The CSR informed me that their system showed the item was received, but there was no additional information. She suggested that I call back on Thursday.

I called back on Thursday, August 3, and was informed that the CPU had been sent to their vendor. The turnaround time was longer than I had the patience for, and I was certain that the CPU was faulty. I asked if I might escalate to a return instead of a replacement order – the CSR got it approved, and I went back to the drawing board.

I ordered another AMD Ryzen 5 1600 and an NVIDIA GeForce 1030 from Newegg on the morning of August 4. Unfortunately the CPU was not available for ShopRunner two-day shipping, but the GPU was.

My order arrived on August 8. I tested by building on top of the motherboard box. I powered the machine on, hoping for the best.

Just the same as before, the CPU light came on as soon as the board powered up.

I called GIGABYTE support and spoke with Robert again. I brought him up to speed on my situation. This time, he offered that a BIOS update may help move things along. Robert offered that he could give me a call back the next day, but I told him that I could drop him an email if there was any improvement.

I called Micro Center. They moved at the tail end of 2014, and I wanted to be sure that there was a space where I could tinker with the build in-store.

Meanwhile, I drafted a plan of attack:

Plan to start by swapping the CPU to a Ryzen 7. If the board POSTs successfully, I will upgrade the BIOS, swap back to the Ryzen 5, and test again. Hopefully that’s as far as I will have to go.

If the board fails POST with the Ryzen 7, I’ll swap RAM.

And if all else fails, I’m throwing in the towel, because I just might not have the patience for building systems 😀

On August 9, I headed to Micro Center with parts in tow. It takes about half an hour for me to reach the store. After parking my car, I went in, and headed for the Knowledge Bar, which struck me as being an appropriate first step.

I signed in there, then asked an associate who was standing by the laptops whether there was any space to tinker with builds, explaining that I’d brought my parts with me and wanted to get to the bottom of my no POST issue. She told me that the old store had a designated space for tinkering, but there was no such space in the new store, and the Knowledge Bar was probably my best bet. I thanked her and moved on.

I headed to the Build Your Own PC counter, where I explained my situation to an associate working that area. He asked me which motherboard I was using, and remarked that it was picky on RAM. He told me that I could test at their counter, so I went back to my car to retrieve the parts.

The associate brought me a module that was known to be compatible. Running that lone stick of RAM resulted in a successful POST, and I was greeted by the GIGABYTE UEFI for the very first time. The board was running BIOS F6.

That stick of RAM had relatively loose timings, so I opted for something tighter. I verified that the board would POST using my newly selected RAM, paid, and went back home.

I installed Windows 10 Professional – the process went smoothly.

I was outside of the return window for the Patriot RAM that I initially ordered, but I decided that I ought to test it further now that I had the system working. Was it DOA?

With only the Patriot module installed, the board predictably failed to POST. The strange thing is that the board POSTs successfully with both modules installed, and all 16GB of RAM are addressable. I don’t understand.

Final Parts Listing

CPU: AMD Ryzen 5 1600 (Amazon.com)
Motherboard: GIGABYTE GA-AB350-Gaming 3 (Amazon.com)
Memory: 8GB Kingston HyperX DDR4-2400 HX424C15FB2/8 15-15-15-35 (Amazon.com, datasheet)
Memory: 8GB (1*8GB) Patriot Viper 4 DDR4-2400 PV48G240C5 15-15-15-35 1.2V (Amazon.com)
SSD: SK hynix SL308 250GB HFS250G32TND-N1A2A (Amazon.com)
PSU: EVGA 450 BT, 80 PLUS Bronze Certified (Amazon.com)
OS: Windows 10 Pro

Final Notes

My eagerness to get this build completed resulted in some unfortunate oversights, resulting in significant expenditure of time and energy to rectify.

Before placing the initial order for parts, I referenced the QVL. The memory that I ordered, PV48G240C5, does not explicitly appear on the QVL. However, PV48G240C5K does.

While the GeForce 1030 specifications (NVIDIA) indicate that it is capable of driving 7680×[email protected], the GIGABYTE GeForce GT 1030 Silent Low Profile 2G (GIGABYTE) that I ordered outputs a maximum 4096×[email protected] through its HDMI-2.0b port. The DVI-D port can drive at most a 2560×1600 display.

Furthermore, Newegg’s product listing for the GIGABYTE GeForce GT 1030 Silent Low Profile 2G erroneously stated that it had three ports: one each of Dual-Link DVI-D, HDMI 2.0b, and DisplayPort. Referencing the product images on Newegg would have uncovered this discrepancy, leading me to seek the ground truth at GIGABYTE’s product page, and avoiding the hassle of returning a product. Fortunately, I was able to return the GPU to Newegg without incurring a restocking fee.