(ajharmon89) #417

I purchased and downloaded Graswald today and it is working excellently on Blender 2.79, however when I try to download it on 2.8 I get this error.

I have the latest version of Blender 2.8 (I redownloaded it today), so I don’t believe that is the issue.

Any ideas of what the issue might be?



(Kareem Ahmad) #418

Graswald version 28_01b is known to be broken.
Version 28_01c should be working fine, but I’m not sure if Julius has had a chance to upload it yet.


(skarkkai) #419

Thanks for your thorough reply. My post was mostly to see if reporting bugs this way works, and I’m glad to see it does. So I’ll elaborate.

  1. I figured this out: undo history. I set an undo memory limit, which solved the problem. As to the magnitude of “leaking”, adding a system would use 200 MB of memory, and removing it would use another 200 MB, which added up fast when experimenting.

  2. I haven’t been able to repeatably produce this problem. However, if I select “Link to Scene” and then inspect the material of an object that draws as black, it looks as in the attached screenshot. If I change to eg. “low” material detail, the material looks fine. Is there some way I could debug this further? I can send you the .blend file if that would help.

  3. By “translation” I just meant the texts that show in the UI. The first problem I noticed was the apparently unevaluated reference as seen in the attached variant-desc.png. Then let’s look at the “Use shared mat” control as an example. Searching for “shared mat” finds nothing from the manual, because the text talks about “Unique vs Linked Material”, not about “shared” materials. The small “using linked mat” image seems outdated, as the control now says “link to scene”. The very first screenshot in the manual is from yet another version of the add-on, I assume. This kind of things make the manual difficult to use and understand.



(ajharmon89) #420

Thanks Kareem! Once Version 28_01c is available will it be posted here or should I look for it somewhere else?


(skarkkai) #421

I’m currently able to repeat problem 2 for a brand new Creeping bentgrass system on medium detail level by simply saving the file. That turns the material black. When I then move mouse pointer over the detail level selector, all the material controls below the basic/advanced control disappear.

The problem can be temporarily fixed by selecting low detail level, saving, and switching the detail level back to medium. If I then save, the problem is back.

The problem is not happening for the low detail level, but it has in the past.


(Julius Harling) #422

Normally it will be posted in the Graswald RELEASE thread:


(Kareem Ahmad) #423

28_01c is available now

1 Like

(jachtarfranko) #424

Works well, thanks


(ajharmon89) #425

Thanks for the updated version! It now installs correctly. :slight_smile:

Now my issue is that when I click on the + button I get an error message, and Blender can’t seem to find any of the plant models. Any idea why this would be?


(ajharmon89) #426

I ended up restarting and trying again, and this time everything seems to be working well! :slight_smile:


(skarkkai) #427

I’ve also noticed that the objects with Grasswald systems on them keep accumulating particle systems that don’t show in Graswald UI, as well as empty material slots. All of this might be somehow related to the fact that I’ve been duplicating the objects with Graswald systems.


(skarkkai) #428

Renaming the object with a Graswald system on it seems to be a good way to make Graswald lose track of the particle system, which will then result in weirdness. And that of course happens when duplicating objects. It would be nice if Graswald were smarter in those situations. Does Graswald rely the particle system having a name generated from the grass species and variant?


(Kareem Ahmad) #429

Graswald should be using pointers to keep track of emitter references, and while particle systems are given a default name, the name isn’t how they are accessed later on…

I’ll definitely look into this issue.


(skarkkai) #430

Saving seems to be what triggers possibly all of these problems. Today I’ve not had any problems until I save, at which point often all or at least amost of the systems start immediately showing black (or transparent for high detail systems). Needless to say this is making Graswald nearly unusable for me.


(skarkkai) #431

Given that using the latest version 1.15 is a pretty frustrating experience, can I download the previous version somewhere? In general it’s nice to be able to install also earlier versions of software.


(Kareem Ahmad) #432

I’m not sure, Julius typically manages all the uploads.

But you’ve given a lot of details, so I should hopefully be able to resolve all the issues in short time.


(Kareem Ahmad) #433

The way graswald deals with duplicates, is that it offers you a button to

If you don’t… issues may arise. I need a better way to deal with duplication… but that will also break backwards compatibility.


(Kareem Ahmad) #434

I cannot seem to replicate the error in 1.15 nor the would be 1.16

Do these errors still show themselves if you don’t mess around with duplicating objects?

Actually let’s try this. Go to your addon directory (probably {username}/Appdata/Roaming/Blender Foundation/Blender/2.79/scripts/addons )
And edit this file: Graswald/helpers/

Just add the # as shown.

Then tell me if this fixes the issue. If it does, that really narrows down our search.

And let’s continue this in PM


(skarkkai) #435

Just letting people know we got this bug figured out and it should be fixed in the next version 1.16.

1 Like

(Alan) #436

Very frustrating. Bought this months ago, haven’t been able to use it since.
Bought again, in December.

Latest version, Graswald_28_01c, does not install, can’t read code text - is off screen left.
Have removed. Useless.

Mac OSX 10.14.3, 3.2 GHz Intel Core i5, NVIDIA GeForce GTX 680MX 2048 MB

Alan A.