Jim Young

Thanks Christopher. All these abbreviations. Have to stop speed reading as it is not working... Sorry Stan for hijacking your topic. Best regards,

Glad I was able to help. Welcome to AVSIM! Best regards,

Product upgrade was released in July 2015 and announced here. Any additional release information is advertising. Topic closed. EDIT: Think I'll merge this with the release topic instead.

I use the developers recommended settings of 30% for MyTraffic6. UTX2 is tough on fps but so is other similar products. Are you using it with GEX? NickN has posted his settings for UTX2 in the GEX/UTX forum and I use those settings. Still, high autogen settings will be hard on your fps. Best regards,

OOM's can happen on super powerful computer systems too because, when you run out of the allocated 4GB's of virtual address space (VAS) that you operating system provides, you will get an OOM. Just in case you have not seen this from PMDG - http://support.precisionmanuals.com/kb/a108/vas-management-stopping-out-of-memory-oom-errors.aspx. If you have high setting/overclock, I would think your VAS usage would be depleted faster as it is processing things faster. Only when we get to the 64 bit applications will we be truly able to crank up our powerful systems as VAS will still be limited in 64 bit applications but the amount of VAS Windows allocates will be almost impossible to deplete. Lockheed Martin did do some optimizing of their graphics and other things that could be optimized but it does not eliminate OOM's. I use the freeware tool called FSUIPC to monitor my VAS usage during a flight and, when it starts going down to a level that will cause an OOM, I will turn off things that might be causing the loss, like my weather program, ASN. On page 3 of the AVSIM CTD Guide (link in my signature), we provide instructions for configuring the FSUIPC tool - Monitor VAS (modified from the guide to show only the information you need as you have a 64 bit operating system) Startup program and then enter the Add-on Menu and select FSUIPC. Once FSUIPC is open, click on the Logging Tab and enter 024C under Offset and select S32 under Type. Select where you would like to have the usage displayed. The FS Window is for Full Screen sessions. The FS Title Bar is for Windowed Mode. AVSIM recommends you also check the Normal log file as this provides you information on how much VAS you had to start out with and then logs usage throughout your flight. The VAS usage is displayed in Kilobytes (KB’s). The value represents the amount of VAS left so, the lower the value, the more VAS being depleted. The max amount of VAS allowed in computers with 64 bit Operating Systems is 4GB’s if running 32 bit applications like FSX/P3D. To convert the KB’s to the amount of GB’s, you should use one of the Byte converters on the Internet like the following: Byte Converter. You will never see 4194304 KB’s displayed as this equals 4GB’s. You might see around 3GB’s (3145728) remaining when you first start up FSX/P3D but that too would be unusual. Do not be concerned with the amount of VAS remaining when you first start up. It fluctuates during a flight session. One of the things I do after using FSUIPC to monitor my VAS usage is to open up the FSUIPC.log after a flight and review it (I have a shortcut to the fsuipc.log on my desktop). It will show you how much VAS was used just to load P3D to the setup screen, then loading to your departure area in your flight plan, and then showing the VAS usage during the flight. You will always see VAS going down dramatically as you descend to your destination. the log will also show you the average FPS during the flight and average VAS usage. Sometimes I'll run Process Monitor which I configured to run and only show P3D and P3D addon's loading (see page 4 of the AVSIM CTD Guide). I want to make sure there are no scenery loading on the other side of the world where I'm flying. Photoscenery will load if enabled even if the scenery is located on the other side of the world and take up valuable VAS. I have seen FTX/Orbx stuff loading too that is far, far away from my flight plan but it is usually the Orbx/FTX Objects loading. Nothing you can do if you are flying over FTX areas but it is upsetting to see these object loading thousands of miles away. But, there are things I might see that I can shutdown during the flight. Maybe that will help, maybe not. You know we really did not have these problems when FSX (P3D is basically FSX as it uses the same engine) was first released. We had less powerful systems back then and everyone kept their settings at a modest level. Everything was 32 bit then. Then we heard about a /3GB switch that would give us up to 3GB's of VAS (we only had 2GB's of VAS available then to use) and we started cranking up our FSX settings thinking we had more space and power. Some computer experts gave us tips on tweaks we could use to maximize our enjoyment of FSX. Now, we have extremely powerful systems (compared to the systems back in 2006/2007), 64 bit operating systems, the ability to overclock, and we all think we can now max things out. We could except for the VAS limitations. Hope this helps. Best regards,

Topic locked. This old topic has run it's course. Maybe start a new one.

FYI, your post was removed as you tried to regurgitate an old topic (necropost). The removal appears to be valid IMHO. Best regards,

