Jump to content

All Activity

This stream auto-updates     

  1. Past hour
  2. You can scrap that 'probably'. 😉 In all my months of using BATC I haven't said a single word (to BATC at least LOL). I don't even have a mic attached to my PC. Since last week you can toggle the UI with a single key/button and 'say' the first request with another key/button which makes it all quite convenient. (Would be even better if BATC would get an ingame panel and options to say every possible request with a key/button but the current setup works well.)
  3. Great shots, Todd. I have been to California a couple of times, but, you might call that ignorance, had never heard of this National Park. It sure looks interesting and I too would love to go there and explore it further.
  4. **Minor Update 1.0.25.EA** ```- Added email verification to registration process. - Many bug fixes for reported system crashes. - Better gate leniency to allow for bad gate data to still be handled in the case no useable gates are found. - Fix for bindings on non-US keyboards causing a crash. - Continued work on voices. Should now allow for Irish voices on the Premium Voice Model.```
  5. Thanks for letting me know. I'll look into it but I think I know what it is already and will come up with a fix very shortly. In the interim, if you only uncheck when all three app status items are green(ie. you are in an active flight) it shouldn't crash.
  6. Many thanks for commenting, my friends! I was wondering that too, that is why, except for the last picture, I showed a motor boat. It got a propeller! 🙂
  7. @Reset XPDR When Unchecking OLOD the app (b14) crashes.. It happens on both pc’s. Freshly downloaded and just want to Uncheck OLOD. When restarting the app OLOD is unchecked. That did not happen with all other test versions ( tested up to b12 before )
  8. GNS 530/430 does not work for me. Both are black and I found no way to make it function. I'm with the piston and in SU15 beta.
  9. That's because, if you are looking at the TAXI_PATH definition, it doesn't really make much sense to have coordinates for a "path". A path is just a segment with a start and and end (the START and END parameters) which are just integer indexes to a list of TAXI_POINT elements (they are just before the path in the SDK docs). The TAXI_POINT have coordinates, which are expressed as offsets in *meters* (BIAS_X and BIAS_Z) from the Airport reference point, which is finally in Lat Lon. So, assuming you wanted to "draw" a map of taxiways, you need to: - First get the basic Airport record (from ICAO), which will tell you basic things, like Lat/Lon of its ref point, but also how many taxi points and paths there are, which you'll surely need https://docs.flightsimulator.com/html/Programming_Tools/SimConnect/API_Reference/Facilities/SimConnect_AddToFacilityDefinition.htm#airport - Get all the TAXI_POINTs and store them away in some table. - Get all TAXI_PATHs and use the Start and End as Indexes into the table of TAXI_POINTs, so you can draw the individual segments. If you only work in Lat/Lon, since the taxi_point data is expressed as an offset in meters from the airport center (as many things in the Navdata API are), you'll need some formula to add a linear distance to Lat/Lon, like the popular GeographicLib (Open Source and available on many platforms and languages), to get the actual Lat/Lon coordinates of the various points. You can also get a list of TAXI_NAMES, which the TAXI_PATH references to, as indexes.
  10. I agree with you because the only thing that works best is what is paid for, otherwise why differentiate between paid and free products?
  11. Today
  12. According to the scale on the cabin pressure controller, the Turbine Duke can sustain a typical airliner cabin altitude of 8,000 ft only up to a pressure altitude of 22,000 ft. Question: How do real-world operators typically deal with this? Do they limit their cruise altitude to FL 220? Do they use supplemental oxygen above FL 220? Do they simply accept the higher cabin altitude? IIUC, cabin altitudes up to 12,000 ft are legal, though they may not be prudent for extended periods of time.
  13. You can say exactly the same in reverse: if you don't extract data from the sim, the instructions received won't match what users SEE in the *actual* scenery, if that scenery is not up to date to real world, which happens very often because, while it's reasonably easy to get updated Navdata from various providers (you either pay, or require your users to pay by having a separate subscription), updating sceneries is way more complex, and it's even more complex the more detailed they are. Default airports, with all their flaws, are *easier* to update (and we'll see it after World Hub comes out), because the "data" directly drives the visual generation, so you add/move a taxiway, and will be moved both in the navdata and visually (you'll only need to fix vertical signage), but fully customized 3rd party add-ons, which feature completely custom background photoreal images, with multiple layers of custom ground textures, ground markings and vertical signs (possibly fully customized), take much longer to update, so it's very common for the scenery not to be up to date to real world. In these situations, not taking data from the sim, will force users to taxi basically ignoring what they see outside, and stick on the map, assuming the airplane *has* a moving map feature which is connected to updated Navdata, like one with Navigraph integration. Taxiing this way, even if might be "realistic", is not very fun, and it's quite frustrating not being able to rely on the various ground markings or vertical signs, because you KNOW that, if the ATC gave you a taxi routing based on real world, you can't be 100% sure the scenery will match. What I can tell you for sure is: if you stick to the decision of using only real world data, lots of users (those who pay for add-on sceneries) will only be frustrated by having a bad experience on the scenery they bought, and saying "the ATC always says the truth", even if it's technically correct, it's not helping to improve the usability, and if you think all hundreds/thousands of add-on sceneries will be eventually updated, it's really a lost battle: scenery developers are usually busy with the next scenery rather than update the old ones, because it's the next scenery that brings money to stay alive, and in some cases, it might not even possible to update, because new aerial images might not be available yet, there are many reasons why sceneries are out of date but, regardless of the reasons, they usually ARE. That's why I suggested to offer the OPTION to use Navdata from Simconnect, at least on ground, where the relationship with Navdata with the actual visible scenery (and its eventual disagreement) is more distracting.
  14. MFS2020 using Microsoft Ai as an ATC INSANE!! Manchester - Dublin (youtube.com)
  15. That only works for escalators. (Stand on the right, pass on the left).
  16. I haven't tested using default aircraft since I never fly them. Yes I believe Riva tuner is sub optimal if trying to cap using Frame Gen. I am not using AI traffic. I fly on VATSIM and found incredible FPS gains by reducing the FSLTL model matching to 2k liveries however it didn't seem to affect the stutters.
  17. I wasn't 100% sure about that but during my testing over the last couple of months I find I get much better performance and less stutters when capping inside of NVCP rather than RTSS.
  18. 😁 MFS2020 using Microsoft Ai as an ATC INSANE!! Manchester - Dublin (youtube.com) As expected, it can potentially be used also with P3D and XP... Aerofly FS... Aerowinx PSX... Airlinetools... Ehehehehe
  19. I assume OP already know it but Rivatuner will indeed introduce a lot of stutters and performance drops if you cap while running FG. If you wanna cap using FG, use the Nvidia Control Panel cap.
  20. Have you tested using a default aircraft at a default airport? Is Riva Tuner known cause any problems? Edit: are you using AI Traffic?
  21. I was just thinking that it might be a good idea to check to see if the stutters were still there in DX11 mode, and with PG disabled. It may give someone else with more technical knowledge than I have a clue as to the source of the problem.
  22. AFAIK, at least from my experience, in P3Dv6 we have to enable VSync also in-sim because contrarilly to v5 the setting only through NCP or NI will not work. OTOH I second that choice for adaptive 1/2 refresh rate in NCP or NI. Also got from some other posts I've read in the past that we should use as few as possible settings from within the sim. Leaving VSync unchecked and not limiting FPS in sim works better, so they say, and can be forced through NCP or NI, and save CPU cycles and Temps... Problem as I noted aboe is that if I do not set VSync in sim and only set it in NCP or NI, it doesn't work, or at least the FPS counter in sim shws varying FPS way above 30 / 60 FPS... Thus, with v6 we have to also enable VSync in sim. My only grip with P3D, also v6, are the temps it reaches, specially the CPU 😕 They're always a good deal suprior to what I get in either XP12 or MSFS 😞
  23. The TAXI_PATH has indices of the starting and ending TAXI_POINT, and that has an offset in meters from the airport reference point; you can compute the lat/lon from that. (The information has to be there in some form, or the WT avionics wouldn't be able to draw the airport layout. Edit: Duh, that's not true obviously because the WT avionics use JavaScript. But the SimConnect API has matured quite a bit too now - though it's still pretty clunky, in the finest tradition of Win32 APIs. 😉)
  24. Does SayIntentions respond with regional accents where appropriate?
  1. Load more activity
×
×
  • Create New...