Forum Replies Created
-
AuthorPosts
-
lumin8
ParticipantA new update. It wasn’t any of the above. It was the naming convention. My file name had a “+” in the name (“Chair_AO+Shadow.jpg”). When I originally changed the name, that was what made it work and not the removal of the Metadata. You server obviously doesn’t like the “+” symbol but works fine when reviewing locally. I’ll retest my entire scene by just changing the names.
ParticipantOk… confirmed. I removed all the metadata and the jpg image and it works on your server. As mentioned, the original image was created from a PNG file. I’m ok with this as it helps both on file size and easy to fix my scene without adjust textures. I’ll just run a script to remove all metadata from my jpg textures.
ParticipantI solved the issue with a work around by resaving the the jpg which originally was saved from a PNG. The images are identical size and look the same but noticed a difference in the image data stored within the jpg file preventing from rendering on the network. As mentioned It works locally but not on the network. I’ll repost this a bug. You server doesn’t seem to like it.
ParticipantI’m using the current version which is I believe is 3.5. I feel that Verge sometimes ignores the name/association of the UV. Instead, it seems to be locked to “A” (first UV set in list) or “B” (second UV set in list). I found that if I emptied the UV and swapped them through copy/paste, it worked. Tough to explain but seemed to fix itself by me cutting/pasting/swapping contents of the UVs themselves. Selecting through texture association seemed to do nothing. Might this have something to do with 2 file nodes being shares with a single (1) place2dTexture node?
I often rename things and noticed this might also be an issue. In one instance, I changed the name back to original and it seemed to work. If you change the name of a UV set that used to be something else in an early version, Verge might be associating with that older UV set name. Something to check. BTW, Maya version is 2020.
ParticipantGood idea on the Layered shader. I assume this will be a hit on the performance at runtime. In the future, consider using the IOR as perhaps a way to dial in the reflection. It may not match PBR physically, but will allow some control over the in specular component. Just and idea.
ParticipantThat is unfortunate and will look forward to an update sometime. I am surprised this isn’t a bigger discussion as it eliminates the ability to creatively find a rotational position for the HDR against the scene. I’m curious if this is a limitation of Maya and if Blender’s version supports it.
Hopefully, you can add this rotation through the 2D matrix node which allow more than 360 around Y axis. It should follow whatever is showing in Viewport 2.0.
-
AuthorPosts