RC6 - .exr dumps containing denoised passes still unopenable by PS + ArionFx or ProEXR (whichever one uses for opening multilayered .exrs in photoshop) nor by any 32 bit image viewing application - maybe there's something wrong on my end, cause I just can't believe what not a single user reported nor confirmed that ...
Hi,
I just tried both mentioned plugins and the exr opens without problems.
Do you have problems with history dumps only? Can you open the exr if you save it manually with "Dump EXR"?
I just don't know what to say, tried saving those using RC6 yesterday - no go, and as before, only the ones which didn't contain denoising passes (denoising off) were openable - have read your post, tried saving again today - and, bam, today's saved ones open like they should, and yeah problem was with both history ones and manually saved Dump EXRs alike. Don't understand why that happened as both yesterday's and today's saves were done using the same RC6 and were saved from the same scenes.
The only things which come to my mind are those:
1st - yesterday I didn't restart my pc after installing RC6 and windows, for some reason, continued using some of those older dll's cached in memory cause I did some renders using RC5 earlier that day (not too likely but still)
2nd - I use symlink for corona's render history folder (due to their quite large size and not too much space left on my ssd C drive) which is physically located on E drive and points to the default location (c:\Users\Antanas\AppData\Local\Autodesk\3dsMax\2016 - 64bit\ENU\en-US\plugcfg\corona\history) - well it's the same trick I use for many other applications which do not allow user to manually set those program's cache\histories\temps\libraries\etc to some other than default locations which are usually located somewhere deep within c drive and after some time make one wonder where the space on c drive has gone )) Maybe there's some sort of incompatibility or rather instability when using this method with corona's history folder for as far as I understand (maybe I'm completely wrong here) corona first saves vfb contents there and then saves\copies it to some user chosen folder if manual Dump EXR is used. If that incompatibility it is the case indeed, then I would surely want to have the ability to set that history folder manually from 3ds max itself as otherwise the render history function is almost completely useless to me, especially when 4k or larger renders are involved due to those files considerable size which pretty fast fills up precious C drive's space.
3rd - some goddamned windows 10's "black magic" which could be actually related or causing the 2 potential reasons above or something else no less sinister ))
@belly - well yeah it could be that too but the thing is those files were\are unopenable not only by photoshop + ArionFx but by other applications as well - for instance, the one which I use for quick previewing of all 32 bit images
http://hdrlabs.com/picturenaut/ couldn't open them too - could you try opening your unopenable by arionFx 13k file using it ? its free and pretty useful for both hdris and exrs alike especially due to it's autoexposure feature which I didn't encounter anywhere else )
@Frood - gotta do that a little later - for now the work beckons again and f***ing phone calls from builders and their ilk don't even let me finish this post and testing the way I would like )