This is RPG Maker MV v.1.6.3.
It turns black when the vertical height is too long.
It’s a disaster when the creators’ names are displayed in the end credits.
1 Like
I am also on RPGmaker 1.6.3. I have never seen this bug before and it’s unlikely it’s a bug from the base software. Can you show what plugin is used for this, and how this event is coded?
The maximum texture size varies significantly depending on whether you are using a PC or a smartphone.
As a result, it cannot always be confirmed, which was a major issue.
While this was fixed in MZ version 1.7.0, it remains unresolved in MV. Despite the cause and solution being clear, MV is simply being ignored.
Okay, I think I understand my confusion. The translator calls the feature “Article Scroll” but it’s called “Show Scrolling Text” in the English version. I am able to reproduce the bug with a script that attempts a 500-line scrolling text.
EDIT: Additionally, I was able to find that 456-lines is the minimum that reproduces the bug that’s roughly a message box 16416 pixels tall which is a little larger than 2^14
4 Likes
What did MZ do with this? Does it split the texture in pieces if it finds that it will be too tall?
I can see it splitting them at some arbitrary size, like up to 2048, and drawing them over multiple frames in multiple textures, you don’t need to display all of them at once anyway.
Just split your message into seamless scrolling text. As it’s too long and hits MV limit
I just looked. MZ solves this by setting a maximum texture height of 2048 pixels. When the message scrolls past a maximum, it redraws the entire window and moves the contents bitmap back down. Their solution does not use multiple textures.
It’s a very clunky solution because it will waste a lot of processing power drawing content outside the texture, but this unfortunately has to be the solution because the engine will not have a way of knowing which part of the message to draw. Any optimization will introduce technical limitations and needs to be customized for the dev
2 Likes
Previously, I encountered the worst-case scenario where a game developer’s test run worked perfectly, but a specific player experienced a bug.
Although a countermeasure plugin has already been distributed, given that such phenomena occur, it is almost ineffective.
To avoid this tragedy, an update to the core script is required.
Sometimes you have to evaluate if the change is worth the hassle, depending on how frequently it happens. If it’s an issue too specific you’ll have problems to reproduce the problem, which is necessary to debug and fix.
Of course if just an update solves it that’s much better. I’d do that anyway, as long as the update doesn’t break anything else, like a plugin that only worked with that previous version.
Did they deliberately choose to do nothing after careful consideration, or were they simply unable to act because they were unaware of the issue itself?
I created this article to seek clarification from the official RPG Maker team.
We are now waiting for their official response.
Yeah personally I don’t have any information regarding their decision around this problem, so all we can do is wait for an official response.
Thank you all for the detailed report and for helping isolate the issue.
We will share this matter with the development team, including the reproduction conditions and the countermeasures taken.
That said, regarding whether to apply a similar fix to the core scripts of MV, we need to confirm the scope of impact, so we cannot make any commitments at this time.
We are deeply grateful for your valuable report and for the analysis provided by the community.
4 Likes