what about speed vs quality?bepeg4d wrote:hi, first of all a big thanks for the rc version, the caustic blur effect seems really promising for speed up pt animation rendering
it seems like almost all the promised features are already here
about the mac version, the performance are very similar to the win version, ungortunately it's more unstable, expecially with pt and pmc (crash report attached).
the comma- point in the numpad doesn't work in this version also.
p.s. what about an histogram graph in the image node for a fast verification of the exposition?
ciao beppe
OctaneRender™ Standalone v1.0 RC 1 [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.
-
gabrielefx
- Posts: 1701
- Joined: Wed Sep 28, 2011 2:00 pm
quad Titan Kepler 6GB + quad Titan X Pascal 12GB + quad GTX1080 8GB + dual GTX1080Ti 11GB
The Caustic Blur Option is one of the biggest improvements of the last months.
Well done.
Well done.
hi gabriele,
in my opinion the new BRDF is much much better than the old one, especially for specular material, in general is no more necessary to mix it with a glossy material to get good reflections. the colours scheme is more accutate now.
i have made a test with an old scene previously rendered with maxwell and now the results are almost equal but with the incredible speed of octane. with the old BRDF the specular materials seems always dark
i'm more than happy with the new rc 1.0
ciao beppe
in my opinion the new BRDF is much much better than the old one, especially for specular material, in general is no more necessary to mix it with a glossy material to get good reflections. the colours scheme is more accutate now.
i have made a test with an old scene previously rendered with maxwell and now the results are almost equal but with the incredible speed of octane. with the old BRDF the specular materials seems always dark
i'm more than happy with the new rc 1.0
ciao beppe
Hello,
It seems this new version is not faster for me :
For the same render :
00.01.55 with the beta302a (geometry 593)
00.02.51 with the v1.0 RC 1 (geometry 612)
no caustic blur
3x gtx 580 Driver 306.97 Cuda 5.0
Any ideas ? Thx.
Niuq
It seems this new version is not faster for me :
For the same render :
00.01.55 with the beta302a (geometry 593)
00.02.51 with the v1.0 RC 1 (geometry 612)
no caustic blur
3x gtx 580 Driver 306.97 Cuda 5.0
Any ideas ? Thx.
Niuq
- Attachments
-
-
Okay ! Thank you Marcus.
Thank you Marcus.Hi Niuq,niuq.cam wrote:Okay !
The update won't fix your problem, since you are using GTX 580, which weren't affected by the bug. You could help us by sending the scene to allow us reproduce the problem, though.
Cheers,
Marcus
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
I tried your scene, and it renders fine, I don't get any of the artifacts shown in your image. Did you use any special settings for that render?mib2berlin wrote:Hi abstrax, change rayepsilon does nothingm try diferent camera angle and fov.
Problem scene is attached.
Cheers, mib.
--
Roeland
Marcus,
I have done the test with cubes.
It's the same.
Almost 10 seconds more with the rc1 for 30 sec with the beta302a
For 3 minutes, That gives indeed a minute difference, like the Lambo scene.
http://dl.free.fr/getfile.pl?file=/PpCrvGdf
Niuq
I have done the test with cubes.
It's the same.
Almost 10 seconds more with the rc1 for 30 sec with the beta302a
For 3 minutes, That gives indeed a minute difference, like the Lambo scene.
http://dl.free.fr/getfile.pl?file=/PpCrvGdf
Niuq
- Attachments
-
-
I have been asked for any more thoughts about the manual...seems like I am cheap techical writing editor 
ok so looking quickly at chapter 1 again
p2 web address needs update to render.otoy.com
p7 make it clear that Octane doesnt run on ATI, no plans to. looking to buy should mention a good practical min vram of 1.5 gb and also make mention that the more vram you have the more sys ram is needed for the 'voxelisation' process. roughly 5-6:1, depeends a little on tolerance of paging in max cases. Note some Octane functionality isnt available for early cards with cuda capability 1.1,1.2?
gpu capability not important for running Octane dual or quad fine.
teslas not cost effective, many quadros relatively expensive lacking cores/under clocked in comparison to Geforce
p8 should probably note win8 compatibility now.
p9 customer section accessed from the HOMEPAGE of the website. Information on where to download and activate is included in the confirmation email when you purchase (or whatever...)
mention active on one machine at a time and transfer process/delay.
probably would benefit from a screen shot of the lower right of the UI showing re/green connected etc. as check on status.
contact email address in case of difficulty, mention occasional planned maintenance of site/Live DB offline and prior warnings posted. refer to info on p21
p10 not enough to say just latest must be suitable cuda version...
disable virus protection?? install by double clicking Octane installer. can be installed on any drive/partition/boot? or best on C:/Programs?? render textures, .obj can be anywhere.. scripts/exporters may have special requirements.
install also creates a folder in ? with license info, recent paths, and custom settings - dont delete or move.
p14 needs an illustration of just the single slot case else it is confusing to behold the expansion box there. mention somewhere about consulting your gpu card makers specs for max power consumption. Check case will take long cards some won't.
refer to consulting sli power recommendations for multiple cards and enough 6/8 pin connectors for. perhaps refer to nvidia sli power supply/mobo listing web address and online power supply calculator +25-35% headroom for capacitor deterioration.
p19 some hardware makers like Dell or Toshiba issue their own drivers. some users also want specific drivers recommended for their pro apps. All recent drivers come with cuda included as well, its just a matter of making sure the cuda version is appropriate for Octane.
p20 ..Fermi or later*...desireable to have ~300+ cores for decent render experience/performance
p23 characters and spaces - not sure is that still the case?
p24 ...file format with current Octane version.
...the best success....1gb vram might be necessary - as worded these really dont give the full picture, rewrite I think
p26 possibly describe what it is you see in the render when you have normals issues. also mention long, narrow triangles. remember not every user is a cg expert. generally manula probably assumes a little too much prior knowledge/self help
p27 vertical lines bugs went away some while ago, just refer to looking at the forums for user identified bugs/issues/known workarounds/more recent builds etc.
UVs must be carefully done in another app. Octane doesnt have any facility to map or alter.
p28 slowness also arises from having an underpowered gpu and from setting large resolutions.
p29 96 absolute minimum for 'see what it is' demos suggest invest in a better card for purchase.
warn about laptop gpu cooling - older nvidia laptop gpu had manufacturing issues prone to damage.
anything else can do - 1.reduce resolution , set camera as wanted (perhaps make use of window zoom), increase res. again 2. change to DL set camera change to pmc if wanted.
p30 symptoms of insufficient power. also gpu 'failed' message in UI, windows bluescreen, blackout, freeze??
mention too closely spaced cards particularly double slot 4xx series, heat rising in case, availability of water cooled cards.
p33 16/8x suitable 4/2x not really desireable, 1x not suitable. mention just slows down data transfer. mix of 16 and 8 as per pcie bandwidth sharing on many mobos is ok.
More chapters to follow based on further feedback and free beer
Personally I would say the manual as is isn't quite up to standard for a final in regard of required detail. Its nicely presented though graphics wise. Maybe if you added this stuff you would then want to make a further pass to make sure it was all in the proper order, not repeated etc.
ok so looking quickly at chapter 1 again
p2 web address needs update to render.otoy.com
p7 make it clear that Octane doesnt run on ATI, no plans to. looking to buy should mention a good practical min vram of 1.5 gb and also make mention that the more vram you have the more sys ram is needed for the 'voxelisation' process. roughly 5-6:1, depeends a little on tolerance of paging in max cases. Note some Octane functionality isnt available for early cards with cuda capability 1.1,1.2?
gpu capability not important for running Octane dual or quad fine.
teslas not cost effective, many quadros relatively expensive lacking cores/under clocked in comparison to Geforce
p8 should probably note win8 compatibility now.
p9 customer section accessed from the HOMEPAGE of the website. Information on where to download and activate is included in the confirmation email when you purchase (or whatever...)
mention active on one machine at a time and transfer process/delay.
probably would benefit from a screen shot of the lower right of the UI showing re/green connected etc. as check on status.
contact email address in case of difficulty, mention occasional planned maintenance of site/Live DB offline and prior warnings posted. refer to info on p21
p10 not enough to say just latest must be suitable cuda version...
disable virus protection?? install by double clicking Octane installer. can be installed on any drive/partition/boot? or best on C:/Programs?? render textures, .obj can be anywhere.. scripts/exporters may have special requirements.
install also creates a folder in ? with license info, recent paths, and custom settings - dont delete or move.
p14 needs an illustration of just the single slot case else it is confusing to behold the expansion box there. mention somewhere about consulting your gpu card makers specs for max power consumption. Check case will take long cards some won't.
refer to consulting sli power recommendations for multiple cards and enough 6/8 pin connectors for. perhaps refer to nvidia sli power supply/mobo listing web address and online power supply calculator +25-35% headroom for capacitor deterioration.
p19 some hardware makers like Dell or Toshiba issue their own drivers. some users also want specific drivers recommended for their pro apps. All recent drivers come with cuda included as well, its just a matter of making sure the cuda version is appropriate for Octane.
p20 ..Fermi or later*...desireable to have ~300+ cores for decent render experience/performance
p23 characters and spaces - not sure is that still the case?
p24 ...file format with current Octane version.
...the best success....1gb vram might be necessary - as worded these really dont give the full picture, rewrite I think
p26 possibly describe what it is you see in the render when you have normals issues. also mention long, narrow triangles. remember not every user is a cg expert. generally manula probably assumes a little too much prior knowledge/self help
p27 vertical lines bugs went away some while ago, just refer to looking at the forums for user identified bugs/issues/known workarounds/more recent builds etc.
UVs must be carefully done in another app. Octane doesnt have any facility to map or alter.
p28 slowness also arises from having an underpowered gpu and from setting large resolutions.
p29 96 absolute minimum for 'see what it is' demos suggest invest in a better card for purchase.
warn about laptop gpu cooling - older nvidia laptop gpu had manufacturing issues prone to damage.
anything else can do - 1.reduce resolution , set camera as wanted (perhaps make use of window zoom), increase res. again 2. change to DL set camera change to pmc if wanted.
p30 symptoms of insufficient power. also gpu 'failed' message in UI, windows bluescreen, blackout, freeze??
mention too closely spaced cards particularly double slot 4xx series, heat rising in case, availability of water cooled cards.
p33 16/8x suitable 4/2x not really desireable, 1x not suitable. mention just slows down data transfer. mix of 16 and 8 as per pcie bandwidth sharing on many mobos is ok.
More chapters to follow based on further feedback and free beer
Personally I would say the manual as is isn't quite up to standard for a final in regard of required detail. Its nicely presented though graphics wise. Maybe if you added this stuff you would then want to make a further pass to make sure it was all in the proper order, not repeated etc.
Last edited by pixelrush on Tue Oct 23, 2012 12:57 pm, edited 1 time in total.
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