Workflow / Interface Restrictions

[arexma]

we will have funky WSAD movement in one of the next versions I read.

Are these official sources?

+10^100 for WSAD from my part

hmmyes...
http://www.refractivesoftware.com/forum ... 534#p28534

Hey,

It's on our short-term list, probably for the 2.3 final release.
We already have the icon for it.
[....]
Radiance

Dates back a bit to August 2010, however can´t be far. Maybe it caused some bug or whatsoever and isn´t in yet. So I guess it´s neither forgotton, nor not thought about, threre are just more important matters atm

[naik3d]

I got to admit I wasn´t aware of BS Shot and I don´t think a healthy discussion about tools'n'features will hurt anyone, I doubt someone here will now abandon Octane and quickly get a 1000 bucks license for Shot.. and I don´t want to know what price the Pro version has.
Still, take industry giants like vray. For what I know they are on the way to implement GPGPU calculations, while others are done already and then once it´s done it will have an toiletpaperroll attached as pricetag to hold the digits =)
Smallluxgpu... I´d not use it in a production in its current stage, nor is it a commercial product.
How many others are there? Any commercial OpenCL? Maybe you could save me the time googling....

Sure, every confident app should stand out a discussion about competitors.
Im not totally sure about the OpenCL stuff from other apps, but that is not the point mate.
If it is Cuda or opencl, at the end it is speed / flexibility / performance and of course the result.

Many users are using vrayrt or Iray in production. At the end it depends on how you use that feature.
Also don't forget, Shots technique is IRAY from mental images - it is totally integrated and shows
it's power. So if Shot is not production ready then i don't know.

I really would have to look further into BS Shot with the trail, but their demo video shows nothing too mindblowing compared to octane to justify 1000+ Bucks. I rather pay 200 Euro instead of 100 then for octane to keep development going - or for that matter buy a second one. What i like from the video is the distributed rendering.

So, then you have to look definately further into BS fore sure! At the end, it's quite unfair to compare
BS with octane, therefore this discussion is a bit inadequate, but it would be very nice
if we would get some features from BS and more of course.

(Just one example - take a complete naked scene and load it into octane / BS
then start your watch and look how long it takes to get the image ready, then you know what
i'm talking about. You are maybe 4/5 times faster, despite the fact that you don't need to export and export and export your scene
after modification) Please guys, again i don't want a full and complete 3D app with octane.
I'm only talking about performance, speed, quality, WORKFLOW optimization and such stuff.


And to be honest

the mentioned WASD camera feature, i really can not take this serious.
I mean guys, is that really a high priority feature???! Will that boost your
workflow / productivity? I really can't imagine. Maybe i'm missing the point here...


Kian

[matej]

And to be honest

the mentioned WASD camera feature, i really can not take this serious.
I mean guys, is that really a high priority feature???! Will that boost your
workflow / productivity? I really can't imagine. Maybe i'm missing the point here...

Yes it is important, not crucial or high-priority, but one of those workflow things that would help. Try to reach some 'exotic' POVs with the current camera implementation and you'll know what I mean - navigation is too hard than it should be. Changing the camera navigation has been requested by a lot of people.

[naik3d]

Maybe for you matej, but definately not for me.
I don't know what you understand under exotic pov
but navigating the camera was no problem at all.
Actually i think that it is equal like Mayas navigating therefore
i can not understand the feature request, but maybe other users think
different about this.

Also, why don't you do your camera work inside your main 3D app?
( I hope you get what i mean with this question)

Kian

[GeoPappas]

Also, why don't you do your camera work inside your main 3D app?
( I hope you get what i mean with this question)

For stills, setting up the camera inside of a 3D app is ignoring one of the major features of Octane - the ability to move the camera and see results in (almost) real-time. I just wish that mesh lights were also move-able. IMO, that would give Octane a huge advantage to other rendering apps.

But I also agree that camera movement within Octane is not an easy task (at least I haven't totally figured it out yet).

[arexma]

Maybe for you matej, but definately not for me.
I don't know what you understand under exotic pov
but navigating the camera was no problem at all.
Actually i think that it is equal like Mayas navigating therefore
i can not understand the feature request, but maybe other users think
different about this.

Also, why don't you do your camera work inside your main 3D app?
( I hope you get what i mean with this question)

I say it would be a great feature, but as I said, not vital at the moment. It should require a minimum of coding efford to implement it though.
Sure you could do your camera work in your 3D app. But do you have the nice visual feedback you got in octane? no.

I guess on one hand it is a matter of preference and personal taste, on the other hand it is a matter of spirits.
Take the current camera system in octane.
It is made by "technical spirits" therefor you input x,y,z in meters.
An "artistic spirit" would want to walk around his motiv maybe, capture how the sunlight reflects in the one object and mirrors onto the next just right... impossible in your 3D app. Sometimes it is not about *setting* the POV but about *finding* it.

[GeoPappas]

Sometimes it is not about *setting* the POV but about *finding* it.

I completely agree with this statement. This is how it works in photography a lot of the time. You grab your camera and then walk around the subject matter trying to find that right angle where light looks magical.

[matej]

I don't know what you understand under exotic pov

Exotic as "places that you didn't thought of before your could interactively navigate your scene in real time".

The whole interactive experience of Octane needs a better system for navigating around in search of the best POV. In a lot of occasions I was limited by "invisible walls" (gimbal lock, actually) and other sort of limitations (camera leaning on the sides when you try rotate it on just one axis, the need to manually correct the up vector, etc). I don't have problems navigating in any other 3D package, so it's probably not me...

Of course you can set your camera in the 3D app and export it, but that's the "old way", if you know what I mean.

It's not top priority, but it's there on the first pages of TODO list. It's also been announced months ago, as you can verify in the link arexma posted.

[Jorgensen]

Any news regarding a wasd navigation support?

wasd navigation is so simple to use and jet very intuitive - I think.

As it is now, I find navigation in Octane unnecessary troublesome :-/

[shelshok]

I find it sad that when this comes up, the response is to just do it in your modeling app.

Don't you think it would be useful to place/move at least lights in Octane with realtime feedback?

And why give us a placement node at all if things should not be moved in Octane? Why not show a transform gizmo in the viewport when a placement node is selected, and let us move interactively instead of with the awkward -10000-10000 sliders which seem to apply transformations and rotations in a very counterintuitive manner?