Additional Modules Folder and GLSLShader Expansion Pack

[Alex96]

Im am preparing for the update to v2.5 and want to reorganize all my additional Modules that are mixed in to the system tree.

As the manual says, its not recommended to mix own module in the system tree - so I sorted them out now.
I followed now the manual and made a private Additional module folder on my Disk, outside of MMV.
- for the ISF Modules all works fine.
- For the GLSLShader I copied there as well the GLSLShader Expansion Pack to the same place outside in a seperate folder, too.

But now I have the problem, that I can not navigate back any more to the Base-Modules, when once I configured a GLSL module from outside the MMV system tree (on MAC). Because the navigation there is Finder based, not like the ISF.

So the question(s)
- Is the additional Modules Folder concept NOT good for the GLSLShader Expansion Pack?
- if it is, what I am doing wrong?
- it it is NOT, how to do and how to manage it, that I can navigate back to the system modules tree?
- how to integrate OWN GLSL shader modules then?
- I also tried to make an Alias, but that was not working, so far.
- Howto handle the GLSLShader_ExpansionPack when updating to v2.5?

[Sadler]

You don't use Help->Additional Folders for GLSLShader unless you convert them to ISF. GLSLShader can open shaders from any location on your HD and Magic will remember where you last them opened from. If you can find them in Finder you can find them from the GLSLShader node. You manage them just like you manage any other media files.

[Alex96]

Hm, not sure, because at me it looks like following.

For ISF all works fine, I open the private modules via the Add context menu and using the MMV navigation GUI as path to the Modules. All good.

The GLSL Shader Expansion Pack modules - are opened in the "GLSL Shader node" - (the *.txt - files) opening a "Finder tree" on OSX level, with a default path that is set to inside of MMV. I can now navigate to anywhere on my computer and load the modules.
BUT
When opening this project next time and I want to load one of the Basic GLSL shaders files in the GLSL shader node where the module from outside MMV was saved, I can not navigate back to the folder of the Basic Modules INSIDE of MMV, with the path there
/Applications/Magic.app/Contents/MacOS/Modules/Special/GLSLShaders
But I can only load modules from outside MMV any more, unless I open a new "GLSL Shader node" (thats due to the OSX security mechanism)

So when loading a GLSL shader module (Shader_xyz.txt file) from outside MMV, its not possible to load any module from INSIDE MMV afterwards again in the same node. T
So this brings the question back - WHERE to save the promoted "GLSLShader Expansion Pack" on MAC - when the manual says, additional modules NOT to save inside MMV?

up to yesterday I had it there
/Applications/Magic.app/Contents/MacOS/Modules/Special/GLSLShaders/GLSLShader_ExpansionPack
and all worked fine and comfortable - even if the maual says - dont do that - because the update kills this Folder - I understand and can confirm.

So what is the right and convenient way to integrate the "GLSLShader_ExpansionPack" on MAC Sequoia/Tahoe, and my already plenties of own modified Modules, either.?

[Magic]

So it sounds like your problem is that you can't easily navigate back to the original GLSLShaders folder because it's inside the Magic.app application? In other words, Finder doesn't let you do that easily?

[Alex96]

Finder does not allow at all, by default a grabbling inside the App directories.
I think I am not the only one with a MAC,
and have not read nor heard anything in the forum here so far,
so I gues other shoud have similar situations?

Where do they install the Expansion Pack???? What is your idea/Mind?

Even when it works with the navigation, its a nightmare when exchanging a current module from the Base-System GLSLSaders to navigate then to the Expansion Pack folder - back and forth, when the folder are not in the same directory?

so there might be a solution, i guess, but no idea how to. What does MMV recommend how to install the GLSLShader Expansion Pack, that it might migrate the update process unharmed - and offer a good useability to change between the System delivered Base-Modules and the Expansionpack and own modules.... ???

Meanwhile I moved the Expansion pack back in the system tree.... again.... what is not recommended, I know..... but its the only ergonomic and working solution, at me at this time.

[Magic]

Did you disable the option Scene > Scene Editor Options > Load Default Module Files?

If that option is enabled, it will load the default GLSLShader file when you create the module. That's an easy way to get access to the folder, because when you click on the File parameter, it automatically takes you into that folder.

Otherwise, you should feel free to move the GLSLShaders folder somewhere else on your computer that is more convenient. There isn't a problem with doing that.

[Alex96]

IT WORKS - full story below..... THANK YOU!

Did you disable the option Scene > Scene Editor Options > Load Default Module Files?
> NO - it is still tagged in the pulldown menu.

If that option is enabled, it will load the default GLSLShader file when you create the module.
> That is still fine, when creating the module new - but just an example: When I open a project with a SAVED module from outside the MMV tree, then it does not allow me any more to go back to the MMV tree where the standard and default GLSL modules are saved.

That's an easy way to get access to the folder - when you click on the File parameter, it automatically takes you into that folder.
> THATS DOING THE JOB GREAT

I never noticed or read about this possibility - just checked the chapter Additional modules folder again, but do not find anything there in v.2.33 manual....
So thank you for that hint, now I can do a restructure of my modules and update to 2.5 in a couple of time, its just a one click thing that makes life easy.