need help understanding instances better

This is a READ-ONLY snapshot of the Godot Community Forums when TwistedTwigleg was the owner, which is hosted for archival reasons only. The current Godot Community Forums can be found here.

Some links may point to external websites, including the current Godot Community Forums. These websites are not associated with TwistedTwigleg.

need help understanding instances better

jbskaggs

I rewrite my game using hex grid scenes.

Basically a bunch of instances of one scene.

The problem is that mouse entered and and mouse leave work fine. But mouse clicks are weird. Some instances will accept clicks others will not, and some will return the global_transform for another instance not selected. I have been working on this for couple of days and my kidney pain and insomnia is not making thinking easier.

collisions work.- but clicks are spotty and erratic.

Is this because every scene is an identical instance?

here is the script:

extends Spatial


# Declare member variables here. Examples:
# var a = 2
# var b = "text"
var placeme=false
var towertype


# Called when the node enters the scene tree for the first time.
func _ready():
	pass # Replace with function body.


# Called every frame. 'delta' is the elapsed time since the previous frame.
#func _process(delta):
#	pass
   
   
func _on_Canplace_area_entered(area):
#	print("area name: "+str(area.name))
	
	
	match area.name:
		"ShooterCursor":
			$dirt.hide()
			$grass.show()
			placeme=true
			towertype='shooter'

			
		"HealerCursor":
			$dirt.hide()
			$grass.show()
			placeme=true
			towertype='healer'
#			
		
		

func _on_Canplace_area_exited(area):
	if area.name=="ShooterCursor" or area.name=="HealerCursor":
		$dirt.show()
		$grass.hide()
		placeme=false


func _process(delta):
	if get_parent().get_node('ShooterCursor').visible==false and get_parent().get_node('HealerCursor').visible==false:
		$dirt.show()
		$grass.hide()
		placeme=false



func _on_Canplace2_input_event(camera, event, position, normal, shape_idx):
	if (event is InputEventMouseButton):
				if (event.pressed == true):
					if event.button_index == 1:
						if towertype=='shooter':
								get_parent().get_node('ShooterCursor').hide()
								var newtower=Global.shooter.instance()
								newtower.global_transform = global_transform
								Global.current_gold-=Global.shooter_cost1
								newtower.add_to_group("towers")
								newtower.show()
								get_tree().current_scene.add_child(newtower)
								
						if towertype=='healer':
								get_parent().get_node('HealerCursor').hide()
								var newtower=Global.healer.instance()
								newtower.global_transform = global_transform
								Global.current_gold-=Global.healer_cost
								newtower.add_to_group("healers")
								newtower.show()
								get_tree().current_scene.add_child(newtower)

xyz

Check if there is no overlap between collision shapes. Maybe there's a bug in parts of code that generate the hex grid. Try to enable Debug->Visible Collision Shapes to see if everything is looking right.

Erich_L

@jbskaggs said: I rewrite my game using hex grid scenes.

This put a big grin on my face! Remember clicks in 3d space are basically ray casts from the camera, but aside from the 3d geometry, they can also get blocked by UI elements if you're not careful. When you said "spotty and erratic" I too thought of overlap. Could there be two hex tiles in one place on accident? Or a rogue bunny with a misshapen collision shape?
Don't trust those marbles either. Who knows what they're up to. Especially those pukey ones.

jbskaggs

@Erich_L said:

@jbskaggs said: I rewrite my game using hex grid scenes.

This put a big grin on my face! Remember clicks in 3d space are basically ray casts from the camera, but aside from the 3d geometry, they can also get blocked by UI elements if you're not careful. When you said "spotty and erratic" I too thought of overlap. Could there be two hex tiles in one place on accident? Or a rogue bunny with a misshapen collision shape?
Don't trust those marbles either. Who knows what they're up to. Especially those pukey ones.

