Plugins + Scripts Decal Maker

Why i can't load my presets? it's throwing at me a json error, wtf..
i save a preset of texture, named it test. try to load it with a button = file not found...

wtf is that problem, how something so simple isn't working...it's an issue from my side. this plugin has reputation, i must done something wrong

Waslikethem said:

Why i can't load my presets? it's throwing at me a json error, wtf..
i save a preset of texture, named it test. try to load it with a button = file not found...

wtf is that problem, how something so simple isn't working...it's an issue from my side. this plugin has reputation, i must done something wrong

Click to expand...

Are you trying to load a preset with a button as the trigger? I know VAM's json loaders can be really picky about file paths.

Vam uses Unity style paths so lets say you want to load a preset named aa.json that you saved in the Saves/PluginData/Chokaphi/DecalMaker/Presets/ folder

The VAM trigger would accept either as the path:

Saves/PluginData/Chokaphi/DecalMaker/Presets/aa.json
OR
Saves\\PluginData\\Chokaphi\\DecalMaker\\Presets\\aa.json



If that is not the problem can you give me a simple scene and I will see what is going wrong. Its possible I have something formatting incorrectly in the current Beta.

Chokaphi said:

Are you trying to load a preset with a button as the trigger? I know VAM's json loaders can be really picky about file paths.

Vam uses Unity style paths so lets say you want to load a preset named aa.json that you saved in the Saves/PluginData/Chokaphi/DecalMaker/Presets/ folder

The VAM trigger would accept either as the path:

Saves/PluginData/Chokaphi/DecalMaker/Presets/aa.json
OR
Saves\\PluginData\\Chokaphi\\DecalMaker\\Presets\\aa.json



If that is not the problem can you give me a simple scene and I will see what is going wrong. Its possible I have something formatting incorrectly in the current Beta.

Click to expand...

I’ve tested it on versions 49 and 51 — both throw the exact same error. When I save the preset and then load it directly from the plugin, it works fine. But when I try to load the preset via a button, it fails with a 'file not found' error. I was like… WTF? I’ll try to grab some screenshots. I always struggle with uploading pictures to forums, but I’ll give it a shot.

