-
Notifications
You must be signed in to change notification settings - Fork 860
Add Virtual texturing support for HDRP [Skip CI] #7
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
Changes from 231 commits
1f26f12
fcd902a
399056a
07b4fd4
a64dd3c
5c02c51
4aadf7e
7660626
f61dd97
c412be1
88b039d
f208e33
ed3525a
1c84d14
ba7ded9
a9a4bdf
7bd84bd
01a6123
081382f
bd18c1b
b4b5d82
8fec595
9a9a159
86314d7
bcb5258
5775f7c
778ad46
32e2703
813bf0e
afeaf5e
aed8247
185a936
502d957
30a5411
d359625
c29f16b
d880010
7e4c58d
d148a6f
36d4d87
d5b864f
fdbfdd5
50a5d2f
a164b99
d33e54c
3eb21e7
17cfc74
15bba6a
c39607f
c199310
aeb3dd5
635aab2
449cfe0
9125f20
5e4a437
647ad05
76e4472
85baa51
55844bc
59ae769
8785f09
f8e4384
470c3a0
fb15f57
fd0d417
2b2d051
dde00b1
454df6a
21d6024
fc96dab
5efba1f
06904d7
bd8173a
3b875e7
40273a2
3115ff1
2afe2e4
6dffe5a
f16aad7
3352029
3a79574
65adf63
4a52d45
c59d6b4
17b6613
67908aa
a2134b6
23309b6
2b8d947
b630eb9
4f69c5c
dffdb8f
40e1dad
d09b0b7
ffff419
113d672
e62443b
ac70e8b
5c414c8
5faca04
917d8b5
2c0bc80
de8d86c
7b8b379
d82f6fb
e1d0611
5e17592
5096a34
84ed367
d3d3e34
3324a30
dac8ecd
a8b4965
0b30c12
6ce7e26
9118998
0835f8a
01a4d1a
c84953b
b792602
1605fae
3529465
6d0b21b
55f0371
2a2a6a6
1578721
8a7b21c
9ceafc1
7900d60
4a6d6a8
df43ef1
c38ef99
96561a1
479b61e
a10d3c0
0db0a7a
651ecc8
e7c5b52
9ae0283
fef30dd
dc78fc1
68c9e07
f35bfed
4726b99
8ece740
297c60c
5993cf0
b9f2996
35f007a
540aa6d
cb4ae83
0f87deb
567d94e
aa91771
d988d1e
a808adb
0bec9ad
8c1fcf3
a6790a3
3154d21
5a94443
fb69ed8
8f2a552
73fd5df
37db362
00e2b1d
78ebc20
097204a
72a7e54
7be5517
c9e7091
33e6e2b
50201ce
c7bc597
cbfb690
b15c325
a2a13fc
a6c6fa6
1fe9723
51ae695
01e1e2e
b000222
4bb16ba
cb6c5b6
75f1e0c
80840ab
61481e2
ee59f50
1c66655
a811c91
cff826d
471dc7b
36cdb14
81934a5
d87db87
e9c8f86
2746969
0189f1d
276c598
a40e5d2
cdc81d8
8d9c104
aeacc14
0d78cbf
305419f
81a5b31
96af903
2fb543a
bb450fc
18016bf
a193ddb
17ac850
7765e10
3b9579c
a9cbdff
79311ec
c2d6745
54c8bab
02b0377
26681ea
7958167
f3df0ef
7544cd6
f0e5a47
182d5cc
fb6a0d9
4e44814
97a5be2
968bd26
188dca4
f7ba33e
95e3c2d
57ec3e9
16f2079
7f5bd57
a49ae6a
88aee59
d803a6a
ab69f70
4725f91
6b9c6e1
4f52cec
ff6d89b
8b007c5
faba745
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,42 +1,21 @@ | ||
| ### **Please read** | ||
| **PR workflow guidelines** | ||
| * SRP ABV will start automatically on Yamato when you open your PR | ||
| * Changes to docs and md files will **not** trigger ABV jobs | ||
| * Consider making use of **draft PRs** if you are not 100% sure that your PR is ready for review | ||
| * ABV will restart if you add a new commit to a branch with an open PR (hence why you should consider using draft PRs) | ||
| * Adding [skip ci] (case insensitive) to the title of PRs will stop any jobs being trigger automatically - you will need to open Yamato and find your branch to run ABV | ||
| * You can also add [skip ci] to commit messages to prevent CI from running on that push | ||
| * Add [cancel old ci] to your commit message if you've made changes you want to test and no longer need the previous jobs | ||
| **Guide** : https://github.com/Unity-Technologies/Graphics/blob/pr-template-correction/.github/pr-read.png.md | ||
|
|
||
| ### Checklist for PR maker | ||
| - [ ] Have you added a backport label (if needed)? For example, the `need-backport-*` label. After you backport the PR, the label changes to `backported-*`. | ||
| - [ ] Have you updated the changelog? Each package has a `CHANGELOG.md` file. | ||
| - [ ] Have you updated or added the documentation for your PR? When you add a new feature, change a property name, or change the behavior of a feature, it's best practice to include related documentation changes in the same PR. | ||
| - [ ] Have you added a graphic test for your PR (if needed)? When you add a new feature, or discover a bug that tests don't cover, please add a graphic test. | ||
| **Display Addon** : https://userstyles.org/styles/182991/unity-graphics-pr-readme | ||
|
|
||
| --- | ||
| ### Purpose of this PR | ||
| Why is this PR needed, what hard problem is it solving/fixing? | ||
| # Purpose of this PR | ||
|
|
||
| --- | ||
| ### Testing status | ||
| > Why is this PR needed, what hard problem is it solving/fixing? | ||
|
|
||
| **Manual Tests**: What did you do? | ||
| - [ ] Opened test project + Run graphic tests locally | ||
| - [ ] Built a player | ||
| - [ ] Checked new UI names with UX convention | ||
| - [ ] Tested UI multi-edition + Undo/Redo + Prefab overrides + Alignment in Preset | ||
| - [ ] C# and shader warnings (supress shader cache to see them) | ||
| - [ ] Checked new resources path for the reloader (in developer mode, you have a button at end of resources that check the paths) | ||
| - Other: | ||
| # Testing status | ||
| ## Manual Tests | ||
| > What have you tested? | ||
|
|
||
| **Automated Tests**: What did you setup? (Add a screenshot or the reference image of the test please) | ||
| ## Automated Tests | ||
| > What did you setup? (Add a screenshot or the reference image of the test please) | ||
|
|
||
| **Yamato**: (Select your branch): | ||
| https://yamato.prd.cds.internal.unity3d.com/jobs/902-Graphics | ||
| ## Links | ||
| **Yamato**: (Select your branch) https://yamato.prd.cds.internal.unity3d.com/jobs/902-Graphics | ||
| > Any test projects or documents to go with this to help reviewers? | ||
|
|
||
| Any test projects to go with this to help reviewers? | ||
|
|
||
| --- | ||
| ### Comments to reviewers | ||
| Notes for the reviewers you have assigned. | ||
| # Comments to reviewers | ||
| > Notes for the reviewers you have assigned. |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,6 @@ | ||
| .pull-discussion-timeline>div:first-child>div:first-child .js-previewable-comment-form::before, .new-pr-form .js-previewable-comment-form::before | ||
| { | ||
| display:block; | ||
| content: url("https://github.com/Unity-Technologies/Graphics/blob/pr-template-correction/.github/pr-read.png?raw=true"); | ||
| height: auto; | ||
| } |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,26 @@ | ||
| @import "github.css"; | ||
|
|
||
| #write{ | ||
| max-width: none; | ||
| width: 709px; | ||
| margin: 0 auto; | ||
| padding: 5px; | ||
| border: 20px solid #bda668; | ||
| min-height: auto !important; | ||
| } | ||
| #write > ul:first-child, | ||
| #write > ol:first-child{ | ||
| margin-top: 0px; | ||
| } | ||
|
|
||
| body > *:first-child { | ||
| margin-top: 0 !important; | ||
| } | ||
| body > *:last-child { | ||
| margin-bottom: 0 !important; | ||
| } | ||
|
|
||
| h1, h2, h3, h4, h5, h6 | ||
| { | ||
| width: auto !important; | ||
| } |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,20 @@ | ||
| # Please read | ||
| ## PR workflow guidelines | ||
| - Consider making use of **draft PRs** if you are not 100% sure that your PR is ready for review | ||
| - Adding [skip ci] (case insensitive) to the title of PRs will stop any jobs being triggered automatically - you will need to open Yamato and find your branch to run ABV | ||
| - You can also add [skip ci] to commit messages to prevent CI from running on that push | ||
| - Add [cancel old ci] to your commit message if you've made changes you want to test and no longer need the previous jobs | ||
|
|
||
| ## Reminders | ||
| - Have you added a backport label (if needed)? | ||
|
|
||
| > *For example, the `need-backport-*` label. After you backport the PR, the label changes to `backported-*`.* | ||
| - Have you updated the changelog? | ||
|
|
||
| > *Each package has a `CHANGELOG.md` file.* | ||
| - Have you updated or added the documentation for your PR? | ||
|
|
||
| > *When you add a new feature, change a property name, or change the behavior of a feature, it's best practice to include related documentation changes in the same PR.* | ||
| - Have you added a graphic test for your PR (if needed)? | ||
|
|
||
| > *When you add a new feature, or discover a bug that tests don't cover, please add a graphic test.* |
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this line is already in master, so I'm confused as to why this is showing as changed in this PR
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ehn I'm snot sure why this review request was added it must be some sort of tooling? And also not sure why it shows up. Master was merged yesterday > 182d5cc