search

cedricduriau / Cryptomatte

Cryptomatte Nuke plugin, sample images, and specification
BSD 3-Clause "New" or "Revised" License
6 stars 1 forks source link

Fixed module import statement #8

Closed cedricduriau closed 6 years ago

cedricduriau commented 6 years ago
AndrewHazelden commented 6 years ago

https://github.com/cedricduriau/Cryptomatte/pull/8

Hi Cedric.

During the development of the WSL Reactor package manager v1 and v2 releases, and while the Resolve 15 private beta program was running I had the rare opportunity to ask a lot of questions of the BMD staff who worked on Resolve 15 and Fusion 9. This meant I got some useful insight from (Resolve's) Peter Chamberlain, Anish, and Rohit, as well as (Fusion's) Peter Loveday, and Daniel.

Based upon that direct feedback I got from BMD, I wanted to make a comment about your Cryptomatte for Fusion installation procedures and documentation changes.

(Before saying anything, yes I do know Lua Modules are FUBAR in Fu 9.0.2 in how they work inside a Fuse scope so there is that issue to contend with...)

But speaking in a broad generality, no 3rd party tool should be placing any items at all inside the "Fusion:" folder PathMap folders and sub-folders. That location is not deemed the correct or Kosher way for 3rd party installers to do things and is IMHO slipshod and sloppy.

The Fusion and Resolve program files folders are deemed a managed location that the Blackmagic installers can freely remove and replace on each update that BMD delivers and should not be used hold anything not made and installed by BMD.

All 3rd party content that is being installed in Fusion 7-9 and in Resolve 15 should ideally be placed inside the "AllData:" and "AllDocs:" PathMap folders in an ideal situation.

Alternatively, users can add their own PathMap entry like the Reactor installer's "Reactor:" PathMap entry does that would allow you to store your 3rd party content in a folder hierarchy you maintain. Or you can define a custom "LUA_CPATH" and "LUA_PATH" entry.

Regards, Andrew

P.S. If you don't want to take my word for it, I would encourage you to reach out to Peter Loveday if you want to get an external clarification on this point about placing your own content inside of "Fusion:" being a bad workflow that should be avoided.