Just open Windows Explorer and go to the drive where you installed FSX. Right Click on FSX.exe and select Send to and then Desktop. A shortcut will be placed on your desktop. I believe you can also right click fsx.exe and select Pin to Task Bar. Occasionally an icon is not created when the program (or any program) is installed. I also removed your e-mail address as there are scammers on the Internet looking for e-mails to send spam. Just have someone PM you. When someone PM's you, a message from AVSIM is automatically sent to your e-mail address to let you know you have a PM (Private Message). Best regards,

LOL!!!

Hi Monty, AVSIM hosts commercial and freeware forums but, for the most part, we do not moderate commercial forums like PMDG's unless a person is pirating, posting pornography, spamming, and violating license agreements. The forums belong to the commercial developer and he can do whatever he/she deems appropriate. Therefore your complaint is between you and PMDG and you can go to their website and logon and submit a trouble-ticket and PMDG staff may respond. We do not delete topics or posts here at AVSIM unless it is a duplicate post. They are hidden from member's view. Moderating is a difficult task in that you are in trouble if you do something and in trouble if you don't do something. Except for PMDG, all of our moderators are volunteers and they try to do the best job possible. If I interfered with the PMDG Corporation on their decisions, it would be like me going to the Aerosoft Corporation and telling them they shouldn't remove your post form view. What happened to you at PMDG was not public but now it is public as you have posted your complaint on AVSIM. I'm sorry but there is nothing I can do. Just do as I and many of our moderators have to do occasionally and take a deep breath and move on. Best regards,

My PSP is the default. I only own Orbx stuff for the NW. For all of my frequently visited airports or airports where I have bought a commercial version, I'll rename the AFCAD in the MyTraffic\Scenery folder. Your post reminded me to also do this for KPSP and I checked and had not renamed it yet. That may indeed be the problem. I will check later to see if that fixed it and, if it didn't I'll post back. I have seen duplicate aircraft at KSTL (Taxi2Gate) and KCLT (Imagine) and I had renamed both of those airports in MyTraffic. Best regards,

In MyTraffic6, aircraft takeoff and land based on the flight schedules in the program. You might have hit the wrong time of the day when most aircraft are up in the air. Eventually though, it will begin to fill up the airport as aircraft land and taxi to the gate. So, at departure, there may not be many aircraft but when you get to your destination, the airport should have tons of aircraft at the gates and aircraft taking off and landing. That's how the developer explained it in his manual anyway (page 18, Operations Manual and page 23 for AI Traffic Density Settings) and one reason why I keep my slider at no higher than 30% because 100% isn't going to get you a full airport immediately but you have 100% of your aircraft flying and trying to follow the programs flight plans. That's all over the world. My issue so far has been duplicate aircraft at the airports. For instance, at Palm Springs, I'll see two FedEx aircraft inside each other at 30% AI setting. The manual says this will happen frequently if at 100% but a reduction below 94% should stop most of the duplicate flights. Well, they haven't for me at many of the airports. Sometimes I'll see two aircraft sitting at the same gate. Sometimes I have to look hard to see those duplicate aircraft though. Back to PSP, I got rid of the duplicate aircraft by reducing the AI setting to 15%. That's the setting I use now and most of the time I see a lot of aircraft. By the time I get to my destination at KLAX, there are 3-4 heavies ready to takeoff and many other aircraft at the gates. Best regards,

Hi Ed, We are aware of the problem and you cannot do a basic search but, if you hit the cog next to the search button and go to Advanced Search, it works perfectly. Go figure! It may take some time to figure this one out as so far we cannot see anything wrong with the code. Best regards,

Tapatalk refused to make their app compatible with our forums so Tom (the late owner here at AVSIM) got rid of it. I use Chrome and have no problems visiting AVSIM (and sometimes moderating) with my SmartPhone. Best regards,

Hi Ron, Yes but I do not own the aircraft yet. I just made the announcement so others can check it out. But it looks like it will have the same AP as in all other twin engine aircraft. The Alabeo website has more information on what's included and some specifications. Best regards,

