RPG Maker Forums

After a bit of debugging, I started thinking the issue would be a bug in PIXI. That worried me, because if I were right fixing it would be quite complicated. But after digging deeper I found out that it was related to PIXI, but was being caused by my own code, and then I started to see the solution.

So, to draw the text in a window we first have to create the contents object, and for that we have to determine its dimensions (width and height). Without wordwrap that's an easy task. Width is the same as the window (minus padding) and height can be calculated with an Window_Base function called calcTextHeight. But when using wordwrap, the real text height is determined at the text drawing phase, as each character is draw individually to check whether the whole word will fit in the available width or not.

Artificially incrementing the height variable works (like multiplying it by a high number, like 10 or 100), but you risk creating a contents object so big that it exceeds the WebGL maximum allowed memory (which value depends on your GPU). The result is a black square where the text should be when you try to load the text.

I couldn't find a way to automatically fix that for both wordwrap and non-wordwrap users alike, so I included a parameter to enable or disable the fix, which consists on trying to "guess" the text height beforehand. To do that, the code counts the number of characters on the text and divide by the window width, resulting in a rough estimate to how many lines it may require. However, the dev can still force linebreaks, so I also count how many of them I can find in the text and add that to the number of lines. The resulting number is multiplied by the line height. And there you go, a rough estimate as how big your text will get.

At the end, I compare the result from calcTextHeight to this number, and choose the higher one as the contents height.

If you create a huge wall of text you can still stumble into the black square issue, but I have run tests with up to 102 lines, still good. Considering the plugin's expected use, that is already a crazy high number. If you need to go bigger than that I strongly advise you to break your text into smaller bits!