02-24-2017, 11:08 AM
Our tech support guy is under the weather, so I'll see if I can help.
When users have trouble with memory, it's often because of too many objects, such as highly detailed multiple-room sets, or a "cast of thousands". There are some tricks to deal with that, such as splitting a set into multiple simpler sets, using background actors from the "Extras" category, and using a background image pasted to a wall or billboard rather than actual background objects.
As for crashes, that may be something we can fix if we can get enough information.
On thing that may help is a crash report. That's something that the Mac OS generates when a program crashes, and you see a message offering to send the report to Apple. It doesn't do us any good for the report to be sent to Apple, we need it sent to us. There are 2 ways to go about that. One, when the "FrameForge quit unexpectedly" dialog appears, click the "Show Details" button, copy all the details, and paste it into a post here or click here to e-mail to me. Two, in the Finder, select the menu item Go > Go to Folder..., and in the resulting text field, type:
~/Library/Logs/DiagnosticReports
This will open a folder containing all your old crash reports. Look for ones with a name starting with FrameForge. Such a file can be attached to an e-mail or post.
The other thing that would be very helpful is an actual previz file that reliably crashes when you follow certain steps, along with a cpack file containing any nonstandard objects or textures used therein. (Use File > Export > Nonstandard Objects & Textures to create such a cpack.) It sounds like you're using large files, so it may not be feasible to e-mail or post. If you use a service such as Drop Box or Google Drive, you can put the file(s) there and then send a shared link.
When users have trouble with memory, it's often because of too many objects, such as highly detailed multiple-room sets, or a "cast of thousands". There are some tricks to deal with that, such as splitting a set into multiple simpler sets, using background actors from the "Extras" category, and using a background image pasted to a wall or billboard rather than actual background objects.
As for crashes, that may be something we can fix if we can get enough information.
On thing that may help is a crash report. That's something that the Mac OS generates when a program crashes, and you see a message offering to send the report to Apple. It doesn't do us any good for the report to be sent to Apple, we need it sent to us. There are 2 ways to go about that. One, when the "FrameForge quit unexpectedly" dialog appears, click the "Show Details" button, copy all the details, and paste it into a post here or click here to e-mail to me. Two, in the Finder, select the menu item Go > Go to Folder..., and in the resulting text field, type:
~/Library/Logs/DiagnosticReports
This will open a folder containing all your old crash reports. Look for ones with a name starting with FrameForge. Such a file can be attached to an e-mail or post.
The other thing that would be very helpful is an actual previz file that reliably crashes when you follow certain steps, along with a cpack file containing any nonstandard objects or textures used therein. (Use File > Export > Nonstandard Objects & Textures to create such a cpack.) It sounds like you're using large files, so it may not be feasible to e-mail or post. If you use a service such as Drop Box or Google Drive, you can put the file(s) there and then send a shared link.
![[Image: JamesWSigFile.png]](http://www.frameforge3d.com/community/images/signatures/JamesWSigFile.png)