Jump to content

  • Log In with Google      Sign In   
  • Create Account

FREE SOFTWARE GIVEAWAY

We have 4 x Pro Licences (valued at $59 each) for 2d modular animation software Spriter to give away in this Thursday's GDNet Direct email newsletter.


Read more in this forum topic or make sure you're signed up (from the right-hand sidebar on the homepage) and read Thursday's newsletter to get in the running!


#ActualKaptein

Posted 09 May 2013 - 05:30 AM

mixing old and new works just fine anywhere, but there's certain restrictions, like you're stuck with the old VAO format
but, i'm guessing you are writing to the texture you're reading from
which if i was a driver maker would crash your computer, just to give you that good reason to read the manual :9

it's not allowed, because the gpu is a huge parallell thingie, and it can't guarantee the results

if you wanted to permanently change the components, you could do it many ways:
1. read texture data to memory and change them with code
2. write to new texture
3. just change the colors on the fly with a shader..

the last one is the easiest, and fastest, since vec4(vec3(1.0) - color.rgb, color.a) is not really slow...

#1Kaptein

Posted 09 May 2013 - 04:13 AM

mixing old and new works just fine anywhere, but there's certain restrictions, like you're stuck with the old VAO format
but, i'm guessing you are writing to the texture you're reading from
which if i was a driver maker would crash your computer, just to give you that good reason to read the manual :9

it's not allowed, because the gpu is a huge parallell thingie, and it can't guarantee the results
just guessing here though =)
if you wanted to permanently change the components, you could do it many ways:
1. read texture data to memory and change them with code
2. write to new texture
3. just change the colors on the fly with a shader..

the last one is the easiest, and fastest, since vec4(vec3(1.0) - color.rgb, color.a) is not really slow...

PARTNERS