Forum Discussion
OverheadSurfer
8 years agoHonored Guest
"mobileMTRendering" Error with Unity 2017.2
I just upgraded to Unity 2017.2, and I'm getting a error on lines 290 & 295 of the OVRLint.cs script that "'PlayerSettings' does not contain a definition for 'mobileMTRendering'". It appears to have been removed from UnityEditor.PlayerSetting" class as part of the changes to version 2017.2?
Are others seeing this or am I missing something?
9 Replies
Replies have been turned off for this discussion
- AnonymousI am having the same issue, still trying to figure it out
- OverheadSurferHonored Guest
I commented out the 'moobileMTRendering' portion of the two lines to resolve, but my impression is Oculus needs to revise their script for Unity2017.2. I had an interesting follow-on issue. On two models of computers, commenting this out resolved the issue, but on my third one I got a new issue with the SteamVR_PlayArea.cs script. The only way I have come up with so far to resolve that issue was to remove the SteamVR_PlayArea.cs and SteamVR_PlayArea.cs.meta script entirely.
- mannixloHonored GuestTemp fix by replace the following code:
if (!PlayerSettings.MTRendering || !PlayerSettings.GetMobileMTRendering(BuildTargetGroup.Android)){AddFix ("Optimize MT Rendering", "For CPU performance, please enable multithreaded rendering.", delegate(UnityEngine.Object obj, bool last, int selected){PlayerSettings.SetMobileMTRendering(BuildTargetGroup.Android, true);PlayerSettings.MTRendering = true;}, null, "Fix");} - stef07ExplorerSame error here. Upgrade from 2017.1p4 to 2017.2f3 created above errors on perfectly working project. Any updates on how to fix?
- sp_mvHonored Guest
imperativity said:
Hi,
Thanks for reporting this. I am forwarding this to our internal teams for their review and will update this thread when I have more information to share.
Please share any updtae about it. I am having this issue after upgrading to 2017.3 - WITHIN_NimaHonored GuestWe are also having this problem with 2017.2
- Temp fix by mannixlo works great but would be good to have a proper solution. (Also using 2017.2)
- Temp fix by mannixlo works great but would be good to have a proper solution. (Also using 2017.2)
- pixelcaseHonored GuestSame issue here on 2017.3
Quick Links
- Horizon Developer Support
- Quest User Forums
- Troubleshooting Forum for problems with a game or app
- Quest Support for problems with your device
Other Meta Support
Related Content
- 8 months ago
- 2 years ago