tom79
Members
-
Joined
-
Last visited
-
The error listed above comes from the .NET framework. Might be that your installation is corrupted somehome. You can try to repair it with this tool: http://www.microsoft.com/en-us/download/details.aspx?id=30135 If that doesn't help, try a complete reinstallation of the Framework: http://www.majorgeeks.com/files/details/microsoft_net_framework_cleanup_tool.html
-
Hmmm, the AXE can use both Navigraph and Navdata Pro navigation databases. Did you switch to Navigraph in the AirbusX configurator? In any case, Aerosoft has a dedicated support forum where you can ask the developers directly.
-
Froogle has a nice tutorial video that also shows how to enter flight plans in the AXE:
-
-
Are you running FSX and Squawkbox as admin? If not you should do so.
-
No, that's for Bojote's Shader 3.0 mod. http://forum.avsim.net/topic/283701-bojotes-shader-30-mod-for-fsx/
-
Bufferpools maybe?
-
The 1M size is just from my personal experience. Your mileage may vary. Theoretically, if FSX needs to load some resource, say a 5MB texture, there must be at least one contiguous block of address space left that can accomodate these 5MB. If not FSX will OOM. Virtual Size is what you should be looking at. Private Bytes doesn't include address space used for DLLs for example. The full explanantion can be found here: http://channel9.msdn.com/Events/TechEd/NorthAmerica/2011/WCL405
-
Correct. Are you still running 32bit Windows? Under 32bit Windows, each application has 2GB VAS (it's acutally 4GB, but only 2GB effectively usable). Under 64bit Windows, each 32bit application has the full 4GB VAS (64bit apps have a lot more). When the free VAS goes close to zero, you should get an OOM.
-
You dont need to monitor other processes. Highlight the "Free" row in VMMap and sort by block size descending in the bottom part of the screen like so: http://imageshack.us/a/img580/941/fsxmemvmo1gdefdrv125m.png First key indicator is the total amount of free VAS, that is the number showing in the "Free" row. Your second indicator is the largest contigous block size of free VAS which shows in the bottom part of the screen. That should show at least 1 meg. Note that VMap doesnt update auotmatically like ProcessExplorer does. So you need tohit F5 from time to time. IIRC you can set it to update automatically, but that degrades performance and ultimately let to VMMap crashing on my system after a while.
-
Actually, I did not regard Dillon's original post to be bashing PMDG but rather an expression of his concern that the old lady FSX may not do it much longer and that we need to start looking out for a new platform in the near future. Maybe I've read it wrong...Dillion fancies himself as our local heresy hunter, opposition prognosticator and cold hard dry ridiculer and general all around know it all show off. I for ne, and I am sure many others as well are not going to take a single more slant from him without serious remedy Enjoy your movie Stephen! I'm off to a concert as well B) Cheers, Tom
-
As far as I understand, that is only relevant to 32bit operating systems. Under Win7 64bit, only the parts of the video memory that are actually used by FSX for GPU resources such as textures are mapped into the address space and that only applies to DX9.
-
AI packages such a WOAI (Word of AI) use aircraft models that are still in FS9 or even FS8 format. These slow down the sim and can cause other problems. So what the OP was asking for is to abandon those legacy AI aircraft models for native FSX models.
-
I think it's considerably less when you select only scenery region.More around 10GB. The installer will tell you...
-
OOMs can also occur when the VAS gets largely fragmented (link). So if FSX needs to allocate 1MB of memory and there is no contiguous block of free address space with at least 1MB size, on OOM would also occur. VMMap can display the structure of the free address space. However, since the OP stated that he is getting OOMs at around 2.7G VAS usage, I doubt that the memory is that much fragmented at this point.