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

dsview & ds input[DO NOT MERGE] #15322

Open
wants to merge 41 commits into
base: develop
Choose a base branch
from

Conversation

hana-alice
Copy link
Contributor

Re: #

Changelog


Continuous Integration

This pull request:

  • needs automatic test cases check.

    Manual trigger with @cocos-robot run test cases afterward.

  • does not change any runtime related code or build configuration

    If any reviewer thinks the CI checks are needed, please uncheck this option, then close and reopen the issue.


Compatibility Check

This pull request:

  • changes public API, and have ensured backward compatibility with deprecated features.
  • affects platform compatibility, e.g. system version, browser version, platform sdk version, platform toolchain, language version, hardware compatibility etc.
  • affects file structure of the build package or build configuration which requires user project upgrade.
  • introduces breaking changes, please list all changes, affected features and the scope of violation.

bofeng-song and others added 30 commits June 1, 2023 13:40
* fix paste component value bug

* fix node.active undo bug
… false (cocos#15232)

* feat: inspector/fbx/mountAllAnimationsOnPrefab default value false

* feat: use getPropValue get value
* add reset function to call when start play

* remove clear

* reset when stop emitting

* rename param & reuse position

* call reset in stop
…) (cocos#15294)

Co-authored-by: cocos-robot <cocos-robot@cocos.com>
* Marionette: adjust additive animation rule

* Rename base -> ref

* Importer UI
@github-actions
Copy link

github-actions bot commented Jun 5, 2023

Interface Check Report

This pull request does not change any public interfaces !

auto resIter = std::find_if(attachments.begin(), attachments.end(), [resID](const AccessStatus& status) {
return status.vertID == resID;
});

auto slotName = rasterView.slotName;
if (rasterView.accessType == AccessType::READ || rasterView.accessType == AccessType::READ_WRITE) {
slotName.insert(0, "__in");
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think __in prefix is not needed?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In shdc we process input attachment eg c0 in #pragma subpassColor c0 into __inc0.
Same time user coding like: pass.addRasterView(user_defined_c0_name, "c0", ...) according to effect, so it's still c0 in rasterView.slotName, which does not match what it is in layoutGraph.attributeIndex.
Not sure if name processing is neccesarry.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think in c++ and effect, __in is not used. __inc0 is an internal variable and will only be used by subpassLoad.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In Vulkan backend subpass input attachment will be bind in descriptor as INPUT_ATTACHMENT, this is the only usage AFAIK.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In that case, I think the name is not needed?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just check the code, that's true, will remove later.

@hana-alice hana-alice changed the title dsview & ds input dsview & ds input[DO NOT MERGE] Jun 8, 2023
@hana-alice hana-alice changed the base branch from v3.8.0 to develop June 8, 2023 09:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet