2019.3.0b4 requesting non existing keyword at index ..

Unity Engine
,
1

after closing unity 2019.3.0b4 for the first time and re-open my urp template project again after i installed the android module, it show these errors

requesting non existing keyword at index 80
requesting non existing keyword at index 81
requesting non existing keyword at index 114
requesting non existing keyword at index 118
requesting non existing keyword at index 136
requesting non existing keyword at index 138
requesting non existing keyword at index 145

etc.

i dont know if its for the android module, or a urp shader keyword problem.

1 Like
2

Happens to me as well. I’m not even attempting Android builds or have the android module installed. Windows only for me. It also not URP related as I have no need for the new Shader Pipelines, I’m still running standard. I would totally rollback to a previous Unity version if I could as performance is crap now. But I’m stuck and its my own fault, I totally forgot to backup before the upgrade. I’l reply back if i find a fix. I can’t even run a play a full build now b\c of this. it will build it just won’t run it. also im running b5.

Appears related to DX11, switching to DX12 makes them go away, but I cant use DX12 with my stuff. So something silly changed with how the editor manages DX shader keywords between 2019.2 and 2019.3

1 Like
3

I also got this, too. An extremely long time to launch the project then saw the errors. I closed and re-opened the project which loaded quicker and no errors.

4

My errors are still there but it’s not affecting the build or compilation so I’m at a loss

5

Could you please submit a bug report for this issue?

6

Started getting lots of console error spam when loading my project in 2019.3.b09+
Doesn’t happen in empty project of course. So wondering if it might be something I’m doing.
May have to submit my entire project as I can’t reproduce.

5151011--510305--keywords.PNG
5151011--510305--keywords.PNG495×1363 90.5 KB

Is this known?
Stack trace:

Requesting non existent keyword at index 128.
0x00007FF6910E643C (Unity) StackWalker::GetCurrentCallstack
0x00007FF6910E98A1 (Unity) StackWalker::ShowCallstack
0x00007FF68F854F15 (Unity) GetStacktrace
0x00007FF691D403E0 (Unity) DebugStringToFile
0x00007FF690BC3B68 (Unity) ShaderKeywordData::GetName
0x00007FF690BC418D (Unity) ShaderKeywordData::GetNames
0x00007FF690C2C4E7 (Unity) ShaderVariantCollection::AddVariant
0x00007FF690C30895 (Unity) FinalizeVariant
0x00007FF690C32A69 (Unity) GetSubProgramForShaderSnippet
0x00007FF690C4D8D0 (Unity) ShaderLab::Program::CompileShaderSubProgram
0x00007FF690C4F756 (Unity) ShaderLab::Program::GetMatchingSubProgram
0x00007FF690C571CE (Unity) ShaderLab::ShaderState::FindSubProgramsToUse
0x00007FF690C480D8 (Unity) ShaderLab::Pass::PrepareVariant
0x00007FF690C426E9 (Unity) ShaderVariantCollection::WarmupOneShaderImpl
0x00007FF690C432B7 (Unity) ShaderVariantCollection::WarmupShadersImpl
0x00007FF690C4239E (Unity) WarmupEditorShaders
0x00007FF691D767CE (Unity) Shader::ReloadAllShaders
0x00007FF68F71C154 (Unity) GfxDevice::CommonReloadResources
0x00007FF68ED71E4C (Unity) ColorSpaceLiveSwitch
0x00007FF690ACDDB8 (Unity) PlayerSettings::SyncCurrentColorSpace
0x00007FF68EF3C3C7 (Unity) Application::InitializeProject
0x00007FF68F882A08 (Unity) WinMain
0x00007FF6927D9122 (Unity) __scrt_common_main_seh
0x00007FFA70144034 (KERNEL32) BaseThreadInitThunk
0x00007FFA72833691 (ntdll) RtlUserThreadStart
7

Have same problem too after upgrade to 3.0b10

8

Same after reopening my project, 2019.3.0f1

3 Likes
9

I’m seeing this as well - it just started in Unity 2019.3.0f1, I hadn’t seen it previously.

10

Yeah I’m running into the same problem with 2019.3.0f1

11

Same here

12

We’re still missing a reproduction project for this issue. If you’re able to reproduce this issue, please submit a bug report with the project attached to it and reply in here with the issue ID.

1 Like
13

I’ve found that deleting the ShaderCache folder in Library stops those errors, which probably means the new editor version using the compiled shaders from an old editor version when it shouldn’t.

Maybe the upgrade process should empty that folder?

Trying to see if I can get the issue replicated consistently for a bug report.

9 Likes
14

OK, so that just stops the issues on Editor start, I’m seeing it when using the search function on a complex scene with a bunch of materials.

15

I just started to get them as I was re-building my project in Unity 2019.3.3f1. I then checked my Layers and I was missing a lot of them. I had done a manual re-build from backups and not a upgrade of my project from 2019.2. So I forgot to re-type back in all my Layers. After I typed back in my missing layers, closed and re-opened the project all the “requesting non existing keyword at index” errors went away.
Hope this helps some of you that are getting this.

1 Like
16

Same for me on 2019.3.0b 12.
And on reopening project, the issue disappeared.

2 Likes
17

same here using 2019.3.0b12 upgraded project form 2018.3 does not affect builds tho, did bilds for pc and xbox without issues and no aparent glitches

5305524--533118--upload_2019-12-21_21-4-34.png

18

Unity Technologies is unable to reproduce the issue and is asking for a project to reproduce it:

If you’re able to reproduce the issue, please submit a bug-report as described in this document:

It’s important that you report these issues together with a reproduction project if you want them to get fixed. If you don’t do it, it might be a long time until someone else reports them or until Unity Technologies find them.

After you submitted the bug-report, you receive a confirmation email with a bug-report Case number. Please post the Case number (number only, not the link) in this forum thread for Unity staff to pick up.

3 Likes
19

I’m sure most people here know how to send a bug report. I also get these errors almost always when I open the Editor, although they don’t seem to affect anything (or at least I didn’t notice yet).

The problem others probably have as well is how to send a useful bug report. I can’t pinpoint the cause, nor the first occurrence (“since 2019.3”); the only reproduction step I found is “open the Editor”, and since the error provides no specific information, I can’t really make a minimal repro project. And it seems to depend on the Library/ShaderCache from the previous posts, so the Library folder would have to be included, too.

If it’s of any use, I can of course send the entire 30GB Assets + 38GB Library folders, but that’s about all the information I can provide about this bug. The stack trace was already posted by CDF earlier in the thread .
The number of the ‘non existent keywords’ errors isn’t the same every time I open the project, sometimes I get eight of them, sometimes two, sometimes none when opening the Editor. I’m attaching the Editor.log (as txt because of the forum extension restrictions) if it helps.

5306547–533271–Editor.txt (61.9 KB)

20

Unity needs better FTP for bug reports, my last bug report on Xbox forum required send whole project. It took me a while to prepare and after uploading there was some kind of issue with the size. They asked me to chop tthe zip in several parts and reupload.
Please understand more and more we’re running on tighter schedules because of the flood of shovelware etc. So we cant take long to prepare repro projects.

3 Likes