jabloomf1230

Pete, No, VOXATC sets the AM for just its DLL (GAU). I didn't think that a DLL could set its own affinity mask independent of the app that references the library , but I looked it up and according to Microsoft documentation, it is doable without too much fuss. Maybe the option in VOXATC doesn’t really work, because there is no easy way of checking what cores it uses.

I know that FSUIPC can set an affinity mask for the specific apps that it spawns via the ini file, but has there been any thought to adding an option to allow setting an AM for the host FSUIPC process? I only thought about this because I had posted something here recently about VOXATC. VOXATC consists of a gauge that has an option to allow the user to set its AM prior to run time.

Pete, I believe that the P3d/FSX SDK Traffic Toolbox DLL Explorer can display the name of the source BGL for each AI aircraft.

Post your question on the VRS support forums. Your problems aren't really related to FSUIPC.

You are better off asking this on the VRS official forum, as you may have a hardware problem. The same question has been asked a number of times there. I have the VRS Superbug and I can tell you that to get the trigger and pickle to work with FSUIPC, one has to use FSUIPC to map the HOTAS trigger button to SHIFT, CONTROL, V and the pickle button to SHIFT, CONTROL, C. Then in the VRS Tacpack Configuration Manager under the category of General Preferences, Trigger Mapping. Set the radio button to keyboard (not controller) , Trigger to SHIFT, CONTROL, V and Pickle to SHIFT, CONTROL, C.

Pete, I did a bunch of testing and I never saw any discrepancy between your largest FCB value and what VMap displayed for P3d. It was also unusual to see any free VAS fragments adjacent in the VAS address map to the largest FCB. The difference between free VAS and largest FCB only seems to be numerically important when the free VAS goes under 400-500 MB. In that range, the sum of the remaining VAS fragments tends to be in the hundreds of MB range. Of course this is with P3d 3.4 and my addon mix. Your mileage will vary. Jay

FSUIPC beeps twice when free VAS reaches 300 MB. You could alter Gypsy Baron's LUA script above to add a beep pattern . Maybe he'll repost with revised code, but you could also do it yourself.

Pete, You can check your result versus Mark Russinovich's utility VMap: https://technet.microsoft.com/en-us/sysinternals/vmmap.aspx Run VMap and then point to either P3d or FSX then click on "free memory" and it will show all the free blocks for the app. The fragmentation view for each 32 bit app is also instructive. Jay

Ed, FSUIPC already provides an easy way to monitor free VAS. Just use offset 024C. I display the value it in the sim's title bar, which is one of the options. Jay

At least it brackets the range between the total free VAS and largest FCB.

The new option seems to work for me without any ill effect on the sim. Howver I will keep testing as I did not try to coax an OOM. As expected, when P3d loads, the displayed FCB value is identical to the free VAS value, but as the flight progresses the disparity increases. I don't have any thoughts on the FSUIPC warning beep other than making it a user option as to which VAS value to use. Thanks again for adding this option and hoping that its usefulness in P3d is short-lived. ;-) As to recovering VAS, I think that Process Lasso supposedly attempts to do this, but I could never see any improvement with VAS usage in P3d so I don't use Process Lasso anymore. I'm guessing that especially now with Hotfix 2, P3d 3.4 probably does the best job that it can with squeezing the last drop of juice out of the VAS lemon. BTW, the new AI traffic limiter and options are great. There's a long thread about it at AVSim, which you probably already saw.

Thanks. I'll let you know what I find.

Thanks, but that's the amount of free VAS available, not the largest contiguous block. The problem with only displaying the total amount of free VAS is that OOMs are caused by the sim trying to allocate an amount of VAS that exceeds the largest contiguous block of VAS that is available. This (VAS fragmentation) is why OOMs occur at a variable amount of free VAS left.

Pete, A preemptive "welcome back" and I hope that you enjoyed your holiday. Would it be possible to add an option to monitor and display the size of the largest contiguous block of VAS that is available to the sim? I found a snippet of C code online that does just that and I have been playing around with it: http://blog.kalmbachnet.de/?postid=9 It seems that this value might be a helpful adjunct for monitoring how close the sim is to an OOM. The most recent P3d Hotfix 2 does do a better job of cleaning up VAS than previous versions, but OOMs still a problem. Or we can just wait until P3d 64 bit is released and then no one will worry about VAS anymore. Jay

Thanks Pete.

@Pete This is not really related to FSUIPC, but I was wondering if you have ever noticed this "misbehavior" amongst SimConnect apps: http://www.prepar3d.com/forum/viewtopic.php?f=6310&t=120711&p=142317&hilit=sode#p142317 Jay

