Printable View
Hi,
I know this is a beta, but I'm interested by the fact that my game seems to run slower in HWA than in normal mode.
It isn't because of the graphics; it is because of the code. I thought HWA would place the graphical load on the GPU therefore freeing up a fairly significant amount of time for the CPU to handle events. Does anyone know what causes this? It's really weird.
Someone else sent me an application that is slower in HWA mode but I haven't profiled it yet. Could you send me your game too? This would help me a lot. :)
This happened to me also. I found that if I clicked off the game so it didn't have focus and then refocused the game it ran much faster... might just be me though!
Ah yes, I haven't yet tested your application either. I wonder what could cause this...
I've profiled the other application, the slow down (or at last a part of the slow down) was caused by a quick backdrop object in ellipse mode. This one is not yet optimized, as well as the gradient quick backdrops. Gradient quick backdrops will be optimized soon, I don't know yet when ellipses will be optimized.
I take it that isn't my one Yves? I can't remember adding a quick backdrop in ellipse mode...
No, it's another one.
The ellipse mode could be done through pixel shaders, maybe that could be the better optimization Yves, isn't it? But this pixel shader should be done in 1.0.
Is the quickbackdrop in tile mode is already optimized, because I've found it a bit too slow. Don't know why...
Hmm... it should be automatically optimized... I'll take a look.
For a quickbackdrop in tile mode, is a texture is created from the size of the object or is the coordinates of the existing texture are recomputed to let it automatically tiled ?
Steven, just for info, your application was slow because I forgot to include the optimized background system box in the installer... will be fixed in the next version. :) I was unable to reproduce the speed difference when the application has not the focus though.
:D thanks Yves
Must just be my computer on the other part! I'll see if it does it again after the update
Something of the same kind happened to me : when the Task Manager was over the application (well the TM is always on the top of everything), the application used to run quicker. But I realized that the application was quicker just because it had not to render the area covered by the Window of the TM => less pixels to render = faster.Quote:
I was unable to reproduce the speed difference when the application has not the focus though
So maybe when a window covers an accelerated area there is less computation from the render engine.
my game ran much slower until I disabled all my physics loops for the enemy qualifier (Which has many copies of events to test for collisions after every pixel of movement, since using fastloops slowed it down before).
I don't know why coding would make it slower for hardware acceleration. I do use a background system box though, that you mentioned above. It also crashes and the collisions don't work so...
The collisions in HWA mode seems to be slower in HWA. Wait for this to be optimized and fully functional. ;)
This is probably one reason why my game runs more slowly. I'll try and get my game sent to you soon Yves.