Closed gohai closed 9 years ago
Hi @gohai,
do all faces in the Wiggling example you've been running have circular holes in them or only three of them? I'm trying to figure out if you are using the old version or the new version, because I updated this example recently.
Could you please copy and paste this version into both 3.0a11 and 3.0b1 and tell me how fast it is?
Hi @JakubValtar, greetings from Vídeň!
I tried with the version you linked: it's 8 fps on 3.0b1 and 22 fps on 3.0a11. Looks similar visually.
Thanks @gohai :)
(Un)fortunately, both releases run the same on my machine. If you have some time, I'd like to ask you for help.
I identified some changes which could cause the framerate drop and I need you to test which one it was. Could you please build the repo at these commits and report the framerate?
Edit: (sorry, linked to wrong commits, now fixed) 71c688d5585c23ae3b521178b41349d6f98c3253 07e9403289f4fdee710f38c90583c4f269adef19 deb29b3d30127763aebf2b0eb977941837b9bbd0
It's okay if you don't have time for this, but I can't solve it without identifying the commit which caused it (and you seem to be the only one running on Pi).
71c688d5585c23ae3b521178b41349d6f98c3253 already has the low fps with the updated sketch you linked, skipping the other commits.
Since I had to manually make a few changes to the commit to get it to run on the Pi (updated build.xml, new JOGL, two shader hacks), I am now also trying plain a11 with the same modifications on top, to be sure.
I quickly disabled SAVE_SURFACE_TO_PIXELS_HACK in 71c688d5585c23ae3b521178b41349d6f98c3253, and yes, it's that very commit (got 21+ fps).
Is there a way to establish whether this hack is needed on a particular platform? If not, could we potentially disable it on the underpowered Pi? (@codeanticode)
Thanks!
From the looks of https://github.com/processing/processing/issues/3559 it seems like SAVE_SURFACE_TO_PIXELS_HACK
may not even be working as intended. But I think @codeanticode has some ideas about how to fix this. Who's taking this one?
We are working together with @codeanticode on it.
@JakubValtar @codeanticode It'd be fantastic if any new scheme would also have a path for GLES2!
Hey guys, this commit should solve most of the problems.
@gohai could you test if things work as expected and without framerate drop?
@JakubValtar could you test static sketches on integrated intel?
Getting 21 fps with https://github.com/processing/processing/commit/eeb9deccb2601793fd3e19b015f956d9da14954f. Thanks @codeanticode! I'll test tomorrow with the binary driver.
Excellent! Do you see any unintended side effects? Can you run static sketches (no draw() function, or noLoop()) without artifacts (particularly, window turning black after the first frame)?
Will try tomorrow!
On Thu, Aug 13, 2015 at 7:38 PM, codeanticode notifications@github.com wrote:
Excellent! Do you see any unintended side effects? Can you run static sketches (no draw() function, or noLoop()) without artifacts (particularly, window turning black after the first frame)?
— Reply to this email directly or view it on GitHub https://github.com/processing/processing/issues/3561#issuecomment-130773891 .
@codeanticode does not work :(((
Just white screen
public void settings() {
size(200, 200, P2D);
}
public void setup() {
background(255);
fill(255);
rect(10, 10, 80, 80);
}
public void draw() { }
Swaps the image and black
public void settings() {
size(200, 200, P2D);
}
public void setup() {
background(255);
fill(255);
rect(10, 10, 80, 80);
noLoop();
}
public void draw() { }
Displays the image, no flickering
public void settings() {
size(200, 200, P2D);
}
public void setup() {
background(255);
fill(255);
rect(10, 10, 80, 80);
}
public void draw() {
background(255);
fill(255);
rect(10, 10, 80, 80);
}
Swaps the image and default background gray
public void settings() {
size(200, 200, P2D);
}
public void setup() {
background(255);
fill(255);
rect(10, 10, 80, 80);
}
public void draw() {
background(255);
fill(255);
rect(10, 10, 80, 80);
noLoop();
}
Still want me to test anything?
Thanks for the offer!
We don't have anything right now. I'll let you know once we solve the flickering without the hack.
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please close if this is a known.. FPS in the demo halved for me on the Raspberry Pi using the new Mesa driver. @JakubValtar?