-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with the erosion solver(I think it is the erosion image) #12
Comments
Thanks for the response. I have an Intel UHD 620 integrated GPU and a Radeon RX 560 discrete GPU.
Thanks, I'll wait for that release then. |
Could you please send a heightmap generated by the Hydra - Heightmaps panel and a heightmap after thermal erosion? The heightmap for susanne seems to generate correctly on your machine but then something goes very wrong during erosion. |
I meant the heightmap result - you can export it using the image button in the Result section (next to the geometry nodes symbol). My only guess right now is that the erosion shaders launch too many threads for older GPUs. Check the console after launch for any errors, but if it runs, then the shaders probably compile fine. I'll try to send you a development version next week with modified shaders. |
Here is a modified version of Hydra: |
Hi. When I try to install this version in the addon menu a warning appears "there is no moderngl module", nor does the submenu where external dependencies could be installed. So I installed them manually but when I restart blender I get this notice in the console:
The hydra panel in the viewport does not appear. |
Btw, I also got what you asked for(with release version 1.1.0). In this case it is a cone-shaped cylinder with subdivisions, the erosion map seems to come out fine so your assumption could be correct. |
Hello and thank you for the heightmap. If both the generated heightmap and the eroded heightmap seem correct then it might just be something during their subtraction. You can also try to generate a landscape from the image (Decouple button in the Image viewer Hydra panel, and then generate in the Landscape panel). There might still be some invalid values that are hard to see. Here is a slightly corrected version of the addon (I messed up an UI element in the preferences, the previous version would throw an exception anyway, sorry): As for the moderngl issue, you could try deleting everything with moderngl and glcontext in Blender's python packages (C:\Program Files\Blender Foundation\Blender X.X\X.X\python\lib\site-packages on Windows) and reinstall it if you haven't done so. I've personally had an issue where Blender was reaching for system python's packages too for some reason. I must admit that getting extra libraries into Blender is a little scuffed right now though. |
An apology for the delay. I just tested the version you sent, although now I focused on running the tests you added to the panel. Since it is data, I don't know what the results mean, so I am attaching the images that were generated and the test file in which I ran the addon (download the .txt and change the extension to just .rar, then unzip). |
Thank you for the data. All individual shader functions seem to work fine and so do large thread blocks, so my idea was incorrect. I may have discovered a bug in moderngl with AMD and texture binding, but that doesn't come up in the erosion algorithms used. Here is a second set of tests (you only need to replace the file in the addon's root): It mainly tests thermal erosion a bunch of times because so far it seems that the addon literaly just fails at subtracting two images. |
Thanks again. |
Of course, I put my help at your disposal. |
I'm happy to help test as well if need be. I'm running an Arc A770 gpu on
Win11.
…On Sun, Oct 27, 2024 at 1:07 PM joelRVC ***@***.***> wrote:
Of course, I put my help at your disposal.
—
Reply to this email directly, view it on GitHub
<#12 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANTHPHB2KD6WUAKAENKK54TZ5VBYLAVCNFSM6AAAAABPK4RFNOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINBQGE2TQMJWHE>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Hi. First of all I want to thank you for creating this, it looks very interesting. I tried it with a mountain model and when the geonodes preview appears, certain parts of geometry jump to infinite locations. I thought it was because of my model so I tried with Suzanne but I get similar behavior, I looked for the image generated by the erosion and in both scenarios it has certain pixels with errors.
I tried with blender 4.3 beta and also with 4.0, in the latter I show the image generated by the erosion:
Blender 4.3b:
B.4.3.mp4
Blender 4.0.2:
B.4.0.2.mp4
The text was updated successfully, but these errors were encountered: