Skip to content
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

Not rendering on 2019.2 #1

Closed
WoLfulus opened this issue Aug 12, 2019 · 3 comments
Closed

Not rendering on 2019.2 #1

WoLfulus opened this issue Aug 12, 2019 · 3 comments

Comments

@WoLfulus
Copy link

For some reason I couldn't make it work on 2019.2 - nothing gets rendered (default import). Plus some errors pop (about file location) if I try to move the the folder to a subdirectory.

Ideas?

@gwaredd
Copy link
Owner

gwaredd commented Aug 13, 2019

It looks like Unity have changed how TextAssets work in 2019 - either intentionally or this is a bug.

For example, if I create an empty project and add a bunch of different text files (txt, json and md) then the default inspector also doesn't render anything either. I would have at least had a basic preview in 2018. Scripts appear ok but they are a different asset type IIRC.

The markdown viewer implements a CustomEditor for a TextAsset, which seems to be picked up correctly but doesn't call OnInspectorGUI() as expected. It's called on input events but not it appears on Layout and Render, suggesting a bug to me - or at least a half-baked behaviour change.

This might require some input from Unity and further investigation

@gwaredd
Copy link
Owner

gwaredd commented Aug 13, 2019

Almost certainly this bug in 2019.2 ...

https://issuetracker.unity3d.com/issues/overridden-oninspectorgui-method-is-not-called-when-using-customeditor-typeof-defaultasset

Suggest you also login and upvote it, see if that gets unity's attention :)

https://forum.unity.com/threads/oninspectorgui-not-being-called-on-defaultasset-in-2019-2-0f1.724328/

@gwaredd
Copy link
Owner

gwaredd commented Nov 3, 2019

Apparently there is a fix coming in 2020.1, however I've checked in a workaround for the bug in 2019.2.

8e70f5b

@gwaredd gwaredd closed this as completed Nov 3, 2019
gwaredd pushed a commit that referenced this issue Nov 22, 2020
gwaredd pushed a commit that referenced this issue Apr 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants