- Feb 18, 2015
- Reaction score
- First Language
- Primarily Uses
Interestingly, neither of those are happening for me anymore. Maybe something on Steam's end?
Not sure, but they both still happen to me. I took the screenshot this morning and opening MZ directly makes steam say "lol hi you're running rmmz now" when before, it didn't. Really kicking myself for not buying the direct version...Interestingly, neither of those are happening for me anymore. Maybe something on Steam's end?
There is actually an answer they could give, in any software development company I have worked I have used basically the same answer. Basically is confirming or denying that it is in the backlog of bugs or whatever name they use for that, some companies have a different name. If you go back a little in this trhead, you'll find that I ask if a certain bug is in the backlog and they answered basically that it's not even in their radar. So yes, there is a "default" answer to that question. I don't expect them to add a patch immediatly or hurry a release only because of the issues listed in this or any previous release thread, just knowing they know that the issue exists and that it is at least in their backlog should be more than enough.I don't think there are any of the moderators who would be competent to give us an answer. It's a bug in the last update, because when I choose to downgrade to the previous version 1.1.1, everything goes as I expect. So for now, I'm using an older version. When it fixes, I'll allow it to update to the latest version again. It's rather ridiculous when I have a project folder open and I can't run a project directly from it, butI must extra clicking via shortcut elsewhere is quite a regressive solution. Fortunately, they didn't put this feature into the MV, because if I'm redoing the project from the MV to the MZ and if it was same extra clicking as in the last MZ update, I wouldn't give it.
I've noticed an issue with the new version of the corescript.
Certain windows' background extends to the right outside the borders. I have tried this in a blank project with no plug-ins; and the issue still occurs. I'm attaching images from a blank project to demonstrate. It's most noticeable when a custom windowskin is used, but if you look closely you can see it also occurs with the default Window.png file.
This seems to happen when using the "Show Text" command, and in the battle scene, in skill/item select dialogs and the battle messages (e.g. "Enemy appears").
The windows display perfectly normally when downgrading the corescript to 1.0.2
View attachment 182390View attachment 182391
rmmz_managers.js:2030 Error: Failed to initialize graphics.
at Function.SceneManager.initGraphics (rmmz_managers.js:1909)
at Function.SceneManager.initialize (rmmz_managers.js:1881)
at Function.SceneManager.run (rmmz_managers.js:1870)
at Main.onEffekseerLoad (main.js:141)
at Object._onRuntimeInitialized [as onRuntimeInitialized] (effekseer.min.js:33)
at doRun (effekseer.min.js:15)
at run (effekseer.min.js:15)
at runCaller (effekseer.min.js:15)
at removeRunDependency (effekseer.min.js:15)
at receiveInstance (effekseer.min.js:15)
I thought that particular error looked famliiar, so I referred back to a screenshot someone sent me when they played one of my games that was made and published to my webserver well before the v1.2.0 update happened--at least I think so--and sure enough, it was same error:Since I upgraed to 1.2.0 I am receiving sporadic reports from players that they are now getting a startup crash with the message
I can't reproduce this myself and everything worked fine for them before the upgrade.
Does anybody experience similar issues?
Is there any way to tell which version of RMMZ an already-deployed web game was built on?
Aah thanks, I feel dumb now. Yeah, the game that error's from is built on 1.0.0, so I guess this is some sort of weird bug that goes all the way back to the beginning.In the developer console, Utils.RPGMAKER_VERSION is a global variable containing the version (defined in rmmz_core.js)
The core scripts also have the version in a comment at the top of the file.