I've never seen my VAS hitting 4GB's. My VAS after loading P3D, is not even 2GB's but it appears it stays at that level for most of the flight and begins to shrink only when landing or getting near a airport. Still, P3D appears to be trying to keep at least 400 MB's of VAS. But this scenario is thrown out the window when I have several addons enabled, like ASN and GEP3D and UTX. If you can, turn off cloud shadows, especially if you are going to have a long flight. I think cloud shadows are nice but only for VFR flights or short flights. At FL330, there's no reason to have the shadows enabled as you are up in the clouds yet your sim is using the resources for cloud shadows. Autogen is particularly hard on resources by P3D optimized those textures and the way autogen is loaded and it has seriously gotten better. Instead of running Process Explorer and Process Monitor, set up the VAS usage report in FSUIPC. It works for the registered or unregistered version. I have the guidance for setting it up in the AVSIM CTD Guide around page 4 or 5. What I like about this monitor is the fact it logs your VAS usage throughout the flight and, when you complete the flight and shutdown P3D, you can go to the FSUIPC folder and open up the FSUIPC.log (I have made a desktop shortcut to this log). It will then tell you how much VAS was used just to load up P3D, how much VAS used after loading your flight, and then a running counter of VAS all the way to the end of the flight. It will also show you your average FPS during the flight and the high/low amount of VAS usage. What I do with these logs is save them after a flight as something to indicate what flight the log was for, such as KORD_KSTL.log. I can then go and fly the same route, but this time change the aircraft or take away the weather program, etc., etc., and then see what the log says after this flight. Lots of hard work but everyone is trying to tweak and get the best settings possible for their personal computer system and doing less and less flying and this method of seeing what is taking up all of your resources is a way to have some fun and maybe solve some of the problems hitting your system. When we finally get to a 64 bit P3D, you can then turn up your settings as you will basically have unlimited VAS for a flight (there will still be limits but the amount of VAS space will be almost impossible to exceed). Then what are we going to do? No more OOM's and we can enjoy a full flight? What kind of fun is that!! LOL I'm glad my tip on the EMT tool worked for you too. Best regards,

In the AVSIM CTD Guide, we have instructions on setting it up: To run this utility properly, you need to capture only FSX/P3D/FS9 events. It would be nearly impossible to find a possible glitch or issue if Windows events or other system activities were being logged too. AVSIM recommends opening of the Process Monitor when you are on the active runway and preparing to takeoff to save space on your HDD: Startup FSX/P3D/FS9, as appropriate, to the Setup Screen. Open Process Monitor Click on the Filter tab and then Filter…. Click on Architecture and scroll down to Process Name Click on blank box and select FSX/P3D/FS9, as appropriate Click Ok or Apply NOTE: AVSIM recommends you click on the filter tab again and then select ‘Save filter…’ and name your Filter – FSX (or P3D/FS9). Then, in the future, you can startup Process Monitor before opening your application and watch what is loading as your application loads to the Setup Screen. You can use the utility while in Full Screen mode or Windowed Mode. In Windowed Mode you can monitor what is happening instantly but it is best to run Process Monitor in Full Screen (unless you are seeing freezes in Windowed Mode). When the flight is finished, immediately go to the Process Monitor application, click on it to bring it into focus, and hit Ctrl+E on your keyboard to capture the events (event logging will continue until you do this and make it more difficult to locate the cause of your crash). Shutdown FSX/P3D/FS9 and begin your investigating! You can also save the log for future investigations but remember the file will be as large as 8GB’s or more and using valuable disk space. I have used the 3.11 version. I'll have to download and try the latest version. I just downloaded and installed the latest version (3.2) and it is running just P3D perfectly. Best regards,

Alabeo just released the PA23 AZTEC. Check it out! Best regards,

