Thanks, I did so. Still, I think this thread is useful to keep around, because it's not just one version, there are at least four (FMRTE 12, 13, 14 and 15) and could possible be more - therefore, more people could encounter it and, fortunately, I was able to find and provide a workaround.
But, if I may, I would like to ask you to do me a service (and likely, to the community and the devs as well), if you would be so kind. As I have said, I have not been to test the bug for FMRTE 16 and later, so could you test to see what happens if you use a different resolution in newer versions of FM and FMRTE (which one you might have). I am interested in particular if the bug occurs in FMRTE versions which appeared after Win10 was launched.