Language…
13 users online: Ahrion,  Alex, codfish1002, Daffster, Golden Yoshi, HD_DankBaron, OEO6, Shiki_Makiro, Sokobansolver, Spicy Jalapeno, spooonsss, VinylHeart, Zavok - Guests: 72 - Bots: 420
Users: 55,019 (2,217 active)
Latest user: Luillo2377

Modernized Romi's VWF Cutscene Tool - Current version: v2.0

  • Pages:
  • 1
  • 2
What about having a feature to do different things depending on which button is pressed? Or is the ASM command already good enough for that?

Also, does it let you change the size of the display space?

----------------

I'm working on a hack! Check it out here.
I'd say you can use [compare=*,*,*,*,*] for that, but compare doesn't wait for anything as far I remember. Shouldn't be that hard to implement if it's tied to button inputs.

As for the second question, I added a tag to change the space width in 2.0, it's [space width=*].
No, I mean the vertical space on the screen that's occupied by the text.

----------------

I'm working on a hack! Check it out here.
Speaking of features, a nice one would be to change the colors of specific font, like for example changing font color 2 or blue to a brown one. The command could be like this:
[font change = C, XXXX], where:
C = color of the font or 2;
XXXX = RGB color of the new color, like 001F which is red.
Speaking of 'fixing' the tool, isn't it possible to make the tool use Python 3 at worst?
In case it can't happen, I may resort to a last thing. I hope it will work.
Edit: I did manage to open wvftool.py in word. There's quite a lot of code. Not sure what to do to make it work with Python 3.0 or lower.
After I managed to upgrade to Windows 10 with some help, I did use the tool again and now it works. Perhaps I'll upload a video with some features in my style. I won't show all.
I hate to bump this thread after a few months, but I wasn't sure where else to go. I've got a bit of experience with the old version, but I've been trying forever to get this to work and all it seems to give me is this:



Can anyone help me out? It does this both with the included sprites AND ones I've generated myself and I just can't figure out whats happening.

EDIT: Welp, as soon as I posted this, I realized I never replaced patch.asm in the addmusicK folder, so I'm definitely an idiot. However, I guess that brings me to another question: Will this be updated anytime soon for the latest addmusicK version?
Originally posted by KDJewl
I hate to bump this thread after a few months, but I wasn't sure where else to go. I've got a bit of experience with the old version, but I've been trying forever to get this to work and all it seems to give me is this:



Can anyone help me out? It does this both with the included sprites AND ones I've generated myself and I just can't figure out whats happening.

EDIT: Welp, as soon as I posted this, I realized I never replaced patch.asm in the addmusicK folder, so I'm definitely an idiot. However, I guess that brings me to another question: Will this be updated anytime soon for the latest addmusicK version?

Assuming you mean v1.0.8 for AMK, I made this for R-ACK. All I really did was compare lx5's code to what was there and carefully replaced the spots that I needed to check.
Want progress on 100 Rooms of Enemies: The Nightmare Edition? Go here to see.

Are you a sample porter and wanna help with 100 Rooms of Enemies: The Nightmare Edition? Private Message me or Mellonpizza for details. Expect trading "resources" in exchange. 4 more left.




I got a somewhat similar problem.

I did replace the patch-file for addmusicK with the one from Daizo Dee Von - but I get nothing but a black screen. Music still plays but nothing else happens. But addmusicK doesn't seem to be the problem for me - from what I can see it seems to be the SA-1-patch. (I use 1.40)

I wonder if anyone got this to work with SA-1? Or is there something different I need to do on a SA-1-Rom?

The thing is I tried to apply everything on a Rom without SA-1 as a test and there it seems to work fine - with the exception that the ExAnimation-tutorial doesn't seem to work properly - I get wrong sprite-graphics and nothing is animated. ... but I could live with that, actually.

But I would be definitely interested to know why I can't get it to work at all on a SA-1-Rom. :(

I haven't tested anything with the latest SA-1 Pack. Can't guarantee I'll find a fix, but I'll check it at some point.
I hate to come out of the woodworks and bump this thread, but I'm having a similar issue regarding Python's syntax error.



Afaik I have all of the txt files and dialogues set up correctly, but I get this same error from using the code referenced in lx5's Github page.

Code
python3 vwftool.py def.txt list.txt vwf_data1.asm


I also tried navigating through Python to the correct file directory only to get the same error above. It was previously mentioned that the problem was solved when their OS was switched to windows 10. Might this be the same issue considering I'm using Windows 11?
Install a newer python version.
I don't think it's really the Python version which is an issue and more that you use the Python interpreter as the command line (when it is more useful to test stuff or do some simple calculations). You actually want to use a command line such as cmd.exe or PowerShell.
True, I thought fstrings were introduces in 3.7, but a quick google search says 3.6, which they have lol.
Originally posted by lx5
Install a newer python version.

I did initially use 3.10 with similar methods but to no avail.
Originally posted by MarioFanGamer
I don't think it's really the Python version which is an issue and more that you use the Python interpreter as the command line (when it is more useful to test stuff or do some simple calculations). You actually want to use a command line such as cmd.exe or PowerShell.

I navigated through command prompt to the correct file directory, only to get a different error, "Python was not found; run without arguments... >Manage App Execution Aliases." I went back to version v.3.10 and got the same error.
-----

So, I figured out what the issue was. It wasn't the Python version, but moreso about how it is installed. When installing Python, for some reason making a PATH is unchecked by default and was missed. To fix this, I right clicked on This PC > Properties > Advanced System Settings > Environment Variables. Then under system variables, find 'path', click edit, and add two new directories:

C:\Users\*yourname*\AppData\Local\Programs\Python\Python310
C:\Users\*yourname*\AppData\Local\Programs\Python\Python10\Scripts

After confirming, I reset my pc and went back to command prompt, navigated to my cutscene directory, and used the aforementioned code, just without the 3.
  • Pages:
  • 1
  • 2