Hmmm. No overlapping tiles. When a rabbit is placed he does have two collision areas. I wonder if his collision area is blocking surrounding tiles. This gives me some direction though.

jbskaggs

Alright I have two collision actions needed on these tiles. mouse enter /exit and mouse button input

Today when I booted up and started working all the tiles quit receiving and mouse inputs. So I hide everything and found thru trial and error that my mouse click input collision is blocking my mouse entered. disable the mouse input and the enter and exit work. Enable and they quit.

Currently I had two collision areas and two collision shapes on the tile. (tile is not the right word this is just an instance I use as a tile)

the first one I used to have signals: mouse entered, mouse exited, and mouse input

but It would not get mouse clicks

so I added a second area and deleted the mouse input signal from first area and added signal to second area.

This sort of worked for a long while. But then it all started getting more buggy. Until today when I could no longer receive mouse enter / exit signals with the second area's mouse_input signal active and had to disable it to turn mouse enter back on.

So now I am trying to figure out how to do what I need. This was why in the original 3d version of my game I was not using tiles or instances because I hit this problem before and gave up.

Seriously this makes me feel like a simpleton- I've designed multistory buildings, million sq ft malls, chemical factories, written novels, built intricate furniture, and built robotics and now I cant make a stupid obj turn green when I hover over it and create an instance when I click on it without messing it up. I have the same feeling I did when tried to play Dark Souls- I got my ass kicked- over and over and over.

And this is simple beginner stuff to boot.

xyz

area_entered signal doesn't happen when mouse enters the area. It happens when another area enters the area. If you just want to check if mouse entered the area you should use mouse_entered signal.

Since your area_entered fires, I'm assuming you are dragging a rabbit area along with the mouse cursor and it generates the signal. You should eliminate/disable colliders from rabbits when placing them. They are probably picking up click events, and blocking them from reaching tiles.

jbskaggs

@xyz said: area_entered signal doesn't happen when mouse enters the area. It happens when another area enters the area. If you just want to check if mouse entered the area you should use mouse_entered signal.

Since your area_entered fires, I'm assuming you are dragging a rabbit area along with the mouse cursor and it generates the signal. You should eliminate/disable colliders from rabbits when placing them. They are probably picking up click events, and blocking them from reaching tiles.

I had already switched to mouse_entered and suspected it was the rabbit. So I changed to testing using only mouse cursor. And the problems I described above occurred. Just now I retested if I have the two signals. And I am back to some tiles receive signals some dont. Im searching the game now looking to see what else is blocking the input.

xyz

Ideally you should only have one area per tile, and preferably with only one collider. Try to first test if a single instance operates as expected, then try with two instances, then with many.

jbskaggs

Using your method of testing I now have the tiles working properly, and discovered that after I place a tower it can block collision to the tile next to it. SO I need figure out how to disable the tower's collision while the towercursor is active.

So would this be a good use of the collision layer then?

xyz

Not sure if layers would be of any help here. Simply set input_ray_pickable property of rabbit's area to false.

jbskaggs

Hey that worked! Well back to the bug that led to this series of bugs. The targeting of marbles.

This improved my morale though. I had gotten frustrated.

Erich_L

Ah I feel bad I should have thought of this because I had the same problem for quite awhile making my grid based game. When dragging an object around I had to disable the input_ray_pickable bool on all the other objects on the grid that would get in the way.

jbskaggs

no prob!

My constant pain makes me more susceptible to anger and frustration at things I shouldnt get upset about

Erich_L

Let the anger flow through you =D. Am I smelling an update coming soon? =)

jbskaggs

Yes kinda Im packaging a winexe file as Im typing this. I really only have one major bug left and that's the rabbits don't track the marbles and shoot properly. But Im posting this tonight to see if the placing rabbits functions.

The background tiles are Kenny's creations. So more of placeholders now.

My wife saw I was struggling emotionally when she came home from work and took me out for chinese food. This was nice. Now I am feeling better:)