Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Warning
Severity: Informational
Symptom: Missing Events in Event Log
Details: Investigate why 42% (74,848) events were lost during data collection. The settings for Event Tracing for Windows (ETW) maximum buffers and buffer size may not be optimal depending on which data sets are being collected.
Related: Event Tracing for Windows
The game is newly installed on this computer
Game files were verified
Nothing new from that so far
were would i find
C:\Windows\Performance\WinSAT\DataStore\Formal.Assessment. (Recent) WinSAT.xml
If you are getting 2 fps with the ultralight trike on some farm strip then there's more problems than the graphics settings.
If you have tweaked your config file, try running without the tweaks. It would be easy to mess something up when you change that file, especially if you're using some setting that is higher than what you could get in the settings dialog in the game.
I have a high end computer with my frame rate locked at 20 (default which was set during install) and there are still times it falls below that when things get too complex, like flying a complex plane into Anchorage. I had most of my graphics settings at or near max and this ended up producing occasional Out Of Memory errors. I lowered a few settings one notch and have had no OOM problems since.
Hook
The payware version (Steve's DX10 Scenery Fixer) is the further development of the freeware DX10 Shader Fixers in the link above. It contains numerous improvements, including automatic installation (and many additional fixes not included in the freeware version) that really make FSX fully functional in DX10. See: https://stevesfsxanalysis.wordpress.com/features/ for more details including how to purchase. Highly recommended, not least for the excellent cockpit shadows not available with DX9
The developers (ACES Studio) were not able to finish programming DirectX 10 by the time the sim was due for release in stores. Microsoft's bean counters decided that initial sales were more important than producing a fully polished simulator for the long run.
Since X-Plane 11 is a 64 bit app, it should be almost impossible to get an OOM error unless you have only a small amount of RAM. The same applies to v4 of P3D.
OOMs are caused by too little RAM (or virtual address space - VAS), not VRAM.
Prepar3D version 2.5
What are you suggesting?
Neither did I until I got my current computer. I would get crashes on the previous computer but the Event Viewer never indicated out of memory and I never got the dialog from FSX or P3D.
I'm trying to imagine under what circumstances you could get an OOM from a 64 bit program.
An airplane with lots more features than default and it doesn't matter the size of the aircraft. The A2A Piper Cub is a complex plane even though it is very simple because of internal processing.
Hook
Someone might actually have too little RAM?
This whole sequence is bizarre.
Hook
My first ever OOM was produced by the A2A Piper Cub, which uses a lot of VAS, but the major problem was loading it into a flight over another A2A plane which had already used a lot of VAS. A two hour flight from Durant OK to Dallas and I hit the OOM while circling the downtown area. Another flight on the same route with the same plane but continuing on to F00 used 3852 meg (out of 4096) while the same flight with a simpler aircraft (Golden Age Stearman, the old version, not the one currently available) used 2883.
None of this addresses the OP's 2 fps but even if he gets his frame rate to an acceptable level if his sliders are too high he's at risk of an OOM. Which is why I mentioned it.
Hook
That was a question, not a statement. Please do not misquote me.
Hook
Further to this make sure you test with the default flight on the paraglider aircraft. After a complete steam vertify you should be seeing around 50-60fps.
Also, make sure to set your view distance to something realistic like 60-90NM. Shadows are a real frame killer and so is any type of anti aliasing. Pro-Tip: up your resolution using nvidia control panel and turn off AA altogether. This has saved around 10fps for me in the past.
Have you any 3rd party aircraft from Carenado or using fsuipc??? My frames dropped to less than 5fps after installing an update to the Cessna G1000. Were 50-60fps before.
I have had a similar issue such as yours running the sim in Dx9 mode but fixed it switching to Dx10 (using Steve’s dx10 fixer tool). Dx10 looks way better anyway.
Pro-tip: try switching between dx9 and dx10 modes as some 3rd party add-ons can mess with this setting in your config file inside your my documents folder. This has caused me a headache or 2 in the past.
And the best bit of advice I could give anyone reading this is just switch to P3Dv4 or X-Plane and save yourself any more worry. Both of which are supported by the developer and upgraded much more frequently. 64-bit is the way forward my friend.