godotengine / godot

Godot Engine – Multi-platform 2D and 3D game engine
https://godotengine.org
MIT License
90.36k stars 21.06k forks source link

Code complete not working. #87416

Closed Deyaero closed 9 months ago

Deyaero commented 9 months ago

Tested versions

v4.2.1.stable.official [b09f793f5] After testing previous versions the bug could not be reproduced and autocomplete was working perfectly completing properties and methods.

System information

Godot v4.2.1.stable - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 2060 (NVIDIA; 31.0.15.4584) - AMD Ryzen 7 5800X 8-Core Processor (16 Threads)

Issue description

Autocomplete has stopped finishing node properties and methods. I will use animation player nodes as an example. If you type "$AnimationPlayer.p" you should see a suggestion for play and then which animation to auto fill the string but nothing appears for play. This problem has persited through multiple devices and projects which leads to assume that this could be the engines bug. (just so i knew it wasn't the animation player only. cpuparticles also failed to complete the proporties. It wouldn't autocomplete "emmiting" which is important for particle managment and slows down the work flow. Desktop Screenshot 2024 01 20 - 11 08 07 14 Desktop Screenshot 2024 01 20 - 11 08 00 54

Steps to reproduce

Add a root node (2d or 3d) and add an AnimationPlayer node as a child. Create and animation for the node. (could be anything, the problem still persists) and now write the line of code to play the animation, it typically looks like this "$AnimationPlayer.play("_whatever_you_named_theanimation"). Play nor anything past that written will autocomplete. The line of code still works if written by memory with the correct syntax but it harder, inconvinent, and time wasting.

Minimal reproduction project (MRP)

MRP.zip Apologies for not knowing how to create and MRP.

HolonProduction commented 9 months ago

Duplicate of https://github.com/godotengine/godot/issues/86108

dalexeev commented 9 months ago

Thanks for reporting the bug nonetheless!