Romax Usability

There are 2 memories that Romax uses, Image size and the external memory, increasing the image size leads to the decrease of other (external) memory.The image memory is for the Romax model, loadcases & results. Any FE & 3D views are stored outside of the image memory (i.e. in external memory).

The total memory that Romax uses is around 4GB, so increasing image size reduces the memory available for FE/3D views.Image Size allows the amount of memory available for model design (rather than solvers),load cases and results  to be set.

The amount of memory available to the external Static, Dynamic and FE solvers remains unaffected.So, image size is not used to increase performance.

Image size should not be increased to maximum, because this reduce the amount of memory available for FE deflections/3D views.

The image size should only be increased if  error is encountered while running high number of duty cycles ,when we get error while opening a model and out-of-memory errors.  

I would recommend setting the image size to between 1 GB and 1.4 GB as a general rule.  It also helps to remove unnecessary duty cycles and load cases from the model to help keep the image size memory to a minimum.

Pro tip - Did you know that the Image Size is stored within the RomaxDT.ini file and can be modified in a text editor.  In the past I have seen the .ini file become corrupted, which has stopped Romax from opening.  Opening the .ini file and entering the following (pick the image size you require) can resolve this problem.

• 0.2GB = oldSpacePages=52429
• 0.4GB = oldSpacePages=104858
• 0.6GB = oldSpacePages=157286
• 0.8GB = oldSpacePages=209715
• 1.0GB = oldSpacePages=262144
• 1.2GB = oldSpacePages=314573
• 1.4GB = oldSpacePages=367002
• 1.6GB = oldSpacePages=419430
• 1.8GB = oldSpacePages=471859