1.0.8 available

[banksie]

Liking the new interface quite a bit.

Two comments though, the executable in the process list still lists it as GBPVR.exe - this PVRX2 a temporary name I take it?

Secondly the priority options in the config.xml currently are ignored by the frontend. Setting 'ForceHighPriorityClient' to true seems to have no effect. This is causing a bit of VSync related tearing on my machine which bumping the priority manually through the task manager fixes.

[gkovacsp]

Is there anyone having problems with the irremote.ini file to find the PVRX2 window, while it is not in the foreground?
I mean the commands like the following:

NAVDOWN={findwnd(,PVRX2)}{SendMsg(32771,225,0)}

I replaced the GB-PVR to PVRX2, but it doesn't send the message to that window, when it is not in the foreground.
It worked well with the old UI.

Gabor

[dfdario]

WOW, verything working fine here!
Some messages are still in english and buttons are too small but new interface is very nice (my wife said).

[MixMan]

I am compiling a list of strings that doesn´t translate.....and adding strings to translations. In time I will post a new Excel sheet for translations.

[sub]

Liking the new interface quite a bit.

Two comments though, the executable in the process list still lists it as GBPVR.exe - this PVRX2 a temporary name I take it?

Are you sure you're not running GBPVR.exe instead of PVRX2.exe? It definitely shows up as PVRX2 in the process list here.

[banksie]

Are you sure you're not running GBPVR.exe instead of PVRX2.exe? It definitely shows up as PVRX2 in the process list here.

Ach, no, I know what happened and that is my doing. Sorry, not a bug at all. I renamed the executable to get the new interface via the tray icon which I use a lot... Shows what happens when I post late at night.

Experimenting further I don't get the Vsync tearing issue when running on the primary display, only when I shunt it over to the TVout secondary display. Presumably this is a quirk of the ATi drivers for the HD2900 series cards. I can work around it by manually setting the priority so it isn't an important issue.

[sub]

Ach, no, I know what happened and that is my doing. Sorry, not a bug at all. I renamed the executable to get the new interface via the tray icon which I use a lot... Shows what happens when I post late at night.

No worries.

Experimenting further I don't get the Vsync tearing issue when running on the primary display, only when I shunt it over to the TVout secondary display. Presumably this is a quirk of the ATi drivers for the HD2900 series cards. I can work around it by manually setting the priority so it isn't an important issue.

There was a patch posted in '1.0.8 survival guide' thread that may fix this this. See the post about running on a secondary monitor.

[banksie]

I am running the patch, but I am not activating GBPVR on the second monitor. Being a fickle beast I use GBPVR on my LCD screen a lot as well as pushing it over to the TV. So I use hydravision to push the GBPVR window over to the second display when I want to use the TV.

Do you think altering the config to start on the secondary display will make a difference? I am happy to test it if you do think so.

[sub]

Do you think altering the config to start on the secondary display will make a difference?

Unless you configure it to start on the second monitor, then hardware acceleration will only be available on the primary monitor, leading to jerky video playback and animations when you drag it over to the second monitor.

[banksie]

Unless you configure it to start on the second monitor, then hardware acceleration will only be available on the primary monitor, leading to jerky video playback and animations when you drag it over to the second monitor.

Okay, just testing it now and yes that does cure the tearing issue nicely. Does this mean if I start it on the secondary display and then force it over to the primary it will similarly revert back to software playback only?