Pete, Thanks, FSDeveloper was the first place that I browsed and the BGL boundary type information is interesting. I did create a dummy airport between KALB and KSWF with just Boston Center (ZBW) comm frequencies, but LAAP didn't use the audio streams, even though they showed up in f5.csv correctly. I must have done something else wrong, so I'll keep working on it. Jay EDIT: The Center boundary file is bvcf.bgl and is located at: <main sim folder>\Scenery\World\scenery I looked at both the P3d and FSX versions with various viewers and it just has Boundary sections. Some have Com subsections, so that's where the frequencies reside. <BoundaryStart lat="N43 39.569" lon="W076 46.093" minimumAltitudeType="MSL" altitudeMinimum="0.0M" maximumAltitudeType="UNLIMITED" altitudeMaximum="100000.0M"/> <Com frequency="135.2500" type="CENTER" name="BOSTON"/> <Line lat="N43 39.952" lon="W076 46.046"/> I used ScruffyDuck's most recent version of BGL2XML to parse the file.

This isn't exactly a support issue, but I have a question about MakeRunways. It generates a number of files designed for use with various 3rd party apps. One of the files is F5.csv and it contains the various comm frequencies by type. I understand that these frequencies are culled from all the airport bgl files that are listed in scenery.cfg. My interest is specifically in comm type 10 (Center). Some airport BGL files have these frequencies and some don't, depending on the surrounding airspace types. My question is when one clicks the ATC menu item "Request Flight Following", where does FSX/P3d "find" the ARTCC/ACC frequencies and the center boundaries? It can't be from the individual airport BGL files. I spent the last hour using Google trying to figure this out. My interest has to do with matching real time ATC audio streams to the active sim comm frequency. I purchased the donationware app LAAP (Live ATC Auto Play) several years ago and it works great with a database that it creates using f5.csv : http://laap.atc.free.fr/presentation-en.html When I fly within the Minneapolis ARTCC region, it happily finds the Center's audio streams, but that's because many of the airports in the this region of the US have the Center comm type built in to their BGL file. In other areas, like for example New York and New England, this rarely works, mainly because most of the airports do not have Boston and NY Center frequencies included in their BGL file. If the ARTCC boundaries and comm frequencies aren't stored in their own BGL file(s), would creating a dummy airport with the Center comm frequencies work for my purpose with LAAP? Or would doing so just muddle the sim up worse? Would it be safer to just add Center comm frequencies to various airports with Airport Design Editor? Unfortunately, this latter approach could be tedious.

I'm pretty sure that not rebooting after the V3. 3 client install caused the problem. I vaguely remember a few posts on AVSim that describe odd behavior of joysticks in P3d after doing a client update without a reboot.

Pete, That's been my previous experience also... Just install the new P3d client, then install the updated version of FSUIPC4 and then everything works fine. This time for some reason, it didn't, so I renamed the FSUIPC4.ini file and reprogrammed all the buttons and axes. My guess is that not rebooting the computer after the client install was probably my dumb mistake. Anyway, all is good now. Jay

I updated the client version only of P3d to V3.3. I then installed FSUIPC 4.955. Disabled controllers in P3d. I set up axes and buttons from within FSUIPC4 UI. All the axes work on both the stick controller and the throttle controller as they did in V3.2. All the buttons work on the stick controller. None of the buttons work on the throttle controller. The buttons are recognized by various Windows joystick tester apps and the Saitek calibration app. EDIT: Redoing axis and button assignments fixed it. I deleted attached log file and ini snippet.

Exception code 0xc0000374 (heap corruption): https://social.technet.microsoft.com/Forums/windows/en-US/578396fd-29c0-4dd3-b002-5e2e8df1b398/exception-code-0xc0000374?forum=w7itprogeneral http://blogs.msdn.com/b/calvin_hsia/archive/2015/01/30/10590143.aspx I saw this exception previously, but I haven't seen it in probably 6 months. At the time, it had something to do with MyTraffic 5.4, but the exact cause was not determined.

Same here. CTD. Faulting application name: Prepar3D.exe, version: 2.5.12943.0, time stamp: 0x54e39da6 Faulting module name: ai_player.dll, version: 2.5.12943.0, time stamp: 0x54e39da2 Exception code: 0xc0000005 Fault offset: 0x00045d19 Faulting process id: 0x864 Faulting application start time: 0x01d0538cd180f3d7 Faulting application path: G:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Prepar3D.exe Faulting module path: G:\Program Files (x86)\Lockheed Martin\Prepar3D v2\ai_player.dll Report Id: 26f9a090-bf80-11e4-822c-001fbc02953f Faulting package full name: Faulting package-relative application ID:

Pete, I thought that I would thank you here for all your hard work on this and also for trying to help me out over at AVSim. Maybe DTG will figure this out at some point and the few of us that have this CTD can use the sim again. Jay