Plugins Studio Maestro

[hazmhox]

I'm not asking for code review, I asked for both your json files.

Please, show me both your files.

 

[hazmhox]

Please understand that I'm in a very big refactoring of Maestro, and I have not much time to spend on the support right now. I prefer to have the original files to debug myself while I'm refactoring.

 

[AlienAxeMan]

I'm sorry if I've done something to offend you. I thought providing a detailed description of the bug and proposing a simple one line solution would be appreciated, as that's something I would appreciate if it were my plugin. I seem to have miscalculated on that.

I've attached the preset files you've requested.

 

[hazmhox]

I'm sorry if I've done something to offend you. I thought providing a detailed description of the bug and proposing a simple one line solution would be appreciated, as that's something I would appreciate if it were my plugin. I seem to have miscalculated on that.

I've attached the preset files you've requested.

Absolutely not! I'm just very focused on that thing, I want to share it asap as I find it very cool so I might feel a bit blunt, but that's not the case at all.
I'll test the files and check your code afterwards, I'll @ you or mention you if your suggestion was indeed correct : )

Giving you a tiny tease to apologize for my unintended bluntness
(You might understand the scope of it just with that shot)

 

[hazmhox]

Your debug was indeed correct. I fixed by enforcing the FOV at 40.
I'll credit you as a contributor as I will for everlaster on the vector issue.

Thank you for your time and reporting this, this is always welcome to catch potential unwanted bugs!
Did you had any other issues?

To answer to this:

That has not been my experience. VAM properly handles resources in subfolders, detecting them in all cases, including showing that I have downloaded them, avoiding duplicating them, etc. I've been operating this way for years, with no other issues prior to this plugin's error message.

VAM does work with vars in subfolders, but it is not its native design. You (the user) have to make the choice and changes to be in that state. VAM will never move vars in a subfolder. Hence why I don't do additional code.

To give you a bit more perspectives: you can't even fathom the stellar requests I have in private or through discord messaging due to the fact I have quite a few popular releases. I had once a dude asking me to fix/change my code because my plugins rely on var references. That dude decided that the var system wasn't good and extracted ALL vars locally and modified all his scenes to have them work on those local versions... which sounds like an insane endeavour, but well ¯\_(ツ)_/¯
Anyway, he said that my code wasn't obviously handling that situation... and ask for changes, which I refused.

I can't count the amount of person I had asking me for optimizing enviros because they "lagged on VAM"... and all of them had a 3TB install with over 25K morphs. Or the ones that had modified dll versions of VAM that were crashing unexpectedly.

I could go on and on about "modded" aspects of VAM which ended up in requests.

Now, to get back on the subfolder vars, let's say I'd realize a trend is coming true, and like, 7 users out of 10 would have that situation. In that scenario I would obviously consider doing additional code.
But this is not the case, you're the first one raising that behavior... because, let's face it, there are probably 4 people in total in that community who cares about how the var files are ordered

So my motto is "I prefer to spend time on meaningful features". If your case even tho unique, could help you improve the way you're using Maestro, or boost your productivity... whatever, I would definitely consider it. But in that scenario, that's not even remotely the case ^^

When I'm done with the next release, if someday I feel bored... I'll check what I can do for a subsequent patch

 

[hazmhox]

hazmhox updated Studio Maestro with a new update entry:

Studio Maestro 2 Update

View attachment 430347

Studio Maestro 2 is a huge game changer for virtual photography and brings a fully customized Desktop UI.
Here is a (probably) non-exhaustive list of changes:

• Desktop only Custom UI
• Improved VAM vanilla UI design for VR users
• Added several controls for the camera: Exposure, GI, Camera sync to view, Look At rotation...
• Added offset control for the light rig
• Added auto-centering on character for the light rig
• Added a...

Read the rest of this update entry...

 

[cmramlow]

This update is epic! Thank you for all this crazy hard work, hazmhox!

The only update beyond this would be somehow using AI to turn these cool screenshots into photo realistic images

 

[hazmhox]

Funny enough, someone contacted me about that (suggesting implementation with their service and everything). We're not very fond of the idea because we actually love the VAM output AND all those services are a bait to subscribe to something.

But all and all, a feature like this would simply push the final result to a generation service. So this is something you can already do on your own.

 

[zqwvc1419]

~ Hello dude.
~ Since I downloaded your plugin, I know there is such a thing as session plugin in VaM.....
~ Do you know what other plugins are session plugins? Dude.

 

[hazmhox]

~ Hello dude.
~ There are a bunch of session plugins...
~ Like Post Magic for instance. Dude.

Honestly, I can't tell you all the plugins that are session based. That's not the primary way to create plugins nor that it's mandatory to make a session plugin to do stuffs : )