Pixel object crashes my application

[vertigoelectric]

The save system for my game includes saving a thumbnail screenshot of the visible area of the frame where the player saved his progress. It has been working perfectly.

Earlier, I made a comment about my game being laggy and someone suggested HWA. I tried it out, and my game ran BEAUTIFULLY! Absolutely perfect... except for one thing: Now my screen capturing doesn't work.

I've asked about this in the Gwerdy chat, and someone walked me through how to use the Pixel Object along with the Overlay Redux object in order to save the thumbnail and basically achieve the same effect as the Screen Capture object. Though it was a little more work, I gave it a try. However, it wasn't working. I don't know what was going wrong, but the game was crashing whenever I tried to save.

I narrowed it down to being a problem with the Pixel Object. At first, I thought saving pixels in too many fastloops at once was the problem, but even if I set it to just 1 loop, it would crash. If I set it to 0 loops, it would not crash, but of course it wouldn't be using the Pixel Object then, either.

I will try re-downloading the Pixel Object and attempt this again. Perhaps I got a buggy one or something.

If anyone has heard of the Pixel Object crashing other apps, or if someone has a suggestion on another way I can save a thumbnail image of the current game window, I would really appreciate the tips.

Thanks.

[maVado]

That code on Gwerdy worked for me, the only issue was that you do not put "Always" and "On loop" on one event and that on start of frame the objects are not drawn yet, so a blank screen will be saved, wait at least for 1 fps update then it should work. No chrashes for me.

[vertigoelectric]

That code on Gwerdy worked for me, the only issue was that you do not put "Always" and "On loop" on one event and that on start of frame the objects are not drawn yet, so a blank screen will be saved, wait at least for 1 fps update then it should work. No chrashes for me.

Well it crashes my app every time, and only if I use the Pixel Object. I don't have "Always" and "On Loop" together.

Oh, and I just remembered. Any actions calling the Pixel Object (through an expression) cause the app to crash. I even omitted the use of Fast Loops altogether and tested just trying to set a single pixel to the Overlay using the Pixel Object. One event, one action, one pixel. Still crashed.

[LB]

put "Always" and "On loop" on one event

How does that solve anything!? That doesn't make sense! Can't you just use "Run this event once: Start Loop" ?

[vertigoelectric]

LB, putting "Always" and "On Loop" on one event isn't even an issue here. Please try to stay with the matter at hand so that my problem can get fixed. Thanks.

[MechatheSlag]

are you using hwa? It crashes in hwa

[Ran_TH]

are you using hwa? It crashes in hwa

Earlier, I made a comment about my game being laggy and someone suggested HWA. I tried it out, and my game ran BEAUTIFULLY! Absolutely perfect... except for one thing: Now my screen capturing doesn't work.

Yes, he is.

[Atom]

Does anyone know when the extensions not currently working will be converted to HWA, will that happen with the upcoming betas?

I know that overlay redux won't get ported (but it's one of the most useful) and possibly others due to clickteam not having the source code. I hope it's only a few that are like this and not lots.