Weird Battle Back Glitch

[ashikai]

Alternate title: can someone please explain battlebacks to me?

(I was going to post this in the JS support, but I don't think this is plugin related...)

Basically I've been stitching this game 'o mine together, and today I thought "hey, I should have a proper battleback for this battle." So I made one the same resolution of my game (960x540)...and that's when I noticed something really weird. The battle back I put in should have looked like this:

Spoiler

Instead produced a screen that looked like this:

Spoiler

....which implies that the battle back is scaling to a ridiculous level (making a 48px square fill the entire screen) or somehow pulling a common color and filling the BG with that (because I've been able to get it to turn pink/red (the color of the bricks) as well). Now obviously the above image is with all my plugins in, so I disabled them all (ALL OF THEM), grabbed an RTP battleback set and got the following:

Spoiler

...which BAFFLES me.

Obviously I have tried using battlebacks in a fresh project with no issues. I end up with this which is my expected result in the first place.

Spoiler

I know this issue is caused by the fact that my project files are older than MV 1.4 or MV 1.3.5. However I'm really REALLY hesitant to upgrade these files because doing so breaks YED_SideviewBattlers plugin (which is kind of important as that's what powers all my character animations).
(as far as I can tell the file that fixes the battlebacks AND breaks YED_sideviewbattlers is the rpg_core.js file)

So I guess what I'm wondering is if there's another way to work with battlebacks without working with the built-in battlebacks since those are a bit of a lost cause for me? Or is this a situation where it's better to see if anyone's interested in trying to fix YED_sideviewbattlers instead?

 

[Kyoku]

Maybe there is something wrong with your battlers, the only thing that hasn't been changed when you tested. I don't know why your battlers wouldn't work, maybe they were just not the correct size, maybe they were scaled down to a real small size, but I doubt that would cause it to all go down to one color, just try and switch the battler sprites with default and see what happens, if all else fails and there is just something wrong with your project copy everything over to a blank one and try again.
EDIT: Just figured out what YED_sideviewbattlers plugin was. So ignore what I said in last sentence sorry. Ummm, is it possible to just get the RPG Maker update that IS meant for your game and overwrite the other updated version? Never tried it, so I'm probably wrong.

 

[bgillisp]

Have you tried making the battlebacks the same size as the default? The defaults are 1000 x 760 or so (per GIMP). Maybe open them in GIMP, scale yours to that size, and see what happens?

 

[ashikai]

Have you tried making the battlebacks the same size as the default? The defaults are 1000 x 760 or so (per GIMP). Maybe open them in GIMP, scale yours to that size, and see what happens?

I've tried ALL different sizes and combinations for the battle backs. The problem ISN'T the sizing since, in that last screenshot up there, I tried using the default MV battle backs and got a brown screen instead of green (I was using a dirt battleback for battleback2).

If I update rpg_core.js, YED_sideviewbattlers BREAKS, but the battlebacks fix themselves. The other files don't have any affect on either of them, it's just rpg_core.js.

 

[bgillisp]

You might then need to look into why it is 'breaking' that one file, as no one else has reported it breaking with updates, and that is still a supported plug-in by Yanfly that I know of.

 

[ashikai]

@bgillisp Nonono, YED_SideviewBattlers is Yami and Archeia's plugin. You're thinking of YEP_AnimatedSideviewBattlers. That's a different plugin which I am also using, but that's not where the issue is as the breaking affects both actor and enemy animations. But regardless, the question was about another way to handle battlebacks or whether that's too complicated and I should just find or hire someone to fix the plugin instead.