itch.io

Can you specify what exactly happens? A video would help a lot.

Did you make sure to follow the documentation? I'm unsure which rotation you are speaking of, for the one along the surface normal, see:

https://cookiebadger.github.io/assetplacer-docs/painting_orienting.html

for rotating an asset and storing the rotation for next item that will be placed, see:

https://cookiebadger.github.io/assetplacer-docs/placing_assets.html

You're very welcome! I'm glad I finally made it happen :)

just got back to you there! This issue is known, unfortunately. Thank your for reporting it again, though. I'll try to fix it in the next version. The wait between versions will be less this time, so stay tuned for the next updates. 

Can you try the following:

1. delete the line that reads:

const PlacementMode = AssetPlacerState.PlacementConfigState.PlacementMode

2. replace every instance of 
PlacementMode 
with 
AssetPlacerState.PlacementConfigState.PlacementMode

I am wondering how that conflict comes to be. Can you tell me, which system are you on? Also, it might help if you could provide a copy of your .godot file, to see which settings you have. Does the plugin work in a new and clean project with default settings?

Hey again,

is there any error that is thrown in the very beginning when you enable the plugin before `Nonexistent function 'process' in base 'Nil'.`? I suspect there is a problem with creating the PlacementController object. Can you open the files "res://addons/assetplacer/viewport_3d_controllers/placement_controller/placement_controller.gd" and "res://addons/assetplacer/viewport_3d_controllers/viewport_3d_controller.gd" inside the script editor and see if any compile errors are thrown? Maybe a class you are registering collides with my controller classes. 

In any case, try if adding the AssetPlacer to a clean project works. If you prefer, you could also send me your project and I'll see if I can find the cause of conflict.

Hello! 

Are you able to enable the plugin after deleting it from the addons folderand adding it back again?

Hello! Thanks for reporting, and I'm glad to hear you were already able to resolve the issue. The particular error looks like either something with the folder or file naming went wrong, or maybe the plugin was already enabled before all the files copied succesfully.

Regardless, let me know if you find anything else. This version has a lot of architectural changes, so it'll be great to know if something needs fixing!

Best regards

Update on this topic: I have rewritten the entire plugin in GDScript, so now it is usable with the standard Godot version! Just download the version 1.5!

Hello, update 1.5.0 is out, please try and see if you can find any issues with it. This particular problem should be adressed!

Hello! To share libraries, you also need to share the assets that are referenced by the libraries. For example: if you have all your assets inside a folder "res://assets", and you want to share the library, I'd recommend putting the library file and the assets folder inside a folder. To your new project, add a copy of that assets folders, such that you again have "res://assets" and paste the library file(s) into the library directory. This is the userdata folder by default, but you can change it to be the resource directory res://, in Project Settings -> AssetPlacer -> Settings -> Library Save Location. This way, you can have the assets folder and the library files next to each other.

Hope this helps!

this is not the correct contact. My handle is @_cookiebadger. Not the underscore before the name. There is no number.

I don't seem to have gotten any message, are you sure you sent something?

Hello. Seems like you need to log in with the account which you purchased the plugin with. If you didn't log in during a purchase, please find your receipt and contact me via Discord.

they're in order of appearance - that was configured in the LATEX template from uni :)

Make sure you followed the installation steps carefully, especially the "build" part (https://cookiebadger.github.io/assetplacer-docs/installation.html). Notice the small build button next to the play button in Godot 4.2+.

If this does not help, remove the addon, but also remove the "mono" folder inside the ".godot" folder in your projects root directory. Then, add plugin again and build. It should work now.

Otherwise, try the plugin in a new project, to see if the issue is related to the project you are adding it to, and let me know your findings.

Debug collisions is only for when you want to use the surface placement mode. It might be that the feature has been removed in newer Terrain3D versions. 

Can you provide a video or animated image showing what you mean by the jagged snapping? It might be intended behavior. Snapping is predominantly designed for flat sections of the terrain.

Hey!
There is a paint mode for this purpose, you just have to enable Snapping (set the step equal to your tile size), and then click and drag to place multiple tiles. You can see it in action here:

https://cookiebadger.github.io/assetplacer-docs/painting_orienting.html

yes, of course this is possible!

Please closely follow the instructions: https://cookiebadger.github.io/assetplacer-docs/installation.html

You need to have .NET installed on your machine for C# scripts to work, the latest version can be downloaded here: https://dotnet.microsoft.com/en-us/download/dotnet

Don't forget to actually press the C# build button (hammer icon) in the top right run bar of the editor! 

~CookieBadger

Hey, thanks for reaching out :)

While nobody specifically asked me this before, I figured that the components I developed might be handy for an in-game level editor too, although major adaptions would have to be made. Since the editor has a similar structure as a Godot game (scene tree, process() functions, input events), re-purposing at least some parts of the tool would certainly be possible. However, all the plugin logic that ties into the EditorInterface, for example, would need to be stripped out, so you will have to dive into the plugin's code base quite deeply for integrating it into an in-game level editor.

Hope this helps, let me know if you have any specific questions about the source code and implementation.

awesome game. love how it hits at insurance companies making their claim procedures purposefully terrible. it perfectly reminded me of cancelling an adobe subscription 

Okay, I'm sorry that you had this extra effort just to get the plugin working. Do let me know if you ever have the problem again, and if regenerating the NuGet Config helps in that case.

Best regards, and happy developing!

Alright, since you have nothing uncommon there, it should be safe to delete both .sln and .csproj files, and see if that fixes the issue.

If it doesn't, then I guess there must be an issue with either your .NET installation (or Mono, but better not to use Mono anymore), the NuGet configuration, or some stuff within your userdata folders. 

As a start, you should try and make sure that NuGet works. From the docs:

