FiniteSingularity
Member
Apologies- I just saw your two comments.
Can you post a screenshot of what you're describing? I'm not sure I'm fully following what the issue is, and this would help me to troubleshoot/diagnose.
- Thread starter FiniteSingularity
- Start date
Can you post a screenshot of what you're describing? I'm not sure I'm fully following what the issue is, and this would help me to troubleshoot/diagnose.
FiniteSingularity
Member
Yes, I have been working on getting flatpak working with all of my plugins. I thought SGS was one that was already working, but I'll look into it later today.
OtterNas3n
New Member
Not sure if its only me, but sometimes on OBS launch the stroke is not shown, i have to manually change a setting inside the filter back and forth to make it work again.
FiniteSingularity
Member
It is a known bug with Stroke/Glow/Shadow and the latest OBS release. I’m currently working on a fix, and hope to get something out soon.
OtterNas3n
New Member
Hey Finite!
Any News on this? What's the latest version of OBS that did not had this issue? Can't remember but would then rollback to that, as i use the Stroke a lot ^^
FiniteSingularity
Member
Apologies, this month has gotten away from me with work stuff.
In terms of versions that should work OK in the short term, anything before OBS 31.1.0 should work properly.
0x.dt
New Member
Hi Finte,
Thanks for making this! I’m currently on macOS and running OBS v32. I’m using the new Metal(experimental) renderer for performance reasons, but I noticed the plugin only renders when I switch to OpenGL.
I realize Metal support is still experimental and might take extra work to support, but I was curious—should this be expected behavior? Or is it possible to get it working with Metal and I’m just missing something?
Thanks for making this! I’m currently on macOS and running OBS v32. I’m using the new Metal(experimental) renderer for performance reasons, but I noticed the plugin only renders when I switch to OpenGL.
I realize Metal support is still experimental and might take extra work to support, but I was curious—should this be expected behavior? Or is it possible to get it working with Metal and I’m just missing something?
FiniteSingularity
Member
Hi @0x.dt -
Unfortunately, this is the expected behavior. Not all shader features are implemented yet in the Metal renderer, and SGS relies on some not-yet-available functions. As soon as these functions are available, I’ll be working hard to make the plugin work with it.
0x.dt
New Member
Hey Finte, thanks for your reply! This has really sparked my interest in diving deeper into plugin development and even writing my own shaders. I’m trying out some new things and learning a lot along the way!
OtterNas3n
New Member
Hey Finite,
any News on a fix for the disappearing Stroke (Source) on OBS launch?
It's the only thing holding me back to update OBS
Cheers,
Otter
any News on a fix for the disappearing Stroke (Source) on OBS launch?
It's the only thing holding me back to update OBS
Cheers,
Otter
Luciano Ballatore
New Member
Hello, how are you? I'm having a problem with the plugin on the stroke filter and I would like to know if you could help me solve it. Thank you very much in advance.
The problem I have is when importing a collection of scenes, since I had to uninstall and reinstall OBS. And what is happening to me is that in all the scenes and sources where I had the stroke filter applied with a source as the fill type (a video from another scene that is constantly active and running), it seems as if it were turned off.
This didn't happen before reinstalling OBS; in fact, it worked very well. But now I have to go into the filter's configurations to move a parameter to get the filter to turn back on. Furthermore, when closing and opening OBS, the change does not persist. So every time I close and open OBS, I have to reconfigure it.
However, if I create a new scene or source, the filter works normally; it only stops working with the imported scenes and starts working again when I move a parameter like the mask threshold.
I would like to know how I can fix this so that it works again, as I have many scenes involved and creating them again would take a lot of time. Thank you again. Best regards.
The problem I have is when importing a collection of scenes, since I had to uninstall and reinstall OBS. And what is happening to me is that in all the scenes and sources where I had the stroke filter applied with a source as the fill type (a video from another scene that is constantly active and running), it seems as if it were turned off.
This didn't happen before reinstalling OBS; in fact, it worked very well. But now I have to go into the filter's configurations to move a parameter to get the filter to turn back on. Furthermore, when closing and opening OBS, the change does not persist. So every time I close and open OBS, I have to reconfigure it.
However, if I create a new scene or source, the filter works normally; it only stops working with the imported scenes and starts working again when I move a parameter like the mask threshold.
I would like to know how I can fix this so that it works again, as I have many scenes involved and creating them again would take a lot of time. Thank you again. Best regards.
FiniteSingularity
Member
Hi Luciano-
This is a known bug on Stroke/Glow/Shadow related to a change in how sources are loaded in OBS 32. The good news is, I’ve got a working fix and am finishing up testing. I should have a new (fixed) version out tomorrow.
FiniteSingularity
Member
FiniteSingularity updated Stroke Glow Shadow with a new update entry:
Bugfix Release 1.5.3
Read the rest of this update entry...
Bugfix Release 1.5.3
Read the rest of this update entry...
FiniteSingularity
Member
Apologies that this fix took me so long to get out. There is another (more edge case) issue that I've also been trying to fix, and finally decided to do two separate releases. If you're having the issue where your stroke/glow/shadow is not showing on OBS launching until you manually open and adjust a parameter for the filter, please give the new release a try- it should fix this. If not let me know, and I'll investigate further.
StefenTower
Member
Chrome is reporting a virus in 1.5.3. Windows Security is saying Trojan:Script/Wacatac.H!ml was in the download.
FiniteSingularity
Member
Also replied to your post in the QAU thread. Will repeat what I said here, so folks are aware:
Thanks for letting me know. I assume you're using the installer? Unfortunately, for the first few days that a new release comes out, since I don't have an EV signing certificate (I only have an OV cert, as EV certs are quite expensive), the installer sometimes shows as a false positive for a Trojan. If you wait a few days it should go away (and I'll report the false positive to Microsoft, which should speed that up). Its a pretty common issue with OBS plugin installers.
Alternatively, feel free to try the manual install zip method, as this typically wont pop a false positive.
StefenTower
Member
Yes, I was using the installer. Thank you for your response. I'll just set it as Allowed in Windows Security.
Luciano Ballatore
New Member
Thank you so much! The update works perfectly, all my scenes are running smoothly now. I really appreciate it. It’s been a pleasure talking with you. Take care!