jabloomf1230

Gold
  • Content count

    4,458
  • Joined

  • Last visited

Community Reputation

773 Excellent

2 Followers

About jabloomf1230

  • Rank
    Minister of Silly Walks
  • Birthday December 30

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    none
  • Virtual Airlines
    No

Profile Information

  • Gender
    Male
  • Location
    NY Hudson Valley, & WA

About Me

  • About Me
    Pilot License, Professional Engineer, Ph.D Engineering.

Recent Profile Visitors

2,965 profile views
  1. jabloomf1230

    shorten voxatc training files

    This problem started when MS restricted the speech trainer that was built-in to approximately 14 lines of text. This happened with the the Windows 10 1709 update and impacted all flight sim apps that use the built-in speech trainer like MCE, P2ATC and VOXATC. There are actually a few suggestions in this subforum. One user suggested splitting the training file into two shorter pieces, but I'm not sure how they did that. I do know that the VOXATC speech trainer uses XML template files, that can be found in the the VOXATC folder. They start with either IFR or VFR, for example, IFRDEP.xml. You could try editing these files with Notepad (or better yet Notepad++) to make them shorter. Make sure you save the originals in a safe location outside the VOXATC main folder, in the event that you make an editing error. Not all flightplans create a training file that exceeds 14 lines, so try using the default XML files first.
  2. jabloomf1230

    Just Flight Traffic Global (Early Access) Available

    My prediction is we are going to see other freeware installers like MAIW's Matrix that are legal (permission obtained from the model, paint and schedule authors).
  3. I suspect that ATC will have something to say about that.
  4. jabloomf1230

    Limiting Framerate kills framerate - why?

    FFTF Dynamic also has a frame rate range target, but in Prepar3d.cfg, the frame rate limit is set to 32. Vsync is on, but with a 60Hz monitor, I've never seen any difference, either on or off.
  5. jabloomf1230

    Limiting Framerate kills framerate - why?

    4.0 Correct. As stated a few times before, FFTF doesn't range from 0 to 1, but rather from some small number (0.01) to integer values like 1, 2 or even 4. Since FFTF only a limit, there are diminishing returns of setting FFTF at an integer value, as there may never be such a high demand in the sim for scenery texture loading. Hence, such a high value will have no effect. As Gerard has stated, it's best to set the high FFTF value at a number that is just above the default (0.33) and then see whether that improves matters. I originally ran FFTF Dynamic in a range of 0.01 to 0.4, but after experimenting, I have been using 0.2 to 0.65 and 7,000 AGL. Each setup will need its own experimentation to see whether autogen and texture loading starts noticeably lagging. All this "goodness" (AA, mipmapped textures, model multiple LODs, "the blurries", autogen not loading, etc.) is left over from the ACES team trying to keep FSX usable even when the hardware is stressed. Without these shortcuts, portions of the screen would end up rendering as black. With these tricks, at least the sim continues to look vaguely unobjectionable. In contrast, LR (although they use some of the same time-honored tricks) just set a lower FPS limit of 20. When that is breached, XP11 goes into "slow motion mode": https://www.x-plane.com/kb/the-simulators-measurement-of-time-is-slow/
  6. jabloomf1230

    Limiting Framerate kills framerate - why?

    Thanks. I posted that because people were questioning the use of FFTF > 0.33 with FFTF Dynamic.
  7. jabloomf1230

    Limiting Framerate kills framerate - why?

    FFTF is a maximum limit. If a frame takes 33 ms (that's roughly 30 fps) to render and FFTF is 0.33, then a maximum of 11 ms will be spent running fiber jobs. As I understand it (and this hasn't changed going all the way back FSX), if 11 ms isn't needed, then the fiber jobs will use less than that. It's possible that LM changed the way that FFTF works, but the above concept means that FFTF could have values greater than 1.0. It's just an upper bound as to how much time is spent loading scenery textures.
  8. jabloomf1230

    Limiting Framerate kills framerate - why?

    I may wrong about this but isn't this all about math? The frame rate limiter clips any frame rates above the limit, so in your case 40 fps. Hence, frame rate will vary between the minimum and 40. If you want a mean frame rate of 40, the limit would have to be higher. If one continually lowers the frame rate limit, the range between the minimum and limit will become smaller and smaller and hence the mean frame rate will approach a central value.
  9. jabloomf1230

    LatinVFR Baltimore Terrain/ Ground Issue

    It's actually designed not only with a custom mesh but as I pointed out, it also utilizes multiple airport background polygons of differing AMSL, to provide realistic flat spots in the terrain mesh. Most airports just have one airport background polygon that flattens the terrain at the same AMSL as both the runways and aprons and also eliminates landclass autogen.
  10. jabloomf1230

    fsx atc maydays

    VOXATC does this quite nicely, so the task can't be that monumental. It handles engine failure, fuel critically low, hydraulic failure, avionics failure and passenger critically ill. Once the squawk is recognized, ATC will vector the user to nearest airport that can handle the aircraft. VOXATC also provides vectoring around weather. The other 3rd party add-ons probably do some of or all of this too, but I've never tried it when using those add-ons.
  11. jabloomf1230

    LatinVFR Baltimore Terrain/ Ground Issue

    See if this file is installed in your BWI folder: KBWI_ADEP4_RGM_CVX.bgl This file contains the airport background flatten polygons which establishes the airport elevation and and the exclusion polygon that eliminates autogen, etc. from displaying within the airport. Also check that you don't have another 3rd party version of KBWI installed. Lastly, make sure that your third-party airports are the highest priority in your scenery library. LatinVFR KBWI has various flattened elevations within the airport proper.
  12. jabloomf1230

    Airport AI traffic clusters around user aircraft

    It doesn't happen to me, but then again I use the FSUIPC traffic limiter with VOXATC. I just looked with Little NavMap while on the ground at Flightbeam KDEN and the AI are spread out nicely at various gates. I'll check their KMSP when I get a chance.
  13. It's been awhile since I had UTL installed, but doesn't it have a bunch of settings to adjust the traffic level in order to optimize frame rate? Or do they no longer work? See section 5.3.2, Traffic Generation Options in the UTL Manual. I do know that the comparable settings in FSUIPC work beautifully with BGL-base AI traffic.
  14. jabloomf1230

    Descent problem

    Thanks. I suspect that the bogus tower frequency might have caused the crash problem described by the OP, but unless it reoccurs for him, I wouldn't create an updated airport with ADE that deletes the tower frequency. fsaerodata already has the airport's comms matching the real world, so no change is needed for fsaerodata users.
  15. jabloomf1230

    Descent problem

    Let me think about it some more. Do you know offhand if LECD has an active control tower in real life? I looked at a few websites but I couldn't tell if it did or not.