Frame rate drop - very simple jit.qt.movie + slab - Just me ?????
Hello
I would really appreciate if someone could look at this very very simple patch
and let me know if they experience the same drop in frame rate.
We believed to have fixed this issue in 5.1.2, but from your other post it sounds like you are using 5.1.2. Can you please double check and confirm? Apple's compositing manager has changed and there are some mysterious issues on Snow Leopard when we have a fullscreen window that isn't composited with other windows.
The two things you can try for the moment if 5.1.2 isn't working for you are:
- type "; jitter glreadback fbo" in a message box and click it
- use a window which is one pixel shorter than the screen resolution
A quick question, however, is what happens if you use jit.window's fullscreen message when the window is on the second screen instead of simply changing the window size?
-Joshua
Hi Joshua
yes I'm on v5.1.2
It does work with jit.window's fullscreen message
But I don't think I can use that with my application with TripleHead2Go.
Where am I supposed to attach the "; jitter glreadback fbo" message ?
Marie-Hélène
just put it in a message box and click, no need to attach to anything.
read up in the documentation on "messages to max" for more info.
Joshua
So I connected the message "; jitter glreadback fbo" to gl.render and clicked on it
It works :-)
Is there any information regarding this message, I'd like to understand !
All I found is in the Max 4.6 doc
jitter16-release-notes.txt
jit.gl.slab - fix for glreadback fbo unsupported format errors
Marie-Hélène
It's a relatively geeky feature for using different OpenGL infrastructures for performing the method of rendering so that the results can be used as a texture for subsequent operations. Maybe someday it'll get it's due documentation, but in general we've wanted to avoid focusing on this level of functionality for users, and have tried to make the default rendering options work for most people.
In the meantime, if you google jitter glreadback or search the forums, you might find some decent descriptions.
However, I don't see any reason why you couldn't use fullscreen for the triple head to go. As far as the OS is concerned, I believe it just looks like a single monitor, and then it does the splitting without the OS knowing anything about it. So I would imagine "fullscreen" would span the three monitors (or however you have it configured).
We'll investigate further the differences between our fullscreen mode and what you are experiencing with setting the window size manually.
Thanks for the report.