Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
Tags

B.Map (Beta)

After Effects Texture Mapping Plugin 路 By Wunkolo

Bugs Sticky

A topic by Wunkolo created May 01, 2020 Views: 717 Replies: 11
Viewing posts 1 to 3
Developer

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!

Plugin crashes with this version.

Looks like plugin plugin is some difficulties to load.

Developer

Please provide more details!

This is a very experimental plugin that uses the Vulkan graphics API so it will matter what GPU, OS version, and driver that you have.


WIN 10

GeForce GTX 1070

NVidia 451.67

Developer

What is the symptom of the crash like? Do you see an error message or does it just close entirely?

long loading and then crash and appears adobe crash popup.

Hi Wunkolo!

Well, unfortunately I can't get the plug-in to work (same for B.Carve - crashing as well).
I create a comp, place a PNG and try to apply the plug-in and AE just crashes.
Tried with AE Beta, 2022, 2221 and 2020 - you list 2020 as supported, so I tried that version a couple of times.

Windows 10 Pro, 64-bit
NVIDIA GeForce RTX 3070
Studio Driver 511.09

B.Carve gives this error when crashing:  B.Carve plug-in generated an unexpected exception.
Also this somtimes: This effect cannot be applied because it cannot be initialized. Try reinstalling or contacting the plug-in developer. ( 25 :: 3 )
B.Map: AE crashes with no error, but generates the crash report.

The last two lines of the report:
"adobe\B.Map.aex"
"vulkan-1.dll"

As you already mentioned possible permission issues, I gave full access to vulkan-1.dll and the other three files with vulkan in the name, but that didn't help.
Running AE as admin doesn't do the trick either.
Do you have any other tips to get B.Carve and B.Map to work?

Thanks, Lars. 

Developer

I've re-uploaded an alternative version of the plugin that you can re-download and try that adjusts the initialization a bit. Lemme know how it goes! If it has initialization issues again though, is it possible that you can provide more information from your crash report? It seems to be having an issue with initializing Vulkan, despite your system clearly being capable of supporting it. If you'd like you can send it to me at wunkolo(at)gmail.com for privacy.

Note for myself: (Build date: Sat Jan  8 16:38:42 2022)

Thanks, sent an e-mail. 馃槈

Developer

Got it thanks! Gonna try and dissect what's going on here..

Just checking in - have you had the time to look at it and an idea if the plug-ins could work at my end as well?  As I did pay a little bit for B.Map & B.Carve, it would be nice being able to use them. 馃槄 Thanks!

Developer (2 edits)

Been trying to find out any sort of consistency between the systems where it does/doesn't initialize correctly it has me quite stumped 馃檨. Others seem to be getting it too.

I can't seem to pick out any particular thing causing it, even switching between the Studio/Game-Ready Nvidia drivers. Opening the dump files sent over in WinDbg was giving me "bad_dump" issues and was not providing any more details. I was iterating with someone else that was having the issue to no avail either and their installation was a more bare-bone workstation installation too.

If you could, do you perhaps have any crash-log(not crash-dump) files in your Adobe AppData directory?

You should be able to put "%APPDATA%\Adobe\After Effects" in your explorer path and it will take you there, and within there you should see a folder like 22.1 there and a logs folder within that where you may find .crash files.

For example, my After Effects 2022 crash-log folder is: "%APPDATA%\Adobe\After Effects\22.1\logs". And in there should be timestamped files that identify the particular crashes if it correlates with any recent crashes you got with the plugins in particular.

Feel free to email it to me rather than post it here.