StandAlone Player and ViewPort player acts different?

I did know for example that with StandAlone player, it was not possible to use bpy library. But now , when experimenting with Collisions, the results can be different. First, it seems that the order in which the controllers are executed are not the same.

Hi raptor, I never tested this.
I’m using an interaction between the logic bricks, an assassin called logic nodes, which is not in development anymore, and I will try to introduce Eevee on the mix.

It’s getting things done at the moment

@blenderaptor

Have you tried marking the controllers that you want activating before others as INIT (?)

yes, i did. But even so, the result variates depending if it’s Standalone or Viewport. To more precise, the order of objects in HitObjectList is different with the collision sensor.

@blenderaptor

Ah ok. This problem has never happened to so me so I can’t help you :\

You trigger something, with colliding against an object with a property right?
The order of the colliding objects doesn’t matter. As only one have the property he will trigger the event.

i know that. The fact is : the objects i’m colliding with have the same propety. I just want to to give the importance to the last one. sensor.hitObjectList returns a list but obviously ordered different weither standalone or viewport player. Anyway, as long i detected the bug, it’s ok

I would recommend always running in the standalone player, since ultimately it is the runtime in which the game is exported to.

2 Likes