Animated busts and picture based animations.

● ARCHIVED · READ-ONLY
Started by Astfgl66 143 posts Page 5 of 8 View original ↗
  1. Fixing that bug gave me some inspiration:
    I've added a few new functions for those of you using it to manage busts:

    - dim picture, sets the picture to grey
    - light picture, sets the picture to full color
    These two commands should allow you to act as if busts are selected or unselected depending on who's speaking, directly from the message window.

    - move picture home, moves the picture back to its original coordinates
    - fadeout picture, moves the picture a bit to a chosen side, set it to grey, set it to transparent over the course of a few frames before erasing it
    This should allow you to end conversations with a bit more style.

    These four new commands are available via script call and text codes.
    You can download the update in the OP, I've updated the pastebin.

    Further instructions on the commands below:
    Code:
    * ===================================================================
     * VN Commands
     * ===================================================================
     * As of V13, several VN like commands have been added to facilitate your life.
     *
     * -------------------------------------------------------------------
     * Light picture:
     * This will set the picture tone to (0,0,0,0), basically fully bright, over
     * the course of 30frames, acting like if the bust was selected.
     *
     * Script call:
     * $gameScreen.picture(id).light(duration)
     * duration is optionnal, if unspecified, will do it over 30 frames.
     *
     * Text code:
     * \LP[pictureId]
     * You can't specifiy a duration if doing it via textcode.
     * -------------------------------------------------------------------
     * Dim picture:
     * This will set the picture tone to (0,0,0,255), basically fully grey, over
     * the course of 30frames, acting like if the bust was unselected.
     *
     * Script call:
     * $gameScreen.picture(id).dim(duration)
     * duration is optionnal, if unspecified, will do it over 30 frames.
     *
     * Text code:
     * \DP[pictureId]
     * You can't specifiy a duration if doing it via textcode.
     * -------------------------------------------------------------------
     * Move picture home:
     * This will set  move the picture to its original coordinates over the
     * course of 30 frames.
     *
     * Script call:
     * $gameScreen.picture(id).moveHome(duration)
     * duration is optionnal, if unspecified, will do it over 30 frames.
     *
     * Text code:
     * \MPH[pictureId]
     * You can't specifiy a duration if doing it via textcode.
     * -------------------------------------------------------------------
     * Fadeout picture:
     * This will set  move the picture back 20 pixels in either direction,
     * set its tone to grey, and change its opacity to 0 over the course of
     * 30 frames before deleting it, erasing the bust from the screen.
     *
     * Script call:
     * $gameScreen.picture(id).fadeout(duration,direction)
     * duration is optionnal, if unspecified, will do it over 30 frames.
     * direction is optionnal as well, 1 will move th epicture left, -1 right.
     * If you want to specifiy a direction, you must specify a duration.
     * You can only specify a duration if you want to.
     *
     * Text code:
     * \CPR[pictureId] this will fadeout the picture to the right
     * \CPL[pictureId] this will fadeout the picture to the left
     * You can't specifiy a duration if doing it via textcode.

    I think this will be it for a while, barring any bugs appearing.
    Have a nice day!
  2. The fade out script call is very neat. before I was only able to do it the traditional way by several lengthy commands. Now it is streamlined to only 1 line of command.
  3. Nice work as always :)
  4. Thanks!

    I figured that if I had a fadeout command, I might as well have a fadein command.
    I've added a fadein command that moves the picture a bit, sets opacity to max and tone to bright over a few frames.
    To use it optimally when setting up your pictures, set them up 20 pixels back, with an opacity of 0 and a grey tone, then start your message with the fadein.
    I've also added a command to move a picture relatively to its current position.
    Both of these have text codes too, so you can add a bit of life to your busts directly from the message window.

    Code:
    * -------------------------------------------------------------------
     * Fadein picture:
     * This will move the picture forward 20 pixels in either direction,
     * set its tone to bright, and change its opacity to 255 over the course of
     * 30 frames, acting as if the picture appeared.
     *
     * Script call:
     * $gameScreen.picture(id).fadein(duration,direction,distance)
     * duration is optionnal, if unspecified, will do it over 30 frames.
     * direction is optionnal as well, 1 will move the picture left, -1 right.
     * distance is optionnal and is to be given in pixels
     * If you want to specify a distance you must specify both other parameters.
     * If you want to specifiy a direction, you must specify a duration.
     * You can only specify a duration if you want to.
     *
     * Text code:
     * \FPR[pictureId] this will fadein the picture to the right
     * \FPL[pictureId] this will fadein the picture to the left
     * You can't specifiy a duration if doing it via textcode.
     * -------------------------------------------------------------------
     * Move picture:
     * This will move the picture relatively to its current position.
     *
     * Script call:
     * $gameScreen.picture(id).movePictureRel(x,y,t)
     * x and y are the amount of pixels you want the picture to move
     * t is the duration in frames
     * y and t are optionnal, if omitted the picture won't move on the y
     * axis and the x movement will be done over 30 frames.
     *
     * Text code:
     * \MPR[pictureId,x,y,t]

    Hopefully these should make your life easier too.
    Have a nice day!
  5. Hello, not sure if it's a bug but I found an issue with AnimatedBusts(20042019 V14)
    It doesn't happen always but when it does, whenever you change the next show picture#1 with a different xy coordinate after an animated picture, in the case below, from a blinking animation. The show picture#1 you're supposed to change into will not appear and instead show a misaligned picture of the previous animated show picture#1 which adopts the xy coordinate of that picture#1 that it's supposed to change into.

    This does not seem to happen with AnimatedBusts(02102018 V12) so I have decided to roll back to that version for now. I just want to report my findings as I was testing out the features today. thanks!

    jFcEwgr.jpg C7bPBaw.jpg

    Here's a rerun of that scene using AnimatedBusts(02102018 V12). This one proceeds smoothly to the next show picture #1 with no issues.
  6. Alright, the sprite bitmap wasn't updating properly when showing a picture that was already on screen.
    It should be fixed as of V15.
  7. Cool, tested and it works, thanks a lot!
  8. This is a great plugin ^^ But I was wondering, is there any way the pictures can be added to the message window automatically? Like in Galv's bust plugin? I'm using Yanfly's message core and the textboxes appear over the speaker's head like a comic bubble. I'd like the pictures to appear along the textboxes but it will be hard to do as the events change position...
  9. Use the create animation text code.
    Using a variable it will allow you to set up an animation completely and memorize it so each time you want to call it you only have to use \ca.

    The only other way is programming it yourself.
  10. If I use that text code, will the animation be placed automatically near the textbox? I'm sorry I can't try it right now because I'm not near my computer.
  11. You'll need to create a picture at the right coordinates for it to work.
    It only automates the animation part.

    I don't intend to update that plugin unless things break or I'm commissioned again.

    Your best bet would be to make a plugin request thread to get the coordinates of the message window when shown, and to have them automatically set to variables.

    Meanwhile if you need the message window coordinates you'll get them with this:
    Code:
    SceneManager._scene._messageWindow.x
    SceneManager._scene._messageWindow.y

    This is assuming the plugins you use use the default message window, and are only moving and resizing it. It may not work depending on your exact plugin setup.
  12. Thank you! I'll try using those script calls. Maybe it'll work.

    Edit: @Astfgl66 Thank youuu!!! It works! Those script calls were all I needed ^^
  13. I'm glad everything is working then.
    Have a nice day!
  14. I'm sorry, but the plugin still doesn't work with Kino's Slow Text plugin when I try to synch the mouth with the text box... Am I doing something wrong?
  15. Nope. Compatibility was broken a while ago, despite my and kino's plugin not changing, around the MV 1.6 release if I recall correctly.

    I haven't looked into it since, and it's not in my plans in the foreseeable future as I don't use that plugin.
  16. cedr777 said:
    I'm also curious about the compatibility with those two, it would be nice if they can both work together. It's been so long since we got a visual novel plugin like this.



    Do you know how to work this plug-in? I bought it and I'm unable to get the hang of it... I'm an artist and story writer, my mind is too cluttered atm lol.
  17. @Blue1 This thread is not for that plugin. Please create a new thread in Plugin Support asking for help with this plugin.
  18. Combining this with some voice acting scenes are gonna breath more life into my busts! Thanks!
  19. Sorry to bother you again, but...
    For reasons unknown, in only one cutscene I got this error message:
    PLmFY0C.jpg

    PLmFY0C
    Like I said, it happens in only one cutscene, and it's not a problem of the map... Maybe two characters talking made conflict... :/
    HdV4sFh
  20. TomorrowAvenger said:
    Sorry to bother you again, but...
    For reasons unknown, in only one cutscene I got this error message:
    PLmFY0C.jpg

    PLmFY0C
    Like I said, it happens in only one cutscene, and it's not a problem of the map... Maybe two characters talking made conflict... :/
    HdV4sFh

    Use the older version. The newest one is bugged. It happens when pictures are deleted. Could be plugin compatibility issues, not sure. But this one works for me.