Particle Shader Broken with Krakatoa PRTLoader / Phx PRTReader and VRayGPU

[Joelaff]

When I load a PRT file in using a Krakatoa PRTLoader I can select this PRTLoader as the particle source for a ParticleShader (PHXFoam). This renders correctly with VRay CPU. However, it renders nothing with VRay GPU (hotfix1).

The same thing seems to happen with a Phoenix PRTReader.

The Particle Shader renders fine if the particles come from a Phoenix Liquid directly.

The Krakatoa tools (esp MagmaModifer) are indispensable when dealing with particle stuff. So I am really hoping this can be made to work.

Thanks.

[Svetlin.Nikolov]

Oh, this one seems to have slipped through testing. Should be an easy fix. Have you noticed if it's affecting only Bubbles/Splashes, or only Fog for example?

[Joelaff]

I couldn’t see any of the modes, but I didn’t try to tweak the settings to test to be sure they weren’t just faint (e.g. fog or particles). Bubbles definitely did not work. I don’t think any of them did.

Thanks.

[georgi.zhekov]

Hey,

The Phoenix PRT reader seems to be working on our side, may be there is something we're missing - can you send us a scene along with a few prt files so we can check what is going on?
You can either attach it here as a zip file or send it to the support mail with a link to this thread.

As for the Krakatoa PRT loader - indeed this one is not working, will log it in our bug tracker and I hope we'll have a fix soon.

Thanks!

[Joelaff]

Let me see what I can put together. I know I was testing this in a simple test scene.

In my actual project scene I know PRT Reader did work over or twice, it also produced crashes of Max which I will see if I can narrow down for you.

i am also sure the PRT Reader did NOT work in my simple test scene. Will try to find that for you.

Of course I really hope to get the PRTLoader working as we use the MagmaModifier for all kinds of tricks and that does to work on PRTReader. (Could it be made to work? Either by you guys, or in conjunction with ThinkBox? It would be nice if the MagmaModifier could be used on any of the PHX particle object types. I assume this is some kind of object class setting. )

[Joelaff]

I sent a scene to support and referenced this thread. When I get a ticket number I shall post it.

Thanks!

[Svetlin.Nikolov]

Awesome, thank you very much! If we get the crash it would be great as well. Not sure if getting magma to work with Phoenix is possible at all - gotta check, but anyway, you will probably need some thinkbox license, so not sure this would be useful...

[Joelaff]

You do need a ThinkBox Krakatoa License to use Magma, but I think a large number of VFX houses use Krakatoa. So I would say definitely useful if it is easy to do (like just adding something to a list of acceptable types/classes or something).

Once you have access to Magma you really just fall in love with it. It is a crazy power flow graph to handle particle manipulation.

https://docs.thinkboxsoftware.com/pr..._overview.html

[tashko.zashev]

Hi,
Can you give me the ticket number you have received from our system, because I can't find any new cases from your account opened in the latest few hours ? If you don't have a ticket number, then try to resend your email to support@chaosgroup.com.

[Svetlin.Nikolov]

Hehe, I know what Magma is, what I meant was that I need to find out whether there is a programming interface to it...

[Joelaff]

Hi,
Can you give me the ticket number you have received from our system, because I can't find any new cases from your account opened in the latest few hours ? If you don't have a ticket number, then try to resend your email to support@chaosgroup.com.

I never got a ticket number back. I just re-sent. Mailserver shows:
Aug 4 17:46:24 po postfix/smtp[9935]: 48639F80BBA: to=<support@chaosgroup.com>, relay=ASPMX.L.GOOGLE.com[74.125.69.27]:25, delay=4, delays=0.24/0.06/3.1/0.61, dsn=2.0.0, status=sent (250 2.0.0 OK 1596581184 t8si122118iol.62 - gsmtp)

So your google mail server got the message. Perhaps they are flagging it as spam?

Just got a reply:

Your ticket number is: 314-119-5516

[Joelaff]

Hehe, I know what Magma is, what I meant was that I need to find out whether there is a programming interface to it...

LOL. Sorry. I think it is a matter of setting up the object as whatever class/ID will take a MagmaModifier. But I don't code Max plugins at this time. I am sure Bobo at ThinkBox could tell you in an instant.

[georgi.zhekov]

Thanks, we got the files. Seems like there is something strange with the PRT sequence as it's not working with our PRT reader, while other PRTs we have tested work correctly. Where does it come from?

Logged this and the Krakatoa PRT loader issue in our bug tracker and I hope they will be fixed quickly. Will update the thread once we know more.

Cheers!

[Joelaff]

It's a pretty standard PRT Sequence written by Krakatoa (who created the PRT format). It was initially a PFlow flow.

Here are the settings. Perhaps some of the channels are not handled on your end? I figured they would be ignored if that were the case.





Note also: I have had issues with the PRTReader with a PRT sequence I created using the Chaos PRTExporter from the quad menu as well. This was in fact the one that was crashing (which I am still trying to find). This one also did not start a frame zero. It started at around 119 I think.,. Both sequences worked fine with Krakatoa's PRTLoader.

[Svetlin.Nikolov]

Alriight, raising this thread from the dead like a zombie.

Or, alternatively - the thread is rising from the ashes like a phoenix :>

Fixed a bug where PRT caches that contain many numbers did not render correctly in vrscenes, meaning V-Ray Standalone/V-Ray GPU/Chaos Cloud - such was the case with the 'particles__part01of12_####.prt' caches from this issue.

The fix will be in tomorrow's nightlies