chrisbrackenbury

put jit.window on screen 2 ,switch to maximised,switch on qmetro then take a look at the error reports in max window.

if you re-start max then leave the window on screen 1 then switch qmetro on its ok even if you move it to screen 2 and maximize

just updated to 5.1.4
and then this
put jit.window on screen 2 ,switch to maximised,switch on qmetro then take a look at the error reports in max window.
if you re-start max then leave the window on screen 1 then switch qmetro on its ok even if you move it to screen 2 and maximize
seams to happen on xp only
system
xp sp2
intel quad
nvidia gforce 9800gt
opengl 3.2

strange-behavior-since-5-1-4-update-on-two-screens

This looks like a tough one. There are a variety of things that could be going on here. It could be a driver issue, an XP issue, a Max issue, or a combination of the three. We are taking a look and hopefully will be able to make this work smoother, but in the meantime, you will want to move the jit.window over to the second screen after you start creating your render contexts and textures.

Regarding the second patch, 'foo' is already being used in the Jitter global namespace, so this object will always come up as bogus.

This looks like a tough one.  There are a variety of things that could be going on here.  It could be a driver issue, an XP issue, a Max issue, or a combination of the three.  We are taking a look and hopefully will be able to make this work smoother, but in the meantime, you will want to move the jit.window over to the second screen after you start creating your render contexts and textures.

that change works but you cant go full screen as the same error pops up so ill just use adjust accordingly.

Thanks Ben
that change works but you cant go full screen as the same error pops up so ill just use adjust accordingly.
regards chris


Another workaround to try is to create a borderless window the @size of the second monitor (setting the not using fullscreen) on the first monitor and then move it over, either manually or by setting the @rect.

that was my work round when i found the full screen bug, all is OK right now with the changes so thanks for your help Ben at least i know its not me :) .

thanks Ben
that was my work round when i found the full screen bug, all is OK right now with the changes so thanks for your help Ben at least i know its not me :) .
regards Chris


strange behavior since 5.1.4 update on two screens