If you import an anme-scene with images into another the imported scene gets scaled to the dimensions of the new current scene. So, import and 500x500px scene into an 1000X1000px scene and the images gets scaled to double size.
When updating these images (through scripting) the images gets scaled to their right size in comparison to the current scene, so the images all of a sudden gets shrinked to half their size in the example above.
Bones and everything else imported stays their size though so the whole scene gets broken and you either have to manually rescale all resized images or revert to last saved version to get them back to right relative size.
Imported images reloaded, gets resized.
Moderators: Víctor Paredes, Belgarath, slowtiger
- synthsin75
- Posts: 10280
- Joined: Mon Jan 14, 2008 11:20 pm
- Location: Oklahoma
- Contact:
There's no script access to the info you'd need to change to fix that.
From the file format:
The 'shape 3.4 3.4' is the shape of the image. Reloading in a larger dimension project changes this to 'shape 1.7 1.7'. This could be fixed by script if you want to parse and write to the open file and then reopen the file.
This looks like a pretty valid bug here. If there were script access to this, it'd be an easy fix. Personally I don't mind reading the open file, but I don't like the idea of writing to it.
Hopefully this info will help MC fix this, or better yet keep adding to the script interface.
Until then I'd try matching the donor projects dimensions to the destination project before importing.
From the file format:
Code: Select all
### image layer values
image "image path"
avi_alpha false
shape 3.4 3.4
This looks like a pretty valid bug here. If there were script access to this, it'd be an easy fix. Personally I don't mind reading the open file, but I don't like the idea of writing to it.
Hopefully this info will help MC fix this, or better yet keep adding to the script interface.
Until then I'd try matching the donor projects dimensions to the destination project before importing.

I have to check some of my scripts.
I had the same issue and was able to fix it... uh... er... somehow that I don't remember. It had to do with those funky numbers. There was a way to "force" AS to update the image size.
I could be completely wrong about this of course but I remember a script I created for a big project that required replacing images. The images came in too small (due to the reason you mentioned) there was a way to "trick" AS to do it "right" by the order of the image replacement or something like that.
I will let you know if I can figure this out again.
-vern
I had the same issue and was able to fix it... uh... er... somehow that I don't remember. It had to do with those funky numbers. There was a way to "force" AS to update the image size.
I could be completely wrong about this of course but I remember a script I created for a big project that required replacing images. The images came in too small (due to the reason you mentioned) there was a way to "trick" AS to do it "right" by the order of the image replacement or something like that.
I will let you know if I can figure this out again.
-vern