Just wanted to add my two cents here as well.
I am using MZ for about half a year now, constantly checking these forums. While I'm pretty sure that one could say the thread author got a bit 'angry', I can totally see why that is.
I am using this line of software for over 10 years now and I am actually astonished how the polishing has decreased with the last iteration (although I would bet this 'change' came already along with the remade build for MV). It is also a bit perplexing to me that, as
@RHachicho mentioned, nobody really seems to notice these kind of things.
There are actually a lot of minor nuisances I'd noticed early when using the program and I'm wondering how nobody else seems to care - or if for some reason my system is the only one causing them. I did intend to make a own thread about them and can still do if desired, but after seeing a lot of these threads popping up this month, I think that it does fit in here to as a short summary to justify my point.
- Dark Mode starting to flicker randomly when using the interface or stopping to move the mouse
- Scroll bars in every window getting a bugged starting point, not selecting the right item and jumping when refreshing itself after moving
- Above problem causing entire parts of contents to be visually missing before the refresh
- Some interfaces not remembering the selected category or item after closing (Ressource Manager)
- Software always launching in windowed full screen and jittering when trying to maximize
- Textboxes (for example in plugin parameters) not refreshing their text marker location, so every second text box the letters will not be auto-marked etc.
- No multiple selection of items with mouse, had to guess that you need to hold shift for that
- Ressource Manager not having confirmation prompts (Combine that with the scroll bar issue)
- MV Animation page still having one or two optical bugs like the maximum frames (also, why is there no selectable background for the MV mode, I am pretty sure the old iterations had that)
These are just the things I still had fresh in mind, I'm certain there are a few more. Now again, should have their own topic, but what I'm referring here to is that I do not remember Ace having such lack of polishing. Say about this software and the probably smaller development team what you will, but for what it was, I could always proudly say that the software was stable and polished in what it tried to accomplish.
For some reason, this just isn't the case anymore and it perplexes me that apparently either no one else is having these issues or just doesn't care.
I see how these things could be nit-picking if one simply uses the software more casually. And that's totally fine. But the software promises a working environment for more dedicated projects, as well. And the above mentioned problems make it really, really tiring to work with the program over a long period of time - not even on a single day, but over weeks and months.
All of this brings us back to the most problematic issue - the crashes.
I am aware that one needs very detailed information to deal with something like this. But I get the impression that, again, up until this month, apparently nobody noticed. Is it really that rare of a problem, or something that these users are doing wrong? Every thread basically comes to another conclusion, leaving this error in the program - which again is... really not a good working environment.
So, instead of just ranting, here is my information about this issue:
This bug occurs when trying to load up lists of files that have been imported. This is the general gist, anyway, as more and more iterations of this seem to come up.
At first it happened with the picture event command when selecting a file, now someone reported it also happens with the opening of tileset files. That I can indeed confirm, as it happened to me as soon as I finally came around to adding these files to my database. Probably took about 5 database entries (so about 20 times opening the file list) to get the software crashing.
I would bet some money that one could reproduce this even with opening the files for characters and so on, but this is not yet confirmed.
Now, about these files. The common answer is: Your files have been named wrong.
This is the file system I use for every single file in my project: XX_XX_00_(XX_XX).file
Please explain to me what could be wrong with that. After reading into these forums I even got back to my files and removed every space before brackets as this is apparently a no-go.
So what's left are the brackets - are they the problem? If so, gotcha, I'll remove them and try again.
The thing is though, my picture and tileset folders do not use them. And it still crashes.
The only thing I can assume here is, if anything particular is responsible, it is the amount of files. I indeed have over 100 tileset and 400 picture files. However, if you are telling me this software can't handle this, we are back to the 'more dedicated projects' issue.
The other thing mentioned were file paths. I did not change the file path for creating projects. It's still inside my documents/rmmz folder. I also changed the project to not have spaces in the name, either.
If you still have any solutions left for it being a user generated problem, I am honestly all ears. I actually do not care if I or someone else needs to fix the problem, as long as there is a solution.
Because the problem is that it also does not happen after a long amount of time, necessarily. Saving the project, as some mention from time to time, also does not fix this entirely. It sometimes seems like prolonging the issue, but it also tends to crash directly afterwards, as well. Sometimes after 30 minutes, sometimes after 10. Sometimes after 30 hours, but only if I'd only work on things not related to file-list opening. Yes, I left the program open for days or a whole week and it never crashed one single time as long as I did not open these lists. If I do, though, for adding maybe 20 picture commands to an event, I need to save between at least every 5-8, as it will very probably crash in between.
This is what makes this so annoying - it doesn't happen after hours, where one could accept it, save his work and refresh the program by restarting it. It happens within half an hour and always either removes your progress or forces you to restart the program every 5 list entries or 10 work minutes. Which I am pretty sure is not that healthy for your project either, constantly relaunching the software like that.
If desired, I can also add some details about my computer if it helps any - just ask. In general, it is however a freshly bought pc with enough hardware to run the games, and especially the software. I even re-installed windows two weeks ago, but the problem existed back then as it does now. There is also not much installed besides the software and some minor other ones. Basically, this PC should not have any issues running the program from a software (except the OS may being an issue), nor from a hardware capability standpoint. So the only thing could be the very specific setup in its entirety, like the CPU or GPU...or the SSD. Again, I can share my specs, but I am pretty sure this problem shouldn't exactly stem from that.
So in the end, if it's not an user issue, it has to be related to something the software itself can't handle in this exact moment, for whatever reason. Seeing as it can handle it a couple times before crashing, I would assume it is either memory related or something in the routine to call these lists is causing a problem the software, maybe under certain situations (like what you opened before or what it had to process beforehand) cannot handle.
Sorry for the long post, I am also not sure how much it helps. I just wanted to make clear that this is indeed an issue - and I would actually be interested in why it is that either no one notices it or just doesn't have it. Or them, if you add the stuff mentioned at the beginning.
I do indeed love this line of software - otherwise I wouldn't use it. But as mentioned, the lack of polish certainly has increased. There is a fine line between what is acceptable, especially if you know 'the whole package' of the RPG Maker world, and what is just having a decline in quality. At the very least, it would be great if one would be able to trust the software he is working with, as it is quite a long relationship you're going to have with it.
[Edit]: Seems the new update 1.5 indeed addressed the crash issue, at least in theory. Hopefully it also prevents the cause mentioned in here and it doesn't have multiple ones. Would be great to see it gone completely.