armory3d / armory3d/armorpaint

Bump node issues

Open
#895 0 comments 1 reaction 0 assignees View on GitHub
bug
Dominant language
C
Stars
5k
Forks
553
Avg merge
3d 11h
Merged PRs (30d)
6

Description

**ArmorPaint version:**
ArmorPaint.org - v0.8 (2021-04-28) - e334850

**OS/device including version:**
Win10 x64

**Issue description:**
Bump node produces several unexpected results.

**Steps to reproduce:**
**1. Issue**
Build the following graph in ArmorPaint and in Blender
![ap1](https://user-images.githubusercontent.com/28649121/116391402-66f95180-a81f-11eb-9424-ec45b93363af.png)

By using the standard 2mx2mx2m cube from Blender in both programms, we get
![ap1](https://user-images.githubusercontent.com/28649121/116391632-b475be80-a81f-11eb-835b-c9a12bcf4cd6.png)
ArmorPaint's result is way different
![ap1](https://user-images.githubusercontent.com/28649121/116391748-d53e1400-a81f-11eb-9a6f-e2c6147dac1d.png)

**2. Issue**
I build myself a simple Bump height map
![height](https://user-images.githubusercontent.com/28649121/116391825-ebe46b00-a81f-11eb-844d-2e8048813b98.png)
and used it in Blender and in ArmorPaint. The idea was to compare the normal vector directions.
Blender:
![ap1](https://user-images.githubusercontent.com/28649121/116392158-657c5900-a820-11eb-9335-dd415d48b122.png)
ArmorPaint:
![ap1](https://user-images.githubusercontent.com/28649121/116393552-10414700-a822-11eb-8c66-52c795ede239.png)
Notice that the normal vector directions are different. If you look carefully you can see that they differ by a flip in y-direction. To highlight this I set strength 5 in ArmorPaint vs. strength 1 in Blender as the strength differs.

Contributor guide

No contributing guide indexed for this repository

Research direction

Reproduce both reported bump-node graphs in ArmorPaint and Blender using the standard 2m cube and the supplied height map. Compare the resulting normal directions, especially the Y direction and the different strength values; done means ArmorPaint's results match the Blender comparison for these cases. No source file or test is named in the issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
blender
Domain
computer-graphics
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.