Well, I cannot say you didn't provide sufficient information! You detailed your actions and issues well! You received a StackHash error when running EZDOK. Here's what the AVSIM CTD Guide says about a StackHash (better I copy this than write it all out again): StackHash – See also BEX and NTDLL.dll above. There is no module on your computer system named StackHash so no need to look for it. If the StackHash is shown as the faulting module, it will have four characters next to it like StackHash_0a9e. That represents the memory address of where the fault occurred. Do not try to look for it. You will not find it. There is no known solution (except one) to BEX/StackHash errors other than reinstalling Windows and FSX but some have accidently fixed their problem by lowering fsx/display driver settings, rebuilding the FSX.cfg, changing voltages/overclocking settings in the BIOS, disabling all scenery add-ons in the Scenery Library, and/or shutting down FSX only in Windowed Mode and starting up in Windowed Mode but never in Full Screen. One known solution is disabling MyTrafficX 5.4c in your Scenery Library. An AI schedule might be causing this crash as the schedule may be looking for a flight and it cannot be found. There are also AFCAD’s that come with MTX and some of those may contain objects. If disabling the program in the Scenery Library works, then you should reinstall the product and use the default schedules. I did not include any of the other information in the CTD Guide about this issue as I no longer support those "solutions" but the "probable fixes" above were taken from Googling all flight simulator websites looking for possible solutions to a StackHash and these were the ones I found worked for others. EZDOK is simply not configured or installed correctly. I have removed EZDOK from my computer as it is buggy and requires hours, sometimes days, to set up properly so there will be no errors. I don't need it. The Russian developers need to develop a product that works right out of the box with little or no additional configuration. Instead, they have issues written fixes for getting around certain issues with their software. I suspect the bad installation of EZDOK (probably a SimConnect issue), is the cause of the StackHash. Do you have all of the SimConnects from FSX installed? I have no expertise in SimConnect as it is used in Networking and getting an addon like ASN to communicate to P3D. ASN does an excellent job of setting up SimConnect so their product works efficiently with P3D. EZDOK has not upgraded their product to make it work out of the box with P3D and I doubt they ever will. They are hoping people who have configured EZDOK to work with P3D perfectly will tell users how to install their product and how to configure their product. Our SimConnect forum might have some advice. There is most likely solutions in the P3D Forum. If you cannot find any solutions to getting EZDOK to work properly without causing a StackHash, then you will have to uninstall it and hope the developer issues updates to fix the problem. You need to make sure your system overclock is removed until this problem is fixed as a too high or too low CPU voltage setting will cause a StackHash and/or NTDLL.dll error 100% of the time even though AppCrashView is showing EZDOK as the fault. You will have to uninstall EZDOK and restart P3D and make sure P3D is again stable. I always cringe when I hear people reinstall DirectX. DirectX comes with your Operating System - http://windows.microsoft.com/en-us/windows/directx-faq#1TC=windows-7. If you updated DirectX, you will now need to scan your system for any corrupted files as DirectX can only be updated through Windows Update - https://support.microsoft.com/en-us/kb/929833. Since you have Windows 10 installed, I would also check the Internet for updated hardware drivers. I use Driver Booster which is free but it has a lot of nags to try to get you to buy it. Still you can update everything for free. Windows 10 is still new and new hardware drivers for your HHD's and USB ports, etc., are updated quite frequently to get rid of bugs found. Hope this helps. Best regards,

The ASUS AI Suite is one of the worse ever developed and I have long time ago removed AI Suite from my computer and installed only the drivers I need. I still have issues with the AMDA00 driver and just disable it as updating it is impossible (well, I did get it to work once). I think the ASUS techs in Taiwan could care less about making their product work w/o any issues. They continue to make newer motherboards and continue to issue the buggy ASUS AI Suite. Okay, I'm off my soapbox.... You can go into your system configuration and disable any of the startup programs. Startup programs are really not needed. You need to then look under the services tab and look for any ASUS service or a service related to DipAwayMode and disable it. To get to your system configuration in Windows 10 go here - http://windows.microsoft.com/en-us/windows-10/how-to-open-msconfig-in-windows-10. I had to disable ASUS Com Service and ASUS HM Com Service to fix my problems with my system and have seen no adverse issues as a result. It is almost impossible to delete these services once they have been installed. Maybe that's by design of the techs at ASUS. Whenever I reinstall my OS again, I will not install these services or anything in the AI Suite. One poster on the internet fixed his problem with dipawaymode by disabling it in Scheduling - https://rog.asus.com/forum/showthread.php?55493-DipAwayMode-exe-event-log-entry-on-each-boot-reboot. Best regards,

I have removed the off-topic posts. It is not just the FS9 Forum where members accidentally (or on purpose) make posts in the wrong forums. It is one reason why we have Moderators and the 'Report' button. The 'Report' button sends your complaint or issue to an AVSIM Moderator immediately who will take a look at the post or issue and take necessary action deemed appropriate. I suspect you mean the AVSIM Forum page? What is wrong with it? The forum is set up in the similar manner as all of the other forums so I'm confused. Best regards,

Since you just reinstalled Windows you problem is most likely caused by a bad driver. There are a lot of new drivers that have been released for this new operating system and they keep getting updated to eliminate the bugs. Here is a possible solution from the ASUS website - http://vip.asus.com/forum/view.aspx?id=20140316060356859&board_id=1&model=X79-DELUXE&page=1&SLanguage=en-us . I would also run a Driver Updater program. I use Driver Booster which is freeware but it has a lot of nags to try to get you to purchase it. You don't need to - http://www.iobit.com/en/driver-booster.php. Best regards,

Did you enter the highmemfix=1 parameter in the Graphics section of your config? A bad bufferpools tweak will do this too. Best regards,

Hi, The topic just below yours provides information on how to use our search feature until we can find the code to fix this issue. Just click on the cog next to the search button and go to advanced search. It works. Best regards,

The error is most likely with the GPS and not with the Aerosoft product. Crashes with aircraft gauges are common and it may be just a permission issue. So, when you click on a gauge that was not "blessed" by FSX or your computer system, your computer will not allow you access to it. What aircraft are you using? Is it an addon? Did you install it with Administrative Privileges and/or was UAC and any anti-virus program disabled from scanning your installation and use of the product? What sim are you using? What operating system? Best regards,