Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Image Frame Sequence as Displacement? #15

Open
enzyme69 opened this issue Jan 23, 2018 · 3 comments
Open

Image Frame Sequence as Displacement? #15

enzyme69 opened this issue Jan 23, 2018 · 3 comments

Comments

@enzyme69
Copy link

Does Growth respect and understand Image Sequence? Will it update frame by frame, like if I use a clip or movie or image sequences of procedural texture generated using Sverchok and then applying it to the mesh?

@hsab
Copy link
Owner

hsab commented Jan 23, 2018

I've had success with an image sequence but testing an mp4 with h264 codec gave me some UV issues. Will keep open for next release.

2018-01-23 05_21_18-blender d__hirad_desktop_new folder 2 _imagesequence blend

@enzyme69
Copy link
Author

screen shot 2018-01-25 at 12 04 29 pm

umog_box_vertex_008_2018_01_25_01_05.zip

I got a Sverchok setup that changes Vertex Weight overtime based on frame as above. I thought it would work with UMOG but apparently while umog is baking, the varying vertex weight is not updating.

@hsab
Copy link
Owner

hsab commented May 1, 2020

If you can update this with 2.8, I will have a look at it. I think the problem comes from the fact that unlike Sverchok, GN has a locking mechanism, meaning that it doesn't really iterate over the frames, but it will only use the frame range to calculate how many simulation steps are necessary. Once this is done, the python code will start and lock the thread, executing N iterations for each frame in range. However it is not actually using blender's playback functionality.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants