|
Post by jalpilot on Feb 1, 2013 21:11:55 GMT -5
Firstly, I'll list my specs and OS GPU: GTX 670 CPU: i7 @ 4.5GHz RAM: 8GB 1866MHz Cooling: H100 OS: W7 64bit
So I really have no idea how it could be anything to do with my system, as it's perfectly capable of running FS9. This is usually happening with the PMDG 747, it's very, very frustrating. There's no performance issues at all, constant 60fps+ in very dense areas such as Overland Haneda with full settings, 100% AI and using the PMDG 747. Is there anything I can do to fix it? Maybe a .cfg edit? I have no idea what to do... (Oh and I also checked through my scenery, no empty texture files, all looks good)
|
|
swag
Ramp Rat
Posts: 37
|
Post by swag on Feb 2, 2013 5:36:16 GMT -5
Firstly, I'll list my specs and OS GPU: GTX 670 CPU: i7 @ 4.5GHz RAM: 8GB 1866MHz Cooling: H100 OS: W7 64bit So I really have no idea how it could be anything to do with my system, as it's perfectly capable of running FS9. This is usually happening with the PMDG 747, it's very, very frustrating. There's no performance issues at all, constant 60fps+ in very dense areas such as Overland Haneda with full settings, 100% AI and using the PMDG 747. Is there anything I can do to fix it? Maybe a .cfg edit? I have no idea what to do... (Oh and I also checked through my scenery, no empty texture files, all looks good) OOM errors are a sign that the application runs out of virtual address space (which is almost totally unrelated to actual memory, i.e. RAM). Try running a 4 GB patch on FS9.exe. I use www.ntcore.com/4gb_patch.phpOn Windows 7 64-bit this doubles the amount of virtual address space that FS9 can request. Usually that is enough for prevent OOM errors for occurring, unless you have lots of aggravating factors such as landclass files in directories that also have texture subdirectories etc.
|
|
|
Post by jalpilot on Feb 2, 2013 10:34:44 GMT -5
Well, after a flight from Osaka to Haneda including two go arounds, no crash at all! Seems to have fixed it, thank you very much!
|
|