-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Invalid fragment shader generated #168
Comments
The conversion also outputs black for "light0Color": {
"type": "FLOAT_VEC3",
"value": [
0,
0,
0
]
}, |
ghost
assigned fabrobinet
Nov 1, 2013
fabrobinet
added a commit
that referenced
this issue
Nov 2, 2013
fixed on dev-2 Note: the model had issues, it refers to a camera but no cameras are defined. |
Thanks - when are we merging dev-2 to master? Also, will look into what the Modo exporter is doing; this should have been a trivial test case. |
I hope by Wednesday. |
now on master. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A trivial model exported from Modo generates the following fragment shader, which does not compile because it doesn't define
ambientLight
.@fabrobinet will send you the model.
The text was updated successfully, but these errors were encountered: