If I’m understanding correctly, you’d like widgets to be shared across editor types? This would result in being unable to modify particles at the same time, so it would probably be a toggleable setting.
w plugin, can’t believe it’s free lol
1.0.9
Changes
-
ZOffset now uses a step size of 0.1 instead of it’s previous 0.5, to allow for more precise control
-
Attributes now use
EmitCountandEmitDelay(#7)
Fixes
-
Changes to an instance name now update topbar buttons correctly (#5)
-
Values inside the NumberSequence editor are now rounded to 3 decimal places in the interface. (#4)
-
Yet another experimental fix for a potential recursive state error. If the issue arises again, let me know… (#3)
-
Context menus now work again on properties in the instance tree. (#6)
This is a relatively experimental release, I haven’t tested that extensively - if you notice any issues, please let me know.
2 Likes
As a former VFX artist, this has to be one of convenient plugins to use eeveeerrr…
Nice release!!
The error when trying to store a texture in the library is still persistent, it only seems to be happening to certain textures however. Otherwise its a great plugin!
I’m also having the same issue, where certain textures tend to freeze or significantly alter my studio’s performance when trying to store them.
There is also a problem that occurs when I add new textures, in which you sometimes get redirected to the homepage when putting a new texture, then the texture won’t show up unless you expand the size of the plugin (mine was on the left side of the studio window)
At first when this happened, scrolling down didn’t work either with my trackpad at first (no scroll bar appeared until I made a new texture)
(I was using a MacBook Pro + Trackpad scrolling at the time)
I’m afraid I’ll have to chalk it down to Fusion 0.2’s state management (and 99% a mistake on my end that makes it even harder to debug) then - I’m out of ideas when it comes to solutions for this.
At some point, I plan to update my component library and the plugin to Fusion 0.3, which should make these issues more obvious and allow me to patch them, while also encouraging better state management (=better performance, generally).
This is a monumental task however, and I won’t be able to do so for the foreseeable future as I’ll have to practically redo all underlying libraries and the plugin itself.
Did you yourself run into this issue? Or maybe this issue only happens on certain systems?
I can reproduce it unreliably, weaker systems do appear to cause it a lot easier through.
I’ll give my specs for reference if it would help at all, I have a pretty powerful pc.
CPU: AMD Ryzen 7 3700x (8 Core)
GPU: AMD Radeon RX 6950 XT
RAM 64GB ddr4
I have noticed that using ctrl+v causes the error more frequently than if you type in the asset id manually.
1 Like
I agree, most of the time when I use the ctrl+v function to apply the ID, that’s when the occasional freezing loops would happen.
I have found that the crash never happens (atleast for me) if the vfx editor is locked in as a tab in studio and not yust floating by itself. I was able to import around 20 textures without any error.
Thank you for making this amazing plugin, I am currently having issues with it crashing each time I attempt to add a new texture to the storage and I am not the only one with the same issue…
The plugin is really good! So is the UI