mirror of
https://gitlab.com/lvra/lvra.gitlab.io.git
synced 2024-12-24 14:50:25 +01:00
Merge branch 'main' into 'main'
Remove Envision AppImage warning for WiVRn, add Unity troubleshooting step for RHEL/Fedora Closes #1 See merge request lvra/lvra.gitlab.io!45
This commit is contained in:
commit
051570b401
2 changed files with 11 additions and 2 deletions
|
@ -23,8 +23,6 @@ Envision is still considered alpha-quality and highly experimental.
|
|||
|
||||
You can download the latest AppImage snapshot from [GitLab Pipelines](https://gitlab.com/gabmus/envision/-/pipelines?ref=main&status=success).
|
||||
|
||||
**Please note that WiVRn will not work properly by AppImage, if you utilize the AppImages to run WiVRn you must extract the contents of the AppImage and then execute the Envision binary.**
|
||||
|
||||
## Getting Started
|
||||
|
||||
Upon launching Envision, you will need to select a profile on the bottom of the left side bar.
|
||||
|
|
|
@ -69,6 +69,17 @@ Patches for both the Worlds and Avatars SDK are available: https://github.com/Be
|
|||
|
||||
## Troubleshooting
|
||||
|
||||
### Unable to activate Unity license
|
||||
|
||||
If you are using a Fedora or RHEL-based distribution, this may be caused by an OpenSSL configuration option.
|
||||
|
||||
To verify that this is the problem, check your `~/.config/unity3d/Unity/Unity.Licensing.Client.log`.
|
||||
If you see the text `Interop+Crypto+OpenSslCryptographicException: error:03000098:digital envelope routines::invalid digest`, running the following command as root will re-enable SHA-1 cryptography and resolve the issue:
|
||||
|
||||
`update-crypto-policies --set DEFAULT:SHA1`
|
||||
|
||||
For more information, see the RHEL documentation on [security hardening](https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/9/html/security_hardening/using-the-system-wide-cryptographic-policies_security-hardening#proc_re-enabling-sha-1_using-the-system-wide-cryptographic-policies).
|
||||
|
||||
### Shaders fail to include some .cginc files
|
||||
|
||||
This can happen with Poiyomi. It's caused by case-sensitivity. You may need to edit the shader files directly. Open them in any text editor, and correct the casing of filenames.
|
||||
|
|
Loading…
Reference in a new issue