[r100]ridiculous scaling after going back

Hi Ash,

New version looks cool. I was trying my website menu on r100 to check for visual changes.

Although it's visually the same (which is great) I found a quite weird but.

When I click on one of the link and go back to the page with the back button of the browser, the page gets dramatically scaled (didn't notice it was scaling until I mousovered some blurry pixels)

Here you can try it

https://dl.dropbox.com/u/23551572/C2-Games/menu/index.html

The one exported with r99 is here

http://yanngranjon.com

I'm in fullscreen crop mode

and this bug only appears in chrome (didn't test ie or safari)

In firefox though, it's weird when I go back the layout appear in the same state as when I clicked on it. It doesn't seem to restart the layout. (same with r99 and r100)

tell me if you need the capx

That's weird. I tried it but I'm not finding any issues with it at all, seems to load the same way as it starts off on.

I tried it, and it happened to me. Quite weird.

i.imgur.com/ZXu6a.png

andreyin

yep thanks for the screen that's exactly the bug (:

happened to me too. Interesting. On a side note, the words look really cool without the text in front (just the particles spelling them out)

Looks the same for me.

It looks awesome btw!

Sounds like a chrome bug.

I had a similar scaling bug when changing the size of the window in scale mode, the layout jumped to the bottom right hand corner.

johnnysix.net/games/FollowTheLeader01k/

Sorry but the R100 do not run well...

Like the systeme "pick all" condition, doesn't include all instance.

It doesn't take the instance created during the run::::

Yeah, it's a chrome bug.

Works fine on IE 9

Happens in Firefox too. That's very strange, how would going back in the browser affect your game? Does it happen in preview as well?

I don't think it's a browser bug, I think it's a problem with the WebGL renderer in Construct 2. If you look in Chrome's console this error comes up:

'uniformMatrix4fv: location is not from current program'

I found why this error was happening and fixed it for the next build - since it correlates with the problem happening, I think that means this issue should be fixed in the next build. Let me know when r101 is out if it's better.

Should be fixed in r101, can anyone confirm?

Ashley

I confirm, can't reproduce with r101 (: