I can also confirm this issue in R15, 17 and 18.aoktar wrote:Confusing. You're on diffuse type and tabs belong to specular type.mr_seq wrote:I just installed the R2 update and it seems like the "Emission" tab has disappeared from the material?
(In the attributes manager, it's still there in the node editor)
Am I the only one with this problem?
Version 3.04.5-R2 (05.12.2016)-Previous stable
Moderators: ChrisHekman, aoktar
- nycjunglist
- Posts: 25
- Joined: Tue Dec 22, 2015 6:20 am
Ryzen 9 3950x | 128 GB RAM | 2x 3080Ti
Could you pls check with this version?nycjunglist wrote: I can also confirm this issue in R15, 17 and 18.
viewtopic.php?f=85&t=58047
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
Is it still the case that the LV is always one step behind, when adjusting anything? Lights, colours, materials. Change the light value, hit enter... nothing. Change it again, the LV shows the value you first changed it to.
It's a really frustrating way to work when you have to set a value twice just to see the change update. Makes it hard to A/B two different values or even work quickly.
Apologies if this has already be asked, did a search and came up with this being a problem in 2.14 I think and so should have been solved well by v3?
Also, some clones not showing in LV when render instances are on. Some of the clones from cloner show, random ones do not.
Thanks
It's a really frustrating way to work when you have to set a value twice just to see the change update. Makes it hard to A/B two different values or even work quickly.
Apologies if this has already be asked, did a search and came up with this being a problem in 2.14 I think and so should have been solved well by v3?
Also, some clones not showing in LV when render instances are on. Some of the clones from cloner show, random ones do not.
Thanks
1-Do you have any proof for this issue? I don't never see. I'm using this plugin everyday. And I'd be fixed that if there's so serious problem. You may have a partial problem with your settings. I can't be happy to see this kind of keen words. Have you ever asked for a fix for that if there's a problem we couldn't see?sbstnc wrote:Is it still the case that the LV is always one step behind, when adjusting anything? Lights, colours, materials. Change the light value, hit enter... nothing. Change it again, the LV shows the value you first changed it to.
It's a really frustrating way to work when you have to set a value twice just to see the change update. Makes it hard to A/B two different values or even work quickly.
Apologies if this has already be asked, did a search and came up with this being a problem in 2.14 I think and so should have been solved well by v3?
Also, some clones not showing in LV when render instances are on. Some of the clones from cloner show, random ones do not.
Thanks
2-What's it? You can't use render_instances inside of another render_instances. It's our limitation.
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
Thanks Aoktar, I didn't realise about the render instances inside render instances, that was indeed what I was doing. I have corrected my scene, thanks!
The LV update has been an issue for me in every single version for v3 release on MacOS C4D (or at least 3.03, 3.04, 3.05, I started using Octane with 3.03).
Is it a settings thing? Any change I do, I have to make 2 actions for Octane to update. Which is either, apply the value twice for the parameter (eg, set value and hit enter, set same value and hit enter), or set value, then click an object or move the camera or do something that is a second action, to cause Octane LV to update.
My settings are default as attached screen grab.
The LV update has been an issue for me in every single version for v3 release on MacOS C4D (or at least 3.03, 3.04, 3.05, I started using Octane with 3.03).
Is it a settings thing? Any change I do, I have to make 2 actions for Octane to update. Which is either, apply the value twice for the parameter (eg, set value and hit enter, set same value and hit enter), or set value, then click an object or move the camera or do something that is a second action, to cause Octane LV to update.
My settings are default as attached screen grab.
@sbstnc: Could you pls check it with "sync on geo. updates"? Because it's not happening on me or someone else as i know.
See video about updates: https://vimeo.com/196456214
See video about updates: https://vimeo.com/196456214
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
It's not default for OSX version. Because it causes problems on multi-view mode in viewports of OSX. Btw we have to test it again after your post. But it doesn't work as you said. And nobody says that too. That's strange. You may think to update C4D.sbstnc wrote:That's fixed it, thank you so much for pointing me in the right direction. This is so much better to work with!
As it was not the default (I don't think?) I did not assume that changing this would lead to a better experience for me.
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
I am on the latest R18 with updates, sorry the hardware/software details were not in my signature.
The other thing I have noticed ( and I am not sure if this is expected behaviour or not) is that the LV will refresh and start over each time I click a tag or an object in the attributes manager. I have always found this odd that since no change is being made, only selection, the LV would redraw. Maybe not a big deal, just curious what is happening here.
The other thing I have noticed ( and I am not sure if this is expected behaviour or not) is that the LV will refresh and start over each time I click a tag or an object in the attributes manager. I have always found this odd that since no change is being made, only selection, the LV would redraw. Maybe not a big deal, just curious what is happening here.
While you talk about those you should describe more details. It's on a simple scene or complex with lot of content. There's a few cases which is hard to avoid. Cloners with some effectors and motionblur. C4d always trigger update messages and hard to understand should we update or not in real. In particular cases.sbstnc wrote:I am on the latest R18 with updates, sorry the hardware/software details were not in my signature.
The other thing I have noticed ( and I am not sure if this is expected behaviour or not) is that the LV will refresh and start over each time I click a tag or an object in the attributes manager. I have always found this odd that since no change is being made, only selection, the LV would redraw. Maybe not a big deal, just curious what is happening here.
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw