queue_redraw not running the _draw function

Ironfort

Currently working on a reticle that changes sizes after a user hovers over it, at the moment I have the camera controller script calling a function inside of my reticle draw script which eventually calls a queue_redraw. I have checked and every step of the process runs, but when it comes for the _draw function to run, it simply doesn't?

Code currently looks like this:

Function inside of camera controller that calls function in reticle_draw:
camera_controller.gd

func _interact_cast():
	...
	if current_cast_result != null:
		if current_cast_result.is_in_group("Grabbable"):
			reticle_draw.set_crosshair_radius(10)

Function in question inside reticle_draw:
reticle_draw.gd

func set_crosshair_radius(new_radius):
	radius = new_radius
	update_crosshair()

Which calls the following function:

func update_crosshair():
	print(radius)
	queue_redraw()

Any clue what could be going wrong with the script?

xyz

Ironfort Post your scene hierarchy and also _draw() code.

Use ``` or ~~~ tags to properly format code blocks.

Ironfort

xyz

func _draw():
	print("drawing")
	draw_circle_crosshair()
	

func draw_circle_crosshair():
	var gap_rad = deg_to_rad(gap_angle)
	
	var arc_segments = [
		# Bottom-right quadrant
		[gap_rad / 2, PI / 2 - gap_rad / 2],
		#Bottom-left quadrant
		[PI / 2 + gap_rad / 2, PI - gap_rad / 2],
		# Top-left quadrant
		[PI + gap_rad / 2, 3 * PI / 2 - gap_rad / 2],
		# Top-right quadrant
		[3 * PI / 2 + gap_rad / 2, 2 * PI - gap_rad / 2]
	]
	for arc in arc_segments:
		var start_angle = arc[0]
		var end_angle = arc[1]
		
		var points = []
		var angle_step = (end_angle - start_angle) / segments
		
		for i in range(segments + 1):
			var angle = start_angle + i * angle_step
			var point = Vector2(radius * cos(angle), radius * sin(angle))
			points.append(point)
			
		if points.size() > 1:
			draw_polyline(points, color, thickness, true)

xyz

Ironfort What gets printed? Also why is reticle_draw.gd a tool script?

Best to make a MRP. Sources of problems like this often become apparent in the process of making it.

Ironfort

xyz The script is a tool script since the tutorial I followed claimed it would allow me to see the reticle inside the editor (Couldn't get it to work), also could you explain to me what an MRP is?

xyz

Ironfort MRP is a minimal reproduction project - a fresh project that only contains the problem reproduced with minimal means.
https://stackoverflow.com/help/minimal-reproducible-example

Toxe

Ironfort also could you explain to me what an MRP is?

https://en.wikipedia.org/wiki/Minimal_reproducible_example

Basically a project that is trimmed down to the essential parts and that you can upload here, if you don't want to upload your real project.

Toxe

update_crosshair is getting called as well and prints the radius?

Ironfort

xyz

Toxe

reticletest-2025-08-06-19-05-40.zip

21kB

Here, I think I removed most of the unecessary stuff from the other build. All the commented prints are just debug so I could figure out where it was that the code was failing on.

DaveTheCoder

Toxe Basically a project that is trimmed down to the essential parts and that you can upload here, if you don't want to upload your real project.

Even if you're willing to upload your real project, an MRP is preferred.

xyz

DaveTheCoder Even if you're willing to upload your real project, an MRP is preferred.

👆️

Ironfort

DaveTheCoder What I sent is the MRP version, the project itself was mostly empty, I copied the code I felt was necessary and so it wouldn't break anything, meaning just the camera, raycasting and draw. As well as a bare bones level to check if the reticle change works.

Toxe

DaveTheCoder Even if you're willing to upload your real project, an MRP is preferred.

True. What I was thinking about were basically simple beginner projects that already are pretty small so it doesn't really matter. But you are right.

xyz

Ironfort What I sent is the MRP version

It isn't really. The idea behind MRP is to re-create the situation that causes the problem from scratch, using only what's minimally needed. You build up to the problem, not strip down from the problem. This can often help you yourself figure out where's the issue.

Ironfort

Fixed it by changing the location of the UserInterface scene and all its nodes into the PlayerController scene, then linking the reticle_draw script into the camera_controller script via a reference call.

There most likely are better options than this, and options that allow for doing this using two different scenes, but I know jack shit about this engine and as such have no way to figure that out

xyz

Ironfort If there were problems with node paths, the engine should have reported that in the debugger at runtime.