Clicking Render does not create images - Desktop
Render Button Does Not Create Images
Use this article when clicking Render does not create output images, especially on older Windows systems or installations with low Java memory allocation.
Overview
Render failures can be caused by an unsupported Windows environment, a 32-bit Windows installation, low memory allocation, or a very large source image that requires more memory than ROES has available.
Check the Diagnostics Log
Open Diagnostics
Go to the Home pane and click the Diagnostics button at the lower left.
Show the log
Click Show Log.
Check the operating system value
At the beginning of the log, find the operating system value. Make sure the system is not Windows XP and is not using a 32-bit version of Windows.
Check memory allocation
Below the operating system entry, check the memory allocation value. It should be higher than 768MB. Ideally it will be a four-digit value, such as 3996MB.
Check for Java heap memory errors
If the memory allocation is low or only three digits, check the end of the log for entries like:
If this appears, ROES did not have enough memory available to render the image.
Possible Cause: Large Customer Image
This can also happen when the customer image is very large, such as a pre-rendered file that was resized up in Photoshop and placed into a larger product size.
Using a smaller version of the image can help reduce the memory needed during rendering.
Possible Cause: JNLP Installer with Low Memory
If Windows is 64-bit but the memory allocation is only three digits, such as 768MB, the customer is likely using the older JNLP installer instead of the native Windows installer.
Have the customer exit ROES, remove the old Java ROES installation, and install the newer native ROES version using launch.msi.
Important Note
If the system is Windows XP or 32-bit Windows, resolve the operating system limitation before focusing on image size or ROES installer type.
Expected Result
After ROES is running on a supported 64-bit Windows system with enough memory allocated, and the image file size is reasonable, clicking Render should create the output images successfully.
Escalation Notes
- Collect the Diagnostics log and confirm the operating system entry.
- Confirm whether Windows is 64-bit or 32-bit.
- Check the memory allocation value and look for Out of memory: Java heap space.
- Ask whether the customer image was enlarged or pre-rendered outside ROES.
- If memory is low on a 64-bit system, verify whether the customer is using the old JNLP installer instead of native launch.msi.