I have two more bugs (one i already stated, but now i see what's going on)
When using -benchmark the window opens and the cube instantly jumps from side to side erasing some (still black) pixels on the bottom (see below).
This is by far worse when using the normal double-click - Window opens, black - Sound starts, cube zooms in from behind, erasing the black background while moving around the window and through that slowly revealing the checkered background this way, looks wrong (Actually i get that sometimes with SDL ports too)
People are dying. Entire ecosystems are collapsing. We are in the beginning of a mass extinction. And all you can talk about is money and fairytales of eternal economic growth. How dare you! – Greta Thunberg
- Sound starts, cube zooms in from behind, erasing the black background while moving around the window and through that slowly revealing the checkered background this way, looks wrong (Actually i get that sometimes with SDL ports too)
Hmm, very strange. Is possible that you can pause by pressing p and take a screenshot of the bugs. As it's easier to confirm if it's a bug or "feature" or else and how it actually looks...
That was the non synced version. Rendering frame-rate seems right I think, compared to my Sam440ep-flex 800MHz with Radeon 9250, where I get about 52.9 FPS and 609 RPFS in Windowed mode.
2) When the cube hits the lower corner of both sides the background checkmark gets wrongly filled on a hit
Ok, now I see what you mean I think. When the cube hits the floor the checkered floor may seem little weird just after the impact, but that seems to just be an illusion, as I can't see anything abnormal when stepping each frame by frame.
The "lower corner" I can't reproduce either, sorry.
EDIT: Ahaa, there might be a situation when hitting the floor/wall that may cause a trail from the cube for just a frame or so. Not sure if that actually is the case, but that might be the thing you see. I will investigate and see if I can expose it till the next update or so (at least after the one that is in the works now), thanks.
*** BoingCube benchmark *** Name: -benchmark10 (Counts iterations per ten seconds.) Version: 1.20 (20151129) Mode: Windowed NON-synced Iterations: 1454 frames Duration: 10004 ms (10.004 seconds) Rendering time: 455 ms (0.455 seconds) [lower is better] Frame rate: 145.3418632547 FPS (frames/second) Result: 3195.6043956044 RFPS (rendering frame-rate) [higher is better]
BoingCube -benchmark -gofullscreen
*** BoingCube benchmark *** Name: -benchmark10 (Counts iterations per ten seconds.) Version: 1.20 (20151129) Mode: Fullscreen NON-synced Iterations: 1455 frames Duration: 10009 ms (10.009 seconds) Rendering time: 564 ms (0.564 seconds) [lower is better] Frame rate: 145.36916774903 FPS (frames/second) Result: 2579.7872340426 RFPS (rendering frame-rate) [higher is better]
Bugs:
- The trailing is still there BUT it only happens if you start BoingCube in normal or benchmark, close the window and start the non-normal version again. The Window will come up completely black and background will be revelaed as the cube moves over it The Screen will be mostly erased, just not the bottom, there, it will still reveal parts of the black background on hit.
Screenshot
Seems like the 7850 squeezes another 100 frames compared to the 7750 (Gotta get me a better gfx board then after all) Although cpu goes 100%, so maybe there's a bottleneck too?
People are dying. Entire ecosystems are collapsing. We are in the beginning of a mass extinction. And all you can talk about is money and fairytales of eternal economic growth. How dare you! – Greta Thunberg
Thank you very much for the screenshot Yeah, looks broken...
Quote:
the non-normal version
What do you mean with the "non-normal version", do you mean BoingCube in fullscreen-mode?
Quote:
tThe trailing is still there BUT it only happens if you start BoingCube in normal or benchmark, close the window and start the non-normal version again.
So if you start BoingCube normal or benchmark, it looks ok?
And then if you start BoingCube again, the "non-normal-version", it looks broken like in the screenshot you posted?
So if you start BoingCube normal or benchmark, it looks ok?
And then if you start BoingCube again, the "non-normal-version", it looks broken like in the screenshot you posted?
I really need to phrase my sentences so that everyone understands
To reproduce:: 1) Double-click BoingCube 2) Close the window repeat from #1 (Every once in a while - every three times for me, roughly - the window will open up, showing the checkered background. Instantly when the boingcube appears the background will be blackened and the cube will draw it's trails through it)
All the other appearances are more or less random, but once it happened i can make it happen again by opening/closing boingcube for a few more times.
Hope that helps
People are dying. Entire ecosystems are collapsing. We are in the beginning of a mass extinction. And all you can talk about is money and fairytales of eternal economic growth. How dare you! – Greta Thunberg