Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

WebGL Renderer resolution halves on refresh #3

Closed
LawrieCape opened this issue Mar 7, 2013 · 4 comments
Closed

WebGL Renderer resolution halves on refresh #3

LawrieCape opened this issue Mar 7, 2013 · 4 comments

Comments

@LawrieCape
Copy link

I'm trying out a Pixi WebGL demo, based on one of the Photon Storm ones. I'm running it in Chrome 25.0.1364.152 through Xampp local server.

When I'm updating the JavaScript, saving & refreshing, every so often the renderer seems to get confused and drops the resolution of all Sprites by about half. Upon refreshing again, it does it again until all assets are completely invisible. Booting the page up in an incognito window seems to solve it, but I thought I'd mention it.
@GoodBoyDigital
Copy link
Member

Interesting.. If it works in an incognito window it sounds like it may be a caching issue?

@LawrieCape
Copy link
Author

Yeah, I think so. It's not really a problem, it's just happened on 2 machines for me and I thought it was a bit odd :)

@arcanis
Copy link

arcanis commented Mar 22, 2013

Are you using Chrome ?* There is an issue about this (the problem should be resolved in master, so in a few weeks / months on the standard build).

*Woops, didn't see. You are :)

englercj pushed a commit that referenced this issue Apr 2, 2015
@schervenkov
Merge pull request #3 from chalgoman/patch-3
69a2b2d 
Added lineHeight parameter
bigtimebuddy pushed a commit that referenced this issue Feb 28, 2017
@ivanpopelyshev @bigtimebuddy
default value for settings.SCALE_MODE was not respected in loader (#3… (
f732b00 
#3797)

* default value for settings.SCALE_MODE was not respected in loader (#3787)

* how did we miss that?
@lock
Copy link

lock bot commented Feb 27, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Feb 27, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@arcanis @GoodBoyDigital @LawrieCape