05-31-2020, 04:23 PM
Hi Jaume!
Nice integration, glad to see you have it already working :-)
I don't think it's annoying at all, however my personal opinion doesn't matter as this is an aesthetic choice related to game design. It's best to beta-test the game ang get feedback from testers.
One question: the effect of the background "jumping" over the top part of the window is intentional or a bug of the implementation of the glitch? It feels a bit strange because the glitch gets contained by the other three sides of the window, feels somewhat broken. Just an opinion.
Regarding thicker lines, they can be achieved but not just by tweaking a parameter, the algorithm must be modified a bit. In make_glitch_map(), when determining that a line must be glitched, following n lines must be loaded with the same value, and c must be skipped by the same amount. For example for 3 pixels thick lines:
Keep the good work!
Nice integration, glad to see you have it already working :-)
I don't think it's annoying at all, however my personal opinion doesn't matter as this is an aesthetic choice related to game design. It's best to beta-test the game ang get feedback from testers.
One question: the effect of the background "jumping" over the top part of the window is intentional or a bug of the implementation of the glitch? It feels a bit strange because the glitch gets contained by the other three sides of the window, feels somewhat broken. Just an opinion.
Regarding thicker lines, they can be achieved but not just by tweaking a parameter, the algorithm must be modified a bit. In make_glitch_map(), when determining that a line must be glitched, following n lines must be loaded with the same value, and c must be skipped by the same amount. For example for 3 pixels thick lines:
Code:
val = rand() % 1000;
if (val < HGLITCH_AMOUNT)
{
glitch_map[c] = -HGLITCH_STRENGTH;
glitch_map[++c] = -HGLITCH_STRENGTH;
glitch_map[++c] = -HGLITCH_STRENGTH;
}