Thanks for sharing this here m_hinks.
@DADAL That gets you direct support here in the forums by me. Seriously, there went a lot of development time (german engineering) and dedication into this release and there is more to come.
To give you some insight: psd-manager does not use some 3rd party library to write PSD files. It was developed only for use by psd-manager (Adobe was tight lipped about their file format since version Photoshop 6.0). I have researched the innards of the PSD file format for years to provide the best compatibility, compression and speed possible. Thanks to this psd-manger writes everything on the fly, so the complete PSD file is never held in memory. So you can write a PSD file of 1 GB and use use only maybe 10 MB of RAM and do crazy things like add 500 layers. There are lazier ways to do it - but that’s just not my way of doing it. Who wants to run out of memory when saving a file after a long render session. A nice piece of art wants to be saved in a file format exporter that was developed with the same care and dedication 
Let me try to summarize the V-Ray specific changes in psd-manager 3.0:
A PSD file was sometimes exported even though VRay rendering was aborted. This has been solved (Workaround for a VRay 2.0 issue).
The following notes are from the psd-manager 3 help file.
V-Ray Framebuffer:
If you don’t need to save render elements into the PSD file:
Then you can enable the V-Ray Framebuffer as long as you:
- have assigned a Render Output filename in the Render Setup dialog Common tab
- and have the Save File checkbox enabled
This ensures that V-Ray will create the 3ds Max G-Buffer that psd-manager needs to export objects, materials and scene layers. Should you forget to set these options psd-manager will warn you about this. If you don’t want to produce additional files besides the PSD file you can use the *.xxx file format. This is a fake file format that does nothing (a part of psd-manager).
If you want to save render elements into the PSD file:
Then you should disable the V-Ray Framebuffer, this ensures that psd-manager can access the rendered image, render elements and the multi-layered G-Buffer.
V-Ray 32-bit support
VRay only creates a 32-bit 3ds Max Framebuffer if the main render output file format is set to HDR or EXR. There is no option in the V-Ray user interface to set the color precision of the 3ds Max Framebuffer manually (e.g. for PSD export or other file formats that support this). There is a MAXScript property that can be set to enforce the 32-bit 3ds Max framebuffer creation (renderers.current.output_force32bit_3dsmax_vfb = true). When you switch the PSD file format to 32-Bits per Channel (HDR) psd-manager shows a dialog that lets you set this property automatically.
V-Ray Render Elements
psd-manager has built-in presets for all V-Ray 1.5 & V-Ray 2 render elements.
V-Ray Material Effect ID Override
You can use the Material Effect ID Override option available in V-Ray materials. Values in the range 0 to 255 are supported
I wonder if there is an upgrade, because I have an earlier version.
There are direct links at the end of the press release.
I also would like to thank Vlado for his help over the years and all psd-manager users out there that entrust their images to psd-manager.
Best Regards,
Daniel Schmidt - psd-manager Developer
Psssssd… work is under way to support the V-Ray framebuffer render elements. Stay tuned - 3.0 is just the start…