15 July 2017 23:48
Hi there:
I have updated to the new version 17.06 and I am having quite a few problems with my existing projects. Maybe you can help me with some of it. I think I must not be the only one who have noticed it.
I was using a system for the cameras in a first person/third person shooter game I've been working on that involved moving the camera to the various positions using empties. And it stopped working with the new update. I have read the release notes and I've seen something has changed in the camera module, and in the constraints module too.
The problem is I was using append_copy_trans function of the constraints module to append the camera to the empties which in turn are parented to the physic body of the character using append_stiff constraints. It worked like charm in the 17.04 sdk but in the 17.06 sdk it doesn't.
All my intents to make it work in 17.06 were unsuccessful, I have tried with different constraints and without parenting to the empties but all I got was using an append_stiff_cam constraint, which is deprecated to append the camera to the character but it was working very badly, turning as it would have a lot of sensitivity, in turn with the recommended append_stiff function the frame rate would fall to only 7 frames per second I don't know why.
Then I got back to the 16.04 version but I was surprised with a strange behaviour in Firefox, which I've been using for time without a problem and I've seen the workers were getting disabled in the console as the app were being loaded. I don't know if this behaviour is caused by an update of Firefox or what. Previously it worked fine and the physics were logged as using their own thread, I remember.
So, Firefox were not allowing me even debugging which makes impossible to go on with the programming and I have had to change to Chrome. In chrome everything got back to normal, the physics thread working and the camera working right. Just fun again, thankfully.
Does anybody knows anything about this behaviours? I am surprised, mostly but the strange behaviour with the physics in Firefox. It was working with 17.04 until I updated Blend4Web and then when I redownloaded the 17.04 version it doesn't work anymore.
Hope someone can make a tutorial about the right way to use the cameras now as it seems to have changed quite a lot, until then it seems I'll stay with 17.04.
I have updated to the new version 17.06 and I am having quite a few problems with my existing projects. Maybe you can help me with some of it. I think I must not be the only one who have noticed it.
I was using a system for the cameras in a first person/third person shooter game I've been working on that involved moving the camera to the various positions using empties. And it stopped working with the new update. I have read the release notes and I've seen something has changed in the camera module, and in the constraints module too.
The problem is I was using append_copy_trans function of the constraints module to append the camera to the empties which in turn are parented to the physic body of the character using append_stiff constraints. It worked like charm in the 17.04 sdk but in the 17.06 sdk it doesn't.
All my intents to make it work in 17.06 were unsuccessful, I have tried with different constraints and without parenting to the empties but all I got was using an append_stiff_cam constraint, which is deprecated to append the camera to the character but it was working very badly, turning as it would have a lot of sensitivity, in turn with the recommended append_stiff function the frame rate would fall to only 7 frames per second I don't know why.
Then I got back to the 16.04 version but I was surprised with a strange behaviour in Firefox, which I've been using for time without a problem and I've seen the workers were getting disabled in the console as the app were being loaded. I don't know if this behaviour is caused by an update of Firefox or what. Previously it worked fine and the physics were logged as using their own thread, I remember.
So, Firefox were not allowing me even debugging which makes impossible to go on with the programming and I have had to change to Chrome. In chrome everything got back to normal, the physics thread working and the camera working right. Just fun again, thankfully.
Does anybody knows anything about this behaviours? I am surprised, mostly but the strange behaviour with the physics in Firefox. It was working with 17.04 until I updated Blend4Web and then when I redownloaded the 17.04 version it doesn't work anymore.
Hope someone can make a tutorial about the right way to use the cameras now as it seems to have changed quite a lot, until then it seems I'll stay with 17.04.