![]() ![]() This is an important topic for Windows Store apps (a.k.a. Option #1 and #2 are the only choice for a Windows Store app that supports ARM (Windows RT). However your application must have a special error message mode that runs if you are only able to create a Feature Level 9.1 device that says something like "This application requires Feature Level 10.0". ![]() According to the Windows Store app requirements, you are free to list a minimum Feature Level higher than 9.1 as a requirement for your application, (3) You write your application to require Feature Level 10.0 and compile all your shaders for Shader Model 4.0. This can become quite complex, but gives customers the best experience based on their hardware. Multiple versions of some shaders and likely multiple versions of the rendering code based on the available feature level. a version of the same graphical effect that doesn't use Geometry Shader). a Geometry Shader based effect), and you would have to write a fallback solution that worked on Feature Level 9.1 (i.e. Some effects would require Shader Model 4.0 (i.e. You would have many shaders compile using vs/ps_4_0_level_9_1 profiles and use them in all versions. ![]() For example, you could support Feature Level 9.1 and Feature Level 10.0 in your application. (2) You write your graphics system to scale across Feature Levels. This is probably sufficient for many applications, but this is rather limiting if you are trying to create a rich graphics experience such as those in games. (1) Your Windows Store application is written to only use Feature Level 9.1. You have three basic choices when dealing with this scenario: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |