Jump to content

  • Log In with Google      Sign In   
  • Create Account

We're offering banner ads on our site from just $5!

1. Details HERE. 2. GDNet+ Subscriptions HERE. 3. Ad upload HERE.


#Actualmhagain

Posted 01 February 2013 - 11:21 AM

The most obvious explanation is that your hardware doesn't support linear filtering of RGBA16F cubemaps, but if so that should just generate a GL error (or best case drop you back to software emulation) rather than crashing. Nonetheless, if that is the cause (you didn't say what specific NV hardware you're talking about so it's hard to say) the driver mess-up is in the crash, not in the lack of support (which would be determined by your hardware and not by anything in software).

#2mhagain

Posted 01 February 2013 - 09:19 AM

The most obvious explanation is that your hardware doesn't support linear filtering of RGBA16F cubemaps, but if so that should just generate a GL error (or best case drop you back to software emulation) rather than crashing. Nonetheless, if that is the cause (you didn't say what specific NV hardware you're talking about so it's hard to say) the driver mess-up is in the crash, not in the lack of support.

#1mhagain

Posted 01 February 2013 - 09:18 AM

The most obvious explanation is that your hardware doesn't support linear filtering of RGBA16F cubemaps, but if so that should just generate a GL error rather than crashing.  Nonetheless, if that is the cause (you didn't say what specific NV hardware you're talking about so it's hard to say) the driver mess-up is in the crash, not in the lack of support.


PARTNERS