search

nerk987 / txa_ant

Textured version of the A.N.T. Landscape blender addon
84 stars 10 forks source link

TXA Landscape addon throws errors in bForartists 3.0 #11

Closed trilobite53 closed 6 months ago

trilobite53 commented 2 years ago

First, this is a remarkable addon. Thank you so much for making it available to the Blender community. Your addon works flawlessly in Blender 3.0. But this report is about errors and dysfunction in bforartists 3.0. I have already reported the problem on the bforartists forum. They recommended I post here.

Thanks.

I am going to present a series of screenshots that should illustrate the problem txa_landscape_1 The TXA Landscape panel displays normally(above).

txa_landscape_2 After hitting the “Landscape” button, a terrain mesh is added and throws the displayed error (above).

txa_landscape_3 After selecting one of the available “Preferred Material” presets (in this case, Alpine) this error is displayed (above). txa_landscape_4 Rendering produces the result displayed above.

Here are my specs…

= Blender 3.1.0 Alpha System Information =

Blender:

version: 3.1.0 Alpha, branch: Unknown, commit date: Unknown Unknown, hash: Unknown, type: Unknown build date: Unknown, Unknown platform: ‘Windows-10-10.0.22000-SP0’ binary path: ‘C:\Program Files\Bforartists 3\3.0.0\bforartists.exe’ build cflags: Unknown build cxxflags: Unknown build linkflags: Unknown build system: Unknown

Python:

version: 3.9.7 (default, Oct 11 2021, 19:31:28) [MSC v.1916 64 bit (AMD64)] Python (External Binary):

binary path: ‘C:\Program Files\Bforartists 3\3.0.0\3.1\python\bin\python.EXE’ version: Python 3.9.7

GPU:

renderer: ‘NVIDIA GeForce RTX 2060/PCIe/SSE2’ vendor: ‘NVIDIA Corporation’ version: ‘4.5.0 NVIDIA 496.76’

System

Processor AMD Ryzen 7 3700X 8-Core Processor 3.59 GHz Installed RAM 32.0 GB Windows 11 Pro 64-bit operating system, x64-based processor

ReinerBforartists commented 2 years ago

Thanks for reporting the problem here trilobite53. We have meanwhile found the cause. It was indeed a problem at our end. We had renamed the "Subsurface Radius" prop in the principled shader to "Subsurface Radius (R,G,B)" to make its purpose a bit more clear. And broke the API by that.

Sorry for the trouble. As told, the problem was at our end. And is now fixed.