Deprecation Warnings? Help Please

[Raven Burns]

I am at a loss right now, I am pretty new with the Dev Tool (F8).

My problem are these Deprecation Warnings, and these Pixi errors show up as well.

I have pinpointed when these Warnings occur.

Every single time a player transfer occurs. This includes loading a new map (even with no parallax mapping *EI: Black Screen/Blank Map*)

When you open the Character Menu and Exit.

After awhile these warnigns build up and up until it starts to lag my game to a complete halt. I have tried contacting help for this all over the place and nobody is answering me. I am sorry if I am breaking any forum rules or something but I really need help with this. I have dedicated my life and money to making this and several novels.

As for the Pixi errors, I have no clue what they mean and I am not familiar with how Pixi handles Javascript. I am not a programmer so this is probably why I am having so much trouble trying to fix this. I beielve it is also slowing my gameplay down. Outside of combat is fine and the FPS meter is always showing 55+ even when these warnings build.

However, during Battle, it lags everytime I use an attack. Stops then plays the animation. After the animation plays it seems to not lag as badly. But sometimes still will in random enc. As for Item Use. This lags every single time in a fight. Lags, then plays the animation. after it is played the animation plays smoothly afterwards for the current fight. Upon going to a new fight it lags the exact same way.

I am thinking these warnings have something to do with it but I have no idea. This is really fusterating me.

I have updated MV properly, I have unistalled, cleared download cache from steam, intergity. All of it, and this is still an issue.

I am Using RPGMAKERMV 1.3.4, I have gone back to every other previous and forward version and they all do the same thing, even 1.0

It seems to say something about Oranges plugins and MBS Map Zoom.. along with the rpg.core and pixi itself.

Also, this is not happening in a new project. Test Project works perfectly.

Again, sorry If placed this in the wrong area and what not, I am new to this forum.

 

[TomatoKing]

Your orange lighting plugin is outdated, so it's probably causing a memory leak, either see if there's an updated version or remove it.

Have you tried disabling it? The warning message there pretty clearly state where the problem is coming from.

 

[Skunk]

I believe it may be your Mapzoom plugin conflicting with the game itself.
I would update all your plugins

 

[Raven Burns]

Thank you for the response you guys. I have updated all of my plugins. I thought I had very recently but i must of just thought I did. I have tried to find a zoom plugin and overlay plugin/lighting system to replace these but i am having no luck.

EDIT: Alright, the problem is the Orange Lighting plugin. When I turn it off, there is no deprecation. Guess i'll have to find another lighting system, but I don't know of another one that is up to date with 1.5.0 or 1.4.1

EDIT 2 (Soultion): I found one, and its way better. I have used terrax before but it was really buggy now its nearly perfect. Thanks.

This can be closed now.

 

[mlogan]

I've moved this thread to MV Support. Please be sure to post your threads in the correct forum next time. Thank you.

Tech Support is for installation/running type problems.

This thread is being closed, due to being solved. If for some reason you would like this thread re-opened, please report this post and leave a message why. Thank you.

 

[Andar]

Alright, the problem is the Orange Lighting plugin. When I turn it off, there is no deprecation.

No it is not a problem - or not yet to be exact.

"Deprecation Warning" is a warning, not an error. And this warning message is for the plugin writers to inform them of future changes in the pixi.js (or where ever that deprecation warning comes from).

It basically means "you're using an old function in your program - we decided to remove that function in a future version of our API. You should use the time until we update that API to update your program with the replacement function, so that your program will still work after we update our part".
And they usually display that warning for several months before making the update, and keep the old function for some time to improve compatibility before finally removing it from the API.
And only after that old function is removed, the deprecation warnings turn into real errors "unknown function"