#Sequencer AttachTo+StretchTo
1 messages Β· Page 1 of 1 (latest)
This is the macro I execute to attach the "rays"
const target = game.user.targets.first();
new Sequence()
.effect()
.file("jb2a.energy_beam.normal.bluepink.03")
.attachTo(token)
.stretchTo(target, { attachTo: true })
.belowTokens()
.persist()
.play()
Nope, this is on a droplet on digital ocean
Okay, so does it happen with just one attached effect?
I'm still waiting for the reload π
I't went out of memory before I had time to remove all the effects
Seems like your hunch was correct
It does not happen with zero attached
it does not happen with one
but, it does with two
Interesting, I'll take a look and see if I can't reproduce it. What's your system specs btw?
Running bleeding edge chrome on windows on a desktop with 32GB ram, a 4Ghz Intel Core i7 cpu, and a Geforce GTX 1060 3GB gpu
Yeah gonna be hard for my 3080 to reproduce the problem π
I'll give it a shot, it really shouldn't crash, never had that
The scene has 13 of the generic fire from JB2A
as tiles, several animated lights, and yeah, the energy beam as well from JB2A
That might be it
Try an empty scene with three attached effects
You're basically forcing your browser to play 16 YouTube videos at the same time
hehe.. the BBEG scene is supposed to be epic.. maybe not..gpu crashable epic.. I'm trying an empty scene now
So yeah. Same thing
Well dang, I'll give it a go when I've got some free time
Cool π
I'm on v2.1.14 of sequencer and v9b269 of foundry here
I'll double check on v10 as well
If the order matters, the "attach to" are the outer ones, and the "stretch to" is the central one.
Same effect on Foundry v10.285 with sequencer 2.3.5.
Good luck hunting πͺ² π
I'm off to bed
@karmic harbor
So I think I managed to fix this, but it's an expensive solution; I basically have to preload and precreate each individual file in the attached sprite so that I have the sprites ready to go when I switch over to them
Was it race conditions?
Nope, basically videos in chrome are stupidly slow to buffer
or rather, slow to start buffering
Which means that if I try to call play on the video before it has started buffering, the entire tick method of the effect was blocked
and with enough of that happening at the same time, the entire pixi render engine fell over, for some reason
π
But if I pre-create them, it seems fixed?
It's not perfect, but it stops the crashes and effects getting stuck in space
the effects themselves still stutter, due to that buffer issue
I tried to have a shared sprite video texture for multiple of my sprites, but then their video start/pause was linked
Yep, that's why I have to spawn multiple videos for each sprite
Which is why it's expensive
If you can, I would recommend using a specific range increment for the dual attached effects
like 30ft
I was talking to pixi devs about it and their response was .. have you heard about spritesheets?
Will do.
SpriteSheets? For high quality transparent webms? π
hehe. yes. even showed me a way for how to automatically render the webms into sprite textures
wot, please do show? π
Not super detailed but still π
For my short animation sequences for the birds it would even be plausible. I opted for another way out though. I load the video a couple of times and assign the birds to different groups. It didn't take more than 3 groups to get rid of the synchronized look
Btw. I didn't say it before, but Sequencer is awesome work π
Did you look into how much work it is to create localized sounds?
I have not, but that sounds like an interesting idea
Let me know if you'll do it, or I'll look into the work needed to do a pull request on it βΊοΈ
I'm open to pull requests, so please do! I like collaborating with people π
Sequencer is open source, after all! π
I just have to get my two last modules over to v10 first ,π
@karmic harbor Could you try installing this pre-release, and give it a shot again?
https://raw.githubusercontent.com/fantasycalendar/FoundryVTT-Sequencer/next/module.json
I can do that. A bit later though, my kid is hogging the computer on Valorant
This version is confirmed to be CrashFreeβ’οΈ
Nice, great news