So, there is the nebula4temprepository folder, which I assume is the location for everything. Within it, there are folders for Programs, Vectors, Setups, and so on.

With the libraries, taking AlexB 9k SSL Console as an example, they normally have 2 folders for Library and Skin. The Library has folders such as Programs, Vectors, and so on. The Skin folder seem to have skin-related stuff with some instructions.

Is it a case of simply merging the ones from the Library folder (being Programs, Vectors, and so on) from the AlexB Library into the one in the nebula4temprepository, or do they need to go within some kind of User/Addon type of location?!

Also, do the addon libraries for Nebula 3 work in the Nebula 4 on the sister site?

 

ATME:

yes, and

yes.

 

So, here is the nebula4temprepository folder I have:



Now here is an example of an addon library (AlexB Vinate Neev 64 Dynamics):



Is it a case of copying the folders and merging them in, i.e. Programs to Programs, Vectors to Vectors, and so on? If so, is the Skin folder in the AlexB meant to be merged into the Skins foldder (note the extra "s" in the nebula4temprepository folder?

ANd lastly, do I need to install the LibraryInstaller.exe, and what exactly does this install?

 

Yep, that's how it worked here.

Oh, damn, this I don't know, haven't tried an Alex B.

 

What's important is that an .n2s file ends up in you n4 skins folder, so it's probably just a typo. For n4 you also need a property file (which if i remember correctly is a .ini). If it doesn't come with it, the skin is not compatible with n4.

 

It's yust to automate all that copy and paste, if you already did that manually, there's no need to run the installer

 

This is what I assumed as the .n2s files are in both the Skins and Skin folders, so I assumed they were the same but just checking!

These are Nebula 3 libraries, so don't have the .ini files. Does that mean they won't work, or that they will work just without the skin?

 

Google ---> Link Shell Extension

 

My whole N4 folder with all the sub folders (patches, presets, programs, ...) doesn't have a single ini file and all is working.

 

iirc the neb 3 skins for Alexb don't work on neb 4, but there is a work around for cubwise I think. search for Azzimov on Patreon, he makes skins for nebula. if you got an extra buck a month toss it his way imo he's in Ukraine and making skins for one of the clunkiest (and best sounding) programs ever, he could use it haha.

even if you don't give him money there is a lot of tutorials and extra skins on there for free.

 

Then i don't remember correctly . There is another file aside from the .n2s which is the properties file, but don't remember the extension. Should come in a "properties" folder and goes into the properties folder of n4.

But no, vectors and programs work independently from the skin, so even if the skin doesn't work the library will.

 

I have only xml files in Properties.

 

Those are the ones then. Don't know why i said .ini, probably because i had to edit one at some point and when that happens is usually a .ini file. Also i just saw it's actually a bunch of them. Damn my memory sucks.

Anyway, i don't know if those are strictly necessary for the skin to work since all they basically do is tell n4 which skin to load, but skins that are built for n4 come with that, so if you don't see it it's probably not met to work with n4 (even if you load them manually)

 

IIRC, there are some N3 libs that do not come with a skin by default. In this case you need to use the def Nebula GUI.