PVRX2 - D3DERR_INVALIDCALL messages in native log

[ubu]

When executing PVRX2.exe, the GB-PVR window opens but with no content. The PVRX2.exe-native.log has the following message:

2007-07-08 16:18:35.659 VERBOSE SetRenderList creating new texture (720 x 480)
2007-07-08 16:18:35.689 ERROR m_pD3DDev->CreateTexture(uiElement->image->Width, uiElement->image->Height, 1, 0, D3DFMT_A8R8G8B8, D3DPOOL_MANAGED, &texture, NULL) failed
Error code : 8876086C
D3DERR_INVALIDCALL
Invalid call

This message is the repeated for every CreateTexture call (lots!).

I've used dxdiag to check that DirectX3D is healthy and, AFICT, the Visual C++ redistributable installed OK (shows up in Add/Remove Programs).

gbpvr.exe seems to run OK (not surprisingly).

[sub]

can you zip and attach the complete PVRX2.exe-native.log?

This isnt remotely over Remote Desktop or similar?

[ubu]

can you zip and attach the complete PVRX2.exe-native.log?

Attached.

This isnt remotely over Remote Desktop or similar?

Nope. I was going to try that next.

This is running on a fairly puny laptop - 900mhz P3, 256MB RAM, built-in ATI Mobility 2D video apapter, XP Pro. In the past it's run GB-PVR well enough to have it be my plugin installer app test box

[sub]

This is running on a fairly puny laptop - 900mhz P3, 256MB RAM, built-in ATI Mobility 2D video apapter, XP Pro. In the past it's run GB-PVR well enough to have it be my plugin installer app test box

Unfortinately I dont know if you're going to get this working. It looks like the device isnt up to doing the Direct3D stuff, and fails just creating the textures.

You could possibly look for updated drivers. Hopefully newer drivers might resolve it.

(sorry!)

[ubu]

Unfortinately I dont know if you're going to get this working. It looks like the device isnt up to doing the Direct3D stuff, and fails just creating the textures.

You could possibly look for updated drivers. Hopefully newer drivers might resolve it.

(sorry!)

So, just for future reference, successfully running the dxdiag Direct3D tests (and watching little revolving cubes on your screen) does not neccessarily indicate that a given system willl be able to run PVRX2?

I'll check out if new drivers are available but its no big deal. Just that being able to do test installs on that machine was a bit helpful on the WAF front.

[sub]

So, just for future reference, successfully running the dxdiag Direct3D tests (and watching little revolving cubes on your screen) does not neccessarily indicate that a given system willl be able to run PVRX2?

No, not necessarily. PVRX2 uses really large textures (like the background image), which is larger than some cards can handle.

That may or may not be the problem here though. Hard to tell, but it is failing to create the texture.