Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove built-in render pipeline support #467

Open
elfin8er opened this issue Mar 2, 2024 · 2 comments
Open

Remove built-in render pipeline support #467

elfin8er opened this issue Mar 2, 2024 · 2 comments
Assignees
Labels
refactoring Ugly code that needs to go

Comments

@elfin8er
Copy link

elfin8er commented Mar 2, 2024

I am trying to test a table using Unity's built-in render pipeline, but balls don't seem to be working currently. According to the documentation: "the built-in renderer is legacy not recommended", but I see no mention if it not being supported.

Unity version: 2022.3.6f1

Steps to reproduce:

  • Create a new Unity project with the 3D template
  • Install VPE packages:
    • org.visualpinball.engine.unity
    • org.visualpinball.unity.assetlibrary
    • org.visualpinball.engine.pinmame
  • Save a default .vpx table from VPX
  • Import .vpx into VPE using Visual Pinball > Editor > Import Wizard
  • Enter Play mode
  • Pressing/holding Enter doesn't launch a ball
@arthurkehrwald
Copy link
Contributor

I don't think it makes sense to support it. The built-in render pipeline is slowly being phased out and supporting three different render pipelines is just a maintenance nightmare. I can't think of any benefits for users either.

@freezy
Copy link
Owner

freezy commented Feb 8, 2025

Yes, I think we'll remove support for the built-in renderer.

I think the path forward is to focus on HDRP and when Unity merges the pipelines in v7, we'll adapt accordingly.

@freezy freezy changed the title Support for built-in render pipeline? Remove built-in render pipeline support Feb 8, 2025
@freezy freezy self-assigned this Feb 8, 2025
@freezy freezy added the refactoring Ugly code that needs to go label Feb 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
refactoring Ugly code that needs to go
Projects
None yet
Development

No branches or pull requests

3 participants