Page 20 of 28

Re: OctaneRender® for Poser (Windows) 2.06 [STABLE]

Posted: Sun Sep 07, 2014 2:31 am
by face_off
The service release 4 for poser 10 and pro 2014 is out ... i hope fix it the subd on prop
I haven't read anything that indicates SR4 addresses this issue. However with Octane 2 you can get Octane to do the subdivision, so this issue has a good work-around.

Paul

Re: OctaneRender® for Poser (Windows) 2.06 [STABLE]

Posted: Sun Sep 07, 2014 6:42 pm
by RGUS
Why does "Reconvert Materials for this Prop/Figure from Poser" now require a "Refresh the Octane Scene from Poser"? to show the changed materials on skin or clothing or any material that you change in the poser scene.
It never use to and restricts workflow.

Re: OctaneRender® for Poser (Windows) 2.06 [STABLE]

Posted: Sun Sep 07, 2014 7:43 pm
by Krew
RGUS wrote:Why does "Reconvert Materials for this Prop/Figure from Poser" now require a "Refresh the Octane Scene from Poser"? to show the changed materials on skin or clothing or any material that you change in the poser scene.
It never use to and restricts workflow.
You beat me to it. :) I was just going to mention this also.

Re: OctaneRender® for Poser (Windows) 2.06 [STABLE]

Posted: Sun Sep 07, 2014 8:47 pm
by TRRazor
I also found that - although otherwise working just wonderfully - the HDRi Studio Pro Plug-In has a bug that when you change the values of the lights added (for example the power) the light uncontrollably jumps to the very top of the scene.

Not sure what triggers this problem, as it otherwise runs fantastic.

Re: OctaneRender® for Poser (Windows) 2.06 [STABLE]

Posted: Sun Sep 07, 2014 10:43 pm
by face_off
Why does "Reconvert Materials for this Prop/Figure from Poser" now require a "Refresh the Octane Scene from Poser"? to show the changed materials on skin or clothing or any material that you change in the poser scene.
It never use to and restricts workflow.
I cannot replicate this problem. Which version did the issue first appear in? Does it happen on the Default Andy figure?
the HDRi Studio Pro Plug-In has a bug that when you change the values of the lights added (for example the power) the light uncontrollably jumps to the very top of the scene.
I cannot reproduce this problem either. Which build of HDR Light Studio are you using pls?

Paul

Re: OctaneRender® for Poser (Windows) 2.06 [STABLE]

Posted: Sun Sep 07, 2014 11:31 pm
by Krew
face_off wrote:
Why does "Reconvert Materials for this Prop/Figure from Poser" now require a "Refresh the Octane Scene from Poser"? to show the changed materials on skin or clothing or any material that you change in the poser scene.
It never use to and restricts workflow.
I cannot replicate this problem. Which version did the issue first appear in? Does it happen on the Default Andy figure?
I have this same issue. It first started in version 2.6.0.24 and it does happen on the default Andy figure. Here are some pictures of a test using Andy. In this test, picture one is Andy as he loads into Poser. Picture two shows the result after I added a rope texture to the entire figure and selected "Reconvert Materials for this Figure/Prop from Poser". The final picture shows the correct texture applied after the scene is refreshed. I've also tested with Auto Refesh on and get the same result.

Default Andy:
Image

