• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

Blocky artifacts when using a position map - Help!

New Here ,
Jun 04, 2023 Jun 04, 2023

Copy link to clipboard

Copied

Capture.PNG

launcher_launcher_position.png

I'm having a strange issue with my position map, when applying a texture to my model that uses the map it creates these blocky artifacts all over the texture.

 

I'm baking my maps in Marmoset, and I've tried messing with the settings and nothing has worked. This is testing with only the position map applied, it makes no difference if I add all the other maps.

 

I've linked what the artifacts look like in the paint window and the position map that I am using from Marmoset.

 

Any help would be appreciated!

TOPICS
Baking , Bugs & Crashes

Views

722

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

New Here , Jun 05, 2023 Jun 05, 2023

Seems like it was an issue in Marmoset, I had samples set to x16 but bits/channel set to 4 or something.

 

Fixed it by setting the bits/channel to 16 as well.

Votes

Translate

Translate
Adobe Employee ,
Jun 05, 2023 Jun 05, 2023

Copy link to clipboard

Copied

Hi @Billy30285371kndh,

 

Thanks for the message.

 

The UV islands are really packed and it can result with various issues and this is probably one of them. Make sure to let a decent margin between the UVs and I'd also advise you to avoid to small UV islands.

 

Let me know if this doesn't work.

 

Cyril Dellenbach (Micro) | QA Support Artist | Adobe

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jun 05, 2023 Jun 05, 2023

Copy link to clipboard

Copied

Seems like it was an issue in Marmoset, I had samples set to x16 but bits/channel set to 4 or something.

 

Fixed it by setting the bits/channel to 16 as well.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Jun 05, 2023 Jun 05, 2023

Copy link to clipboard

Copied

LATEST

Thanks for confirming - it may help others

Dave

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Resources