- #PHOENIX FIRESTORM VIEWER WONT SAVE SETTINGS INSTALL#
- #PHOENIX FIRESTORM VIEWER WONT SAVE SETTINGS UPGRADE#
This requires the Boostrip pip already installed.
#PHOENIX FIRESTORM VIEWER WONT SAVE SETTINGS INSTALL#
Install virtualenv by opening a Windows command prompt and enter: Note: Having to copy autobuild.xml and modify the copy from within a cloned repository is a lot of work for every repository you make, but this is the only way to guarantee you pick up upstream changes to autobuild.xml and do not send up a modified autobuild.xml when you do an hg push. Set AUTOBUILD_CONFIG_FILE=my_autobuild.xmlĬopy the FMOD Studio path and md5 value from the package process into this command:Īutobuild installables edit fmodstudio platform=windows hash= url=file:///Īutobuild installables edit fmodstudio platform=windows hash=c3f696412ef74f1559c6d023efe3a087 url=file:///C:\firestorm\3p-fmodstudio\fmodstudio-1.10.2 Wrote C:\firestorm\3p-fmodstudio\fmodstudio- is an internal build id of the package.
Near the end of the output you will see the package name written and the md5 hash below it: This is because of the FMOD Studio installer being executed. While running the Autobuild build command, Windows might ask if you want to allow making changes to the computer. Change these values to the version you downloaded:
Right at the top, you find the version number of FMOD Studio you want to package (one short version without separator and one long version). If you downloaded a different version of FMOD Studio that is currently used in the viewer, you will have to modify the file build-cmd.sh in the root of the repository. Additionally, we recommend returning it to default once the mesh you're trying to see is visible. Please see this comment on a related JIRA ticket for an explanation of the possible drawbacks of increasing this setting. Under no circumstances should you increase this beyond 64. (If Advanced is not visible on the top menu bar, press Ctrl-Alt-D.) If it does not help, try increasing the value from the default. If none of the above work - and make sure you try all of them first! - then in the top menu bar, open Advanced → Debug Settings, type in Mesh2MaxConcurrentRequests and gradually decrease (not increase) the value. HTTP fetching may be overloading your router please try the suggestions given here if they do not help, revert the changes made then return to this page and continue. If mesh is simply slow to appear, but does appear eventually, that is not necessarily a problem with mesh itself please work through this page: Slow Rezzing.
#PHOENIX FIRESTORM VIEWER WONT SAVE SETTINGS UPGRADE#
This may need to be done from scratch each time you upgrade to a new version. For other antivirus apps, see our Whitelisting Guide, and be sure to whitelist all parts of the viewer. If you have Webroot SecureAnywhere Antivirus, see Webroot Issues. In that case, try going to Preferences → Graphics → General, and enable Hardware Skinning. There are also rare instances of glitches where mesh that you are wearing appears worn by another avatar (yes, it is bizarre!). Go to Preferences→ Graphics -> Rendering and disable both of the Alpha Mask Rendering options. In some cases, worn mesh attachments will not render properly still. (The optimal value for draw distance is entirely dependent on your own hardware you will need to experiment to find what works best for you.) If you have difficulty rendering mesh, lower it if your draw distance is over 128, set it to 128, or less. Make sure you have a reasonable draw distance. If this remains greyed out, then increase the level of Render Quality until Basic Shaders becomes enabled and can be checked. Go to Preferences→ Graphics -> General then enable Basic Shaders. Depending on your specific hardware, certain settings that need to be enabled for mesh, may be set off by default. So you have the latest viewer and still can't see mesh - what's the deal?
0 kommentar(er)
