Jump to content

Search the Community

Showing results for tags 'oom'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • New Member Forums
    • Welcome New Members!
    • Help Using the AVSIM Forums
    • Help Creating an AVSIM Account and Logging on to AVSIM
  • AVSIM Fixed Based Operations (FBO)!
    • Hangar Chat
    • Flight Planning
    • Virtual Reality (VR) Hardware and Games
    • Letters to the Editorial Staff of AVSIM
    • All About Us
    • Crash To Desktop (CTD) Forum
    • The Bargain Hunter's Shack
    • Classified Ads | Want Ads | Swap Meet
    • AVSIM's Round the World Race Forum
    • AVSIM Reviews Feedback
    • The File Library General Forum
    • Flight Sim & Aviation User Stories
    • In Memoriam of Tom Allensworth
    • In Memoriam
  • Microsoft Flight Simulator Forums
    • Microsoft Flight Simulator (2020)
    • MS FSX | FSX-SE Forum
    • The Microsoft Flight (2012) Forum
    • The FS2004 (FS9) Forum
    • Flight Simulator Tips and Tricks
    • Shared Cockpits | Multi-Player Forum for FSX | FSX-SE | P3D
    • MS FSX | FSX=SE | P3D Simconnect Forum
    • FSX | P3D Missions Forum - How To
    • FSX/FSX-SE Aircraft and Panel Design Forum - How To
    • FSX | FSX-SE Scenery Design Forum - How To
    • The Paint Shop - The Aircraft Painter's Forum - How To
    • Mesh Scenery Design - How To
    • TTools for MSFS Forum
    • Add On Developer's Forum
    • DX-10 Discussions, Hints and Help
  • The Prepar3D Forums
    • The Prepar3d Forum
    • Prepar3D Tips, Tricks and How To's
  • The X-Plane Forums
    • The X-Plane General Discussions Forum
    • X-Plane Tips and Tricks
  • The IPACS Aerofly Forums
    • IPACS AeroFly FS2
  • Simulator Screen Shots, Real Aviation Photos, & Videos
    • The AVSIM Screen Shots Forum
    • Real Aviation Photos
    • Aviation and Flight Sim Video Forum
  • Hardware & Operating Systems Discussions
    • WIN10 OS Forum
    • WIN8 OS Forum
    • The Win7 OS Forum
    • MOBO | RAM | CPU | HDD | SSD | Desktops | Laptops
    • Monitors | Multi-Monitors | Video Cards | Drivers
    • Hardware Controllers | Joysticks | Drivers
    • Networks | WIFI | Routers | Ethernet | DSL | Cable Modems
  • Commercial Support Forums (Hosted by AVSIM)
    • FS2Crew Support Forum
    • Mindstar Aviation Support Forum
    • The RealityXP Support Forum
    • The Official DX10 Scenery Fixer Support Forum
    • The Multi-Crew Experience (MCE) Support Forum
    • Virtual Avionics Support Forum
    • Lorby-SI Support Forum
    • Pilot2ATC Users Forum
    • The Carenado Support Forum
    • The Alabeo Support Forum
    • Remote CDU for Phone / Tablet Official Support Forum
    • Airline2Sim Support Forum
    • SX Airport Design Forum
    • P3D Tweak Assistant (PTA) and RealismShaderPack
    • The simPlugins Support Forum
    • SimSettingsManager Official Support Forum
    • simFDR General Support Forum
    • Blue Sky Star Simulations Support Forum
    • Capt. PERO Support Forum
    • Flysimware Forum
    • Mid-Atlantic Air Museum Simulations Support
    • FSReborn Series Support Forum
    • Desk Pilot - Shared Cockpits
    • PhotoSim Labs - Bahamas sceneries
    • Fulcrum Simulator Controls
  • User-to-User Support Forums
  • Freeware Support Forums
  • Virtual Airlines News and Discussion
  • Home Cockpit Builders
  • Other Civil Aviation Simulators
  • International Language Forums
  • Other Forums

