Did you test it on Windows in OpenGL or DX?
DX allows quite a lot of stuff as it handles many things internally. Stuff that OpenGL will not allow just like that, stuff for which you would have to write handling code in your application.
I think thats exactly what happens here as BM will choose 1 single gpu as its primary device and just use that. But Vista / DX seem to share it depending on the position.
On OpenGL (at least on OSX) you have to do that yourself if you want 3D accelration or create it on all which BM does not do. It uses the primary as any game, thats it. (with sli or virtual sli both together could form a single device)
The problem is not multi monitor support here but that you try to handle 2 distinct GPUs instead of a single one.
But some way to define the "fullscreen" on a multi screen system would be nice and definitely needed for a 2008 pure game oriented language.
DX allows quite a lot of stuff as it handles many things internally. Stuff that OpenGL will not allow just like that, stuff for which you would have to write handling code in your application.
I think thats exactly what happens here as BM will choose 1 single gpu as its primary device and just use that. But Vista / DX seem to share it depending on the position.
On OpenGL (at least on OSX) you have to do that yourself if you want 3D accelration or create it on all which BM does not do. It uses the primary as any game, thats it. (with sli or virtual sli both together could form a single device)
The problem is not multi monitor support here but that you try to handle 2 distinct GPUs instead of a single one.
But some way to define the "fullscreen" on a multi screen system would be nice and definitely needed for a 2008 pure game oriented language.