solomon wrote:Hi Karba, was " use viewport background" fixed in this build? any hope of it being fixed for 1.55b as well?
Fixed what? viewport background should work in both.
solomon wrote:Hi Karba, was " use viewport background" fixed in this build? any hope of it being fixed for 1.55b as well?
HHbomb wrote:@solomon,
you must :
- check "use viewport background"
- check "alphachannel"
- uncheck "keep environnement"
should work (it works for me)
mbetke wrote:I have just a minor thing:
Everytime I change the render output resolution to certain pixels I also have to change them again for the interactive viewport in the kernel tab.
Can you make a small button which copies over the sizes from the render output to the kernel tab?
mbetke wrote:...I often do final renders in the interactive viewport.
boris wrote:hi karba
we have the following problem with the 2x versions (on two different systems, both max design 2012 x64):
max crashes when closing a scene and ask if we want to save a copy. the scenes are NOT corrupt afterwards.
- the crash happens only on some scenes (bigger scenes)
- could be the crash happens only on scenes which were edited with pre-2x versions of octane
- the crash won't happen if we just edit the scene without ever opening octane preview window
i hoped maybe this was fixed with the memory bug but it wasn't.
it's minor but a bit annoying..
acc24ex wrote:not sure if this issue came up before - check out the animation and the window with the specular texture
- I didn't try any denoising filters in afters.. any recommendations?
.. on max 2015 with this version of octane
.. (still not as stable as 2014 with octane 1.18 which is still use for production.. but much better, with random crashes)
boris wrote:boris wrote:hi karba
we have the following problem with the 2x versions (on two different systems, both max design 2012 x64):
max crashes when closing a scene and ask if we want to save a copy. the scenes are NOT corrupt afterwards.
- the crash happens only on some scenes (bigger scenes)
- could be the crash happens only on scenes which were edited with pre-2x versions of octane
- the crash won't happen if we just edit the scene without ever opening octane preview window
i hoped maybe this was fixed with the memory bug but it wasn't.
it's minor but a bit annoying..
quoted myself from 2.06 release. same with this release.
Users browsing this forum: No registered users and 2 guests