Use this thread to report on any bugs that you've come across. Please include the version of After Effects you're using and any associated crash dumps that you can provide!
Sorry about the issue... What version of After Effects and what Operating system are you running on for reference? I can look into recreating the issue myself and solving it!
Also! If you are on Windows, you're in luck!
I've done brand new total recreation of the PixMap plugin called B.Map that is GPU-Accelerated and is available for free now that you can try as well!
Hey! Thanks for using my plugin!
Do you have any more details about these crashes or the circumstances that lead to it crashing? Maybe then I can find a way to proceed further and get this more stable! What would really help is if you had a reproducible circumstance so I can recreate the issue on my end and pick through what the cause might be.
For Windows though, I also have developed a newer GPU accelerated version of this plugin that you may try out as well!
Hello! Thanks for your response, well, maybe this helps, the MotionArray.com team attached this screenshot when they got the crash. When i use it in MAC OS, nothing in particular, just working a bit and navigation in the project template and it crashes, i need to save several times because of this issue. I hope it helps.
Thanks
tinomotion :)
Im sorry that i can麓t click on the "view report" button because i didn麓t make that screenshot, the review team of Motion Array did, they also sent me this video with the crashing problem, me when i use it on a MAC, i dont get any error message, it just crashes and leaves AE.
Please letme know if you can see the video.
Thanks
https://www.dropbox.com/s/wszstgqgexsfwzw/bandicam%202021-08-05%2010-52-38-788.m...
EDIT: I just open up the project on my MAC and it crashed, but i manage to get the error message code, i copy the error to a text edit file and uploaded here because its a bit extense:
https://www.dropbox.com/s/yqdksn5v8ug69xh/PixMap%20Error%20Message%20on%20MAC.rt...
Let me know if it helps :)
The crash log in your edit is precisely what I needed! I can see exactly what's going wrong now and can get a fix going!
I updated the Windows build with the fixes that I've identified. If it is possible that you are able to test it, let me know how it goes!
It might take me some time to update the OSX build as I don't have access to an OSX machine anymore and will have to spin up a Virtual Machine or build server to get that going. I'll reply once I have an updated OSX build uploaded as soon as I have that pipeline setup again!
Edit: I've updated both the Windows and OSX build! Let me know how it goes!
Wow! Wunkolo! You are the best! you made me so happy! i will finally be able to submit a lot of templates with your plugin! Thanks a lot for the efford and the support! And im happy also i helped to give feedback! i Will download again the plugin and tested! Will let you know! Thanks! Im happy! :)
EDIT: I just download and installed again the new version of PIXMAP and crashed again: here is the crash log:
https://www.dropbox.com/s/0vffqlb600enaww/PixMap%20Error%20Message%20on%20MAC%20...
I hope it helps :(
Oh no! tested again and still crashing in MAC OS. Here is the crash report:
https://www.dropbox.com/s/g9rebvgs7ti7t12/PixMap%20Error%20Message%20on%20MAC%20...
Hope it helps :(
Hello, thanks for the plugin.
I have noticed that when setting the V repeat to "clamp" I have to offset.y to the negative height of the UV map, otherwise, the mapped texture is below the bottom edge :/ It looks like some miscalculation bug in the plugin.
Also when the sampled texture is bigger than the UV map resolution, it gets cropped.
I use After Effects CS6 on Windows 10
Looking into this! Looks like the clamp arithmetic might be somewhat off somehow, or the incoming coordinates are being handled wrong. How are you generating your UV texture? It might be handling the UV coordinates differently, such as by having the 0,0 pivot being the top-left rather than the bottom-left. Causing the Y axis to be flipped.
You say that if the UV texture is smaller than the sampled texture, that it gets cropped. Can you explain this a bit? Is this still in relation to the `clamp` arithmetic?
I would say that B.Map (beta) works as expected regarding this issue. I'm generating my UV texture using Shadron app and GLSL shaders, they are in RGBAF32LE pixel format TIFF file. Also regarding cropping, the B.Map (beta) works flawlessly, here in PixMap it seems that base resolution from which the texture normalized coordinates are calculated is taken from the STMap rather than from the sampled texture.
Only issue not solved in B.Map (beta) is that it crashes when the layer with applied effect is pre-composed, while the effect is enabled.
I think the vertical flip you are experiencing is due to the (0,0) pivot of your UV map being at the bottom left corner rather than the top-left. The darkness of the pixels at the bottom-left here indicate this is where your origin is and is why your image is flipped vertically due to it using OpenGL conventions(Y is Up rather than Y is Down):
OpenGL is the only graphics API that defines its texture-space like this. While DirectX/Vulkan/Metal/After-Effects/etc define the top-left corner of their texture-space as the 0,0-origin.
My unit tests have PixMap and B.Map behaving the same, except for how their scale operation works(B.Map scales about the center (0.5,0.5) while PixMap scales about the origin (0.0, 0.0). In my next update I'll can tweak the texture scaling-operation so that they both scale about the center!