OGEngineClient + Edge + Unity v1.1.0

OGEngineClient + Edge + Unity v1.1.0

This complete Unity distribution bundles NextGenSoftware.OGEngine.Client.Edge.dll, shared client dependencies, Edge Runtime/ONET libraries, platform plugins and Unity Runtime/Editor integration. No separate OGEngineClient ZIP is needed. Preserve .meta importer settings. The NextGenSoftware.OASIS.Edge.Unity NuGet wrapper distributes a UPM tarball under tools/unity; use Add package from tarball in Unity Package Manager. Standalone Edge and non-Unity OGEngineClient profiles are separate products. See https://github.com/NextGenSoftwareUK/OASIS/blob/Development/Docs/Devs/EDGE_DISTRIBUTIONS.md for the four-distribution comparison.

What's new in v1.1.0

Other changes

• Refresh Unity ZIP documentation without repushing immutable NuGet wrapper (77473ee)

Downloads and requirements

Release assets: select the archive matching your operating system and architecture. Do not use a Windows binary on Linux/macOS or assume a managed package proves native platform support.
NuGet packages resolve reusable managed dependencies; native executables, Unity packages and mobile conductor artifacts are separate distributions. Consult each archive/package README for native libraries and external-service prerequisites.

Installation and configuration

Extract the matching binary archive or install the exact NuGet version listed in the release inventory. Preserve the archive dependency layout. For reusable libraries, integrate the documented public API with your host lifecycle rather than treating the package as a standalone application.
Use the public Default OASIS_DNA.json template where included, then configure the providers and endpoints required by your application. Obtain authentication through the supported application flow; never copy production credentials, tokens or private keys into public templates or client packages.

Verification and known limitations

Build, packaging and publication checks are not proof of physical Android/iOS execution, two-device convergence or Unity IL2CPP behavior. Check the dated release inventory for actual evidence and outstanding acceptance tasks; do not infer completion from a successful upload.
On failure, retain the actual error code/message, check authentication, configured service availability and native dependency/architecture match, and avoid exposing secrets in logs.
Verified release inventory.

Full changelog

This is the first release under this component tag series; the commit list above is the component changelog for the initial version.