CONTENT: 1x Bass, 3x Lead, 1x Pad, 1x FX. Download for free below
FILE NAMES: BS – Anubis.nmsv, LD – Osiris.nmsv, LD – Seth.nmsv, LD&FX – Ra.nmsv, PD – Isis.nmsv, FX – Horus.nmsv
Unfortunately once the initial wallpaper is set, we can’t change the image anymore. Even not by setting different initial wallpapers for each script tab. Because the last applied wallpaper will be the one and only initial wallpaper for the whole instrument. But we can either offset the initial wallpaper that means moving it via set_skin_offset() or we can use a label element to set up multiple backgrounds. Even dynamically like switching them on a button event. The set_skin_offset method is explained in this article
Download all Resources (nki, images)
to create your custom UI and place custom controls you can chose between a grid system or exact pixels.
The instruments background image is called “wallpaper”. Its’ the basic background texture where all UI elements (knobs, buttons etc) get layered on top. Just to give you an example: we could take our default graphic software and design a realistic synth surface wallpaper (png file) containing “sockets” for some knobs and buttons with detailed shadows, light reflections etc. After on we can create the individual knobs & buttons and place them exactly inside the designated sockets and areas by layering them on top of our background wallpaper.
CONTENT: 2x Bass, 2x Lead, 2x Pad. Download for free below
FILE NAMES: BS – FattyMoog (applause).nmsv, BS – Thinna (applause).nmsv, LD – ImPulsive (applause).nmsv, LD – Slimma (applause).nmsv, LD & PD – MeGaga I (applause).nmsv, LD & PD – MeGaga II (applause).nmsv
Like in other programming languages in KSP there are variables, arrays and constants. These can only be declared inside the on init callback but can be used throughout the whole script then.
Read more »
The Basic code structure is very simple. There are several callbacks where you basically put in your code. At least you need the init callback on init ... end on The code inside callbacks gets executed when specific events happen. For example playing a note on your keyboard always executes the “on note” callback.