I didn’t mean that, but the issues with the .NET upgrade.
Is everything completely sorted out there?
As already said, any regressions found thus far were fixed, lol.
Oh, I actually missed that, my bad.
Okay, I’m really sorry that I’m basically just taking up this entire thread right now, but I just launched it for the first time, and unlike the regular FE Builder, I can’t adjust the window size and the text also looks like this:
Anyone know a way to fix this?
I started a new discussion for your question: Incomplete text display · laqieer/FEBuilderGBA · Discussion #23
2 Likes
Oh yeah, I should also mention that with changing window size, I can make it take up the entire screen and also drag the horizontal length just fine, but I can’t change any of the vertical height, it’s just stuck to taking up all of the screen height and I can’t change it.
That’s…NOT a usual issue? Even in original builder, I already had the issue with the vertical resizing being broken in random patches, so I didn’t note it down as a specific regression.
Ha, you’re right, it is broken, in the sense that I can’t undo it, definitely wasn’t always this way.
But in this forked version, it always starts at maximum vertical height already and just has to stay that way.
In vanilla FEBuilder, I can at least reset it by closing the application again, here that doesn’t do anything because the default height is already max.
Same issue for me, on two different PCs. It’s specifically the map list in the main menu that is affected. I checked other menus and I don’t see regressions there.
However, the spacing in unit descriptions seems to have been changed, which leads to display issues. Examples from Sacred Stones:
Puzzling regressions all in all.
That is actually a scroll, not a cut-off. To see what I mean, keep leftclick pressed to select the text in the preview and move the mouse up and down.
It is a scroll, yes, but it wasn’t like that before. The altered spacing leads to a lot more descriptions requiring scrolling.
Actually, I found out that the cause of the text not displaying corrected seems to be a Windows update that messed with resolution of apps, specifically DPI.
But from what I understand, your only options are to have it displayed incorrectly at a high resolution, or correct at a blurry resolution.
At least those have been my options so far from messing around with the compatibility settings of the exe file.
I would hope this is something that can be fixed on the other end, so that it always displays correctly.
And I also have a question about the skill system.
The new C-SkillSystem is far from being as intuitive as the older one with its integrated editors, and I don’t think I want or need to learn about this one for the rather small project I’m working on.
So I wanted to ask if the last regular SkillSystem update, 20220703, is considered to be stable enough and free without bugs, to the point that I should be able to use it without worrying.
And if it’s maybe the best idea to apply the patch as early as possible, to make sure any other patches I might want to apply afterwards are properly filtered out and blocked if they aren’t compatible with the skill system.
Sorry to bother you, hope it’s okay to single you out specifically, but since you did help before and seem relatively active here, I thought you might be able to answer my question above on the skill system.
I’m not really particularly active for years(I am mostly present recently because I just wanted to give the communities a solid by translating stuff to german and advancing hacking of “unused versions” like EU and the prototypes as far as I can with my inability to really understand and write any meaningful code, lmao), so the basic answer is “I don’t quite know”.
From what I remember, it was “stable enough”, but contained a few annoying bugs. The source skillsystem has itself always been a bit buggy too because it is just such a big project containing many interlocking secondary patches and bits of functionality and thus it is not surprising that a build 3 years out of date, thus lacking many critical fixes, is showing its age. And due to the major complexity of adapting it to Builder, it is uncertain if it can ever be updated
And I >think< all the patches that are incompatible are actually blocked, but I cannot be 100% sure because that list is insanely big, so it would be a pain to double-check.
Tldr: Go ahead if you want to, it is entirely usable and has been used in many projects before, but it DOES come with the inherit risk of something being broken and you having to account for it with there being little anyone can really do due to complexity. Just be careful and ready to make compromises.
Well, my project is just gonna be a small 5 chapter long thing, so I’d assume there won’t be many things it can interfere with.
Still, do you happen to know like anywhere I could look where some of these bugs might be documented?
Do I just scroll through the infinitely long original FEBuilder thread?
You could hit up the github and check for any commits past that date to see what issues the old one has.
Some things I’ve seen:
Problem is that it’s hard to say which ones were already present in the last FEBuilder version and which bugs were added later, but thanks!
So far, I don’t think anything is a big deal for me personally though.
So yeah, if the general consensus is that it’s mostly stable and isn’t gonna introduce many new issues to a ROM, then I guess it’s fine.