"Your system does not support the required VMR9 video renderer"

[SilverE2]

I reformatted and I keep getting this message when I try to run GBPVR. Help?

[barkers123]

Was about to make an almost identical posting..!

This only happens for me in FSE mode (PVRX2) and only after coming out of standby. I now have Hip shut down PVRX2 before standby and restart it on resume but it still comes up pretty consistently.

After I hit Ok to the message, it will start and work fine. Seems like some sort of timing issue, maybe it hasn't finished cleaning up before the system tries to start it again or something. Dunno. Any ideas anyone..?

[hzwaal]

This only happens for me in FSE mode (PVRX2) and only after coming out of standby. I now have Hip shut down PVRX2 before standby and restart it on resume but it still comes up pretty consistently.

After I hit Ok to the message, it will start and work fine. Seems like some sort of timing issue, maybe it hasn't finished cleaning up before the system tries to start it again or something. Dunno. Any ideas anyone..?

I have the same thing. It seems related to the nVidia drivers for the 6150, which I also have. I could never find a proper solution for this and just stopped using FSE and accepted the fact that there is some tearing in the custom VMR9 mode. I recall that there was something with a delayed start that solved this for some people, but it didn't for me. See also this thread: http://forums.nextpvr.com/showthread.php?t=28992

In any case, I'd be really interested if you find a solution for this.

[frankmcg]

No ideas I'm afraid but only to add that I saw this for the first time yesterday as well, also using FSE mode and an nvidia 8500gt card.

[gEd]

I've been having this problem for a couple of years. The graphics card hasn;t fully woken up and so can't respond to gbpvr so it barfs.

I made a feature request to (optionally) report this error to the log and then quit so that my monitoring script would be able to restart gbpvr after receiving this error.

[barkers123]

Been fiddling on this today.

Have set Hip scheduler to issue an "Esc" keypress and then start GBPVR on resume. If the message pops up, then the Esc kills it and GBPVR restarts. If it doesn't then the Esc and restart are harmless.

Seems to work Ok, though have not tested it extensively.

[jonack]

I also have this problem, but am running W2k, with latest drivers on everything. GBPVR works fine, but PVRX2 doesn't work, so I guess I am relegated back to GBPVR, oh well!

[wtg]

This is a long-shot, but in the past I've had this message pop erroneously when I was launching gbpvr via a remote connection using VNC. If I launched gbpvr and exited my VNC connection quickly, gbpvr would come up and then I could reconnect and everything worked fine.

This doesn't happen for me anymore using pvrx2 in full-screen exclusive mode, but if you are using a remote connection to work on your machine and you know your system does indeed support VMR9, it's something to look into.

[gEd]

I also have this problem, but am running W2k, with latest drivers on everything. GBPVR works fine, but PVRX2 doesn't work, so I guess I am relegated back to GBPVR, oh well!

if you get it every time you try and start pvrx2, then make sure
a) u have a dx9 compatible graphics card
b) directx 9© installed
b) WMP 9 or over installed (just for good measure)

[SilverE2]

Experimenting further...I see that I get this message when I select "EVR" as the video renderer, but not VMR9. Weird!