I am running an Alienware R13 Core i9-10980 @ 3.1ghz, with Nvidia Geforce RTX 2080 32gb of ram and Enscape version 3.3.1 . The vast majority of renderings we create are in the 2000pixel width range for small prints and viewing on screens. Whenever I try to run a larger image (say 4000 pixel width or above) enscape crashes almost immediately. If a 2500pix image renders out in about 5 seconds, I cant understand why a larger resolution image wont "simply take a little longer" instead of crashing. in other words, I would expect a correlation between render time and resolution (higher res = longer process) but not a crash. Having the ability to render larger images for large printed boards, banners, etc is a necessity in architecture and this functionality seems to have dropped off in the more recent versions of enscape. (For example, in much earlier versions, prior to having RTX video cards etc, we could run 8000 pixel images on a GTX1080 card and it would work fine)....
here is a quick task manager synopsis of the above scenario:
Render Size: 2500px Memory Usage: 16.8gb of 32 Render time: +- 5 seconds Video Card and CPU usage: negligible
Render size: 3000px Memory Usage: 17.8gb of 32 Render time: +- 5 seconds Video Card and CPU usage: negligible
Render size: 3500px Memory Usage: 19gb of 32 Render time: +- 5 seconds Video Card and CPU usage: negligible
Render size: 4000px Memory Usage: 20gb of 32 Render time: +- 5 seconds Video Card and CPU usage: negligible
Render size: 4500px Memory Usage: 20gb of 32 Render time: freeze and crash Video Card and CPU usage: negligible
I thought it was interesting that there is a fairly consistent increase of 1gb of RAM for every 500px increase in image size until I hit 4500 where it hit 20gb and went flat and crashed.
Any feedback would be great, thank you!