[r100]: small bug, negative values for shaders

Bugs will be moved here once resolved.

Post » Thu Aug 23, 2012 4:18 pm

@Ashley : I saw that when doing a mistake. When you enter a value for one of the shader effects (for example Gamma), if you enter a negative number when it doesn't mean anything (for example a negative gamma), the behavior of the IDE is becoming strange (from whitening all the project, to crashing). I think a simple abs(Effect_value) should do the trick to avoid the bug.
B
33
S
9
G
6
Posts: 709
Reputation: 6,704

Post » Thu Aug 23, 2012 6:02 pm

This is deliberately allowed because for many effects parameters outside the intended range can actually have interesting or unusual results, which you may want to take advantage of for creative purposes.

So it may look graphically weird, but it should never crash. Can you reproduce any of the crashes? Sometimes they may also be driver bugs, have you tried updating your driver?
Scirra Founder
B
359
S
214
G
72
Posts: 22,952
Reputation: 178,600

Post » Thu Aug 23, 2012 7:54 pm

Okay, I understand the desired outcome. (Although a negative gamma still doesn't mean a lot ). Anyway, I think the crashed is related to the fact I was trying that inside VirtualBox (it's not working properly inside it, anyway...)
B
33
S
9
G
6
Posts: 709
Reputation: 6,704

Post » Thu Aug 23, 2012 8:03 pm

VMs either have no GPU support at all, or AFAIK their GPU support is pretty buggy, like having really bad drivers. So I would assume it's that, unless you can get any crashes on a non-virtual OS... and even then, I would still say it's a driver bug :P

It's a real shame how cool GPU technology is, but how crappy drivers and support make it hard for everyone to use it. Anyway, I'm going to close this report for now.Ashley2012-08-23 20:04:32
Scirra Founder
B
359
S
214
G
72
Posts: 22,952
Reputation: 178,600


Return to Closed bugs

Who is online

Users browsing this forum: No registered users and 3 guests