Area 2D: Can't understand what's up (Godot 2.1)

PCMXMS

So, I'm having this issue: the area 2D is not behaving as (I would have) expected. See the figure: <img src="http://i280.photobucket.com/albums/kk172/pcmxms/bug_zpsmays9dlr.png" alt=""> The effect of the big collision shape is to zoom the camera out. In the figure "in game 1", the hero is inside the area 2d collision shape, but there is no zooming out. In the figure "in game 2", the camera has finally zommed out. I don't understand what's happening. Isn't the area2d node supposed to use a collisionshape to define the area? Thanks in advance!

Ross

So the zooming works but doesn't happen when you think it should? Put a print statement in your area_body_enter function and watch the log to see when it happens. Are you changing the collision shape with code at all? We might be able to help more if you post the code you're using.

PCMXMS

<a target="blank" rel="nofollow">Ross</a> said:

</blockquote> Here is the code: 

extends Node2D # member variables here, example: # var a=2 # var b="textvar" var area = null var inside = false var out = 1 var back var state var hero = null func _ready():     area = get_node("Area2D")     back = get_node("/root/Mundo/Course/hero/physics/Camera").get_zoom()     state = back     hero = get_node("/root/Mundo/Course/hero")     set_fixed_process(true) func _fixed_process(delta): #    if inside == true: #        zoom_out() #    else: #        zoom_in()     if area.overlaps_body(get_node("/root/Mundo/Course/hero/physics")):         if inside == false:             hero.inside = hero.inside+1         inside = true         if hero.inside!=0:             state = hero.get_node("physics/Camera").get_zoom()         zoom_out()     elif !area.overlaps_body(get_node("/root/Mundo/Course/hero/physics")):         if inside == true:             hero.inside = hero.inside-1         inside = false #        zoom_in()     if hero.inside==0:         state=hero.get_node("physics/Camera").get_zoom()         zoom_in() #    print(hero.inside) func zoom_out():     if state.x < out:         state=state+Vector2(0.005/hero.inside,0.005/hero.inside)         get_node("/root/Mundo/Course/hero/physics/Camera").set_zoom(state)     else:         pass func zoom_in():     if state > back:         state=state-Vector2(0.005,0.005)         get_node("/root/Mundo/Course/hero/physics/Camera").set_zoom(state)     else:         get_node("/root/Mundo/Course/hero/physics/Camera").set_zoom(back)         pass

The structure of the nodes is "Node 2d--->Area2D--->collisionshape2d". I did what you said (monitor the entering) and it happens in the "in game 2" figure :/. Just to clarify a bit: "/root/Mundo/Course/hero/physics" is a RigidBody2D.I fell I have to apologise for my messy code.

Ross

Hmm, and you're sure the collision shape is the size you think it is? I assume the big light-blue box that shows in-game is a sprite that is supposed to match the collision shape?

PCMXMS

Ross said:

Hmm, and you're sure the collision shape is the size you think it is?

</blockquote> I'm not sure I understand what you mean. Maybe I'm not sure of that. How can I be?

Ross

Oh, sorry I'm stupid. You're using the "Visible Collision Shapes" option to see the shape in-game? I didn't know about that. <img src="https://godotdevelopers.org/forum/resources/emoji/blush.png" alt="blush" height="20"> I thought you had sprites to show them in-game.

PCMXMS

Ross said:

Oh, sorry I'm stupid. You're using the "Visible Collision Shapes" option to see the shape in-game? I didn't know about that. :blush:

</blockquote> Yep. The "in game" figures are in game :P those are "visible collision shapes". That's why I'm confused by this behaviour.

Ross

I see why, that doesn't make any sense. Try turning it off and turning it on again? :P That means "if area.overlaps_body()" is returning true at the wrong time? Did you try connecting the enter/exit events to see if they work properly? I can't imagine they would be different though.

PCMXMS

<a target="_blank" rel="nofollow">Ross</a> said:

</blockquote> Connect these events with the collision shape? Didn't work. Don't know if I understood... again... :P Is it possible that this is happening because of the "Node2D" in the root?

PCMXMS

Yep. It has. I have redone the scene without the node2d (just area2d ---> collision shape) and it worked like a charm.

Ross

Sorry, I'm using the wrong words. I mean connect() the Area2D's signals. body_enter and body_exit. Instead of checking overlaps_body every frame. That's the way I usually do it, since it should be better for performance. I'm afraid I'm stumped too. I guess at this point I would try to make a simple example project to see if there's a bug you can reproduce outside of your game.

PCMXMS

Ross said:

</blockquote> I solved by getting rid of the node2d in the root. Not sure, though, why that happened.

Ross

Was it scaled?

PCMXMS

Ross said:

Was it scaled?

</blockquote> Yes, it was. (sorry about the delay on responding. I had to go work :P)