OctaneRender™ Standalone 1.12
Forum rules
NOTE: The software in this forum is not %100 reliable, they are development builds and are meant for testing by experienced octane users. If you are a new octane user, we recommend to use the current stable release from the 'Commercial Product News & Releases' forum.
NOTE: The software in this forum is not %100 reliable, they are development builds and are meant for testing by experienced octane users. If you are a new octane user, we recommend to use the current stable release from the 'Commercial Product News & Releases' forum.
I think what has been done is fine but some things just need some small usability tweaking based on user feedback rather than what coders have anticipated. After all that's why new stuff gets posted in the release candidate testing forum first.
It would be a good idea to go for the adjustible billboards too IMO but I understand about the shadows/reflections issues that arise at present.
I think we are getting a few too many things now that you need to have been following forum conversations to know about because stuff isnt that obvious/directly accessible in the UI, is a little unpolished or perhaps misplaced, or haven't found their way into the manual. Ideally I think you need to employ someone to look at/look after these aspects which is kind of a different mindset/awareness from coding and is really incidental to their mission.
I might have some time to do this myself soon if Otoy are interested. Shouldn't amount to too much work but I think someone needs to catch up with the general development and before it becomes a general problem.
I'd like to suggest that rather than have people scurry off to the PDF by default (and not find an entry), resort to forum searches and questions, or try to make the initial UI style @radiance came up with do everything now and in the future, we have a Help bar or button in the node inspector. This would just be a drop down or fly out text message that offers a few short useful notes about some functionality or other. It needn't appear everywhere, just where there are additional things users should know or would benefit from some explanation.
It would be a good idea to go for the adjustible billboards too IMO but I understand about the shadows/reflections issues that arise at present.
I think we are getting a few too many things now that you need to have been following forum conversations to know about because stuff isnt that obvious/directly accessible in the UI, is a little unpolished or perhaps misplaced, or haven't found their way into the manual. Ideally I think you need to employ someone to look at/look after these aspects which is kind of a different mindset/awareness from coding and is really incidental to their mission.
I might have some time to do this myself soon if Otoy are interested. Shouldn't amount to too much work but I think someone needs to catch up with the general development and before it becomes a general problem.
I'd like to suggest that rather than have people scurry off to the PDF by default (and not find an entry), resort to forum searches and questions, or try to make the initial UI style @radiance came up with do everything now and in the future, we have a Help bar or button in the node inspector. This would just be a drop down or fly out text message that offers a few short useful notes about some functionality or other. It needn't appear everywhere, just where there are additional things users should know or would benefit from some explanation.
i7-3820 @4.3Ghz | 24gb | Win7pro-64
GTS 250 display + 2 x GTX 780 cuda| driver 331.65
Octane v1.55
GTS 250 display + 2 x GTX 780 cuda| driver 331.65
Octane v1.55
I haven't overclocked, but I encounter frequent failures of one GPU of my two GTX 580-3GB on this release.This version is a bit sensible to GPU overclocking... one of my 580GTX get failed (always until I set it to default) no priority.

French Blender user - CPU : intel Quad QX9650 at 3GHz - 8GB of RAM - Windows 7 Pro 64 bits. Display GPU : GeForce GTX 480 (2 Samsung 2443BW-1920x1600 monitors). External GPUs : two EVGA GTX 580 3GB in a Cubix GPU-Xpander Pro 2. NVidia Driver : 368.22.
Wow, I have a speed increase from 3.07ms to about 7.5ms, is this right? No render priority.
Octane 2022.1.1 nv535.98
x201t - gtx580 - egpu ec
Dell G5 - 16GB - dgpu GTX1060 - TB3 egpu @ 1060 / RTX 4090
Octane Render experiments - ♩ ♪ ♫ ♬
x201t - gtx580 - egpu ec
Dell G5 - 16GB - dgpu GTX1060 - TB3 egpu @ 1060 / RTX 4090
Octane Render experiments - ♩ ♪ ♫ ♬
- Jaberwocky
- Posts: 976
- Joined: Tue Sep 07, 2010 3:03 pm
I Like the priority Render mode.I have it set to low and can now get on and do other things whilst Octane renders away in the background.It works well on my my single GTX460. Also this release does seem faster on rendering!..I'll continue to test to see if i can find any bugs.
CPU:-AMD 1055T 6 core, Motherboard:-Gigabyte 990FXA-UD3 AM3+, Gigabyte GTX 460-1GB, RAM:-8GB Kingston hyper X Genesis DDR3 1600Mhz D/Ch, Hard Disk:-500GB samsung F3 , OS:-Win7 64bit
- enricocerica
- Posts: 1012
- Joined: Wed Nov 25, 2009 7:32 pm
- Contact:
The refresh button on the textures seems to be broken ...
Modeling system : I7 32GB Windows 10 & Fujitsu Celsius H720
GPU : 1x Gigabyte GTX580 3GB + 1x MSI GTX780 3GB + 1x PALIT GTX780 6GB +1x Asus Stix GTX1070 8GB
http://www.myline.be
GPU : 1x Gigabyte GTX580 3GB + 1x MSI GTX780 3GB + 1x PALIT GTX780 6GB +1x Asus Stix GTX1070 8GB
http://www.myline.be
On your screenshot there are two different camera settings. To compare speed of rendering you must have identical camera settings - both scenes must be exactly the same.whersmy wrote:Wow, I have a speed increase from 3.07ms to about 7.5ms, is this right? No render priority.
3090, Titan, Quadro, Xeon Scalable Supermicro, 768GB RAM; Sketchup Pro, Classical Architecture.
Custom alloy powder coated laser cut cases, Autodesk metal-sheet 3D modelling.
build-log http://render.otoy.com/forum/viewtopic.php?f=9&t=42540
Custom alloy powder coated laser cut cases, Autodesk metal-sheet 3D modelling.
build-log http://render.otoy.com/forum/viewtopic.php?f=9&t=42540
I have experienced one crash after pulling a LDB material to the node graph. Unfortunately I couldn't reproduce the problem.
The old checker board bg of the node graph looked a bit more pleasing.
The old checker board bg of the node graph looked a bit more pleasing.
I have had difficulties to change the background image, and discovered that it is necessary to delete the previous image and get the checkerboard before loading and aplying a new one. It is better to know ! 

French Blender user - CPU : intel Quad QX9650 at 3GHz - 8GB of RAM - Windows 7 Pro 64 bits. Display GPU : GeForce GTX 480 (2 Samsung 2443BW-1920x1600 monitors). External GPUs : two EVGA GTX 580 3GB in a Cubix GPU-Xpander Pro 2. NVidia Driver : 368.22.
ROUBAL wrote:I have had difficulties to change the background image, and discovered that it is necessary to delete the previous image and get the checkerboard before loading and aplying a new one. It is better to know !
Yes, I mentioned the same problem above. Funny how that wasn't picked up in testing.
(HW) Intel i7 2600k, 16GB DDR3, MSI 560GTX ti (2GB) x 3
(SW) Octane (1.50) Blender (2.70) (exporter 2.02)
(OS) Windows 7(64)
(SW) Octane (1.50) Blender (2.70) (exporter 2.02)
(OS) Windows 7(64)