Thanks RS team!
Cheers,
Chris
OctaneRender® 1.025 beta 2.50 [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.
Thanks RS team. I'll do some testing this weekend. I love it when updates happen on a Friday 

- enricocerica
- Posts: 1012
- Joined: Wed Nov 25, 2009 7:32 pm
- Contact:
The index slider for specular material is not float anymore, only integer value can be selected.
Edit : Same for filmindex
Edit : Same for filmindex
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
Tadaaa! 2.5 Great news!
Will test it next week
Good work!
Will test it next week

Good work!
hi, first of all, thanks for your continuous effort... now, since 2.50 it's really hard to do anything besides rendering, whole machine is exhausted... am I doing something wrong?
Best regards,
Dalibor
Hardware: Intel® Core i7 920 2.66GHz, 12GB RAM, Gainward NVIDIA GeForce® GTX 580 1536MB GDDR5
Software: Windows® 7 Home Premium 64-bit, Autodesk® Maya® 2012 64-bit, Octane Render™ v1.0 beta 2.52
Dalibor
Hardware: Intel® Core i7 920 2.66GHz, 12GB RAM, Gainward NVIDIA GeForce® GTX 580 1536MB GDDR5
Software: Windows® 7 Home Premium 64-bit, Autodesk® Maya® 2012 64-bit, Octane Render™ v1.0 beta 2.52
Ok, I've got a few questions for that:dkalna wrote:hi, first of all, thanks for your continuous effort... now, since 2.50 it's really hard to do anything besides rendering, whole machine is exhausted... am I doing something wrong?
Do you only use the GTX 580 or do you have any other graphics cards?
Which version are you comparing with?
Do you do the comparison using the same scene using the same settings and resolution?
What is the CPU of Octane usage while rendering?
Are only other applications affected that use the graphics card (like Maya) or are there applications like an editor or the web browser that slow down, too?
Cheers,
Marcus
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
testing time again...creating some reporting space...
1. Following on from enrico's report - daylight turbidity setting is now 1.5,2.0,2.5...
The range 2.2-2.5 is probably what people are interested in if it is realistic variance of earth's atmosphere. Perhaps 0.1 increments?
2. Minor discrepancy when setting thinlens focaldepth - type in say 100 and get 99.9999975
3. not a bug specifically here but a general question re changing camera response - I would have thought that you would need to change the camera ISO to match a film speed? say I change presets from an Agfa 100 to a 400 ideally shouldnt the view get darker and I have to alter the ISO setting as well to rebalance?? Perhaps ISO should be redone as a +/- adjustment instead?
4. camera fstop is integer. Far too coarse if you were intending to use increments - needs 0.1 if. Better as float as before if it isnt a bug.
5. I am not sure what viewport/resolution lock does? doesnt seem to lock stuff here...does seem to create an odd custom resolution somehow though... sorry havent figured it out
6. turntable/sun animations still dont allow save as .exr or 8/16 bit .png options.
Seems like a stable test release overall but the integer value issues definitely need to be fixed for this to be used at all. Specular index/filmindex have to be fixed to test absorption properly.
Will keep looking
1. Following on from enrico's report - daylight turbidity setting is now 1.5,2.0,2.5...
The range 2.2-2.5 is probably what people are interested in if it is realistic variance of earth's atmosphere. Perhaps 0.1 increments?
2. Minor discrepancy when setting thinlens focaldepth - type in say 100 and get 99.9999975
3. not a bug specifically here but a general question re changing camera response - I would have thought that you would need to change the camera ISO to match a film speed? say I change presets from an Agfa 100 to a 400 ideally shouldnt the view get darker and I have to alter the ISO setting as well to rebalance?? Perhaps ISO should be redone as a +/- adjustment instead?
4. camera fstop is integer. Far too coarse if you were intending to use increments - needs 0.1 if. Better as float as before if it isnt a bug.
5. I am not sure what viewport/resolution lock does? doesnt seem to lock stuff here...does seem to create an odd custom resolution somehow though... sorry havent figured it out

6. turntable/sun animations still dont allow save as .exr or 8/16 bit .png options.
Seems like a stable test release overall but the integer value issues definitely need to be fixed for this to be used at all. Specular index/filmindex have to be fixed to test absorption properly.
Will keep looking

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
Sorry about the slider issues - I broke it yesterday: I will fix it on Monday. It's not a big problem.pixelrush wrote:testing time again...creating some reporting space...
1. Following on from enrico's report - daylight turbidity setting is now 1.5,2.0,2.5...
The range 2.2-2.5 is probably what people are interested in if it is realistic variance of earth's atmosphere. Perhaps 0.1 increments?
2. Minor discrepancy when setting thinlens focaldepth - type in say 100 and get 99.9999975
3. not a bug specifically here but a general question re changing camera response - I would have thought that you would need to change the camera ISO to match a film speed? say I change presets from an Agfa 100 to a 400 ideally shouldnt the view get darker and I have to alter the ISO setting as well to rebalance?? Perhaps ISO should be redone as a +/- adjustment instead?
4. camera fstop is integer. Far too coarse if you were intending to use increments - needs 0.1 if. Better as float as before if it isnt a bug.
5. I am not sure what viewport/resolution lock does? doesnt seem to lock stuff here...does seem to create an odd custom resolution somehow though... sorry havent figured it out
6. turntable/sun animations still dont allow save as .exr or 8/16 bit .png options.
Seems like a stable test release overall but the integer value issues definitely need to be fixed for this to be used at all. Specular index/filmindex have to be fixed to test absorption properly.
Will keep looking
Cheers,
Marcus
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
Wow, great update. Now im testing the new features.
Good job as well.
Good job as well.
|Q8400, gtx770 4Gb |12 Gb Ram|Win7 64 Bit|C4D R15 Visualize and Octane
my 3D-Blog: http://katerlake.blogspot.com
my Vimeo: http://vimeo.com/user4046032
my FlickR: http://www.flickr.com/photos/45536398@N05/
my 3D-Blog: http://katerlake.blogspot.com
my Vimeo: http://vimeo.com/user4046032
my FlickR: http://www.flickr.com/photos/45536398@N05/