mirror of
https://github.com/Armored-Dragon/overte.git
synced 2025-03-11 16:13:16 +01:00
Overte open source virtual worlds platform.
| android | ||
| assignment-client | ||
| cmake | ||
| debian | ||
| docs | ||
| domain-server | ||
| ice-server | ||
| interface | ||
| launchers | ||
| libraries | ||
| plugins | ||
| script-archive | ||
| scripts | ||
| server-console | ||
| tests | ||
| tests-manual | ||
| tools | ||
| unpublishedScripts | ||
| .clang-format | ||
| .editorconfig | ||
| .eslintrc.js | ||
| .gitattributes | ||
| .gitignore | ||
| BUILD.md | ||
| BUILD_ANDROID.md | ||
| BUILD_LINUX.md | ||
| BUILD_LINUX_CHEATSHEET.md | ||
| BUILD_OSX.md | ||
| BUILD_WIN.md | ||
| CMakeGraphvizOptions.cmake | ||
| CMakeLists.txt | ||
| CODING_STANDARD.md | ||
| CONTRIBUTING.md | ||
| hifi_android.py | ||
| hifi_singleton.py | ||
| hifi_utils.py | ||
| hifi_vcpkg.py | ||
| INSTALL.md | ||
| LICENSE | ||
| prebuild.py | ||
| README.md | ||
| README_hifi.md | ||
| VCPKG.md | ||
HiFi Community Edition
Download (Windows 64-bit, .zip)
Changes for v0.86.0 consist of:
- Audio Buffer choppy audio bugfix by increasing the buffer size.
- User Activity Logger disabled, option in code to log the reports to console.
- CMakeLists.txt configured to work for Polyvox, Interface JSDocs. (may be obsolete)
- Custom Application Title.
- Entity Script Whitelist, no scripts are whitelisted by default.
- Background CMD outputs full log, instant close of application on closing of the CMD-line.
This build has been tested on Windows 10 Pro 64-bit w/ Nvidia graphics drivers.
Whitelist Instructions
The Start - NO STEAMVR batch file launches and sets the whitelist environment variable for you (you have to edit in your whitelisted domains), however if you are unable to launch from the batch file and have to launch interface.exe directly then you must set the Windows environment variable "EXTRA_WHITELIST" with your whitelisted domains comma separated like so: "https://kasen.io/,http://kasen.io/"
The whitelist checks against the domains literally, so you have to be precise to ensure security and functionality. For example, the difference between "http://" and "https://" matters as those will be seen as two different domains in the eyes of the whitelist.