Graswald


(Kareem Ahmad) #391

Ahhh yes, so graswald is now in the UI panel (the one you open with N instead of T) the one on the right hand side. That’s because of all the changes to the tools panel.

The thing in the add menu is only populated when you have some systems.


(Tomáš Luža) #392

Hey Yukon,
I would like to ask about Graswald support for other render engines. Is this addon focused only to Cycles/Eevee or does it support materials for let’s say Corona, Octane or V-ray? Would I be able to use Graswald with those engines aswell?

Thanks T.


(Harald Krokaa) #393

Cant activate the addon. Installed on the latest build from today. 11.01.2019


(tallken) #394

mac osx . blender-2.80-3c3d80ea22af-OSX-10.9-x86_64
why White color in Eevee ???

today
new mac osx blender-2.80-ce3475f74794-OSX-10.9-x86_64

Addon disappear in N panel


(Mats) #395

I cannot activate the 2.8 addon on either latest 2.8 versions, 12.01.2018 for windows, blender-2.80.0-git.ce3475f74794-windows64 and mac, blender-2.80-ce3475f74794-OSX-10.9-x86_64


(Kareem Ahmad) #396

Ok. I’ll grab the latest build and see what’s up


(bakar) #397

Can you please update your gumroad addon at the same time as its Blendermarket counterpart? I can only get version 28_01a whereas apparently a Blendermarket user can get 28_01b. I would expect them to be updated simultaneously.

Just got the plugin and cant install it using the latest version of 2.8. Awaiting the fix :slight_smile:
Thanks.


(Matt Martin) #398

Issue with vertex assignment to display Gras particles. Wouldn’t update until a third (or so) re-opening project file to take. Also removed and replaced instance of Gras for it update to accept the vertex grouping/dispersion.


(Kareem Ahmad) #399

Can you elaborate? And pictures would help too. Or a blend


(Kareem Ahmad) #400

I’ll let Julius know


(kless) #401

Hi, I’ve ran into a strange bug. I have multiple grass systems in a scene on multiple different objects and when I go to select an object with no grass system it will select one of the random object that has a grass system. It also seems to be if the object I’m trying to select is near a grass system that will cause it too. I haven’t been able to repeat the bug in a different blend file. If you would like the .blend file to get a better idea just let me know.


(Kareem Ahmad) #402

yes that would be awesome. You can pm it to me


(Kareem Ahmad) #403

I found one bug. They fixed an issue in the API that I had accommodated. Now just need to undo that accommodation.

EDIT : there’s a lot of changes… so scratch that.

For now I may need to drop backwards compatibility. This is tentative… but the api is changing.


(Julius Harling) #404

Uploaded it :wink:


(Kareem Ahmad) #405

@kless

If you care to know where the issue comes from: I wanted some way for graswald to be able to deal with systems on objects that have been duplicated. So that they can be treated independently if one wants. There was no clean way to do it, so I had objects track the systems on them by some—not great method. Your post still thinks it has graswald systems on it. So clicking it selects the system it thinks it carries. Selecting a system with autoselect emitter enabled selects the object emitting it, which wasn’t that pole. So thus the issue you had. If the system was already selected, it doesn’t do anything and that’s why you could probably select on the next attempt.

I’m not sure I can fix this without an update that will break backwards compatibility. So for now just turn off “autoselect emitter” if the issue comes up.

I’ll fix it in 2.8, and clean up some other messy implementations, since the compatibility will break anyway. I may, once the 2.8 version is done, make a retroactive final version of 2.79 that fixes these issues. This would be forward compatible, but not backwards compatible, for those that want to continue working with 2.79 but still have the option of migrating later. But for now, time to refactor.


(kless) #406

Ah works great now, thank you for the help and fast response.


(Nicholas Pritchard) #407

I’m using the latest version of blender 2.8 (1-13-19 release) and Graswald_28_01b and I’m getting this error when I attempt to activate the addon.


(dazza66) #408

Hi, I Can’t Activate the 28_01b, I couldn’t Activate 28_01a either, I keep getting error messages every time I try and activate, I am using the latest blender 2.80 of the 13th of January.
I don’t know if it’s me or Graswald is being a little Buggy still, though I have noticed other people have got it working so Umm, maybe it’s me, I would really appreciate your thoughts on the matter


(Kareem Ahmad) #409

Its buggy in the Jan 13 version. API continues to change. It’ll be a bit of time before I have a fix. Gonna do some refactoring.


(dazza66) #410

thank you for letting me know, I thought I was getting it wrong