-
Notifications
You must be signed in to change notification settings - Fork 61
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
[Input] Input.mouseObject always returns null #203
Comments
Can confirm that reversing d3d9516 resolves the issue. |
Can now confirm that the issue comes from reading from the Alpha channel, which is notoriously impossible. |
Really? That's bizarre. I couldn't find a reason for it before, but I've been pretty swamped this week and last weekend so I hadn't dug too far in. Why is reading from alpha any different than the others I wonder? |
Also side note, the cursor position is definitely wrong on my laptop. |
Hey @Zedoctor, any chance of tackling this tonight before |
Ended up with a super busy weekend, so no :/ It looks like it could be that the Alpha channel gets lost when any blending is done, but I didn't think we did any blending on that particular FBO, so I'm pretty stumped as to why it's not working correctly. |
To add some confusion to this, Input.mouseObject works on my machine in the labs. Perhaps its an issue at the graphics driver / card level? |
Something about
0.9.0
broke Input.mouseObject. I have tested in Spectral Robot and Sample-Dash-Game.The text was updated successfully, but these errors were encountered: