Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Shader export is a mess #38

Open
xanathon opened this issue Aug 11, 2022 · 2 comments
Open

Shader export is a mess #38

xanathon opened this issue Aug 11, 2022 · 2 comments

Comments

@xanathon
Copy link

When exporting static props this latest version of the bridge are one big mess when it comes to exporting shaders. Even the quite flawed very first version was way better than this.

Only a diffuse texture is brought over, reflection, normal, bump are all missing. Also in the first version material groups were exported, now you get one material/UV for one object and you loose all metarial information. That leads to manual postwork after importing that is just not doable, because it costs so much time, to rework this into a usable asset.

I will go back to the first version. That had it's problems and did generate the nodes wrong in multiple places, also it had problems in Redshift with specular materials or normal maps plugged into bump nodes, but all in all the first verison needed WAY less postwork than this new version. It is not improved, it is lacking in a lot of places, especially materials and shaders. For me the new version is mostly unusable.

@brucek5
Copy link

brucek5 commented Aug 12, 2022

Hi axnathon,
As a user of the Cinema Bridge, I too noticed material creation issues not only with props but also with characters with different types of geoshells.

This last Bridge update was pretty major with a lot a great features, but must have impacted the material conversion. I'm sure they'll figure it out.

Below is what I captured in my Python log while trying to convert materials to Redshift (I replaced the R21_XXXXXX for this posting):

Traceback (most recent call last):
File "C:\Users\brucek5\AppData\Roaming\Maxon\Maxon Cinema 4D R21_XXXXXX\plugins\DazToC4D\lib\DtC4DGuiImportDaz.py", line 396, in Command
rs_mat.execute()
File "C:\Users\brucek5\AppData\Roaming\Maxon\Maxon Cinema 4D R21_XXXXXX\plugins\DazToC4D\lib\RedshfitMaterials.py", line 71, in execute
self.make_rsmat(mat, prop)
File "C:\Users\brucek5\AppData\Roaming\Maxon\Maxon Cinema 4D R21_XXXXXX\plugins\DazToC4D\lib\RedshfitMaterials.py", line 320, in make_rsmat
self.set_up_diffuse(prop, rs_material, rs)
File "C:\Users\brucek5\AppData\Roaming\Maxon\Maxon Cinema 4D R21_XXXXXX\plugins\DazToC4D\lib\RedshfitMaterials.py", line 139, in set_up_diffuse
self.set_gamma(texture_node, "sRGB")
File "C:\Users\brucek5\AppData\Roaming\Maxon\Maxon Cinema 4D R21_XXXXXX\plugins\DazToC4D\lib\RedshfitMaterials.py", line 93, in set_gamma
texture[c4d.REDSHIFT_SHADER_TEXTURESAMPLER_TEX0_GAMMAOVERRIDE] = True
AttributeError: 'module' object has no attribute 'REDSHIFT_SHADER_TEXTURESAMPLER_TEX0_GAMMAOVERRIDE'

@xanathon
Copy link
Author

That is not a problem in the latest version, it already was there from the first release of this third developer team trying their hands on this.

The missing texture mapping is not only a Redshift problem, it also does not work with standard C4D materials.

I have no idea how something like this can even be release in this buggy state.

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

No branches or pull requests

2 participants