PowerVR VS 3.0 Demo!!!
- Thread starter radiATIon
- Start date
SegaR&D said:
and shapeshifting in front of you...
man those people do love their jobs
ActionNews
Newcomer
Kristof said:Well it works on the refdevice...
Do you mean PowerVR hardware running DX9 Demos
Well you don't need DX9 for SEGAs Arcarde , or am i completly wrong ? CU ActionNews
refrast, I assume, is whathe means by reference device.
Mintmaster
Veteran
Kristof, can you confirm what NVidia was saying above? Is the refrast giving you incorrect images with your updated voxel demo?Kristof said:Well it works on the refdevice...
At least both give different images on the refrast than on the nv40 / 61.32(which has sometimes a known performance bug and the latest HLSL isn't also free of bugs, so maybe it's a little bit early to do some real benchmarks). The Cloth demo is nearly working, after some small mods(only minor stuff, driver-bug/prob. releated), VSDisplayPhaseB.vsh seems to be like the problem shader - so no cloth in the final image
3D-Analyse isn't 3_0 ready yet, but I'am working on it.
Thomas
3D-Analyse isn't 3_0 ready yet, but I'am working on it.
Thomas
Mintmaster said:Kristof, can you confirm what NVidia was saying above? Is the refrast giving you incorrect images with your updated voxel demo?Kristof said:Well it works on the refdevice...
We assume that NVIDIA modified an old version of Voxel themselves to work on the new runtime and as part of those modifications broke the demo. The conversion we did (just replace texld with texldl) works just fine and looks exactly as before as far as I know. I definitely know that cloth should be working fine.
Basically if you download the new voxel version from our pvrdev website it should be working correctly on refrast and any hardware which supports SM3.0. If anyone thinks a result obtained on the refrast is wrong send a screenshot to devrel and we'll look into it.
K-
tb said:
Any changes other than the texture format change to R16G16F ?
VSDisplayPhaseB contains the actual vertex texturing instructions so that is pretty much the base functionality that is falling over then ? Could be driver issues with multiple samplers, I use 3 samplers (textures) in that demo. The only other thing I thought of is that I am not setting the actual filtering mode myself, D3D default is point sampling though so it should not be an issue.
K-
hstewarth said:
hstewarth we provide source code for that demo so you can see exactly what is being done, and there definitely is no video card ID detection code in there... AFAIK all PowerVR demos released so far are written for standard APIs and will work on any card that meets the minimum caps spec required.
K-
Interesting effect. Definitely looks like the normals are wrong, the position is hard to say since all kinds of accuracy effects could come into play especially since we have been fiddling with the texture formats.
Actually out of curiosity could you check using caps viewer under adapter formats, any of them, and then subcategory texture formats and then check for which formats they expose D3DUSAGE_DMAP. I wonder if NV40 can only do vertex texturing from a very small subset of textures, possibly they must have 4 components for the vertex texturing to work ?
Bit more work would be to use the following :
Still if you'd try to use an unsupported format why is the call not failing ? Unless I am not checking the return code but even then it should still show up in the debug stream when you enable full dx debug level. Anything showing up there ?
K-
Actually out of curiosity could you check using caps viewer under adapter formats, any of them, and then subcategory texture formats and then check for which formats they expose D3DUSAGE_DMAP. I wonder if NV40 can only do vertex texturing from a very small subset of textures, possibly they must have 4 components for the vertex texturing to work ?
Bit more work would be to use the following :
Code:
An application can query if a format is supported as a vertex texture by calling IDirect3D9::CheckDeviceFormat with D3DUSAGE_QUERY_VERTEXTEXTURE.Still if you'd try to use an unsupported format why is the call not failing ? Unless I am not checking the return code but even then it should still show up in the debug stream when you enable full dx debug level. Anything showing up there ?
K-
Similar threads
