Test Titles on GDN
Once the build is updated, a package is created that can then be used to test the experience on GDN. There are two ways to test GDN titles (authenticated users only, please sign in):
More detailed documentation can be viewed on the Geforce Now Developer Portal.
Testing the React App connected to GDN
Once your GDN account is set up and your title or QA test is prepared, you can now connect this to the React App on your web page. This is also covered in more detail in the Embedded Web Viewer Sample
Edit the stream.config.json <https://github.com/NVIDIA-Omniverse/configurator-viewer-sample/blob/main/stream.config.json>`_ file to to be able to connect to GDN.
set source to
gfn
set catalogClientId - Provided during GDN onboarding.
set clientId to
""
- Provided during GDN onboarding.set cmsId <https://github.com/NVIDIA-Omniverse/configurator-viewer-sample/blob/main/stream.config.json#L8>`_ to match the CMS ID for your asset’s title in the GeForce NOW Developer Portal.
When launching the React app locally, the app should connect to your title on GDN.
To shut down the stream cleanly while testing, you must stop the React app from VS Code. This ensures the stream is not left running on GDN. Refreshing the web page or closing the web page in a web browser does not trigger a clean shut down; instead, this will leave the stream in an idle state and it will eventually shut down via timeout. As a developer, this uses up a resource when you go to iterate on or restart your React app.