Interesting. From 480p to 600p, Flare doesn't scale its rendering, but above 600p it will start scaling up. When scaling up from such a low resolution, there's no doubt that things will get a bit blurry. For our graphic style, this generally doesn't look too bad. It's the text that stands out the most. It would be nice if we could do something like Unity and have the text render at the native resolution (would be really good for Asian languages with complex glyphs).
Thanks for making this. A word of advice for recording stuff in the future: you should make the window fill the whole video area. You can set a specific window size in ~/.config/flare/settings.txt (I use 1280x720 when recording). Then in OBS, right-click on the video source and select "Transform->Center to screen".
YES! The expansion I'm going to be working on has a greater focus on more populated areas, so buildings are a must-have. Not to mention that these look great on their own.
As a side-note, Does anyone still remember Wandercall (or whatever it's called)? I'm still wait for it, because it's the most ambitious promise on taking FLARE Engine to its limits. Whether that ambition will come to fruition in my lifetime or not, I just want to see some progress in it.
Wandercall is Clint's personal project, so progress has been limited by how much free time he has. There's this Github repo, but it's been inactive for several months.
Thanks for the kind words. I tihnk the best docs we have now is to look at the existing flare-game data files in combination with referring to the Attribute Reference on the wiki:
As of 1.05, you can use multiple images in tileset definitions. Example:
[tileset]
img=image1.png
tile=1,...
[tileset]
img=image2.png
tile=2,...
There's no way to tag specific tiles, but you can add comment lines with '#' to help keep track of which tiles are which. flare-game definitions were like that, but the comments got scrapped after I ran them through the sprite packing program.
Flare mods do not have the ability to write data or run external programs.
That sounds like a good solution. If a mod contains a keybindings definition, we can then look for a saved keybindings definition under the current save prefix, e.g. "saves/empyrean/keybindings.txt".
Not possible at the moment. I'm okay with adding it, but I want to make sure that a mod can't clobber a user's personal keybinds. Especially for users with different keyboard layouts. Maybe we could prompt the user that a mod has some default keybinds and ask if they want to use them.
Interesting. From 480p to 600p, Flare doesn't scale its rendering, but above 600p it will start scaling up. When scaling up from such a low resolution, there's no doubt that things will get a bit blurry. For our graphic style, this generally doesn't look too bad. It's the text that stands out the most. It would be nice if we could do something like Unity and have the text render at the native resolution (would be really good for Asian languages with complex glyphs).
Thanks for making this. A word of advice for recording stuff in the future: you should make the window fill the whole video area. You can set a specific window size in ~/.config/flare/settings.txt (I use 1280x720 when recording). Then in OBS, right-click on the video source and select "Transform->Center to screen".
YES! The expansion I'm going to be working on has a greater focus on more populated areas, so buildings are a must-have. Not to mention that these look great on their own.
I might end up using those crystals as well.
Wandercall is Clint's personal project, so progress has been limited by how much free time he has. There's this Github repo, but it's been inactive for several months.
Thanks for the kind words. I tihnk the best docs we have now is to look at the existing flare-game data files in combination with referring to the Attribute Reference on the wiki:
As of 1.05, you can use multiple images in tileset definitions. Example:
[tileset]
img=image1.png
tile=1,...
[tileset]
img=image2.png
tile=2,...
There's no way to tag specific tiles, but you can add comment lines with '#' to help keep track of which tiles are which. flare-game definitions were like that, but the comments got scrapped after I ran them through the sprite packing program.
Flare mods do not have the ability to write data or run external programs.
1.05 is up now: http://flarerpg.org/index.php/2018/04/30/flare-1-05/
I'm aiming for some time this week. I'm working on some developer mode improvements right now, and I might try to squeeze in #1626 after that.
Implemented (look for it soon in 1.05): https://github.com/clintbellanger/flare-engine/commit/3755f4c470c8bbae45...
Keybind loading now goes like this:
The syntax of "engine/default_keybindings.txt" permits defining only the actions you wish to change. Here's an example:
[default]
bar1=Q,Q,joy_0
bar7=mouse_1,mouse_1,-1
character=C,C,axis_3-
inventory=I,I,axis_3+
That sounds like a good solution. If a mod contains a keybindings definition, we can then look for a saved keybindings definition under the current save prefix, e.g. "saves/empyrean/keybindings.txt".
Not possible at the moment. I'm okay with adding it, but I want to make sure that a mod can't clobber a user's personal keybinds. Especially for users with different keyboard layouts. Maybe we could prompt the user that a mod has some default keybinds and ask if they want to use them.
Anyway, I've opened an issue for this on Github, so you can watch there for any developments.
Pages