Categories

  • Articles
  • AVSIM News
  • File Library News
  • AVSIM Reviews
    • Hardware
    • Aircraft
    • Scenery
  • Product Announcements & Press Releases
  • What's New @ AVSIM
  • Interviews
  • AVSIM Editorials
  • Guest Editorials
  • Obituaries

Blogs

  • Tom Allensworth's Blog
  • Gaiiden's Scroll
  • Brandon's Box
  • Jess B's X-plane blog thingy
  • Tom_Test's Blog
  • Alpha Floor's Logbook
  • GolfPilot
  • adi518's Blog
  • Chase's Blog
  • The Big Tour
  • Tales of a Wannabe Pilot
  • Farmer Looking Skyward

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests


About Me


About Me

Found 16 results

  1. My friends, I think most people running P3D are aware that many in our community suffer from Out of Memory errors (despite using the recommended methods to avoid them) and there are also those who like me don't have this problem. While reading a particular post this evening, I wondered if DX11 doesn't have some residual mirror allocation going on, or if there might otherwise be some relationship between OOMs and those with video cards that contain higher amounts or VRAM. In other words, some type of relationship which might result in someone with a video card having 4GB, 6GB, 8GB, etc., with all things being equal, be more prone to suffering an OOM than someone with 1GB or 2GB VRAM. For the record, I'm aware of the differences between DX9 and DX11, so we don't need to have this conversation. I'm hoping that people suffering from OOMs will consider providing some of their system specs in order to help track the source of comparative OOMs (all things being equal between two systems, one system is prone to OOMs while the other is not). This is only for OOMs under Prepar3d (P3D). Terms Used: RAM Physical Memory on the Motherboard VRAM Physical Memory on the Graphics Card VAS Virtual Address Space, basically the specific space set devoted to an application (such as P3D). With a 64bit operating system, the size of allocated VAS can be up to 4GB for each 32bit application. DATA COLLECTION 1. Version of Prepar3d? 2. Processor Type (example: i7 4770K) Overclocked? Turbo Mode Setting)? 3. GPU *Please create separate entry for each video card. Manufacturer (example: Gigabyte) Model Number (example: GTX980) Overclocked? Amount of VRAM? 4. Amount of RAM? 5. Number of monitors in use (may or may not display P3D? 6. Number of monitors on which P3D is displayed on? 7. Did you have more than two airport sceneries enabled during the OOM(s)? Many thanks for your help.
  2. Hi, it would be really helpful if anyone could help me I fly 90% of the time in the PMDG 777 and I always get an OOM error on final My specs: Inter® Core2 Duo CPU E7500 @2.93GHz 2.94 GHz RAM: 4.00 GB (3.00 GB usable) 32 bit operating system. I know its not suitable for gaming I never get OOM when using default airports but when I use da freeware airports the VAS reduces rapidly during touchdown and I get an OOM error. ( I fly in VATSIM) If anyone of you could fix this error then I would be more happier than my wedding day Its really frustrating when one day I was about to land after a 9 hour flight from Delhi to Heathrow and then an OOM error occured just after touchdown... I only wanna use the freeware airports to get the updated taxiways and gates as provided in the charts. Not the payware ones.... I hope anyone could tell me a solution for me
  3. Ok was looking for some possible help. After being visited by our unwanted friend, I wanted to see if I am doing something wrong. I have ensured that I have all of the latest updates and that I am running the latest software. Ok we go I continue to get plagues on the following flight. YSSY (Fly Tampa settings to minimal) to KSFO (Flighthbeam). I am using ASNext with Textures from REX. Only have California Central and Northern Photo scenery activated. All other Airports and Photo scenery are inactivated. I have the FO screens shut off. My system settings are as follows: Textures: 1024 LOD: 4.0 Autogen: None Water: Mid 2x AI Cars, Boats, Ships: 0 UT2 AI Commercial: 60 UT2 AI Private: 0 After I depart YSSY my VAS stays steady at approx 2.8-2.9, however as the day progresses into night the VAS slowly climbs and hits the 4.0 mark. This seems to be common only to this area, I can fly KSFO-EGLL with essentially the same settings, only difference is that when I depart in the night I don't run into the same problem and can make it to EGLL. If you require any further information, please let me know, other than that I am looking for any support to resolve this issue. V/R Kristopher Plummer
  4. Many third-party airplanes today are shipping with 4k/2k textures. While we can debate its usefulness to no end, the fact remains that they are quite memory intensive. There are ways to reduce texture sizes and mip them, but I came across an easy tool which makes it a breeze, http://www.nexusmods.com/skyrim/mods/12801/?, developed by AdPipino for Skyrim and other games. I let this program run through my airplanes folder, to reduce texture size to 1k and mip them also, and then I measured the results. All tests were done on runway at supposedly the most isolated airports in the world, Mataveri International Airport / SCIP. All situation were loaded after fresh start of P3D from saved flights. After loading I panned/zoomed around in both VC and spot view, measured VAS using ProcExp and GPU using MSI Afterburner. While VAS and its effects we all know, I am not sure about GPU memory and its effects, but I still measured it. GPU experts can chime in. System Specs: i7-4700MQ @ 2.8, 16GB 1866Mhz Ram, 755M SLI 2GB DDR5, 128+512GB SSD Settings of note: FFTF=0.0, AM=244, TEXTUREMAXLOAD=27, TEXTURE_MAX_LOAD=1024 Observations: We are saving about 150-300MB VAS, depending upon the Airplane. None of these aircraft had mips in their original textures. Some have 4k textures, some 2k. You might think that just by selecting 1024 as texture size in the P3D settings, it might reduce memory load. But this is not true as you can see above. This maybe because, none of the original textures are mipped, my guess. So if you want you can choose not to reduce the textures, but just mip them. I have not tried this. After reduction, I did not see any visual difference. There were no FPS differences between the textures sizes, so this does not do anything for FPS performance. The B1900D has shimmer in the cockpit controls with the original textures, but after reducing/mipping there is no shimmer :smile: So how can you do it easily? 1. Make a copy of the Airplanes folder in SimObjects directory. Let the copy be in the SimObjects folder itself. 2. Run Ordenador tool (link above), and select the folder copy you just made. And other settings as below Also in the More/Extras tab, un-select backup option, as we already made a backup. 3. Click Start and wait for 10-15 minutes for it to finish. (You may have to confirm the no backup and reduce textures options in the subsequent dialog prompts) 4. After finishing, I suggest you copy the log window and save it as text for future reference if need be. (for me the original folder size was around 21GB and it came down to 10GB after reduction) 5. Rename the original Airplanes folder to something like "Airplanes_ORIGINAL". 6. Rename your folder copy to "Airplanes" You can switch back and forth between original textures and reduced ones just by renaming the folders in future. I also want to try out the new BC6/BC7 texture formats supported by DX11, but the conversion speed is pretty pathetic with the tools today. Maybe in the future. Mega Airport experiments are next up, till then just imagine the savings! Edit: I just realized that the textures more than 1k and being cut in half, but not cut to 1k. E.g. 4k texture becomes 2k, 2k becomes 1k. So finally we are left with 4k converted to 2k. If we run tool one more time, it should convert the 2k (4k originally) down to 1k also. So more savings!
  5. This document is long but if you're interested in why you're suffering from OOM errors and how to avoid them, grab a cuppa something and read on... What do you mean I have to reinstall again? Since installing Prepar3d v2.4 and v2.5, I too have been suffering from OOM errors as well as 'random' crashes to desktop. This has resulted in four reinstalls of Prepar3d and two system reinstalls. Not a pleasant way to spend my spare time but I learned a lot doing it, so time well spent. After my most recent reinstall of Prepar3d v2.5, a few weeks ago, I made the decision to only install native add-ons or non-native add-ons that I can install manually, without the Migration tool. I also decided to install them one at a time, instead of all at once, to compare their performance, evaluate their use i.e. 'do i really need this?', as well as optimising them for use in Prepar3d. 'These go to 11' If more third parties optimised their add-ons and if consumers were more conservative with their settings, a lot less people would be suffering from OOM errors and random crashes. As consumers, we shouldn't have to optimise our payware but as most third party add-on developers focus on looks and not performance, you will never get the best performance you can 'out of the box'. There are a few exceptions where developers provide optimised products that need no further optimising but they are still the minority. The main problem is that most consumers still don't know how to optimise their add-ons and/or want to spend the time doing it. The attitude, 'I paid for it, it should work' prevails, which, as a consumer, I understand, but as someone who wants their sim to look and perform as best as possible, I can't accept. From a developers point of view, I understand the old arguments but they hold no weight with modern graphics cards and recent versions of Prepar3d, there are simply no excuses for not providing optimised products for Prepar3d. I haven't had any OOM errors in Prepar3d v2.5 since optimising my add-ons but I can easily trigger one if I want to. I don't get them any more because I check and optimise every add-on that I purchase and use realistic in-game settings that achieve a compromise between looking great and performing excellently. Multum in Parvo It is possible to have a great looking and smooth sim experience without having all the sliders to the right. By optimising my textures, I have seen a huge drop in VAS consumption and a very noticeable boost in performance. All I did was resize oversized textures (reduce from 4096 to 2048 or 1024 pixel width) and save them in the correct format with mipmaps (DXT1 no alpha, DXT5 with alpha). This cost me a lot of time but everything looks and runs much better now, no more shimmering in the cockpit and no more shimmering in external view. It's the difference between 1.3mb and 16mb PER texture in some cases. Multiply that by ten and you can see what's consuming your VAS. The irony is that the optimised version nearly always looks better. Compared to the time you can spend looking for that elusive holy grail tweak, this one actually has visible and immediate results. The mipmap VC panels option in the simulator does not work as you might expect, you will need to optimise the textures yourself if you want the best result. I have this option off. A quick example, I recently bought a brand new GA third party aircraft developed for Prepar3d. After installing it, I loaded it up only to see that the cockpit gauges shimmer, small text is hard to read and straight lines in textures look like marching ants as soon as I move my head using Track IR head tracking. Half an hour later, I had an optimised product, that looks much better and performs much better, with cockpit text and labels that are clear and easy to read, the gauges now look smooth and the external textures load instantly. The best bit, it consumes much less VAS and frees up resources to run the sim more smoothly. Plane spotting AI aircraft also consume VAS and can easily cost you 20 fps on top if set up too optimistically. UT2 is, in my opinion, the best looking and the best performing AI package, as long as you mipmap the textures correctly, but unfortunately unsupported for Prepar3d, and the last time I used the Migration Tool to install it, I had to reinstall Prepar3d after files became corrupt. My attempts at a manual install also resulted in a reinstall of Prepar3d. The only official AI package that I know of that has been developed for Prepar3d, My Traffic 6, fills the skies with all kinds of wonderful aircraft, even the textures are correctly mipmapped, but unfortunately the models are not as optimised as UT2, so unless I am extremely conservative with the AI sliders, I can cause my fps to drop by 20 frames, great for plane-spotting at airports but not that great if I want a smooth flight out of EGLL. Unification Everybody's setup is unique and no two systems will perform the same, even with the same hardware. This is why the process of 'unification', as practiced by people like Michael Greenblatt or Nick Needham, is so important. Unification doesn't mean tweaking cfg files or resizing textures, it's understanding how to design a system and then set it up correctly for optimal use. The right hardware, the right software, the right add-ons, the right settings... it takes time to learn and it takes time to set up correctly but once you get it right, you get the best sim experience available to the public. You don't need the latest hardware to run everything well, you just need an optimised system and a fast quad core processor. VAS is my currency The FSX/ESP engine was not designed to work with uncompressed textures larger than 1024 pixel width. Even if they load, there is always a price to pay. The currency is VAS. It's not just incorrectly sized textures without mipmaps, high resolution mesh has a price, even third party weather and ATC add-ons can cost you an OOM if not set up correctly. When I met the developer of FEX a few years ago, he showed me FSX running with 4096 pixel width ground textures. Not just at an airport, the whole world was covered in 4096 textures. FSX loaded and ran fine, no signs of an OOM error. This was proof of concept only and ran in a default install of FSX Acceleration but I bet if we had added all of the popular add-ons that we use today, the sim would have crashed too. Some developers have wised up and now offer an extra set of textures for their products, in a 'lower' resolution and are very active in trying to prevent OOM errors. Lower resolution doesn't have to mean it looks worse, default size 1024 textures that are well made look great too. 2048 is the maximum size I allow into my sim. Here's the reality... 4 badly optimised textures can consume around 100mb of VAS. 4 correctly optimised textures consume around 5mb of VAS. Mipmapped textures might appear to have a larger file size than same dimension non-mipped textures but in reality they ease the load on the CPU/GPU and prevent a kind of shimmering that people often confuse with geometry shimmer and try to combat with high levels of forced anti-aliasing. Ever wonder why when you load an aircraft in the Scenario Editor, it takes time to load the textures and when they appear, they are hard edged and unclear? Mipmaps is why, or rather the lack of. Wouldn't you like it if the textures in your shiny new third party aircraft were clear and readable and smooth? Maybe you don't care but the lack of proper custom anti-aliasing options in Prepar3D make the lack of mipmaps even more painfully obvious. Most Payware add-ons are designed to look amazing, that's why uncompressed over-sized textures are used so often. Why should a developer care? They have made a product that looks great and works fine on a default install of Prepar3d. They have done their job. We are purchasing the right to experience this product, no more, no less, it's like buying a ticket for a ride at the fair. We are therefore responsible for ensuring that these products are optimised. But if we combine an unoptimised aircraft with two unoptimised airports and then add high resolution mesh, terrain and cloud shadows, AI, full cloud cover, thousands of buildings covering huge Ultra LOD areas, hundreds of unoptimised cloud textures, what else could happen but... tl;dr - optimise your add-ons
  6. Can anyone help with this as I am completely flumoxed! Since moving to FSX-SE, following a brand new install, and an upgrade to i7 6700 not OC. With 16Gb RAM 3200Mhz and a GTX 770 4gb, I have had numerous OOMs, which I never had with FSX. Now today, i loaded the A2A 182 at Orbx Harvey Field in PNW. Autogen Dense, LOD at 6.5 all the usual things turned down, nothing different from previous flights. Within 30 seconds of climbing into the cockpit, the dinging bell started to suggest an OOM. When I looked at Process Explorer it was showing just shy of 2,7Gb. Very odd. Anyway, I closed everything down and fired up the sim again. This time I reduced LOD to 6. Ah I thought, that must be the problem, although I am still perplexed as to why process explorer was showing less that 2.8 memory usage. I continued my flight west towards Sequim valley airport, about 50 miles away. When I got close to landing, the bell started to ding again and I got those typical graphical spikes climbing out of the ground. Just prior to seeing the sim crash, I switched from fullscreen into windowed to see process explorer showing the same memory usage as before, except maybe 2.9 or so. What on earth has gone on here? Can anyone offer some help with this, as it seems to be happening a lot. Cheers.
  7. Hello, You might remember a tool i wrote a long time ago whose objective was to monitor VAS usage during a simulator session (FSX/P3D). The original FSMem, although featuring memory usage warnings and selectable memory thresholds for these warnings, lacked one feature that i consider the most important: - Memory logging. With this in mind and once i had a couple of days free, i coded a new application from scratch to do just that. FSMem2 now displays a graphic of either used or free memory, constantly displays free and available memory and, most importantly, logs and exports memory usage data. You can then use the logs to better understand when, how, why your memory is used by the simulators. Hopefully this isn't going to be required for long with the apparent proximity of x64 versions of P3D, but for now it might still be useful. README INCLUDED IN THE ARCHIVE DOWNLOAD HERE Here's a small screenshot sample, hope you find this too useful somehow.
  8. Hello everyone, I have just recently flown VATSIM's CTP 2015 westbound. On final approach, the FS made the error noises and crashed. This is strange for me because I am using Direct X 10. I have flown much longer flights 15-17 hour flights without this anomaly, but on this short flight from EHAM-KBOS, an OOM!!! I thought OOMs couldn't happen under Direct X 10. I am using Steve's DirectX fixer to make everything work. Is there some explanation for this problem? Thanks, 1251452 PS: the acars (VAFS sucks) also failed to recover the flight, so all is lost.
  9. Hello all, I haven't experienced oom for a long while since I dicovered the workaround to significantly reduce the risk of OOM (not to select STAR in preflight stage but before descent, because the VAS may continuously accumulate en-route if the STAR has a certain kind of missed approach precedure), but everything got ruined when I flew my PMDG 777 into CYYZ. I am just curious to know if there is someone who has successfully fly a PMDG 777 into Flytampa Toronto CYYZ. Even though I had a flight from Flightbeam KSFO HD to FSDT KLAX, I didn't experience OOM. My settings are definitely not agressive, but moderate. I have no idea why I still got OOM... I have tested the sceneries by Process Explorer, and noticed that 3.1 to 3.5GB VAS has been used just after I started the flight at gate and pan around the cockpit...I have FTX Global with Vector installed. You may say it consumes VAS so much and should be the cause of the OOM, but I have successfully made flights without OOM with the same settings and addons installed for almost a year. Therefore I think there should be some other reasons... In addition, although I have turned "Transparent Glass and Interiors" option ON, I still can't see through the glass of terminals. Does anyone here having any idea? Here are some crucial parameters in fsx.cfg LOD_RADIUS=4.5 TEXTURE_MAX_LOAD=4096 IMAGE_COMPLEXITY=4 AUTOGEN_DENSITY=3 Here are my settings in Flytampa Configurator: 3D Grass...OFF 3D Grass (ramp)...OFF 3D People...OFF Static Vehicles...OFF Animated Cars...OFF Animated Apron Traffic...OFF Transparent Glass and Interiors...ON (all options in "effect" section)...ON Animated Traffic Lights...ON Anson Cheung
  10. Hi Everyone, I've been immersing myself in the forums, here and elsewhere, to research the VAS/memory management problem that most of us who have 3.4 are struggling with. I'm convinced that it's a memory management problem. In any case, I'm curious to find out what the last version was that did NOT have these VAS problems. Maybe I can ask LM to let me roll it back since I started with 3.4 and can't get earlier versions. My VAS problems are pretty much identical to what everyone's been talking about recently. I'm still in the process of tweaking things, but maybe it will be worthwhile to see if an older version is a better option for decent performance/eye-candy until this issue gets addressed. I can hold my own for the most part with out going near OOM unless I'm in the 777 coming into JFK, and next worst airports are at LAXv2 and DFW. I don't have my sliders to the right, except for those run by the GPU, and am using low res textures. Traffic rarely above 10% unless I'm going into a smaller airport and I'll kick it up a little. Frames hover in the low 20s at most addon airports in the Airbus and 737, and of course, performance is spectacular in default ac. The CS 777 is a performance hog, knocking me down to 12-15fps in most cases at any airport, under any condition. Vectors are limited to primary and secondary roads and my cloud textures are also low. I guess what I'm getting at is I understand the VAS problem, and am learning how to manage settings in order to get the most performance vs graphics. But, after 2 weeks of constant tweaking, researching and testing, version 3.4 just doesn't give back VAS once it takes it away. The only way I can regenerate the memory is to save the flight, make it default, and restart P3D. Fortunately because of the SSD, the process only takes about 1-2 minutes. However, I'm wondering if a previous version would perform better, and if so, which one should I ask for? Thanks, John I7-6700k @4.4-4.6ghz (don't know which is more stable yet) 16gb 2100 DDR4 GTX1060 4gb (little better than the 960, but not by much- may return it) SSD for P3D and all addons ORBX Vector, HD Airports, Global, North America AS16 PMDG ngx Aerosoft Airbus Captain Sim 777 (unflyable), will upgrade to PMDG once I can get performance up Various popular FSDT, Flightbeam, Taxi2gate and Fly Tampa for USA and CYYZ, and Aerosoft (EGLL) airports MT6 (had UT2 migrated fine, but took a big performance hit and AI liveries too much to manage and update.
  11. Twice in a row and at about the same point, I am getting an out of memory error not long after takeoff when flying Tutorial 1 for the NGX. It has never occurred anywhere else yet, and in fact, after it happened last night I flew a manual flight for about 2 hours without an issue? I'm in Prepar3d V3.4. Any ideas would be appreciated! Thanks Pete Intel i7-6700 Gigabyte Gaming Motherboard 2 x LPX DDR4 2133Mhz 8GB (total 16GB) Armaggeddon HectotronTex Case Cougar 800W Modular PSU Kingston 240GB SSD Seagate 1TB 3.5" 7200rpm Gigabyte GTX 980 4GB DVD Burner Win 10 64 Bit
  12. Hello captains, I don't know if here is the right place to put this but I think that this is an interesting tool. https://drive.google.com/file/d/0B6atkUYYWmkteHhkaG5aUkVpcnc/edit?usp=sharing This is a software that I wrote to myself but I think that it can be helpful to many people. This software monitors your FSX VAS. It's very intuitive. Just double click on setup to install. After the installation, double click the FSX VAS Monitor icon. If the FSX is already started, FSX VAS Monitor should automatically start to read the FSUIPC offset 024C. If the FSX was started after the FSX VAS Monitor, click the Connect Button and it will start monitoring. there are only 4 adjusts to set, the minimum quantity of memory avaliable before trigger the alarm (in MB), if the alarm will run with the red text blinking and a ding sound, and if the FSX VAS Monitor should start directly on system tray. System Requeriments: FSX (obviously) with FSUIPC installed. It works with WideFS too (Ideal to people that use two or more computers). This software is free to distribute. have a good flights... Fred Matias spilfred@gmail.com B)
  13. Hi, I'm a week into P3D, I've been on FSX for 2 years. I bought a beefed up machine (6700k, gtx 1080 etc) with the intention of bringing my love of FSX to P3D. After reinstalling everything from my AI traffic (WoAi), PMDG 777, to Orbx Global and Vector and about 50+ Airports, I have yet to complete a long haul, 8hr plus in my case, something I was so used to in FSX. For those with a similar configuration and experience in P3D, what should I be doing differently? An example of my last long-haul failure: Imagine Sim's WSSS to FlyTampa EHAM with PMDG 777, about a 13-hour flight (A flight I somehow pulled off in FSX). I took off with 27% VAS remaining, about 3 Hours into the flight VAS had jumped to 14% remaining, 7.5 hours in over Turkmenistan at the break of dawn I get an OOM error and eventual CTD. Any help would be really appreciated. Best, Leon
  14. Hello All, First off the plane is amazing! It does what it is supposed to do if you know how to fly it!! My question is performance related. I have flown the cojones off this thing since she was released but i have noticed one issue with it and i was wondering if you all could potentially shed some light on the situation! Flight #1 N581UP Paint PHNL(FSDT)-KONT(Addon) Left PHNL with no issue, about 3 hours into the flight over the ocean well short of landfall i noticed my VAS was creeping up in the high 80s low 90s OVER WATER! Eventually leading to the Audible ding in the simulator that told me it was to late to save it...Subsequently i save the flight and restarted the PC with AutoSave. I was then able to land without issue after re-loading the flight! Flight #4 N578UP Paint KSDF(BluePrint) -PANC(Aerosoft) SAME RESULT....VAS crept up into the mid 90s this time over Northern Canada...restarted and continued the flight from AutoSave...Upon landing in PANC when i started to pull into parking i was getting the audible OOM ding...I was able to shut down and submit my flight before the sim crashed! Flight #5 N581UP Paint PANC(Aerosoft)-KONT(Addon) Left PANC at about 78%...now as i sit here typing this i am at FL350 over the ocean west of Vancouver with no land in sight and over the course of 2 Hrs and 1 Minute from takeoff the VAS has crept all the way up to 89%-90% 3607MB Could this have been due to a bad install .exe? For reference in the 777 i only see 68%-72% sitting on the ground at PANC Equipment: i7 6700K clocked to 4.5, 16GBDDR4 RAM, Nvidia GTX970, 500GB Samsung SSD P3d.cfg and simmed have been expertly tuned as well for optimum performance. Sadly all tests are pointing back to the plane possibly being the issue! Thanks for the assistance!! Rich M.
  15. Hi, After a series of OOMs I have reverted back to the 376.33 driver for my GTX 1080. NVidia recently released a second hot fix driver, 378.77, has anyone had any time to test it out? Best, Chike
  16. Recently, I was flying the PMDG 777 from EGLL to KSFO (flight BA285/BAW11M), and my route took me ever so slightly south of Iceland and over the southern part of Greenland. After leaving the west coast of Greenland, I received a high VAS warning from FSUIPC, and I realised that my VAS usage was at 94%. This was significantly higher than I would have expected, and - eventually - I got an OOM error (my first one in Prepar3d V3). I honestly can't figure out what caused it; P3D handles VAS very well, and I have flown this flight once before with exactly the same scenery and settings, and there were absolutely no issues. The only difference between this flight* and my previous flight** is that this flight's route took me much closer to Iceland (further north). Therefore, I can only think of three possible causes: 1) Something in Iceland led to an extremely significant increase in VAS usage (in spite of the fact that I don't own any scenery in Iceland); 2) Orbx recently updated the Orbx Libraries, and this was related to whatever caused the OOM error; 3) I flew over Manchester, and UK2000's EGCC caused a dramatic increase in VAS usage (which I find difficult to believe). I am aware that Orbx have a free Iceland demonstration product; however, I have never installed it. I would like to emphasise that the VAS usage when I flew this flight previously was nowhere near 94% when I was leaving the west coast of Greenland, and all of my scenery and settings were exactly the same. The only difference (as far as I am aware) was the route. Thank you for taking the time to read this; I would be very appreciative if anyone could provide a possible explanation for this seemingly random increase in VAS usage. Cheers, Oliver *This route (with an OOM error): WOBUN UL10 DTY DCT SAPCO UN57 TNT UL28 PENIL UL70 BAGSO DCT ERNAN DCT BALIX DCT BREKI DCT 66N040W 66N050W DCT EPMAN NCAE YYN J530 GTF J7 LKT DCT LLC J32 FMG J94 ECA RISTI4 **Previous route (without an OOM error): WOBUN DCT WELIN UT420 TNT UL28 RODOL UM65 TENSO UL603 REMSI DCT DIMLI DCT GINGA DCT GOMUP DCT 61N020W 63N030W 65N040W 66N050W DCT EPMAN NCAE YYN J530 GTF J7 LKT DCT LLC J32 FMG J94 ECA
×
×
  • Create New...