VX Ace to MV Converter

[Shaz]

What does "$game_map is not defined" mean?
Happens as soon as my intro is over in my now converted mv version and the game starts and the player are about to be controlled.

I found out what the problem was. I needed to put in the yep core plugin afterwards in the mv version. Now it seems to work

No. There is no such thing as $game_map in MV. If you got that error, it means you did not go through the list of script calls and fix them up. What plugins you have have nothing to do with it.

 

[SloppyJoeStudios]

No. There is no such thing as $game_map in MV. If you got that error, it means you did not go through the list of script calls and fix them up. What plugins you have have nothing to do with it.

Then I really don't know what dixed it but after taking away all script calls and playtested a lot of times.. nothing worked, then I tried adding that plugin and that worked but I know what coder god you are so you are probably right... That is what I did though...

Now I want to find a new unique battle system for the game. Tired of the sideview and action battle system... Hmmm..

 

[stramin]

This topic should be pinned

 

[Juanita Star]

(And I sure hope Im not necroposting here, unless I misread the rules right now...)

For everyone who did the "VX to Ace" and then "Ace to MV" transfer and got problems with Common Events:

Take the data file from common events from VX and change the "rvdata" to "rvdata2" manually (you know, by adding 2 in the file). Then transfer your Ace project to MV using this tool. That was what worked for me.

 

[Shaz]

@Juanita Star I'm not aware of any issues with common events transferring, unless there was something in a script call that caused an issue. I'd be happy to take a look at both your VX and Ace CommonEvent files if you want to troubleshoot.

 

[Juanita Star]

@Juanita Star I'm not aware of any issues with common events transferring, unless there was something in a script call that caused an issue. I'd be happy to take a look at both your VX and Ace CommonEvent files if you want to troubleshoot.

Thanks! but no worries! The problem was when I transfered from Vx to Ace using a tool for it, then when I tried the Ace to MV here, it would cause me problems for some reason, even when I tred to delete all common events...but I did the change of data to VX manually and the transfer to MV was a breeze. (I did discovered that script calls were a no-no for weapons too).

 

[ZephyrLightningheart]

When I put the 2.0 script into VXA, I get this error message. I also converted my VXA project from VX. I rarely used any scripting. Any scripts have been since taken out.

 

[Andar]

I also converted my VXA project from VX.

that might be the cause of the problem, but I'm not sure.

I remember that all double-converted projects caused problems when MV came out.
pure VXA->MV always wworked, but somehow the VX->VXA converter must have entered wrong values that were ignored by VXA but not by the second conversion.

And I don't remember any solution for that case at all, because it was too rare to reproduce where the wrong data was stored.

Then again that error message suggests a problem with the conversion script itself, like it was improperbly installed. The error described above only caused problems in MV after the conversion, not during it.

 

[ZephyrLightningheart]

that might be the cause of the problem, but I'm not sure.

I remember that all double-converted projects caused problems when MV came out.
pure VXA->MV always wworked, but somehow the VX->VXA converter must have entered wrong values that were ignored by VXA but not by the second conversion.

And I don't remember any solution for that case at all, because it was too rare to reproduce where the wrong data was stored.

Then again that error message suggests a problem with the conversion script itself, like it was improperbly installed. The error described above only caused problems in MV after the conversion, not during it.

If I were to create a fresh project in VXA and remake all the events and maps, would that solve the problem of the double conversion? It would only be VXA to MV with one conversion instead of 2 conversions?

To add it does create the MV-data folder with the converted files but only skills, characters, and actors were created. When I loaded what I had into fresh MV project, the skills.json was unreadable.