Jump to content


  • Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

2,132 Excellent


About JRBarrett

Profile Information

  • Gender
  • Location
    Elmira, NY
  • Interests
    Aviation - Computers - Sailing - Golf

Flight Sim Profile

  • Commercial Member
  • Online Flight Organization Membership
  • Virtual Airlines

Recent Profile Visitors

8,504 profile views
  1. Be sure to turn on both electric hydraulic pumps before setting the parking brake. If there is no hydraulic pressure, the brakes may not actually “set” even though the parking brake handle moves to the engaged position and the red light comes on.
  2. Perhaps. I’m not sure what they are charging now, because the P3D version appears to have been temporarily removed from their shop - I believe to prevent new customers from buying the P3D version by mistake.
  3. The only 737 I am interested in, or have ever been interested in, is the 700. I enjoy all three variants: passenger, BBJ and freighter. I P3D I first had to buy the 800/900 base package because it was a prerequisite for the expansions. It was $99, not $90. Then the 700/600 expansion for $25. You can’t just “lump in” the BBJ and freighter. They were not free - each cost $35. In total I paid $194 to get the 700 with passenger, BBJ and freighter. The 600, 800 and 900 were “there” on my P3D sim installation, but they were a waste of HDD space and money - I never flew any of them. In MSFS, I got the 700 with BBJ and Freighter included for the intro price of 69.95. Since I qualified for the $99 credit I actually paid nothing and still have $30 credit remaining. Now, I realize I am probably somewhat unique in wanting only the 700 and I can’t say I’m not pleased it came out first in MSFS, but even if it hadn’t, the same pricing advantage would have applied. All indications are that the 800 is the most popular 737 model among simmers. If I had wanted that (instead of the 700) I just would have to have waited a few weeks more - and like the 700, the BBJ and freighter versions of the 800 will be included at no extra charge. The only customers that will be at a pricing disadvantage when it comes to P3D vs MSFS, are those who want every 737 variant possible. They will indeed pay more (all together) than they would have paid in P3D. Those who want only one or even two of the four possible models will pay less. I have no problem with PMDG’s pricing strategy for MSFS.
  4. Está bien, puedo entenderte en ambos idiomas.
  5. RAAS is not implemented at this time. EGPWS is fully modeled, with all relevant warnings.
  6. Interestingly, even the Aerosoft CRJ has this feature.
  7. I’m not saying it would be impossible - but it would involve a major change in how LiveWeather is currently implemented, (to deal with a “scaled back” version of the MeteoBlue model for those who want historical data) plus the willingness of Microsoft to host the additional model files in their server infrastructure.
  8. They do, and it is typically used by meteorologists and other researchers investigating climate trends etc. The problem is the huge size of the datasets. There is no way to provide that information to an individual FS user who wants to fly in historical weather for a past date and time.
  9. It’s not that Asobo does not understand the desire of users for historical weather - The problem is that with the system they currently use, it simply is not possible. With MeteoBlue, the entire worldwide atmosphere is modeled. I have worked with other weather models professionally, and they are typically huge - often many hundreds of gigabytes for a complete dataset. MeteoBlue generates and sends the model data to Microsoft every 12 hours where it is imported into Azure to be provided to all MSFS clients using LiveWeather. If a given MSFS aircraft is flying at (example) latitude N35.34, longitude E005.23 at 10,000 feet MSL at 13:30Z it will send a request for the weather parameters for those coordinates, altitude and time, and the Azure server will return it. With Active Sky in FSX and P3D, the complete weather file is sent to the end user’s computer. Their weather file consists of all current worldwide METAR observations (which are in simple text format) all winds aloft for the world, (again in text format), and a very simplified subset of data from the GFS model - adequate to place areas of clouds and precip in the correct locations but not as detailed as what is provided by the MeteoBlue model MSFS uses. I believe the ActiveSky current weather file is only a couple of hundred megabytes in size, and they can easily store copies of the combined METAR/WINDS/simpified model data for each hour of every day going back many years on their servers. It is easy to fetch and deliver historical weather in this way to an individual ActiveSky client requesting it. Not so with MSFS using the complete worldwide NEMS model. The model weather dataset is far too big to be sent to or stored on any MSFS end-user’s computer. The only way this kind of system can work is to have the model stored on the servers at Microsoft, and the relevant data streamed to end users to produce the weather at and surrounding the aircraft location. Historical weather simply is not (ever) going to possible with this kind of system.
  10. It does. WASM aircraft will have to be re-compiled whenever the core sim executable file changes, as is the case with the update to
  11. The Maddog was quite a bit longer actually. About 20 minutes
  12. 4790K OC to 4.2 GHz, GTX1080ti, 32GB RAM - adequate, but not high end by any means. I did one quick flight, and performance was very good
  13. I just installed it and first run took 9 minutes. Not bad - comparable to the CRJ.
  14. In aircraft like the CRJ (and I assume the 737) the aircraft in P3D is coded in C++ uses draw calls to GDI+. The same C++ code (for graphics) running under WASM uses NanoVG for rendering. It does not have to be done that way, and apparently with ProSim, Fenix can move almost everything out of the sandboxed WASM container.
  • Create New...