A Unity ID allows you to buy and/or subscribe to Unity products and services, shop in the Asset Store and participate
in the Unity community.
Discussion in '2019.3 Beta' started by PipebknOT, Sep 21, 2019.
this error still present
I was using 2019.3.0f6, my problem was fixed after updating to 2019.3.2f1. I want to tell what led to this problem, maybe this will be useful for someone.
I liked the way the lightning worked in Standard unity shader, but I'm still not very good at writing shaders and I needed to use few custom textures blended, so I found this post
Where a guy from Unity Technologies suggested taking the shader and the .cginc from shaders pack, and then formatting them. I copied following files:
And then, according to the post, added few sampler2Ds, few float Parameters and an uniform array (for 1023 elems). Then changed the Albedo function in UnityStandardInput.cginc. Everything worked great, but after restarting the editor I was getting errors about "Requesting non existent keywords at index". And again, it was fixed after upgrading to 2019.3.2f1
I'm still occasionally getting these warnings still. Even in 2019.3.2f1. although not as frequent as before. Would be helpful to know where unity would encounter such an issue to help narrow it down and submit a repo
Mhh seems like there are more issues related to this error message. As the fix targets https://issuetracker.unity3d.com/product/unity/issues/guid/1195767/ (Camera replacement shader with local keywords). In that case we need repro for whoever still experiences issue in 2019.3.2.
Well technically, it should happen if material changes shader somehow internally. Which causes the current set local keywords invalid. One of the scenario as you know was with replacement camera shader.
The error message is meaningless for users and looks like something internal was uncaught and made its way out of the engine. May I suggest rewording it for more clarity?
I am getting the error still in 3.2. Though knowing Unity's long standing lack of actually getting fixes out when they say I am not surprised.
I just got this problem, think it had something to do with having Enviro... then adding Aura2, trying it out, with Enviro support, ie it was added to the Camera, then removing the component off the camera, and I just deleted the asset.. oh then the compiler symbol it left behind... and since then this error is showing...
2019.3.3f1 doesn't fix it either
Same here, Just created a new project with Unity 2019.3.3f1 and HDRP template, opened for the first time .
Delete the ShaderCache folder in library fixed it
Same here. My project was originally created in 2019.3.0f6 HDRP then upgraded to 2019.3.3f1 HDRP.
We're missing reproducibles for these additional cases. If you're affected by these errors and are able to reproduce them, please submit a bug report with the reproduction project attached.
I did two days ago. Case 1224795. It includes this error and an additional, possibly related bug.
I am using Unity 2019.3.3f1 and still got the error but this worked for me; I made a backup of the ShaderCache folder in case anything went wrong and I needed to bring it back. But it seemed that deleting it got rid of the errors for me and it also, obviously, rebuilt the Shader Cache folder.
Just wondering what is the Shader Cache for? it sounds like it is used for Shader Variant references(?) but I do no know.
2019.3.5 -Still getting them. Mind you they just show up upon opening the editor and I hit clear and it's gone for that session.
Fixed this for me too... thanks!
Happen again here with a new project with URP template, I change the project for a VR project with open VR, I save , and restart and 200 error message has appear ...
We manged to reproduce the error in this case. Fix going to land in 2019.3.8f1.
Again this fix solely targets the problem in that case, as error is very general, there is a chance there is more similar cases. Hopefully this will be enough, but just to be sure I am going to land in next release extended error reporting.
Hey guys! Talked to Unity support about this issue.
Apparently you have to delete the project "Library" folder and re-open the project to have it regenerated again to get rid of these errors. (this is more of a workaround I guess)
I did this and the errors were gone until the next Unity project upgrade and then I deleted the "Library" again and all was good...again.
!!! P.S. BACKUP your project with the old "Library" folder before attempting this!!!
Just fyi, when you delete it goes away, and then after a while (not sure what triggers it this is the best way I can put it) they come back.
On Unity 2019.3.6f1 I don't see this happening for me anymore. It might be different on a per project basis.
I've got it on 3.6f1 too. I'm running the Universal Project Template setup, and the only assets I have installed are Behavior Designer and Behavior Designer/Movement. The error didn't show up during initial project creation nor during import of the two Behavior packages. It only began when I closed and reopened the project.
Is there anything we should do, other than ignoring the error? For instance, is there a shader or camera setting we need to avoid? I had chosen the UPT setup mainly because of the presets for post-processing and camera setups (something that's always an afterthought in my projects, unfortunately).
My hope was that, by using UPT I'd at least have some presets that were standardized and optimized, without glitches that could mess up the build/scene/lighting/rendering. Should I just roll back to the older releases, or is this truly benign?
I am now on 3.6 and still comes up.
Looks like fix is going to come in 3.8
Not fixed in 3.7
Started a new project on 2019.3.7 and I get this
I can confirm this happens 100% for me, too.
1. Create a project from the URP template and open it with Unity 2019.3.7f1
2. Close the project.
3. Re-open the project
54 errors of "Requesting non existent keyword at index NNN"
Let me just quickly quote this - no wonder it happens in 3.7
It hasn't been solved in 2019.3.5f1, I will upgrade the project once I tackle some more bugs created from just upgrading to 2019.3 from 2019.2.
found again confirmed issue in Standard pipeline 2019.3.3f1
just happened to us in 2019.3.7f1. Seemed to be connected to old substance materials once we imported the Substance importer asset
Yep, it went away when I immediately upgraded to 2019.3.7f1, but the problem has come back again when opening.
It has the same exact number of errors as the video above so it's exactly the same thing.
Thanks Dude. This Worked for me.
As 2019.3.9f1 out. Does anyone still experience this issue (Make sure you delete .\Library\ShaderCache\EditorEncounteredVariants, before the upgrade).
Worked for me. Thanks everyone for investigating this.
Worked liked a charm thank you!
FYI -This is fixed, no longer happens in 2019.3.8F1 !!
I can confirm, same here
Getting this error in 2019.2.19f1
Good to hear.
It will be backported to 2019.2
I found that this was also linked to another error I was getting with Burst - where I did not have an updated version of VS C++ on my computer when I made the build.
Just got it in 2019.30f3. Indexes 199, 146 - 198, 224 - 255. Indexes 226 and 229 happen earlier in the sequence.
After restarting Unity, I have Indexes 146-159 and 229.
I get this error too - using Unity 2019.3.0f5
Requesting non existent keyword at index 131.
0x00007FF67293BE7C (Unity) StackWalker::GetCurrentCallstack
0x00007FF67293F2E1 (Unity) StackWalker::ShowCallstack
0x00007FF67108C255 (Unity) GetStacktrace
0x00007FF67359AF1E (Unity) DebugStringToFile
0x00007FF672417A18 (Unity) ShaderKeywordData::GetName
0x00007FF67241803D (Unity) ShaderKeywordData::GetNames
0x00007FF672480547 (Unity) ShaderVariantCollection::AddVariant
0x00007FF6724848F5 (Unity) FinalizeVariant
0x00007FF672486AC9 (Unity) GetSubProgramForShaderSnippet
0x00007FF6724A1940 (Unity) ShaderLab:rogram::CompileShaderSubProgram
0x00007FF6724A37C6 (Unity) ShaderLab:rogram::GetMatchingSubProgram
0x00007FF6724AB23E (Unity) ShaderLab::ShaderState::FindSubProgramsToUse
0x00007FF67249C148 (Unity) ShaderLab:ass:repareVariant
0x00007FF672496759 (Unity) ShaderVariantCollection::WarmupOneShaderImpl
0x00007FF672497327 (Unity) ShaderVariantCollection::WarmupShadersImpl
0x00007FF67249640E (Unity) WarmupEditorShaders
0x00007FF6735D155E (Unity) Shader::ReloadAllShaders
0x00007FF670F4F204 (Unity) GfxDevice::CommonReloadResources
0x00007FF67059653C (Unity) ColorSpaceLiveSwitch
0x00007FF6723212F8 (Unity) PlayerSettings::SyncCurrentColorSpace
0x00007FF67076392F (Unity) Application::InitializeProject
0x00007FF6710B9EE8 (Unity) WinMain
0x00007FF674033BE2 (Unity) __scrt_common_main_seh
0x00007FF831AE7BD4 (KERNEL32) BaseThreadInitThunk
0x00007FF83356CE51 (ntdll) RtlUserThreadStart
You're using builds from many patches ago, of course you're going to see the errors before they got fixed.