Color Issue
Warning, this gets a bit confusing. I have a light source I use for capture, depending on setup it produces slightly different spectral distribution, but it's been too long since the first of three trips to this cave to remember exactly what setup was in play during capture. All I know is, I shot RAW each time, have used the X-Rite chip charts to create profiles of the setups, tried my best to get each of the three datasets on the same starting point for white balance, but I got off somewhere along the way. When I originally brought images into RC, those from the first shoot were high on red, I used the third shoot as my reference, happy with that color. When I discovered the big discrepancy between shoot 1 and shoot 3, I went back to Lightroom and brought shoots 1 and 2 to match shoot 3:
I then moved these adjusted images from shoot 1 and 2 over to the PC using overwrite. Because I preserved the file names, my expectation was that RC would be fooled into seeing these folders of images as the same ones used on import when first building the project. This worked in one spot higher up in the cave, but here's what I'm seeing in Unreal Engine at the base of the pit:
There is some reality to the shift from red below to green above, as evidenced in the source photography above, but that difference doesn't explain why those source images produce the far more dramatic shift in color on the backend in Unreal. What worked just fine in a different section of cave (that had a similar shift in red in the first shoot next to third shoot) didn't take this time. What could possibly explain that?
Thanks,
Benjy
-
Hi Benjy,
how is the result in RC, when for example you create an orthophoto?
Or in unreal with only flat light?
How do you expect it to be? Not as green in the upper half?
The bottom, which you mention, does not look too different to me to the original photos - I think they look a tiny bit darker because of the added shade from the rough surface...
It looks fantastic, btw! :-)
Please sign in to leave a comment.
Comments
1 comment