You're very welcome! Enjoy creating with it

Thank you. I'm happy you like it and I appreciate your comment! Cheers!

Super Bump is designed to give a high-poly appearance to low-poly objects. I have never tried it with a 2 million face mesh but I would not expect it to work well. Since the mesh is so high-poly, I would render in Cycles and use material displacement. With Super Bump, I find that the most important factor for viewport FPS is how much of the screen is occupied by Super Bump objects, as well as how many Super Bump layers the objects have. IMPORTANT: Super Bump works by duplicating the mesh several times and expanding these duplicates outward. This means that if you use Super Bump on a mesh with 2 million faces, that's 2 million more faces for every layer and it's not uncommon to use 30 - 60 layers. When you say "too many nodes", I must assume you are referring to a procedural material. Procedural materials will almost always have more nodes than a Bitmap based material which uses only textures. The Procedural/Bitmap trade-off is this; Bitmap uses more memory but less processor. Procedural uses less memory but more processor. I wouldn't expect any procedural material to run "smoothly" on a model with 2 million faces, though "smoothly" is relative. In terms of viewport FPS, it's not useful to compare Eevee to Cycles because Eevee will try to draw the complete scene at high quality before moving on to the next frame whereas Cycles can move on after just 1 pass so, yes, FPS will be higher but the image will be unrefined and unusable.

Certainly! All it needs is a height map, procedural or otherwise it will all work.

@@nodesandnoodles thank you