What is stopping you from replacing your current rendering method with Octane?
In my case I got my license mainly to give my share of support for Refractivesoftware and to play with Octane for fun. I don't think I'll be able to switch to Octane for my work any time soon, even thought I really wish that.
Some of the users already stated that the cumbersome import of CAD geometry into Octane stopped them from using it. The currently proposed method for exporting in OBJ is certainly not an option for busy professionals. For me this method is inconvenient, but still acceptable, because typically I don't work with large assemblies.
My main concern is the studio lighting setup.
The integrated Daylight System I guess works fine for architectural visualizations, because one light source is usually enough and the sharp cast shadows are not a problem. For some simple setups rotating a HDRI or using mesh emitters could also work.
But for all of us who have to precisely attune multiple light sources and reflections, neither of the above methods could be an option. Manually exporting and importing the entire scene form the 3D modeler to Octane every single time we need to slightly move emitter/reflector would be extremely unproductive. Besides it ruins the whole real-time concept.
I'm really interested to learn what are the Radiance's thoughts on this major issue.
A Hdrlightstudio Live Plugin could solve this problem nicely, but I seriously doubt we'll see Live Plugin for Octane anytime soon. Also the price of this little program is ridiculously high for what it is.
Still you may want to check it out:
http://www.hdrlightstudio.com/hdrlights ... ation.html
So if I have to make some constructive suggestion I would say - may be some very simplified combination of the current Daylight System and the Hdrlightstudio approach.
For example: support for multiple (3-4) Light Systems inside the Octane scene similar to the Daylight System, but with rectangular shape of the emitter and the following parameters:
Ratio - For the proportions of the rectangular light.
Size – Controlling the size of the reflection and the softness of the cast shadow.
Rotation, Intensity and Color.
It is very simple, but should be enough for most scenarios and I am certain the majority of users wont mind to pay some extra if it is offered separately as a plugin.
What is stopping you from switching to Octane?
Forum rules
For new users: this forum is moderated. Your first post will appear only after it has been reviewed by a moderator, so it will not show up immediately.
This is necessary to avoid this forum being flooded by spam.
For new users: this forum is moderated. Your first post will appear only after it has been reviewed by a moderator, so it will not show up immediately.
This is necessary to avoid this forum being flooded by spam.
I admit it would be nice to have the ability to actually manipulate geometry in the render view. Things like lights and subtle movements of meshes would be convenient. Of course I have already bought a license so I'm invested in refractive and I hope that they continue developing on a path that will benefit my interests.
Windows 7 64bit | AMD Phenom 9550 | 6 gigs ram | Blender, Silo, messiah 4.5 |
Lights will come, and they will evolve. Patience is a big thing here. Now that the administrative stuff is getting taken care of Radiance can get back into working on Octane a lot quicker.
System 1: EVGA gtx470 1280Mb and MSI gtx470 1280 in Cubix Xpander for Octane, AMD 945, 4Gb Ram
All systems are at stock speeds and settings.
All systems are at stock speeds and settings.
Thx for the great render, guys.
Looking forward for lights with IES, material library, UV edit, displace, manipulate with obj models (move,scale,delete), connect with VRAY. And LESS crushes! IMHO It`s necessary things.
I`ll buy it soon.
Looking forward for lights with IES, material library, UV edit, displace, manipulate with obj models (move,scale,delete), connect with VRAY. And LESS crushes! IMHO It`s necessary things.
I`ll buy it soon.
q6600 gtx275 4gbRAM Win 7x86