Andy with Material added after "Reconvert Materials for this Figure/Prop from Poser" [Note that now Andy's default RBG color is also now removed]:
Image

Andy after a refresh using the "Refresh the Octane Scene from Poser" button:
Image

face_off wrote:
the HDRi Studio Pro Plug-In has a bug that when you change the values of the lights added (for example the power) the light uncontrollably jumps to the very top of the scene.
I cannot reproduce this problem either. Which build of HDR Light Studio are you using pls?
I have this same issue also. Moving the light before changing the value will prevent this from happening. My version of HDR Light Studio is: 4.3.20131206.1249, Current Plugin: Poser v1.0.3

Re: OctaneRender® for Poser (Windows) 2.06 [STABLE]

Posted: Sun Sep 07, 2014 11:51 pm
by face_off
I have this same issue. It first started in version 2.6.0.24 and it does happen on the default Andy figure. Here are some pictures of a test using Andy. In this test, picture one is Andy as he loads into Poser. Picture two shows the result after I added a rope texture to the entire figure and selected "Reconvert Materials for this Figure/Prop from Poser". The final picture shows the correct texture applied after the scene is refreshed. I've also tested with Auto Refesh on and get the same result.
I can now reproduce this - thanks. I will post a fix for this shortly.
I have this same issue also. Moving the light before changing the value will prevent this from happening. My version of HDR Light Studio is: 4.3.20131206.1249, Current Plugin: Poser v1.0.3
I still cannot get this to happen (I'm running the same version of HDR Light Studio). Could it be the Octane Viewport is picking up the mouse click from HDR Light Studio (ie. is HDR LS "over" the Octane Viewport)?

Paul

Re: OctaneRender® for Poser (Windows) 2.06 [STABLE]

Posted: Mon Sep 08, 2014 12:16 am
by Krew
face_off wrote:I can now reproduce this - thanks. I will post a fix for this shortly.
Thank you Paul! :D
Krew wrote:I have this same issue also. Moving the light before changing the value will prevent this from happening. My version of HDR Light Studio is: 4.3.20131206.1249, Current Plugin: Poser v1.0.3
face_off wrote:I still cannot get this to happen (I'm running the same version of HDR Light Studio). Could it be the Octane Viewport is picking up the mouse click from HDR Light Studio (ie. is HDR LS "over" the Octane Viewport)?
I can get this to happen very consistently and it's not the Viewport picking up the mouse click (I just tested several times to make sure). My experience is that if you do not move the light, then changing the value will cause the light to jump to the top every time. However, once you move the light a bit, the bug won't repeat itself until you open a new project.

Here is what I would suggest to test it:

1. Set up a couple of lights in HDR Light Studio and save the project.
2. Repeat so that you have 2 or 3 projects to test with.
3. Close HDR Light Studio and the Octane Render Plugin.
4. Launch the Octane Render Plugin and HDR Light Studio as you normally would, load one of your test projects.
5. Without moving a light (and without clicking on the actual light in the main panel) click on a light in the left panel (the light list) to highlight it.
6. Now change the value (watts), and the light should jump to the top.

Clicking on the light itself, or moving the light, seems to "cure" the problem for the duration of the session. However, opening a new project or sometimes re-opening the same project will cause it to happen again.

I hope that makes sense.

Re: OctaneRender® for Poser (Windows) 2.06 [STABLE]

Posted: Mon Sep 08, 2014 6:04 am
by face_off
1. Set up a couple of lights in HDR Light Studio and save the project.
2. Repeat so that you have 2 or 3 projects to test with.
3. Close HDR Light Studio and the Octane Render Plugin.
4. Launch the Octane Render Plugin and HDR Light Studio as you normally would, load one of your test projects.
5. Without moving a light (and without clicking on the actual light in the main panel) click on a light in the left panel (the light list) to highlight it.
6. Now change the value (watts), and the light should jump to the top.
I still cannot reproduce this. Poser now saves the light position, so you shouldn't need to load and save HDR projects. Can you post a screenshot or video of this happening pls? Was it happening in the previous version of the plugin? Are you changing the watt by moving the slider, or entered a power number and then enter?

Thanks

Paul

Re: OctaneRender® for Poser (Windows) 2.06 [STABLE]

Posted: Mon Sep 08, 2014 7:16 am
by TRRazor
Hey Paul,

sorry for replying so late.
I'm using the same version as mentioned above - and the bug is behaving exactly like mentioned here by the folks who answered to my initial post.

If you move the light slightly it won't have the bug - if you don't it does.

I always type the wattage value in by hand, seldom use the slider to set it.
Maybe the hit on "Enter" causes the light to jump to this zero position!?