
OctaneRender™ 1.025 beta2.59 test release [obsolete]
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.
Now that Otoy run things is bug hunting and fixing going to be a little more organized? I mean in the past the community have reported stuff or raised usability issues and some of it just seems to have been forgotten about or ignored. Is there an official list of known issues laying around the office we can refer back to to see what is already known even if it is low priority stuff, rather than search through hundreds of old posts or rely on memory of 2+ years of betas?

In the past the community have also valued dialogue with the coders about issues/experiences, Abstrax was particularly good at this, however Otoy don't seem so interested to engage directly. Is this a correct perspective on it? How do Otoy want to relate to their user base in respect of bugs, usability and requested features? The community have been fairly enthusuastic/active/interested in Octanes development despite everything.


In the past the community have also valued dialogue with the coders about issues/experiences, Abstrax was particularly good at this, however Otoy don't seem so interested to engage directly. Is this a correct perspective on it? How do Otoy want to relate to their user base in respect of bugs, usability and requested features? The community have been fairly enthusuastic/active/interested in Octanes development despite everything.

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
but I thinks "Super" Karba having great dialogue with us at 3dsMax Plugins 

http://www.antoni3D.com
Win 7 64 |GTX 680 4 Gb (Display) | 3 x GTX690 4Gb | Intel i5 |Corsair 16GB
Win 7 64 |GTX 680 4 Gb (Display) | 3 x GTX690 4Gb | Intel i5 |Corsair 16GB
One thing that has been bothering me a little, and I think this issue has worsened in recent betas, although I might be imagining it, is the smoothing. To my mind the smoothing is not quite functioning as it should. 
I remember Roeland tweaked something recently and perhaps this arises from that.
Attached is a close up of a small mechanical part that shows some faceting where I think it really ought to appear smooth. Also attach is the normals render. Clearly smoothing is working to some degree...
What concerns me is the polygonal appearance of the flat surface and the here and there creasing going on around the curved faces.
Has anyone else noticed this issue or thought it is more obvious lately?
I think there is sufficient tessellation in this model for it to appear quite smooth and nicely curved but I could be wrong

I remember Roeland tweaked something recently and perhaps this arises from that.
Attached is a close up of a small mechanical part that shows some faceting where I think it really ought to appear smooth. Also attach is the normals render. Clearly smoothing is working to some degree...
What concerns me is the polygonal appearance of the flat surface and the here and there creasing going on around the curved faces.
Has anyone else noticed this issue or thought it is more obvious lately?
I think there is sufficient tessellation in this model for it to appear quite smooth and nicely curved but I could be wrong

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
- mainframefx
- Posts: 127
- Joined: Fri Feb 03, 2012 1:52 pm
- Contact:
Support for Kepler doesn't mean that Keplers shader units get magically better. They differ drastically from Fermis shader units which is the main reason why the performance is so bad, this is a hardware issue and has nothing to do with octane not supporting it properly.marcio_max wrote:I'm waiting for Kepler.
But my dream come true when a final version ready for the boards Kepler.
1344 Cuda cores ... I'm dreaming of it working properly.
i7-3930K@4,8GHz | 64GB RAM | 2x GTX 560 Ti 448 | Windows 7 x64 SP1
i7-3930K@4,2GHz | 32GB RAM | 1x GTX 560 Ti 448 | Windows 7 x64 SP1
i7-2600K@4,4GHz | 16GB RAM | 1x GTX 560 Ti 448| 1x Quadro 2000D | Windows 7 x64 SP1
i7-3930K@4,2GHz | 32GB RAM | 1x GTX 560 Ti 448 | Windows 7 x64 SP1
i7-2600K@4,4GHz | 16GB RAM | 1x GTX 560 Ti 448| 1x Quadro 2000D | Windows 7 x64 SP1
hi,
if i connect a float-pin to a fall-off node inside a macro, octane crash on both win and mac
here is a first try to make an x-ray material with fall-off map, i've uploaded it on live db
ciao beppe
edit: thanks Karba for the glass with fall-off, never thought to use it in this way
if i connect a float-pin to a fall-off node inside a macro, octane crash on both win and mac

here is a first try to make an x-ray material with fall-off map, i've uploaded it on live db

ciao beppe
edit: thanks Karba for the glass with fall-off, never thought to use it in this way

if i leave the mac rendering, some time after the max sampling is reached, octane crash, so is not possible to do rendering over night
here is the crash report
ciao beppe

here is the crash report

ciao beppe
- Attachments
-
- crash-report-or-1259-26-7-2012.txt.zip
- (15.6 KiB) Downloaded 122 times
Thanks
windows 7 x64 | i7 920 | 12GB | GTX470 |
But I thought it was matter of Cuda programming and with the release of Cuda 5 we could finally hope for a full speed Kepler Card as it is for Fermi ones..but all this is getting rather confusing..2nd hand Gtx 590 are still more expensive than a new Gtx670..mainframefx wrote:Support for Kepler doesn't mean that Keplers shader units get magically better. They differ drastically from Fermis shader units which is the main reason why the performance is so bad, this is a hardware issue and has nothing to do with octane not supporting it properly.marcio_max wrote:I'm waiting for Kepler.
But my dream come true when a final version ready for the boards Kepler.
1344 Cuda cores ... I'm dreaming of it working properly.

Win 7 64 | 2 X MSI AERO GtX 1070| Intel I7-6850K| 32 GB DDR4 RAM | Asus X99 II-A