Skip to content

Comments

Revert "Remove AO export for Blender export target"#1292

Open
williamchange wants to merge 1 commit intoRodZill4:masterfrom
williamchange:revert-898-blender-export-remove-ao
Open

Revert "Remove AO export for Blender export target"#1292
williamchange wants to merge 1 commit intoRodZill4:masterfrom
williamchange:revert-898-blender-export-remove-ao

Conversation

@williamchange
Copy link
Contributor

Suggestion via Discord

I'm not sure it's a good idea as I use the Blender export template as a general export for a PBR full set of textures.
And, as MM exports just what is connected, I found more natural that if I don't want AO I leave the AO input unconnected, if I connect something is because I need it.

In my opinion it's easier as the AO is exported just if you put something on it...so, if you use time and effort to create an AO nodes network is because you need it, regardless if it's physical realistic or not in Cycles (or EEVEE)...so, if you connect to it, I'm expecting it will exported with no further operations like it's for diffuse, roughness, normal and so on.

@Calinou
Copy link
Contributor

Calinou commented Feb 4, 2026

In hindsight, I agree this makes more sense (also because you may export from Blender to another program that does take AO maps later on).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants