Page 1 of 1

Pencil+ again

PostPosted: Sun Jul 21, 2019 8:57 pm
by ignacio
Hi there,
I'm not sure if this is a bug or what.
I'm trying to capture the pencil+ line renderer settings, but I can't.

how I should be doing this? is possible?

Re: Pencil+ again

PostPosted: Sun Jul 21, 2019 9:17 pm
by ignacio
aaand just a little thing.

Double clicking the custom tokens copies them right?
But then If I wanna paste there a PATH, makes me type it everythime. Would be a more convenient way for that?
I can define a Maxscript token, but then I need to plug it here and there... the custom tokens are more convenient but has this little "issue" ?¿


I found a workaround to that, if I delete the variable name then I can paste watever :D, then i just need to write the variable name again afterwards.

Re: Pencil+ again

PostPosted: Tue Jul 23, 2019 3:33 am
by ignacio
and one more with this.

because I can't use the "pencil+ line render" I setted up in Scanline just so I'm able to export the line, even if I don't need the render.
But I have a variable problem with the file now and feels strange.
When I execture the shot from Vexus windows, it changes from Vray to Scanline.
But when I submit the same project to backburner, it won't change and stays always in Scanline :S

I'm using a Maxscript token with a switch.

I can send you the file to give a look if you want.
Thank you!

Re: Pencil+ again

PostPosted: Tue Jul 23, 2019 3:57 am
by ignacio
maybe this makes it a bit mor clear to understand.
I defined a variable per pass that i want to switch between renderers.

Like I said it works on local not on backburner in backburner just picks the first script.

thank you.

Re: Pencil+ again

PostPosted: Tue Jul 23, 2019 4:16 am
by ignacio
doing this... works.. I just separated the Shot that utilizes the other renderer.

It looks like it only executes 1 maxscript token per shot?

Re: Pencil+ again

PostPosted: Tue Jul 23, 2019 5:08 am
by ignacio

I think i will need to get to max script a bit more with vexus.
Thats why nobody is complaining in the forums? with the maxscript snippet we can force almost anything.

renderers.current = Pencil__4_Line_Renderer()
renderers.current = V_Ray_Next__update_2()

was the key to my problems.

still, I think the maybe the maxscript token is doing something wrong.

Re: Pencil+ again

PostPosted: Tue Jul 23, 2019 4:31 pm
by boomer

I'm having a difficult time following all of your posts, so I'll start with your first one. I investigated the failure to capture Pencil 4+ rendererer and have discovered that there is a bug in the renderer that prevents capturing. We have contacted developer relations at psoft to report this.


Re: Pencil+ again

PostPosted: Tue Jul 23, 2019 7:43 pm
by ignacio
Sorry about it.
some times I found 2 or more things that I would like to share but maybe adding them in the same post is not the most clear/clever way.

Thankyou for the pencil+ report. I'll keep an eye on it.

Re: Pencil+ again

PostPosted: Wed Jul 24, 2019 10:50 am
by boomer

Here is the response we received back from PSOFT:
"Thank you for pointing out the issue with the Clone() method. You are right, we have not implemented it. We will consider adding support for it in the next update."

If we hear any further, I will let you know.


Re: Pencil+ again

PostPosted: Thu Jul 25, 2019 12:19 am
by ignacio
Thankyou for taking care.

I kinda find a workaround for the moment.
setup a standard scanline and force then a renderer change by maxscript. still keeps the outputs and I can add elements.
Not so neat, but works.