https://www.cebas.com/index.php?pid=pro ... prd_id=175
Does someone have tested it ?
How is it compared to Octane ?
Moskito is out
I did. I'm one of the betatesters. Currently, I can say that it performs very very well.bicket wrote:https://www.cebas.com/index.php?pid=productinfo&prd_id=175
Does someone have tested it ?
How is it compared to Octane ?
It's main catch is the native MR and Max shaders compability.
Speed wise Octane is better but thinking that it uses its proprietary shaders that's understandable, isn't it?
But I must say it's not slow at all. Being able to use all native shaders, Autodesk materials and Arch&Design.
Motion blur is supported as well.
Best,
My Portfolio
windows 10 Pro. |1070 + 1070 + 1070 + 1070 | i7 @4.5Ghz
windows 10 Pro. |1070 + 1070 + 1070 + 1070 | i7 @4.5Ghz
- Seekerfinder
- Posts: 1600
- Joined: Tue Jan 04, 2011 11:34 am
Mosquitos are so annoying (and so is Max...)
Love the simplicity though. Otoy can learn a trick there.
Seeker
Love the simplicity though. Otoy can learn a trick there.
Seeker
Win 8(64) | P9X79-E WS | i7-3930K | 32GB | GTX Titan & GTX 780Ti | SketchUP | Revit | Beta tester for Revit & Sketchup plugins for Octane
- UnCommonGrafx
- Posts: 199
- Joined: Wed Mar 13, 2013 9:14 pm
Since this is in the general section, I'll state that the problem with this app is that it is only for the one app.
I looked at their catch-line of being able to use all of the native textures of max as a big hurdle to surpass. But Octane-Cinema4d developer showed that this could be done by every app: take the cpu info, put it on a plane that works for the mapping needs, save image and reapply said image to the object based on those mapping needs.
Octane devvers seem poised to do this with their 2.0 approach, or so I interpret. The catchline with that could easily be:
Every app, every texture, go, do your thing.
I like my vision.
I looked at their catch-line of being able to use all of the native textures of max as a big hurdle to surpass. But Octane-Cinema4d developer showed that this could be done by every app: take the cpu info, put it on a plane that works for the mapping needs, save image and reapply said image to the object based on those mapping needs.
Octane devvers seem poised to do this with their 2.0 approach, or so I interpret. The catchline with that could easily be:
Every app, every texture, go, do your thing.
I like my vision.

i7-4770K, 32gb ram, windows 8.1, GTX Titan and gt 620 for display