Projectile-like RigidBody3D loses it's initial velocity when launched from non-zero position with specific direction

[ImmortalOctogen]

Tested versions

• Reproducible in 4.3.x

System information

Godot v4.3.rc2 - Windows 10.0.19045 - Vulkan (Forward+) - integrated AMD Radeon(TM) R3 Graphics (Advanced Micro Devices, Inc.; 27.20.20913.2000) - AMD A4-9120 RADEON R3, 4 COMPUTE CORES 2C+2G (2 Threads)

Issue description

Sorry for the bad English

I was doing the mechanics of firing physical bullets for my project. When I was shooting in all directions, I noticed that the bullets were quite slow when I shot at the lower and upper angles, equal, as it were, 45 degrees.

Normal velocity, when looking at this direction

Low velocity, when looking at THIS direction

Also, I found things that somehow make this bug disappear. Take a look at Gun.gd script fragment:

func Launch_Rigid_Body_Projectile(Collision_Data, _proj):
	var _Point = Collision_Data[1]
	var _Norm = Collision_Data[2]
	#var _proj = _projectile.instantiate() # IGNORE THIS LINE
	#$bullet_hint.add_child(_proj) # UNCOMMENT THIS
	add_child(_proj) # AND COMMENT THIS, TO ENABLE BUG
	print(_proj.position)
	#$bullet_hint.call_deferred("add_child", _proj) # IGNORE THIS TOO
	
	_proj.position = $"../Gun/bullet_hint".position # ALSO DISABLING THIS = NO BUG
	var _Direction = (_Point - _proj.global_transform.origin).normalized()
	print(_Direction*1000)
	_proj.set_as_top_level(true)
	_proj.set_linear_velocity(_Direction*1000)

The script consists of parts that I didn't write, so it looks bad.
So, is this a bug, or do I not know something?

Steps to reproduce

• Download project, launch
  -- Take into account output and Gun.gd. Script prints some position and velocity at the moment of a shot.

Minimal reproduction project (MRP)

velocity trouble.zip

[ImmortalOctogen]

P.S. bullet does not collide with character body, but scans collision (collision mask)

[ImmortalOctogen]

P.S.2 wrong comment, new:

#$bullet_hint.add_child(_proj) # UNCOMMENT THIS
add_child(_proj) # AND COMMENT THIS, TO ENABLE BUG

[ImmortalOctogen]

After switching to Jolt physics and adding in raycast function:

func Camera_Ray_Cast(_spread: Vector2 = Vector2.ZERO, _range: float = 1000, mask: int = 0):
	var _Camera = get_viewport().get_camera_3d()
	var _Viewport = get_viewport().size
	var Ray_Origin = _Camera.project_ray_origin((_Viewport/2))
	print((_Viewport/2))
	var Ray_End = (Ray_Origin + _Camera.project_ray_normal((_Viewport/2)+Vector2i(_spread))*_range)
	var New_Intersection = PhysicsRayQueryParameters3D.create(Ray_Origin,Ray_End)
	New_Intersection.set_collision_mask(mask)#(0b11101111)
	New_Intersection.hit_back_faces = false # ADDED THIS
	
	var Intersection = get_world_3d().direct_space_state.intersect_ray(New_Intersection)
	
	if not Intersection.is_empty():
		var Collision = [Intersection.collider,Intersection.position,Intersection.normal]
		return Collision
	else:
		return [null,Ray_End,null]

Bug got fixed. So, this is 100% Godot default physics issue.

[CreatedBySeb]

@ImmortalOctogen The MRP is meant to be a minimal project that demonstrates the issue, it seems like you have attached a demo of your game since it contains multiple different scripts and scenes. The additional comments also make it unclear under what exact circumstances the issue occurs and how you have managed to work around it.

Can you create a project with the bare minimum necessary to reproduce the issue? This makes it easier to identify what the problem is and debug it, and many contributors will not want to run a large amount of unknown code from the internet (versus an MRP which is easy to read through quickly).

Also, is there a reason why you are trying to add the projectile as a child of the node that is creating it, rather than just adding it to the root of the scene which would be the more typical approach? (And not require top_level)

[AThousandShips]

Closing due to lack of response, if you provide the requested information this can be reopened