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

Improve ShaderLab's compatiblity with the RenderState of Material #2378

Merged
merged 33 commits into from
Sep 20, 2024

Conversation

Sway007
Copy link
Member

@Sway007 Sway007 commented Sep 13, 2024

Please check if the PR fulfills these requirements

  • The commit message follows our guidelines
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

When no RenderState is specified in ShaderLab, render pipeline use the RenderState setting of Material, instead of using a default RenderState.

What is the current behavior? (You can also link to an open issue here)

Runtime will render a material whose shader created by ShaderLab with a default RenderState even if no RenderState is specified in ShaderLab, instead of with the RenderState setting from Material.

Summary by CodeRabbit

  • New Features

    • Enhanced efficiency in shader rendering by optimizing the instantiation of render states.
  • Bug Fixes

    • Prevented unnecessary creation of render state objects when no relevant data is present, improving performance.

@Sway007 Sway007 added enhancement New feature or request shader Shader related functions medium priority Medium priority issue labels Sep 13, 2024
Copy link

coderabbitai bot commented Sep 13, 2024

Walkthrough

The changes in the Shader.ts file involve a restructuring of how render states are handled within the Shader class. The implementation now includes a conditional check to determine if constantMap or variableMap has entries before creating a new RenderState object. This adjustment prevents unnecessary instantiation and processing when there are no render states to apply.

Changes

Files Change Summary
packages/core/src/shader/Shader.ts Restructured logic for rendering states; added condition to create RenderState only if necessary.

Possibly related PRs

  • Enhance ShaderLab documents #2331: This PR involves optimizations in Shader.ts related to rendering states, while also enhancing documentation about ShaderLab, sharing a context of rendering states.

🐇 In the shader's realm, where states do play,
A check was added to brighten the way.
No more waste, just pure delight,
Rendering smoothly, a beautiful sight.
Hooray for the changes, let’s hop and cheer,
For optimized shaders, we hold so dear! 🌟


Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 98de462 and c419fe6.

Files selected for processing (1)
  • packages/core/src/shader/Shader.ts (1 hunks)
Additional comments not posted (1)
packages/core/src/shader/Shader.ts (1)

115-130: LGTM!

The code segment introduces an optimization by checking for the presence of constant or variable render states before creating and processing the RenderState object. This avoids unnecessary object creation and processing when no render states are defined.

The destructuring of constantMap and variableMap improves code readability, and the logic for applying constant render states and parsing variable render states remains functionally correct within the conditional block.

Overall, the changes enhance the efficiency and clarity of the render state handling logic.


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    -- I pushed a fix in commit <commit_id>, please review it.
    -- Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    -- @coderabbitai generate unit testing code for this file.
    -- @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    -- @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    -- @coderabbitai read src/utils.ts and generate unit testing code.
    -- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    -- @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@Sway007 Sway007 marked this pull request as ready for review September 13, 2024 06:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request medium priority Medium priority issue shader Shader related functions
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants