You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by "Justin Mclean (JIRA)" <ji...@apache.org> on 2013/06/05 11:14:19 UTC
[jira] [Resolved] (FLEX-33583) Context3D::setSamplerStateAt
parameters missing in API
[ https://issues.apache.org/jira/browse/FLEX-33583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Mclean resolved FLEX-33583.
----------------------------------
Resolution: Won't Fix
Sorry but this is a Flash Player issue not an Apache Flex SDK issue and we are unable to fix it. Please report the bug in Adobe bug base at https://bugbase.adobe.com
> Context3D::setSamplerStateAt parameters missing in API
> ------------------------------------------------------
>
> Key: FLEX-33583
> URL: https://issues.apache.org/jira/browse/FLEX-33583
> Project: Apache Flex
> Issue Type: Bug
> Components: 3D Support
> Affects Versions: Adobe Flex SDK 4.6 (Release)
> Environment: All environments
> Reporter: Gary Paluk
> Labels: api-change, incomplete, sampler, states
> Fix For: Adobe Flex SDK 4.6 (Release)
>
>
> Their are missing parameters Context3D::setSamplerStateAt API
> When looking at the general parameters sent as sampler state using AGAL, you will notice 5 possible parameters that define the state.
> <cube,linear,mipnearest,clamp,dxt1>
> The current setSamplerStateAt() API signature is as follows:
> public function setSamplerStateAt(sampler:int, wrap:String, filter:String, mipfilter:String):void
> Without all of the necessary state parameters, it deems the functionality as incomplete and unable to perform required functions needed to decouple and manage sampler state at runtime. Having this functionality would be in line with standard practices and provide the ability to reuse shaders for different texture types and allow for samplers to be derived after the the texture type has been derived, both of which are assumed fundamental to sampler state management.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira