Collisions and destructibles

[biox86]

I just tried the project and took a look at the various nodes but I can't see any collision for the fornitures and any kind of destruction like in the preview video. Is the video recorded with a more advanced version than the one in the repo or am I missing something?

Anyway, thanks for this template, it's gonna be a great use case study!

[Nodragem]

Normally the master branch has the destructible pieces of furniture.

If you open level2.tscn, you should see the collision boxes of all the objects, like here:

Here I selected one of the cube, if you want to see more of what is being the scene, you would right-click and select Editable Children and you should see the rigid body and collision nodes:

I add these nodes and set them up during the import (i.e. post_import callback), hence if you drag and drop the .glft file (res://assets/prototype_bits/Cube_Prototype_Small.gltf) in a scene, it will immediately appears with the nodes that makes it destructible.

The post_import function is in res://tools/automation/import_destrutible.gd if you want to have a look at it.

[biox86]

Ok, I did a fresh clone of the repository, but at first launch Godot tells me that res://tools/automation/import_destrutible.gd has parse errors.

The strange part is that if I open the file it has no errors at all.

Reopening the project doesn't give the error anymore, but level1 and level2 still have no collision nor they are generated while importing any gltf.

I also cannot see where the file import_destrutible.gd should be called. Should it be an autoload that maybe has been removed be the parse error during the first open?

I forgot to tell, I'm Godot 4.3 beta1 on OSX.

Thanks in advance for your time.

[biox86]

I'll attach one more image to see better there no collisions are generated.

[Nodragem]

Hello! Thank you for the useful screenshots.

I had a look at the problem this morning, I cloned the project on another laptop, using Godot 4 beta1, and I successfully replicated your issue and found a walk around 😃 !

Issue

The issue is due to using a helper class CollisionTool (to keep my code organised) in import_destructible.gd. It looks like a Godot bug, which I will report. Basically, on the first start of the project, Godot seems to try importing the scenes before to have registered the static functions. Hence, it flags import_destructible.gd has containing a Parsing Error, which is to reference a non-existing CollisionTool class. See the 2 first lines in red below:

Walk Around

For now, you will need to follow this steps:

• start from a fresh clone of the repo
• load the project once
• go in Project > Reload Current Project
• in the FileSystem dock, find and open the folder res://assets/prototype_bits
• reorder by type (to make next step easier)
• select all file ending with .gltf
• right-click and select reimport

Now you should see in the Output tab that the destructible script was added to many objects. If you open level2.tscn you should see that the furniture are now Node3D with a script.

Meanwhile

I will report the issue to Godot repo, and I might remove CollisionTool for now (and have a slightly less organise code).

[biox86]

Great, I just tried to reimport the assets and now everything works as expected.

I started digging into the code: first of all congrats, it's pretty neat! Just looked how importing and setup collision works and it's really useful especially in the first phases. Now I'll continue taking a look and eventually open another discussion with a few things.

At the moment I just have a doubt about a queue_free ordering choice and I found an unused signal definition ( probably you changed something and you forgot that ). Anyhow I prefer to look at everything, so if there's a few little things It could be better to discuss them in a single place instead 10.

Thanks again for the super fast answer! Glad to have been useful ( and sorry, I've been stupid, I could have copied the entire output on first launch but I hadn't thought about that... darn ).

[Nodragem]

No worries, a full review of the code and how to improve it is really welcome. It is a project for me to learn how to use the engine and hopefully be used by others as a working, although not perfect, example.

[NeonfireStudio]

Why showing an error in extends ConditionLeaf

[biox86]

You need to install beehave. Just click on assets, search for beehave, click download and reload the project.

[BitterArtist]

When I run the game in the Godot editor the enemy behavior works fine(Beehave plugin is installed and enabled), but when I export a Windows executable and run the game directly the behavior is not working - they just stand around and never chase or attack the player. Do I have to specifically enable the plugin when exporting?

[Nodragem]

Hello! sorry for the late reply. I just tried to export the project to a Windows executable and it seems to work. From reading about it, it seems that if the export mode is set to "export all ressources in the project", it will export the add-ons as well:

Can I ask you to open a separate issue if this is still happening?

[BitterArtist]

I think it was an import issue, because I didn't really change anything but I re-imported the project and it's working properly now.