The bundle consists from two parts:
1. OctaneRender™ Server
2. Blender - OctaneRender™ edition.
The first part (server) should be run on the same computer as the second one..
After the server is run - you can start rendering (or open a rendered view) from inside Blender. Before the very first rendering you should fill in the server address (only 127.0.0.1 at the time), login and password (your license key info) to activate the server. After the first rendering the server will remember this activation info, and you will not need to enter it again.
You should use only OctaneRender materials inside Blender scenes - the plugin knows nothing about Blender specific materials and textures (about any Blender nodes, generally speaking).
FIXES AND NEW FEATURES SINCE LAST RELEASE
- New 2.24.2 engine.
- Improved the camera view to support the viewport shift.
- Minor fixes and improvements...
Installation:
- Just run the installer to see its command line keys.
- If you need to run the OctaneServer - run it as daemon:
Code: Select all
# OctaneServer &DOWNLOAD
Blender Octane Edition - v9.6 Linux (100.0MB autoinstaller file)
DEMO is available..
Blender Octane Edition DEMO - v9.6 Linux (99.3MB autoinstaller file)
For network slave and daemon please download standalone installer here:
viewtopic.php?f=24&t=50498
Please, if you decided to report a bug:
- Don't post here the reports about how Octane engine works - use the Octane Standalone forum sections for that.
- Give a meaningful description about what you think is wrong and how to reproduce it (in addition to screenshots if any). I can't solve the "one screenshot" rebuses without any meaningful description...
- If you use Google-translator to post here - check please what you got before posting it, and edit it before posting. Ask your friends to check it if you don't speak English.
- If you like to discuss something about the plugin - create a separate thread, don't flood in these testing threads please.
Any meaningless or rebus-like "reports" here will be deleted, just to keep the testing threads clean - because these threads are directly used as the source for fixing and improving the plugin.
