I am with you. Really would love to see some basic tutorials to the guys that have not worked with alembic so much!I'm afraid that the preparation of the script will be too difficult.
Will there be a tutorial? Step by step showing how to do all this?
.. ORBX is completely Javascript!.. using JS in both Octane engine and ORBX seems like a no-brainer...
Yes, that's one of the reasons why we chose Alembic, because it stores animation data very efficiently. The functionality is not there yet in the standalone (only camera paths for now), but it's coming.PolderAnimation wrote:I am not sure if I understand correctly but is it also possible to scrub through animated vertex positions and animated transforms?
Yes, we will provide some well commented scripts that will be self explanatory, so don't worry if you don't have a PhD in computer science (although it helps).m.arc.in wrote:Really impressive!
I'm afraid that the preparation of the script will be too difficult.
Will there be a tutorial? Step by step showing how to do all this?
WASD navigation can be done via a script that listens to user input, in case you want to build a first person shooterpixelrush wrote:What I would like is to be able to use the view window to place camera way points.
How I imagine this would work with an architectural walk through is to move to a plan view in orthographic mode and using a front clipping plane hide the roof/ceiling away. Entering way point mode/tool you left click in the view to place way points all at the same eye height (z) - initially anyway. These would show up as small say, pink cubes or pyramids like blender camera (hidden during render) that you could right click on for its ID details or label for ref . Each cube would have an ID no. xyz, rot values and a pause at /delay value in a table similar to instances and you could edit/add/delete points the later. I suppose 16 or 32 would be enough. Smooth camera paths would be created automatically from these points. Another way to arrive at this data set would be to have wasd + mouse rot camera navigation and moving through the scene yourself take a position snapshot at each point of interest. Anyway just thinking out loud here....
Actually ORBX streams are scripted/driven entirely by Lua (most scripting is done on the host). Lua has a much smaller footprint than JS and executes much faster when calling native routines. With ORBX.js, any 'user script' code that gets executed on the client in a browser is first auto-converted to JS (and suffers no speed hit as native JS). However, when native ORBX client executes these scripts, it does so as straight lua, using a JIT when possible, to achieve the same or better speed as compiled C code.FrankPooleFloating wrote:Good thing I am a programmer... though, Javascript is my weapon of choice. I just did a couple minutes research - Javascript and Lua have a bunch of similarities, so I should be okay, if I end up playing around with this and possibly write some scripts etc.
But I am rather perplexed, that you guys went with Lua...
Very excited about the scripting, an incredibly usefull addition! I even prefer that over object motion blur.RayTracey wrote:Thanks! The new scripting feature that is also coming in Octane 1.5 will allow you to render and save image sequences and specify every parameter per frame of the animation such as the amount of samples per pixel, sun position, DOF, post processing fx, white balance, ... You could also render for example only each 3rd frame for fast previews. With scripting the possibilities are virtually endless, it's very powerful.FrankPooleFloating wrote:Wow RT!!.. very cool!
Will there be an animation render target that will save out sequence frames (png, exr etc)?
Awesome! looking forward!RayTracey wrote:Yes, that's one of the reasons why we chose Alembic, because it stores animation data very efficiently. The functionality is not there yet in the standalone (only camera paths for now), but it's coming.PolderAnimation wrote:I am not sure if I understand correctly but is it also possible to scrub through animated vertex positions and animated transforms?
