Jump to content

[TOPIC: topicViewTemplate]
[GLOBAL: userSmallPhoto]
Photo

Emitters work fine in build 2017.3184 but behave strange in 2018.3280
Started by elvo May 19 2018 08:09 AM

2 replies to this topic
[TOPIC CONTROLS]
This topic has been archived. This means that you cannot reply to this topic.
[/TOPIC CONTROLS]
[modOptionsDropdown]
[/modOptionsDropdown]
[reputationFilter]
[TOPIC: post.html]
#1

elvo

[GLOBAL: userInfoPane.html]
elvo
  • Enthusiast

  • 43 posts
  • Corona SDK

I recently updated Corona from public release 2017.3184 to daily build 2018.3280. I noticed that in all our apps the emitters behave strange when the "camera" moves or if the object, on which the emitter is inserted, moves.

 

I have attached 2 videos showing the same scene, one is run with 2017.3184 (correct) and the other with 2018.3280 (wrong). The shine effect of the gold works with an emitter which is inserted in the chest display group. In the "wrong_behaviour.mov" notice how the shine particles escape the chest as if they have some kind of render delay. In the "normal_bahaviour.mov" the particles' position relative to the chest, remains the same.

 

A similar issue appears in all our apps and in all uses of particles. The case shown in the video is just a minor one, in some cases the effect is unacceptable.

Attached Files



[TOPIC: post.html]
#2

Rob Miracle

[GLOBAL: userInfoPane.html]
Rob Miracle
  • Moderator

  • 25,684 posts
  • Enterprise

We updated emitters in 3199 to behave better in groups. See:

 

https://docs.coronalabs.com/api/type/EmitterObject/index.html

 

Also, you can look at this demo project: https://github.com/coronalabs/demo-emitter-absolutePosition to get an idea of what they changes were.

 

Rob



[TOPIC: post.html]
#3

elvo

[GLOBAL: userInfoPane.html]
elvo
  • Enthusiast

  • 43 posts
  • Corona SDK

Thanks Rob, we made all necessary changes to have our emitters work as they did before.

 

However, I need to say that it would make more sense if this update to the emitter functionality was backwards compatible, no? I mean, it's always welcomed to find new cool features and customizations, but it would be great if the existing projects were not afected by such changes. We've had similar issues in the past with new Corona features that were not backwards compatible. As a result, mysterious bugs were introduced in our apps after building with newer versions.

 

Could you please discuss this with the development team? Thank you!  




[topic_controls]
[/topic_controls]