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!


#ActualChris_F

Posted 26 March 2014 - 01:25 AM


I'm quite sure that the cost will go up if you were to have divergence within a single warp. Try randomizing your index based on the pixel coordinate and see how it fares.

 

Just tried rendering a full screen quad that uses a hash of the screen coordinates to pick a random number to index an array of 262,144 sampler handles to 1x1 textures. Was only getting 8 fps. Would liked to have tried and even larger array, but I was getting GL_INVALID_OPERATION at 521,728 textures. With 256 textures I get 22 fps. My understanding is that Kepler supports this while AMD's GCN flat out does not.


#3Chris_F

Posted 22 March 2014 - 09:03 PM


I'm quite sure that the cost will go up if you were to have divergence within a single warp. Try randomizing your index based on the pixel coordinate and see how it fares.

 

Just tried rendering a full screen quad that uses a hash of the screen coordinates to pick a random number to index an array of 262,144 sampler handles to 1x1 textures. Was only getting 8 fps. Would liked to have tried and even larger array, but I was getting GL_INVALID_OPERATION at 521,728 textures. With 256 textures I get 22 fps.


#2Chris_F

Posted 22 March 2014 - 09:02 PM


I'm quite sure that the cost will go up if you were to have divergence within a single warp. Try randomizing your index based on the pixel coordinate and see how it fares.

 

Just tried rendering a full screen quad that uses a hash of the screen coordinates to pick a random number to index an array of 262,144 sampler handles to 1x1 textures. Was only getting 8 fps. Would liked to have tried and even larger array, but I was getting GL_INVALID_OPERATION at 521,728 textures. With 255 textures I get 22 fps.


#1Chris_F

Posted 22 March 2014 - 09:00 PM


I'm quite sure that the cost will go up if you were to have divergence within a single warp. Try randomizing your index based on the pixel coordinate and see how it fares.

 

Just tried rendering a full screen quad that uses a hash of the screen coordinates to pick a random number to index an array of 262,144 sampler handles to 1x1 textures. Was only getting 8fps. Would liked to have tried and even larger array, but I was getting GL_INVALID_OPERATION at 521,728 textures.


PARTNERS