Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
VRTK error
See original GitHub issue- Source of VRTK (Unity Asset Store)
- Version of VRTK (Unity Asset Store v3.2.0)
- Version of Unity3D (Unity 20181.6f1 personal )
- Hardware used (Oculus)
- SDK used (SteamVR Oculus Utilities)
1.Scripts/VRTK/Scripts/Interactions/Highlighters/VRTK_MaterialColorSwapHighlighte.cs(146,66): error CS1540: Cannot access protected member UnityEngine.Texture.Texture()' via a qualifier of type UnityEngine.Texture’. The qualifier must be of type `VRTK.Highlighters.VRTK_MaterialColorSwapHighlighter’ or derived from it
2./Scripts/VRTK/Scripts/Interactions/Highlighters/VRTK_MaterialColorSwapHighlighte.cs(146,66): error CS0122: `UnityEngine.Texture.Texture()’ is inaccessible due to its protection level
I am facing above this two errors how can I solve this problem. Thanks in Advance. a.nurulhudahossain016.o@gmail.com
Issue Analytics
- State:
- Created 5 years ago
- Comments:10
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Some people use open source projects while understanding the implicit agreement that comes with it. It’s foolish to assume that every maintainer is able to maintain old versions forever or specifically work for you and your interest.
For anyone who isn’t an ass about it: the mentioned bug was fixed almost a year ago and we are resource constrained with literally only two persons working on this in their free time. We do want you to join the thousands of users so you can get their help, too. They aren’t active on GitHub for various reasons.
For anyone who knows what they’re doing: fork and fix the old version that you need to keep using despite there being a non-breaking upgrade path to version 3.3 that is the current stable release, but you already know about as you read releases, release notes and get help from the community already!
Its useful to see these post, even if they’re a bit dated/redundant, since they pop up quickly when doing google searches on the issues (and some people new to VRTK might not know about the slack group or the versioning issues with the asset store vs git)