# PVRVFrame bugs

**URL:** <https://forums.imgtec.com/t/pvrvframe-bugs/1119>\
**Category:** PowerVR Insider\
**Tags:** pvrvframe\
**Created:** [June 29, 2011, 10:19am UTC](https://forums.imgtec.com/t/pvrvframe-bugs/1119 "2011-06-29T10:19:00Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![michele](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.imgtec.com/michele/32/128_2.png) [@michele](https://forums.imgtec.com/u/michele)\
**Post date:** [June 29, 2011, 10:19am UTC](https://forums.imgtec.com/t/pvrvframe-bugs/1119/1 "2011-06-29T10:19:00Z")

</div>

Hi I would like to report what seem to be a couple of bugs in the PVRVFrame emulator build 2.08.28.0634. I am testing OpenGL ES 1.1 under Win7 64bit (GeForce 460M) using “SGX (OGLES1,OGLES2)” profile and the following happens:  
  
  
  
  
  
- GL\_OES\_texture\_cube\_map is exposed but none of the relative function pointers are available, i.e. glTexGenfOES and the others are all NULL. Also enabling GL\_TEXTURE\_GEN\_STR\_OES returns invalid enum. It’s strange this feature is not present because it should be quite simple to emulate on desktop OpenGL even if the semantic is slightly different. Is there a particular reason not to support this extension on the emulator?  
  
  
  
  
  
- Has\_GL\_OES\_blend\_func\_separate is exposed but glBlendFuncSeparateOES is NULL. Is there any particular reason why this function is not supported by PVRVFrame? It’s seems to me it should be straightforward to emulate it given the host GL implementation supports it, isn’t it?  
  
  
  
  
  
Minor ones:  
  
  
  
  
  
- GL\_OES\_fixed\_point is exposed but its functions are not exposed with their OES suffix, i.e. glAlphaFuncxOES shoud return the same address of glAlphaFuncx I guess.  
  
  
  
  
  
- GL\_OES\_single\_precision is exposed but again its functions are not exposed with their OES suffix, i.e. glDepthRangefOES shoud return the same address of glDepthRangef I guess.  
  
  
  
  
  
Thank you,  
  
  
  
  
  
Michele