Forums > Jitter

shared_context issue

October 22, 2009 | 10:14 am


Could someone explain why the second render is blured?

– Pasted Max Patch, click to expand. –
October 22, 2009 | 5:47 pm

Hi Kyred,

Two things:

1. Videoplane was set to transform_reset 0, I set it to 1.

2. dim was 256×256, should match the dim of the original context’s window (320×240). Now there’s no blurring. Hope that helps.


– Pasted Max Patch, click to expand. –
October 23, 2009 | 4:16 pm

Hi Zachary,

The problem with transform_reset 1 is we can’t use camera $1 $2 $3, which is the goal of the patch.

About the texture dimension, it seems that the [] targeted by the "copy_texture" message, takes the native dimension from the context which copies its framebuffer to.

Look by yourself: there is no @dim in the texture, but the dims are 320*240*1. (I did not freeze the @)

I don’t understand why this blur? This is not a dimension issue as what I understand.

However the circles are crenate, and with @fsaa 1 I get more a high res polygon than a real circle.

Any idea?

– Pasted Max Patch, click to expand. –
October 23, 2009 | 4:27 pm

Hi Kyred,

Yes, you’re right about the texture taking the dimension of the copied context’s window. Ok, move your camera to 0. 0. 2.42 in context B and see if you notice any blurring.

You’re zooming in on a videoplane with a 320×240 dim texture. If the borders of the videoplane go beyond the 320×240 window, you get pixelation, as a subset of the 320×240 pixels are being stretched across the 320×240 window. It’s essentially the same behavior as what happens in 2D matrix land.


October 23, 2009 | 8:02 pm

About the 2.42 I don’t really see where from are you taking this value.
But it works fine but … could you explain more?

– Pasted Max Patch, click to expand. –
Viewing 5 posts - 1 through 5 (of 5 total)