Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Support / Updates / Realistic Big Environments

A topic by WungielPolacz created Feb 05, 2024 Views: 169 Replies: 6
Viewing posts 1 to 6

Hello, I have a couple of questions. As I seen videos and screen shots. There was only stylized graphics environments. Can I make with this plugin without any problems big realistic for example forest environments? Using realistic trees models, bushes, rocks etc? I have also question if plugin is including collision to all objects by itself? Or I have to use placing scenes (where for example is tree model with collisions)? Actually I want to use this only for making realistic big environments. Can it handle it? Is it stable with high quality textures, models, animations etc? Or it's just for stylized graphics?


I have also question about support and updates. Are you still updating and supporting it? Can we for sure expect support for some years yet?

I think that's all. Thanks for respond from advance.

Developer (1 edit)

Hey WungielPolacz! The plugin itself should neither have too large of a performance footprint on your development nor should its use be encumbered much when using high-fidelity assets. What you have to take into account though, is that Godot itself  (and other Engines as well) needs to be able to handle all assets that are used. If your scene would, for example, have a thousand realistic trees, that are just instanced as nodes (which the plugin does), you will eventually notice your speed tree to go down, and your frames drop, if you do not take any optimization measures (using LODs, editing with lower viewport resolution, etc.). Hence, if you place an asset that takes a few seconds to instance, than AssetPlacer will be as slow as Godot. If you had no problems using these high-fidelity assets in the quantities you need so far, AssetPlacer should handle them fine. One thing to note, however, is the size of libraries. The more assets, and the more complex they are, the longer loading their thumbnails will take. I recommend having no more than a hundred assets per library. As for surface placement, your objects have to include collisions, as of AssetPlacer 1.2.x.


Regarding the support and updates of the plugin, I can assure you that it will continue, and is in my professional plans for at least this and next year. You have to take into the account, that as of this year, I am still a university student, maintaining this project on the side, and I like to also do not-for-profit work, like contributing to the Engine (I recently worked on Godot's AnimationPlayer) and making free plugins.

I hope this clarifies your doubts, and I could maybe convince you to give AssetPlacer a try! If you have any more questions, please go ahead.

~ CookieBadger

Hey CookieBadger. Thanks for very fast answer. So I see I don't have any other option than buy this plugin. I tried other plugins like that, but no one was working as I expected. I think with this plugin will be different.


Actually I have one more question. Can I use this plugin to make some linear close levels to horror games? Like, I can, but if it's convienient? Or I should use some other plugin to more advance making small, close and linear rooms / areas where player can move etc?

Developer

Of course the plugin does not only help for large open environments, but is very useful for small environments as well, especially if you are using modular assets (e.g. Tile-based dungeon).

Hey CookieBadger. I just bought this plugin, and I have problems with painting assets. And I didn't see any tutorial for this plugin (maybe you should create?). I am clicking Left Mouse Button and trees are not placing. I did everything like you wrote. Added it to addons folder, I built the project and enabled plugin. I think I am doing something wrong because plugin generally works. I also saw your documentation, I think I made everything correct. There is no errors. Just not placing. I am using latest version of Godot Engine 4 Mono. Maybe it's the case? Because it officially supports up to 4.1. Asset is a scene.

Okay, I managed to solve that. It have to be Node3D where assets are gonna to be placed. No classic Node that I created.

Developer (1 edit)

Hello again WungielPolacz, I'm sorry that you had some issues. The problem is that you are using an outdated version of the AssetPlacer that is not compatible with 4.2. Please make sure to get the latest AssetPlacer 1.2.3 and your issues should be fixed.