When I clone and recolor the Weeping Cherry tree the first swatch goes absolutely fine. When I try to add a swatch, any changes to the second swatch affect the first. If I remove the second swatch, the first swatch will be missing textures and the mesh will be gone from the 3d preview in s4s.
I've tried both the Create 3D mesh and Standalone recolor options, and the same things happen.
Please let me know what would be helpful for me to upload for troubleshooting.
Post by minimonster on Jan 14, 2019 11:24:41 GMT -5
Hi icymoons. You may want to try my little trick to getting re-colors to all play nicely with each other. When in Studio, with a fresh clone of the tree, add a swatch from the original swatch, then add another from the new one, then another from that new swatch. You should then have 4 identical swatches in the Studio swatch window. Consider the last swatch to be the 'first swatch', and you should be able to not only delete the first three without any problem, but then also be able to re-color to your heart's content from that final swatch without any other swatches changing.
Post by minimonster on Jan 14, 2019 15:47:37 GMT -5
Hi icymoons. 2 quickie ideas (neither of which are likely the answer, but worth investigating)(?) - 1) a weird instance of the dreaded and as yet unaddressed SSAO bug, 2) the 'Occluders' in the Light entry for the tree causing the issue. I cannot say for sure either, but just in case...
Note: I never until now knew how very much I wanted weeping Japanese maples in my game! Cheers!
I do believe it is part of the SSAO bug (No occluders to remove). When I edited the shadow mesh, the trees started showing the typical presentation of the SSAO bug with the shadows going through them. I followed Peacemaker's tutorial for fixing the bug, but unfortunately the tree do not have an SSAOIntensity entry under their materials. I tried adding one, but no results. Do you know of any other way to change the SSAO presentation of an object? Disabling SSAO works, but I'd like to be able to release these tree without people being forced to use that work around to play with them.
Post by peacemaker on Jan 14, 2019 20:51:42 GMT -5
It looks like part of the issue happening while importing the texture with S4S. I tried importing the texture with S4PE to compare to the S4S version and it does not suffer from the SSAO showing though the mesh. Not sure what sort of process the image goes through when imported. I know PNG gets converted to DDS formart, but not sure if anything is done to a DDS image when importing.
Post by peacemaker on Jan 14, 2019 22:33:51 GMT -5
Ok, so the SSAO issue seems to be caused by the same issue that caused the sunshadows of windows to not correctly show up after the C+D patch (which was fixed after finding the cause). In the materials section, the PosScale should stay at the values 1,1,1,1 but upon importing a texture or mesh, these values are altered. By changing them manually for each entry in each sunshadow lod group, the sunshadow now correctly blocks out the SSAO from behind the object.
This can be done by going to each sunshadow mesh resource in the warehouse tab (group 00100000, 00100001, 00100002 etc). Scrolling down to the fifth edit items button for Materials "items" and selecting PosScale in the popup. Change each value to 1, save and repeat for all entries, then all shadow mesh groups.
there does seem to be an issue where using Reshade the program doesn't recognise the alpha cuttout after editing and cannot seem to find the value that affects this but it is a small issue as only people with reshade would experience it, and most have SSAO off which solves the issue.
Last Edit: Jan 14, 2019 22:49:28 GMT -5 by peacemaker
If you are having problems seeing the CAPTCHA, please clear your browser's cache and cookies and ensure that you do not have any browser addons or extensions that interfere with the display of the CAPTCHA. Then, close the CAPTCHA window and click on the register button to open the CAPTCHA again.