Plugins + Scripts VAMStory

[hazmhox]

Fair enough.
Thanks very much for your input. I’ve got it working on an old scene of mine. I think I just copied a sub scene or something across and edited it there. I’m currently struggling to get it working again but I know it’s possible.
I wouldn’t know how to set up the post process myself so I’m getting a little lost as I can seem to successfully copy it across again regardless. Congrats on the plug in.

You just need to have either Post Magic or Moyashi enabled on an empty atom on the scene ^^
It's quite easy! If you can't figure it out, ask : )

 

[DeadMaroz]

Is it possible to add Render Layer global option to main VAMstory and Actions plugins? Would be grateful))

I want to make UI behave like it belongs to screen space - not affected by postprocessing or light. And render over any objects in worlds space, and be clickable. Before version 30 it behaved like that (if post processing plugin was added to the scene). That bug (as for me, it was a feature ) was fixed in v31.
Or it can be implemented different way and i missed something?

 

[hazmhox]

Read the last messages : )

 

[DeadMaroz]

Read the last messages : )

Yes... I didn't read carefully. Then I'll stick with version 30 for now, with this wonderful bug. The solution is a bit cumbersome with attaching to the camera, but it works.

 

[AWAKENING]

It's AMAZING!!!!
This update is definitely a milestone update - the ability to customize the position and size of the UI is really crucial.
Do you have any plans to make it compatible with older VAM version?

 

[hazmhox]

Do you have any plans to make it compatible with older VAM version?

There is no reason for me to handle older version of VAM as there is no downside updating it.

When VAMS came out two years ago, VAM was pretty much in it's final form and nothing changed pretty much. The only aspect that improved the UX overall is the alert system (which is an excellent way of giving feedback to the user). Making it compatible with versions prior to that would mean I'd need to code custom alerts and feedback for the users.

This would only be an interesting move if everyone was doing that (ie, all other plugins from different creators)... which obviously, is not gonna happen. This means that I would need to inject hours for a simple feature that does not change much in the grand scheme of things, when most other plugins will still require you to have at least the 1.20.77.13

This also means that it means that I'll need to code something for versions of VAM that were release prior to the original VAMStory release. Which means two things :

• If you're playing a scene older than VAMS release : it's impossible to have VAMStory in it
• If you're you're playing a scene older than 1.20.77.13, you can keep the old plugins versions

I know, I know... you're gonna say that you could update an old scene and put VAMS in it. But at this point, I think I'm expecting any creator upgrading a scene, to target players that have an up to date VAM. I've been maintaining some of my plugins for almost 5 years now, and I'm moving forward for people still supporting VAM and people still playing VAM on a daily/weekly/monthly basis.

If you prefer, that's like if you were asking to have Photoshop 2025 with all it's feature... but running in Windows 3.1.

And to be completely transparent, I prefer investing time and ideas in cool updates for the current VAM version, than making it compatible for 3 persons still on VAM 1.10.
If you prefer, that's gonna be a bit blunt... and I know every single bucks count for some people, but if you can't put 8$ to update VAM once every two years, I'm really sorry for these persons but I have to be pragmatic

All my plugins handle legacy content and have pretty much zero breaking changes as much as I can, and the hub allows you (if you want) to keep the historical versions to handle older scenes. You have everything at your fingertips to still enjoy old content ; )

 

[AWAKENING]

There is no reason for me to handle older version of VAM as there is no downside updating it.

When VAMS came out two years ago, VAM was pretty much in it's final form and nothing changed pretty much. The only aspect that improved the UX overall is the alert system (which is an excellent way of giving feedback to the user). Making it compatible with versions prior to that would mean I'd need to code custom alerts and feedback for the users.

This would only be an interesting move if everyone was doing that (ie, all other plugins from different creators)... which obviously, is not gonna happen. This means that I would need to inject hours for a simple feature that does not change much in the grand scheme of things, when most other plugins will still require you to have at least the 1.20.77.13

This also means that it means that I'll need to code something for versions of VAM that were release prior to the original VAMStory release. Which means two things :

• If you're playing a scene older than VAMS release : it's impossible to have VAMStory in it
• If you're you're playing a scene older than 1.20.77.13, you can keep the old plugins versions

I know, I know... you're gonna say that you could update an old scene and put VAMS in it. But at this point, I think I'm expecting any creator upgrading a scene, to target players that have an up to date VAM. I've been maintaining some of my plugins for almost 5 years now, and I'm moving forward for people still supporting VAM and people still playing VAM on a daily/weekly/monthly basis.

If you prefer, that's like if you were asking to have Photoshop 2025 with all it's feature... but running in Windows 3.1.

And to be completely transparent, I prefer investing time and ideas in cool updates for the current VAM version, than making it compatible for 3 persons still on VAM 1.10.
If you prefer, that's gonna be a bit blunt... and I know every single bucks count for some people, but if you can't put 8$ to update VAM once every two years, I'm really sorry for these persons but I have to be pragmatic

All my plugins handle legacy content and have pretty much zero breaking changes as much as I can, and the hub allows you (if you want) to keep the historical versions to handle older scenes. You have everything at your fingertips to still enjoy old content ; )

I got it! Thank you so much for your contributions to the community!