-
Notifications
You must be signed in to change notification settings - Fork 432
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reconsider the default value of FlxCamera.pixelPerfectRender on native targets #1065
Comments
By my observations, the best configuration for low-res (pixel) games are: (HaxeFlixel default)
For high-res games, this works much better:
|
Are these typically always used in tandem? |
Managing this stuff with a global camera flag is fine, as long as it's easy to do, and well-documented for new users to select their preferences based on their game type, as Andrei proposed. |
I'm not sure fixedTimestep is really connected to high res games. It's more related to whether or not the game depends on physics and / or has to be deterministic. Closing this, as nobody really seemed in favor of changing the current default. |
I am really in favor to change the current default. Recent forum post: https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/haxeflixel/Gcw-oxL09T8/jgm5GRaofAIJ Anyone developing anything serious will change these values, modern game engines uses the same:
@Gama11 To grow the user base, this project should be more appealing for commercial development (high-res), not for "game jam pixels". |
I am also in favor of changing pixel perfect rendering value. Especially for targets that use tilesheet rendering. |
Why not set a "FlxG.render = PixelArt"? This way all the settings are pre(-ish) configured. |
@AndreiRegiani That's simply not true, a variable timestep doesn't always give better results. If you rely on deterministic phyiscs, a fixed timestep is usually preferable. I don't see how this is related to the art style. Article on timesteps. Also... "Anyone developing anything serious"? It's not possible to use pixel art for "serious" development then? :P @gamedevsam There's no "especially" here, not using |
|
@Gama11: I understand, so why not make pixelPerfectRender false by default for tilesheet rendering and true for blitting? I'm not a fan of changing the timestep default. |
@Gama11 It's not related to the art style, by "pixel art" I meant low-resolution, example: 256 x 240 with zoom (2x), in this case antialiasing must be off and fixedTimestep false, this is the typical Flixel game. |
@JoeCreates Since |
Currently, it's true by default on all targets for the sake of consistency. However, in most cases,
pixelPerfectRender == false
yields better (smoother) results on native targets at practically no performance loss. On flash however, true is necessary as a default setting for the added performance (although it seems surprisingly usable to have it set to false in Mode).I'm thinking it might make sense to make the default depend on the render mode. Things can't be totally consistent cross-platform, sometimes it makes sense to choose the best setting based on the target - see the special logic in
FlxButton
for no highlight frames + swiping on mobile.pixelPerfectRender:Bool = #if FLX_RENDER_TILE false #else true #end
For people who want to use pixel perfect rendering on native (pixel-art games etc), this would still be easy to accomplish due to the new global camera flag.
cc @gamedevsam @PaulGene @cwkx @schonstal
The text was updated successfully, but these errors were encountered: