Scott Fitzgerald

I've been noticing *something* different in some of my gl patches as

of late, and I think I found it. I am not sure if it has been

In max Max 4.6/Jit1.6, when using [jit.gl.render @blend_enable 1

@erase_color .xx .xx .xx .01] (or some variant in which alpha is < 1.

, much more noticeable as it approaches 0.0), a jit.window will draw

as expected, and when switching to fullscreen, the color xx. xx. xx.

In Max 5, running the same patch, the window will render the

background color as expected, but when made fullscreen, the window

draws itself black, then slowly fills in the background color. When

the alpha is set to the lower bounds, < .10 for example, the color

I would expect this to behave as it did in Max 4.6/Jit1.6.

I have a simple patch that illustrates the example below (obviously

you'll need to run it in max 4.6 & 5 to see the difference).

Thanks for any explanation, fix, or clarification.

Macbook Pro 2Ghz, OSX 10.5.4, ATI Radeon X1600, Max5.0.4/Max 4.6.3 Jitter 1.6.4

I've been noticing *something* different in some of my gl patches as
of late, and I think I found it.  I am not sure if it has been
mentioned so far.

In max Max 4.6/Jit1.6, when using [jit.gl.render @blend_enable 1
@erase_color .xx .xx .xx .01] (or some variant in which alpha is < 1.
, much more noticeable as it approaches 0.0), a jit.window will draw
as expected, and when switching to fullscreen, the color xx. xx. xx.
will present itself as the background.

In Max 5, running the same patch, the window will render the
background color as expected, but when made fullscreen, the window
draws itself black, then slowly fills in the background color.  When
the alpha is set to the lower bounds, < .10 for example, the color
will not fully come up.

I have a simple patch that illustrates the example below (obviously
you'll need to run it in max 4.6 & 5 to see the difference).

differences-in-jit-gl-render-between-1-6-1-7

http://ccrma.stanford.edu/~pkmital/see/jittererasecolor.avi

The first part shows Scott's patch in Max5 and Jitter 1.7 and the

The first part shows Scott's patch in Max5 and Jitter 1.7 and the
second part in Max 4.6.3 Jitter 1.6.3.

i can confirm this, and we're taking a look.

in the meantime, in case you're not already doing this, you can just send erase_color with an alpha of one before going full screen, and erase_color with your desired alpha immediately after.

Anecdotally, and I have no way of making a quantifiable test right

now, it seems when I enter fullscreen mode with OpenGL renders, the

framerate takes a larger hit than it used to. Don't know if it is

related or not, and if there's a way I can verify, I'll pass it along.

On Thu, Aug 14, 2008 at 4:38 AM, Robert Ramirez wrote:

> i can confirm this, and we're taking a look.

> in the meantime, in case you're not already doing this, you can just send erase_color with an alpha of one before going full screen, and erase_color with your desired alpha immediately after.

Anecdotally, and I have no way of making a quantifiable test right
now, it seems when I enter fullscreen mode with OpenGL renders, the
framerate takes a larger hit than it used to.  Don't know if it is
related or not, and if there's a way I can verify, I'll pass it along.

On Thu, Aug 14, 2008 at 4:38 AM, Robert Ramirez  wrote:
>
> i can confirm this, and we're taking a look.
>
> in the meantime, in case you're not already doing this, you can just send erase_color with an alpha of one before going full screen, and erase_color with your desired alpha immediately after.
>
> -rob


The render-erase-fullscreen issue has been addressed for the next

incremental. Thanks again for the report.

The render-erase-fullscreen issue has been addressed for the next
incremental.  Thanks again for the report.
wes


differences in jit.gl.render between 1.6 & 1.7?