Visual Effects Graph in Built In Render Pipline

I was looking at the requirements for this asset

https://assetstore.unity.com/packages/tools/particles-effects/ignis-interactive-fire-system-181079

and under requirements is says Built-in/Standard RP (Visual effects graph 7.3.1-10.2.0)

but I thought VFX was only available in Scriptable render pipelines

https://blog.unity.com/technology/c...th-the-visual-effect-graph-verified-in-2019-3

is VFX graph available in BiRP?

 

Shadergraph and VFX are likely headed to built-in too.

 

That would be cool. The asset suggests that VFX is available for built in now though. But ive never heard this before.

 

Probably just Unity's moving parts moving faster or slower than other parts. It'll end up somewhere sane eventually

 

Yeah, I just installed it in Unity 2019.4 - im surprised because I had no idea Visual Effects Graph could be imported in a Built In Render pipeline project. ill test it out in a bit.

 

You'd probably need to build shaders manually for it if they haven't ported shadergraph to that version of Unity's Built-In pipeline though. I'm guessing 2021.2x+

 

That's too bad - I was looking forward to trying it. But i understand, and thanks for letting me know

 

I can confirm, it works with Visual Effects Graph 7.3.1 and 10.4.0 with the Standard Pipeline.

You'll need to open the VFX and press Compile on each one (there are about 9 of them).

- Install the VFX version
- Optional: Install Post Processing
- Install the Ignis
- Optional: Setup the post-processing layers
- Compile the fire VFX

 

https://github.com/LastAbyss/unity-visualeffectgraph-builtin

 

Frankensteing this thread, anyone have this working on any 2021.3.11+ LTS version?

 

A bit too late to say this but if it previous versions worked with Built-In why the regression? I am glad that Shader Graph is in 2021 Built in but it would be great to have it supported in 2023.

 

Why the shader graph is supported in builtin but VFX graph not supported?
In your opinion, how should I support and create effects? Create 3 separate projects and create new VFX graphs in each project?
Who came up with 3 different and incompatible renderings?
As assetstore developer, I don't want to maintain my assets anymore. Thanks.

 

I think that such a key feature should be available across. Also it makes mad how Unity takes as excuse to abandon support for built in in favour of RP when in RPs stuff has been broken and WIP like forever.

 

Hope Built-in RP will be depricated ASAP. It's pain to support such inflexible and clunky rendering.

 

Built in RP is a perfectly working solution that works out of the box in Xbox One, Series, PS4. 5, PC, Linux, delivers performantly and has been abandoned in favour of forever WIP scriptable RPs which now start to be somewhat become usable in production.

 

I agrée. I use Built In and have released several games with it. I hope it continues to have support from Unity.

 

From what I've been told compiled shaders on the SRPs are a lot more bloated compared to compiling shaders on Built-in. In my own opinion, Unity could have just continued to improve the built in pipeline or made SRP an extension of built in rather than create a replacement and making asset development a lot more difficult.

 

Legacy RP, which you call "Built-in", is extremely different in its core. They cannot coexist with the concept of SRP.
It's agony and hard work to maintain multiple pipelines at the same time. Not only for us, as developers, as asset manufacturers, but also for unity developers. LegacyRP scales extremely poorly, it expands poorly. It is difficult to integrate new features into it, to test them. It's closed, after all, it's a black box.

Once upon a time, there was a fixed pipeline on GPUs, there were no programmable shaders. It was abandoned. It's the same here - you just have to abandon the Built-in pipeline. The time has come.

 

Why don't we have parity after more than half a decade if scriptable render pipelines are so much more flexible?

 

What functional have LegacyRP that haven't in SRP? Or can't be added yourself?

 

I think you answered that question yourself. It you need to create it yourself in URP, but it exists in BiRP, and the only advantage is a questionable performance gain - then it is just a make work project for yourself.

The reality is that BiRP performs just fine on any platform and until recently anyway, URP actually performed worse in one to one projects on Vulcan.

So, the question becomes what is the goal? Why have 3 separate rendering pipelines where shaders need to be created three times? Triple the work for the same outcome. It's no wonder people are annoyed with it.

Don't get me wrong, I'm warming up to URP. And if we don't completely abandon unity over its industry pricing, we will end up needing to adopt it at some point. But paying some dev on your team to recreate shader after shader because of a possible 5 to 10% performance increase that could just be handled by proper asset management isn't something that companies or individuals should be excited about.

That said, I agree, it should be one pipeline that's flexible to all. Right now new developers are still spamming discord and forum posts asking why their BiRP custom shadeded assets from wherever are pink in the scenes. It's setting people up for failure before they even begin.

But I digress. I read their point as why use URP (and manually recreate a bunch of things or see limitations like max number of lights or encounter issues like shadow failures due to URP bugs) versus something built in that 'just works'.