i find the error.
++++++++++++++++++++
Error-
your error is that the plugin call for different path, he's trying to look for the preset in: /Saves/scene/aa.json
{basically, when you call the 'Load Preset File' from a button trigger on your plugin, he's looking for the preset in: /Saves/scene/}
Solved-
i entered this path instead in the preset named (thru the button): Saves\\PluginData\\Chokaphi\\DecalMaker\\Presets\\aa.json -> and it worked.
so i guess the bug is from where your plugin call the preset, maybe you should change the presets that we save with that plugin into /Saves/scene/ instead, this will instantly remove the bug...but i'm not sure this is your wanted end results, which is understanable.

i'm asking myself, how the fuck i'm playing 3 years without your plugin, he's amazing. thanks

Waslikethem said:

I’ve tested it on versions 49 and 51 — both throw the exact same error. When I save the preset and then load it directly from the plugin, it works fine. But when I try to load the preset via a button, it fails with a 'file not found' error. I was like… WTF? I’ll try to grab some screenshots. I always struggle with uploading pictures to forums, but I’ll give it a shot.

i find the error.
++++++++++++++++++++
Error-
your error is that the plugin call for different path, he's trying to look for the preset in: /Saves/scene/aa.json
{basically, when you call the 'Load Preset File' from a button trigger on your plugin, he's looking for the preset in: /Saves/scene/}
Solved-
i entered this path instead in the preset named (thru the button): Saves\\PluginData\\Chokaphi\\DecalMaker\\Presets\\aa.json -> and it worked.
so i guess the bug is from where your plugin call the preset, maybe you should change the presets that we save with that plugin into /Saves/scene/ instead, this will instantly remove the bug...but i'm not sure this is your wanted end results, which is understanable.

i'm asking myself, how the fuck i'm playing 3 years without your plugin, he's amazing. thanks

Click to expand...

EDIT: Looks like I have a bug that wont let a trigger reload the same preset. Will look into that.

Instead of

/Saves/scene/aa.json

Click to expand...

Try without the leading /

Saves/scene/aa.json

Click to expand...

I just saved a scene with a button to load a preset from Saves/scene/aa.json and it seems to work in the current release.

Chokaphi said:

EDIT: Looks like I have a bug that wont let a trigger reload the same preset. Will look into that.

Instead of

Try without the leading /



I just saved a scene with a button to load a preset from Saves/scene/aa.json and it seems to work in the current release.

Click to expand...

For me, it’s not working properly.
When I load a preset using the button from this path → Saves\PluginData\Chokaphi\DecalMaker\Presets\aa.json, it works fine.
However, I’ve discovered another bug:
I saved an empty preset (named Clean.json) that should remove all textures when loaded. But when I tried to apply it on top of an existing preset with textures, instead of clearing them, it duplicated my current textures. This happens when loading through the button.

Also, when I try to load the Clean.json preset directly from the plugin itself, nothing happens at all.
Because of this, I think the preset save/load system really needs an overhaul. Honestly, I don’t understand why something as basic as saving and loading presets feels so messy—it should be straightforward.

At the moment, it seems like you can only truly control the plugin through the UI itself, where you have to manually remove and re-add textures. That’s frustrating and time-consuming.

My suggestion would be to simplify the workflow:

• Focus on making preset save/load reliable.
• Add a clear “Remove All Textures” button directly in the plugin (currently missing from the dropdown menu).

This way, users could easily manage their textures—either clearing everything with one click or loading exactly the set of textures they want.
The slider that makes textures visible/invisible works fine, but it’s too limited for complex setups since it applies to all textures at once, not individually.

In short: overhaul the save/load preset functionality and add a dedicated “Erase All Textures” trigger inside the plugin. That would solve these issues 100%

Waslikethem said:

I saved an empty preset (named Clean.json) that should remove all textures when loaded. But when I tried to apply it on top of an existing preset with textures, instead of clearing them, it duplicated my current textures. This happens when loading through the button.

Also, when I try to load the Clean.json preset directly from the plugin itself, nothing happens at all.

• Add a clear “Remove All Textures” button directly in the plugin (currently missing from the dropdown menu).

This way, users could easily manage their textures—either clearing everything with one click or loading exactly the set of textures they want.
The slider that makes textures visible/invisible works fine, but it’s too limited for complex setups since it applies to all textures at once, not individually.

Click to expand...

There is a clear button at the top right.

Also i think presets are able to stack, so an empty one wouldn't delete/replace the current presets/decals.

Regarding stacking presets i found a bug: if i load some presets on top of each other, single entries get resetted in scale and are bigger than set in the preset.

Electric E-Boy said:

There is a clear button at the top right.

Also i think presets are able to stack, so an empty one wouldn't delete/replace the current presets/decals.

Regarding stacking presets i found a bug: if i load some presets on top of each other, single entries get resetted in scale and are bigger than set in the preset.

Click to expand...

He is wants clear via trigger which I don't think I have created a jsonstorable for

I have one question regarding input images. If i put higher resolution images into the plugin, they look worse then smaller images. Am i doing something wrong? Is there some kind of compression or downscaling going on (perhaps even in VaM itself?) or do you have suggestions for images someone wants to use inside Decal Maker? The pixelation isn't only inside VaM, this is also seen in the exports by DM.

The problem is tied to rescaling an imported image, making it smaller. So the scaling algorithm/method should be the culprit?

I made an example showing the problem, the 4k resolution image gets "pixelated" inside DM (bottom right image) and looks worse than an 1k image:



Also i am almost finished with my first ressource pack. I am a beginner, so i ask myself what would be the perfect workflow creating presets for DM regarding the later correct path - the difference between referencing my local images and later the ones in the var file. At the moment i edit the presets myself with the correct path to the var, but this seems clunky.


Here is a small preview of my first pack if anyone is interested:

Electric E-Boy said:

I have one question regarding input images. If i put higher resolution images into the plugin, they look worse then smaller images. Am i doing something wrong? Is there some kind of compression or downscaling going on (perhaps even in VaM itself?) or do you have suggestions for images someone wants to use inside Decal Maker? The pixelation isn't only inside VaM, this is also seen in the exports by DM.

The problem is tied to rescaling an imported image, making it smaller. So the scaling algorithm/method should be the culprit?

I made an example showing the problem, the 4k resolution image gets "pixelated" inside DM (bottom right image) and looks worse than an 1k image:

View attachment 521184

Click to expand...

By default internally we use 4K RenderTextures but you can change that in the settings menu. The texture is loaded by VAM's ImageLoaderThreaded.QueuedImage routine which I have no control over.

Let me see if I can track down where the problem lies