Use the Unity Reflect Publisher API to build C# applications or plugins that publish 3D models to Unity Reflect.
Перейти к файлу
gsingland 272f171387 Using 3.1.0 nugets 2022-02-03 12:59:29 +01:00
ConfigFileCreator Using 3.1.0 nugets 2022-02-03 12:59:29 +01:00
PublisherSample Using 3.1.0 nugets 2022-02-03 12:59:29 +01:00
.gitignore First sample commit 2020-12-08 11:19:29 +01:00
LICENSE.md Update LICENSE.md 2020-12-10 12:29:58 -05:00
README.md Cleaning up the repo 2021-12-07 11:15:37 +01:00
Samples.sln Merge pull request #2 from unity/feature/config_file_creator 2021-02-18 11:17:50 +01:00
Third Party Notices.md Update Third Party Notices.md (#2) 2020-12-15 19:28:27 +01:00

README.md

About

This repository contains demo projects pertaining to Reflect Publisher API. Node : only Windows is supported right now.

Contents

PublisherSample

This is a small project that showcases how to use the Publisher API in about 100 lines of code. This "tiny exporter" creates hardcoded models and sends them to Reflect, using the C# Reflect API, and can be launched either in GUI or in console mode.

ConfigFileCreator

This is a tiny utilitary program that helps create a config file, which can be very useful for automated publishing.

Publisher API overview

Take a look at the Reflect documentation for a Publisher API overview.

Advanced workflows

Skip Reflect UI

The default plugin behavior is to display the Reflect UI, so that the user can log in and select a Unity project to export their model to. However, as a developer, you might be interested in automated testing, in which case the UI gets useless.

For this reason, the Reflect UI can be skipped and replaced with a predefined config file, by using a single environment variable. You simply need to create a REFLECT_UI_CONFIG_PATH env variable, and set the absolute path to your config path as a value.

You can generate your own config file by running the ConfigFileCreator utilitary. Note that the user token that is set in the config value expires after 30 days.