You could try right-clicking the spell, then holding Shift while you click "reparse" in the lower right. That fixed this issue for me from the update last week.Quote:
Originally Posted by hrscarvalho
Printable View
You could try right-clicking the spell, then holding Shift while you click "reparse" in the lower right. That fixed this issue for me from the update last week.Quote:
Originally Posted by hrscarvalho
As 'anathemort' suggests try doing the reparse with shift held. ( Or test via deleting and re-add a spell ) The data 'held' on the character sheet is very different between the DMSGuild and the forge version. ( The forge version data has changes a couple of times over the last week or so, causing extra re-parse requirement of the spells. )Quote:
Originally Posted by hrscarvalho
Also at the moment 'aura' type spells do now function on the forge version, they will be back, but due to a rewrite of how spell tokens are processed with 'hit box area/shapes' I had to focus on getting this back up and working and stable. So some features were not implemented in the change.
As you can see on the current thread, some 'placement' offsets are still happening with 'nephranka' and his game(s), which has not been tracked down yet.
Hope this helps getting things working for you.
I'm guessing you are the host of this game ?Quote:
Originally Posted by nephranka
Spell tokens can not be added by non-host users, so if your machine has an issues every game you host will show the same issue for all users.
When a player drags out a spell token off the character sheet, it sends a message to the host, and the host adds the spell token. So client machines have zero influence on initial placement. If you have an issue on local games, all games you host will have the same issues for you and all players.
We do need to try and figure out why your machine has this issue.
Are you ok with running a couple more test builds with some extra debug outputs and providing the output into the thread ?
Thanks, Pete
I see now. Yes, I would more than happy to run and post some tests.
I have managed to replicate and debug this to a level.. It can get a random 1.5 scale factor, which I just dont know how to get or what its related to, but it seems consistent. I need to do more checks.Quote:
Originally Posted by nephranka
It was doing this issue on my dev machine, which I'm back working on now, was away for some days last week using a spare machine. ( So maybe the spare machine was not fully updates, not sure when the 4.1.5 release was made, but I'm sure I had 4.1.5 on my dev machine before I left and it was not showing the issue. ) And I could not replicate it on the spare machine at the time late last week.
Anyway its got a random 1.5 factor scale now which seems to be working, but the 4.1.5 has also broken the non-hightlight drag of the spell tokens, so I'm doing some tests on that now.
-pete
v5.4 is now released, if you would like to give that a go. It on the 'live' branch, I've removed the test one off the 'test' branch.Quote:
Originally Posted by nephranka
This should resolve the placement offset, and tidy up a database issues that was been reported on a '\reload'
Tried v5.4 same issues nothing changed.Quote:
Originally Posted by bratch9
Not sure how that is the case, is it better or worse now... As I've scaled the drop position by a factor... so in no way should it be the same ? ( it might not be correct, but is it different ?)Quote:
Originally Posted by nephranka
v5.5 added basic aura mode back, if you drop a spell token onto a non spell token they get linked together when you move the non spell token.
( You can drag the spell token away, but if you move the linked non spell token it will try and jump the linked spell token back to the position of the non spell token. )
v5.6 now does aura rotate and scale of the linked spell token when you scale/rotate the non spell token.