Senior Member
Join Date: Jan 2013
Location: Rochester, MN
Posts: 1,516
|
Daelda, hopefully by now you've filed a bug report using the online form, as the developers are the ones who can help you figure out what's going wrong.
But for what it's worth, here's a couple of notes: Quote:
Quote:
Edit: See how long it takes me to write things sometimes? A dev showed up! :) |
||
#11 |
Member
Join Date: Aug 2013
Posts: 39
|
I've encountered this with other 32-bit programs. Once the commit memory size gets to about 1.7-1.8 GB the program will crash. You can try checking it by doing the following:
It will at least let you know if you are hitting the limit. Last edited by Dakadin; January 10th, 2015 at 12:37 PM. |
#12 |
Member
Join Date: Feb 2013
Posts: 62
|
Update: For whatever reason, the program "fixed" itself and is now working fine. I wanted to wait a while to make sure it wasn't just a fluke. Weird that it did that for a while and then stopped. Dunno what changed.
As to storing Sourcebooks - I run a Harn game and I want to share many things with my players (as they are unfamiliar with Harn). I have attempted to use Google Drive and other solutions and been met with...less than enthusiasm (I think that, of my 10 players between my two weekly games, I got perhaps 3 people that ever used it). However, once I got them the Player Edition of Realm Works, even my most reluctant Player has been fairly enthusiastic about using Realm Works. I still keep my larger files off of Realm Works (for many reasons, including the file size limitations). But even doing that, I have a lot of files (maps, location information, Guild details, etc) that I keep on Realm Works. |
#13 |
Senior Member
Join Date: Mar 2014
Posts: 411
|
Memory allocation stuff can be sensitive to what else you have running on the machine. If you had other intensive apps open, you might not have had 2 gig to allocate...
|
#14 |
|
|