Language…
17 users online:  Alex, Anas,  Anorakun,  bebn legg, Chondontore, Dark Prince, deported,  DeppySlide, Heitor Porfirio, Isikoro,  JupiHornet, KurtHose01,  Maarfy, sholmes,  sincx, Sonic12110, Suru48 - Guests: 199 - Bots: 115
Users: 65,930 (2,194 active)
Latest user: SummerTuner

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

Tool

Latest version (GitHub)



Here's an update to Romi's old VWF Cutscene Tool which is super useful for story driven SMW hacks. It now works with modern tools* and SA-1 without any issues.

I've took the liberty of adding several new things to it, which are listed below:
  • Now makes use of Python instead ActivePerl to parse scripts
  • The sprites are generated for PIXI
  • Full AddMusicK* support
  • Full SA-1 support
  • Plenty of new commands:
    • ExAnimation related commands
    • ASM Code execution commands (once/every frame)
    • More music related commands
    • Toggle ON/OFF switch status
    • Conditional dialogues
  • Documented code to make it easier to read & understand (hopefully)

* = AddMusicK is supported, but only up to 1.0.6. Version 1.0.8 didn't exist when I started this project, this will be updated at some point to support 1.0.8.



Videos








Credits
  • Romi (original version)
  • lx5 (new features, bug fixing and initial vwftool.py)
  • Atari2.0 (improved vwftool.py)



Feel free to report bugs, ask questions and idk what else you'd like to do in this thread.

#lm{zoom}
That video presentation really feels nostalgic, man. For some reason, it really gets me hyped for features of a tool that's already over a decade old. Kudos for making this gem of a tool useable even today!
Feel free to visit my website/blog - it's updated rarely, but it looks pretty cool!
Originally posted by RPG Hacker
That video presentation really feels nostalgic, man. For some reason, it really gets me hyped for features of a tool that's already over a decade old. Kudos for making this gem of a tool useable even today!

Thanks! Also the first video is pretty much the original "hello_world.txt" script with a few changes, maybe that's why it feels super nostalgic.
Are you planning to release this VWF tool?
You know, everyone need this tool for a long time.

THE OLD VWF TOOL IS HERE
Originally posted by Roberto zampari
Are you planning to release this VWF tool?
You know, everyone need this tool for a long time.

THE OLD VWF TOOL IS HERE

Originally posted by me

It has been out for at least 3 months :P
This looks great, but ExGFX83.bin is not in the archive.
I did fix this. A tutorial should be included. Using this can be hard at times.
I tried this again. Got this:



I used this commend in the cmd file:
vwftool.py definition.txt list.txt out.txt
If I use vwftool, then cmd doesn't recognise it and even if it's def.txt, I get the same error above.
Both ActivePerl and Python 3 are installed.
I actually wanted to upload a video with some of its features on my own. I won't show all.
Edlt: I even launched vwftool.py. Got the same error above. I needed to be quick to capture the error.
Apparently I forgot to reply last night...
Originally posted by Rykon-V73
This looks great, but ExGFX83.bin is not in the archive.
I did fix this. A tutorial should be included. Using this can be hard at times.

You're right, I forgot to include ExGFX83.bin.
The only tutorial available is the wiki I wrote.

Originally posted by Rykon-V73
I tried this again. Got this:
*img*
I used this commend in the cmd file:
vwftool.py definition.txt list.txt out.txt
If I use vwftool, then cmd doesn't recognise it and even if it's def.txt, I get the same error above.
Both ActivePerl and Python 3 are installed.
I actually wanted to upload a video with some of its features on my own. I won't show all.
Edlt: I even launched vwftool.py. Got the same error above. I needed to be quick to capture the error.

That's a really weird error. Perhaps is it related to an old Python version? I only tested it in 3.7 and I think Atari2.0 told me it should work fine in newer versions. ActivePerl isn't neeeded btw.
And as the wiki says, try running the script from command line like this:
Code
python3 vwftool.py def.txt <list of scripts> <output file>

Example

python3 vwftool.py def.txt list.txt vwf_data1.asm
The command line told me python3 isn't recognised as a command. Perhaps a tool might have been useful here.
Originally posted by Rykon-V73
The command line told me python3 isn't recognised as a command. Perhaps a tool might have been useful here.

Add python to your PATH. LMGTFY link.
I updated Python and added the command. I get this now

Not sure if this can be fixed and a tool might have been useful for getting vwf_data.asm here.
A standalone .exe version isn't going to happen from me. Releasing Python scripts as executables isn't exactly easy and they're treated as false positives most of the time by antiviruses, not to mention that these .exe files are anormally big for what they actually do.

I'm afraid to say I have no idea what's going on on your side, I've tried the script with Python 3.8.5 and it worked fine.
Wouldn't be a good idea to recode the tool to use lesser versions of Python like 3.0 or close to it? I think I know what the deal is. If I try to install Python 3.7 or more, then the installer told me that I need to upgrade my laptop. And I'm not the person with that much money.
I don't think I'm capable of performing such task. It might be a good idea to ask Atari2.0 about this issue.
Honestly if the problem is with Python > 3.7, you can just install an older version like 3.6 and it should work perfectly fine.
You can't go before 3.6 because the script uses f-strings which are from 3.6 onwards
I also tried with Python 3.5. I don't thin it works there. I got the error in my 2nd to last post.
Originally posted by Rykon-V73
I also tried with Python 3.5. I don't thin it works there. I got the error in my 2nd to last post.

Yeah, my bad, you need 3.6 at least.
I keep on installing/uninstalling Python versions, eventually finding out that 3.6 or above don't work on my laptop. That's quite the shame.
One thing to note: On Windows, you need to enter python instead of python3 since the latter is a thing in Linux/Unix-based systems (where often Python 2 and 3 are installed and not all have fully switched to Python 3).

Tool