hooglstocks.blogg.se - Oculus display driver not working

#Oculus display driver not working how to#
#Oculus display driver not working drivers#
#Oculus display driver not working code#
#Oculus display driver not working license#

Usually, the best solution is either leaving the monitor turned on, or buying a HDMI dummy plug. When people are streaming their desktops, one of the most common problem is that their host displays are turned off, disconnected from the GPU or simply not playing along with Geforce Experience. One of the team members recently came across this project and we all got very excited. We're an open source community supporting a reverse-engineered client for Nvidia's GameStream functionality. Greetings from the Moonlight team over at ! See SwapChainProcessor::RunCore for more information. Any significant work should be performed outside the main processing loop, such as by queuing work in a thread pool. This will directly impact the performance of the user's system, so making use of the Multimedia Class Scheduler Service and DXGI's support for GPU prioritization should be considered. If some information cannot be known immediately in the EvtDeviceD0Entry callback, IddCx allows the driver to call IddCxAdapterInitAsync at any point after D0 entry, before D0 exit.Ĭareful attention should be paid to the frame processing loop. This information determines how the device is reported to the OS and what static features (like support for gamma tables) the device will have available.

#Oculus display driver not working drivers#

This will improve system reliability in case your driver encounters a problem since other drivers will not be affected.Įnsure the device information reported to IddCxAdapterInitAsync is accurate. Since indirect display drivers tend to be more complicated than other driver classes, it's highly recommended that you pick a unique string for this field which will cause instances of your device driver to pool in a dedicated process. One field, DeviceGroupId, controls how the UMDF driver gets pooled with other UMDF drivers in the same process. The INF file included in the sample needs updating for production use. If the device supports multiple monitors being hotplugged and removed at runtime, you may want to abstract the monitors further from the IndirectDeviceContext class.

Handles swap-chain arrival and departure by creating a Direct3DDevice and handing it off to a SwapChainProcessor.Ĭonsider the capabilities of your device.

Manages the creation and arrival of the sample monitor.

#Oculus display driver not working code#

The sample code does nothing with the frames, but demonstrates a correct processing loop with error handling and notifying the OS of frame completion.

Processes frames for a swap-chain assigned to the monitor object on a dedicated thread.

Manages the lifetime of a DXGI factory and a D3D device created for the render GPU the system is using to render frames for your indirect display device's swap-chain.

Contains logic for enumerating the correct render GPU from DXGI and creating a D3D device.

Throughout the code, there are TODO blocks with important information on implementing functionality in a production driver. The sample driver code is very simplistic and does nothing more than enumerate a single monitor when its device enters the D0/started power state. Start at the Indirect Display Driver Model Overview on MSDN.

#Oculus display driver not working how to#

This is a sample driver that shows how to create a Windows Indirect Display Driver using the IddCx class extension driver. If you want me to build on this donate eth or similar here: 0xB01b6328F8Be53c852a54432bbEe630cE0Bd559a It runs in User Mode which means it's less likely to cause system instability like the Blue Screen of Death.

#Oculus display driver not working license#

License MIT and CC0 or Public Domain, whichever is least restrictive - Use itĪS IS - NO IMPLICIT OR EXPLICIT warranty This may break your computer, it didn't break mine.