Haha, hope I’m not crossing the line with “labelling” you a maverick - I know it might be a bit of a misattribution but when one is in the moment anything can happen!
A shame that you can’t import Bryce geometry in to Octane, but I guess it isn’t strange. I’m not sure how many packages out there natively support Bryce files. Not having spent a lot of time in Bryce I’ll ask a silly question: can you convert Bryce geometry to other formats like .obj? Oh, and how do you get Bryce scenes into Octane? Is there a plugin?
Your test scene is looking very promising. I know all about the troubles of working out new material formats from my experiences with Studio to Lux, or at least I would think that Bryce to Octane would be similarly tricky.
No problem over “labelling”, I was just amused.
Bryce to Octane… geometry export is not bad. Not bad at all so far. I’ve already worked out some nice strategies. To tidy things up for Octane I’m using Wings3D to sort out the object/material attribution. I will make tutorials for this process when I’ve got as far as I can and it is fully understood and as optimal as I can make it. Getting the materials out… not so good. There are a few things I can test, and a few strategies that I can think of… but it looks like it will be faffy. But by the time you are ready to contemplate using something like Octane, you really should be ready to cope with faffy! The beauty of Octane for me is that it can sit side by side with Bryce and neither program hinders the other for resources. And in turn, I can use Octane to experiment with accelerated Pathfinding and materials options and then test the results in Bryce on TA, giving me a further insight into the Premium render engine in Bryce.
Click thumbnail to see full-size image