#v10 issues
1 messages · Page 1 of 1 (latest)
That looks to be same error repeating for the most part.
yeah i noticed that also
RollPF$1 bug will be fixed with PF 0.82.2
The other errors are complaining about attributes.hd.total missing on the actor for some obscure reason.
Do you have some error earlier than these?
Guess not..
no i just booted it up, updated... i knew there would be issues since i was using my laptop earlier as a testing ground...
heres a expanded view of one of the errors
sorry just removing my URL
uno momento
I think someone else will have to jump in about the HD total missing. I have no clue right now why it would be happening or how to fix it.
np, i wouldnt even know where to begin
but if i can help atleast show things that are happening and bring it up to fix then.. ya know
so imma pop this stuff in here as well, sent it in the troubleshooting channel and im unsure if they know what to do with it
The first was with a existing scene that i was rescaling to a rescaled webp. It ended up just being better to recreate a scene and work from scratch. Eventually it started giving me issues as well. the second image with the token it would give me a error even if i hit the Alt button
a video of the error in real time
@frigid basin Since you've been active lately, could you take a peek at all this? It's beyond me.
Is that with any active modules? Can the error be reproduced in a new world when importing the scene? Would you be okay with me taking a look at the live world (this would require creating a user for me and giving me access to debug things)? It's okay if you're not on board with that, it might make checking out what goes wrong significantly easier though.
There are a few places where the system has the potential to interfere with PIXI, and that error message is borderline useless when it comes to determining what exactly goes wrong – it's pretty much a generic error signalling that a step was forgotten or taken in the wrong order (in the system, or core Foundry for that matter).
I modules activated
Yup. One sec
Update for @twin pond: I took a quick look around and given that scenes had non-default opacity settings, I decided to blame core Foundry (https://github.com/foundryvtt/foundryvtt/issues/8102).
Well that's obscure. Fixable with a macro, I presume?
The issue does not persist through reloads IIRC, so it should be possible to change the scene config, save changes, and reload.