A simple way to fix the NuGet configuration file is to regenerate it. In a file explorer window, go to %AppData%\NuGet. Rename or delete the NuGet.Config file. When you build your Godot project again, the file will be automatically created with default values.

I can recall this fixing the issue on one of my machines once. I really hope we won't have to reinstall stuff, I wouldn't want you to go through that trouble.

Thanks for the screenshot. Your setup does indeed look correct. 

Sometimes, such issues can occur when certain C# files are not properly (re-)built, and the engine thinks they are at a different location.

Can you try both going to MSBuild and pressing 'Clean Build', and if that still does not work, manually deleting the folder: C:/Users/Ian/Documents/GitHub/liminalita/.godot/mono

This 'mono' folder is where the compiled C# files are put when they are built, so if stuff goes wrong, deleting that often helps.

 If the problem persists, would you please also send me the contents of the .csproj and .sln files inside your project folder? 

Thanks for the patience, by the way, I hope together we're getting to the root of the problem.

Hello sol-vin. 

To my knowledge, the language field in the .cfg does not do much. Please make sure that the plugin is set in the correct folder (inside "res://addons/"), as described here: https://cookiebadger.github.io/assetplacer-docs/installation.html
The installation location should match the location specified in the .cfg file. If you are on Linux, note that uppercase and lowercase are treated differently, so if your addons folder is called "Addons", e.g. it might not work.

Let me know if you need further help. 

thanks for the info. While it's more a workaround than a fix, I'm glad it prevents the problem. I might decide to break compatibility with 4.0 and remove all those deprecated references in an update then.

Apologies for this very late response. I have been looking into this from time to time again,  but still have not found a reliable way to reproduce the issue. So far, it seems like the engine arbitrarily performs a (de)serialization and then the plugin looses certain references.

If you could somehow provide me with exact steps to do in order to get this issue, it might help me find a fix. I would also be interested in your hardware (especially CPU and RAM) to see if the bug is related to limitations in physical resources.

So far, one thing you could try is go to the file addons\assetplacer\placementController\SurfacePlacementController.cs and in line 102 change `editorInterface` to `EditorInterface.Singleton`. If this fixes the issue, please also let me know, so I can include it in a hotfix. 

In the meantime, I will keep trying to find a fix, whenever I have the time.

Are you using any other plugins that could cause an incompatibility? 

Does disabling and re-enabling (temporarily) remove the error? 

Which OS and which .NET version version are you on?

Hello berni94,

I'm glad you like the plugin. Thanks for the report, I am looking into this now. I have not been able to reproduce it for now, but it seems to happen during (de)serialization, i.e. when the plugin is loaded or unloaded. You might be able to get rid of the error if you disable and re-enable the plugin. If that doesn't fix it, restarting the editor might also fix it. 

Unfortunately, it is quite difficult to prevent this type of error during serialization, so I would need some more info to find a potential fix for this. When, and how often does this error occur in your project? E.g. does it happen after you rebuild your C# solution, or right after enabling the plugin? Also, how severe is this issue for your workflow?

I'd appreciate if you could update me on these details.

Glad I could help!

Dear Nathcra,

I've been able to investigate your issues a little. As for the first issue, I gathered that you are probably using the Terrain3D addon and placing on it? If my guess is correct, you are using an outdated version of Terrain3D (0.9.2 or prior). If you were to use Terrain3D 0.9.3 the error would not appear. If updating Terrain3D is not possible in your project, you can easily fix the error spam by going into addons\assetplacer\placementController\Terrain3DPlacementController.cs and replacing lines 30-47 with the code below:

var data = _terrain3DNode.Get("storage"); // legacy (<0.9.3)
if (data.Obj == null)
{
   return new PlacementInfo(PlacementPositionInfo.invalidInfo, "Error retrieving Terrain3D data", Colors.Red);
}
var heightRange = data.As<Resource>().Get("height_range"); // legacy (<0.9.3)
if (heightRange.Obj == null)
{
   return new PlacementInfo(PlacementPositionInfo.invalidInfo, "Error retrieving Terrain3D height range", Colors.Red);
}

As for the second error you found, I can not provide a quick fix, unfortunately. I suspect that deactivating and activating the plugin would temporarily make it disappear. If you are using any other plugins (which could be conflicting) or if the error always pops up after you perform a certain action prior to the viewport clicking you describe above, let me know. If you find any other bugs, I'm glad if you share them as well.

I hope this helps!

~CookieBadger

Hello Nathcra,

thanks for the detailed bug report. Before I start looking into it, would you please let me know the Godot version and AssetPlacer version you are using?

Best,

CookieBadger

Thanks for reporting, I understand what you mean and will look into it 

Hello!

I'm sorry that it didn't meet expectations. You can  request a refund on itch.io only by contacting support.

Best,

CookieBadger

Hello Dawid,

scattering is a larger feature set, that needs time to be designed and developed. A non-mono version is also not a feature that I can just make from one week to another. I am unable to make any estimates for both requirements for now, but I suspect that by the end of the year, you will still be waiting.

I understand it is frustrating when you pay for a product and it does not fulfill all of your requirements. Unfortunately, you are paying to obtain product as-is, and while I hope to provide you with useful updates as often as I can, it does not entitle you to have requests implemented in a given time frame. I do appreciate you supporting the development, though, and hope to come closer to meeting your expectations soon.

Best,

CookieBadger 

Noted!

Hello TranquilMarmot!

Unfortunately the randomizer is not implemented yet. What you see is the UI, that I drafted at some point and which accidentally made it into 1.3.1.

This feature is yet to be implemented.

If you upgrade to the latest version (1.4.1) you'll see that this UI has been removed again.

I'm glad you got it working, and thanks for sharing your findings. I will investigate regarding the project name issue.

Good luck with your projects!