RMMV, Height Error and black screen.

[The_Black_Knight]

So, I reordered my plugins, after which the game was working fine. Now when I try battle testing against the default bats, I get thefollowing:

In addition, even on a completely fresh project, if I try testing against anything, I just get a black screen with no text.
Already tried re-installing the maker.

 

[Silva]

Can you provide an image of the console when this is happening?

To access the console press F8 and navigate to the "console" tab at the top of the window that opens.

 

[The_Black_Knight]

Can you provide an image of the console when this is happening?

To access the console press F8 and navigate to the "console" tab at the top of the window that opens.

You need the top of the log?

 

[Silva]

That's the elements tab. I need the console - it should look like this (yours will have error messages in red):

Spoiler

 

[Andar]

@The_Black_Knight what is your project's core version?

Please open its rpg_core.js file with a text editor and read the number in the title line to us.
Because this error often happens if you use an extremely old core-version together with some recent plugins.

(and no, the core version is not automatically the same as the editor version, that's why you need to open the file with a text editor)

 

[The_Black_Knight]

That's the elements tab. I need the console - it should look like this (yours will have error messages in red):

Spoiler

View attachment 111078

whoops

 

[The_Black_Knight]

@The_Black_Knight what is your project's core version?

1.6.1

 

[Shaz]

The core version of the scripts? Open your js/rpg_core.js file and confirm that that also says 1.6.1? My guess is that there may not be any version there at all, which means you have 1.0.0, because that issue stopped happening from 1.3.1 at least.

 

[The_Black_Knight]

The core version of the scripts? Open your js/rpg_core.js file and confirm that that also says 1.6.1? My guess is that there may not be any version there at all, which means you have 1.0.0, because that issue stopped happening from 1.3.1 at least.

I'm not sure what you mean, but I went to check, and in the "NewData" folder the script is actually 1.6.2, and in the project with the "height" issue 1.6.1.
However:
If I make a new project the file is 1.6.2 too, but I get black screens without text. The window wont even have a name, and I can't use F8 to open the console.
These issues appeared at the same time.

 

[Andar]

then please give us a screenshot of your plugin manager with all plugins listed.

 

[Shaz]

Not in the NewData folder. In the folder of your project.

You can have many projects all at different versions, if you update MV whenever there's a new version, but you don't also update your project.

 

[The_Black_Knight]

Not in the NewData folder. In the folder of your project.

You can have many projects all at different versions, if you update MV whenever there's a new version, but you don't also update your project.

Yeah, it's 1.6.1

then please give us a screenshot of your plugin manager with all plugins listed.

They should be in order, I hope, as I just reordered them. Even if I had all the non-yanfly plugins off, I still had the issue.

 

[Andar]

as I just reordered them

Have you startzed a new game after reordering them?
Whenever you either reorder plugins or turn them off/on, that makes the older savefiles incompatible because part of the plugin data gets stored into them. And then continuing a game that contains that old data can result in a lot of "undefined" errors, simply because the plugin that defined that data has been turned off or is no longer at the expected position.

That said, here is some background info so that you better understand why that error has us asking and doublechecking your project version:
"height" is a property that was introduced in 1.4.0 or 1.5.0 or so to make a lot of things easier - it didn't exist in older versions.
And if a plugin then tried to use this property with older core files, they gave this error because "height" was not yet defined in them.

So whenever that error message came up previously, it was always someone using current plugin versions with a core version 1.3.0 or older.
You are literally the very first case with this error message that has a newer core version.

And I can now only think of two remaining options why you get this error:
1) you have always tested with an old savegame that contained the data of the old core-structure
2) your last update was incomplete and only some of the core files were updated to 1.6.1 (including the rpg_core.js) while others failed to update correctly and are still at pre-1.4
In the second case make a backup and try to update that to 1.6.2 and see if that corrects such a failed update.

correction:
I just thought of a third possibility. Can you go into your project folder and check if it contains a www folder?
Hopefully not because that folder should only exist in a deployed version, never in a project directory - but it would redirect all tests and we would have looked at the wrong folders if that is the case.
If you have a www folder inside your project directory, then delete it and replace your package.json file in the project directory with one from a new project - a failed deployment will create the ww folder and exchange the packages file with the wrong one for the project directory.

 

[Kes]

'Tech Support' is for when you cannot get the engine to run.

[mod]As this looks like it is an updating issue, I am moving this to RPGMaker MV. [/mod]

 

[The_Black_Knight]

Have you startzed a new game after reordering them?
.

Okay, things are running for some reason, for now:
I checked the integrity of the files on steam, but it didn't say there was any issues.
Like an idiot I hadn't checked other troops for encounter. It appeared only the troop id 01 caused the issue, I cleared it, and set enemies there again, and boom, it's working.

With the new projects, the old new project still gave me black screens, but I tried out a new new project, and it works.
Maybe someone can questimate what the issue was from that?

 

[Silva]

My understanding is that an enemy or multiple enemies within the troop had their .bitmap property set to undefined. The bitmap from what I can see is a reference to their spritesheet so for whatever reason this wasn't being picked up correctly. I can replicate your exact problem by adding an enemy to a troop that doesn't have an image set and running a battle test, so I suspect this is what the issue was.

 

[Shaz]

could you have deleted some enemies from the troop? Or added some enemies to the troop but then deleted them from the Enemies tab?