Bruce Nicholson KMFR

In response to Don, I'm also in the So. Oregon area. I live 2 mi SE of KMFR. I work with someone that is also a big FS fan (he's originally from Portland). So that makes at least 3 of us in the area. :-) I go to Portland for business once a month, so if a get together is organized, I might be able to attend.It's been at least a year since I flew the sim out of PDX, as I'm mostly checking out different parts of the FS world. Last winter, when it was getting dark early in the PacNW, I was flying in late evening sunsets throughout South America. For the past 3 months I've been touring Europe. As I write this on my laptop, I'm preflighting the PMDG 737 for a flight out of Prague.I'll be in San Diego for the AVSIM conference and looking forward to meeting any of you that will be there.Bruce

Bob,Very interesting! Thanks for the links to those blogs. It seems those folks that are not allowed to respond have found an alternative way to respond. :-)Apparently progress will be made without throwing the baby out with the bath water. Precisely what those folks voting #3 (the light green) wanted.Bruce

I agree with Mike T.Most of us may want a new graphics engine because the other games today make FS look "old", but the fact is economics rule business. For those people that say chuck the old engine and all the add-ons and bring on the new stuff.... how long are you willing to fly the default planes and the default scenery? The new version may blow away the current version, but is that enough to hold the interest of the hard-core simmer? We all know the majority of FS sales goes to people that never buy add-ons. They play with the sim until they are bored and the sim then ends up on the bookshelf. Even with an amazing "WOW" factor based on a new graphics engine, the hardcore simmer is going to eventually put the new version on the shelf unless a new addon comes along to renew the interest.Microsoft provides scenery and aircraft that are acceptable to sell the product. For the hardcore simmer, these items are marginally acceptable. You'll be waiting a long time for all the things you've come to expect from your sim to be acceptable. I'm not talking 6 months here, but more like years! If people are already happy with FS9 and all the add-ons, then where is the incentive for the developers to spend big money converting to the new platform? That's quite a business risk, not only for the payware developers, but for Microsoft as well. Of course there will be new products developed, but if enough people hang onto FS9, there won't be anywhere near the windfall of products developed for the new platform that we see now with FS9.Mike's suggestion has plenty of merit, from the standpoint of the hardcore user base as well as the product developer. There's plenty of optimization that can be accomplished in combination with incremental advancements by Microsoft.I don't favor a completely new product unless Microsoft admits that they have taken the current graphics engine as far as it can go. Just because we see what other game makers are doing (in a limited environment, not worldwide) is not a reasonable, nor economic reason to scrap the entire program.Finally, if you've been around flight sim for awhile, you already know that new graphics means quirks and bugs. If people complain about stutters now, from a mature but not fully optimized graphics engine, it worries me to think what will come from people that are limited to flying in a default world with default aircraft and there are quirks in the engine. The frustration level will go through the roof!My vote is to make as much advancement as possible, but consider how it affects current add-ons. If some add-ons continue to work and there is significant progress, that's fine. However, don't throw it all out the window just to make a quantum leap forward in technology. A futuristic, lead-edge FS may seem cool when we first get it, just like all new versions upon release, but it'll only take us hardcore users a couple of months to realize we stepped back into the dark ages when there are few add-ons to keep us happy.Bruce

Commercial and freeware developers will get help from MS, just as they have in the past. I'm not worried about that aspect. But what really scares me about a new version of FS is how FSUIPC will need to be redone. There are so many add-ons that use that utility, and we all know that each new FS version breaks FSUIPC since FSUIPC pokes into the core of FS programming. I also don't know if Pete Dowson has it in him to restart from scratch to develop a new version. He was ready to give it up when FS9 was released.So perhaps MS might make the internal addresses known this time, but it'll be revolutionary if they do considering they haven't in the past.I read how people will buy the new version anyway. I can understand that. But think back how long it took for AFCAD, and all the cool utilities we use to get recoded for FS9. I'm not talking about the commercial developers here, I'm talking about the people that take time out of their normal lives to provide us with tools that make FS as great as it is today. MS can assist all they want, but it's unsung heroes like Lee Swordy, Pete Dowson, et al., that take FS to the next level from out of the box (or tin!) and it's not going to happen upon release, or even all that soon after the release.Food for thought when it comes to releasing a new version of FS.Bruce

>> My *only* grumble is that there is no wing-flex (like on the Posky 767-300). Im hoping PMDG will release an upgrade patch!If I ever looked out the window of a real 737 and saw wing flex, I'd have reason to really be worried. The 737 wingspan is not that great to afford a large flex in the wing.Bruce

>> Plus the nav data is really out of date.Check out the FSBuild forum at www.fsbuild.com.The AIRAC data is current through 5.08 and Ernie has also released a beta to work with the PMDG 747. No performance files yet for the PMDG 747, but I read on the PMDG support forum that someone was working on it.As for the nav points that are way out of line, that happens occasionally when two navaids have the same abbreviation. FSBuild selects the first one in the data file that it finds. The easy fix is to just manually select an intersection name in the vicinity of where the flight path goes astray and delete the 11,000+ waypoint from the plan listing. Rebuild the plan and all is fine. :-)Bruce

Thanks Jim,The ASV beta discussion area is no longer active, so I posted here. Do you prefer an email next time?Bruce

Damian,Using build 325 and the following METAR:EFHK 310520Z 35004K 9999 -RA NSC 14/11 Q1008 NOSIGThe Decoded box indicates:Wind:350 True, 4 KtsVis:9999 Meters, 10 SMClouds:NonePrecip:NoneTemp:14C Dew: 11CPressure:1008.00mb,29.77 inchesNote that the Precip decode shows no rain.From the FS perspective, when this METAR first loaded, FS showed light rain, then upon the 10 min update (no change to the METAR), the rain stopped in FS. No further rain during each of the remaining 10 min updates for the current hourly report.Is it possible the NSC is causing the -RA to be ignored? I'm not sure why the first load of the METAR created the rain and the subsequent updates matched the decode box.Bruce

FSBuild will handle GCR planning.Enter the departure and destination airports.Click on the PM button.Once the planning mode screen updates, you'll now have a GCR button right above the PM button. Click it.A great cirle route fills the route table.Go to the Build Options menu at the top and make sure "Build from Route waypoint Table/Grid" is selected.Click PM button to exit planning mode. Build button is now active. Click the build button to finalize the flight plan using the cruise altitude you want.Note that the Name column will show the closest latlon, but the flight plan will contain the precise great circle path. If you don't select "Build from Route waypoint Table/Grid", then the route will select the latlon intersections and your flight plan will be a stairstep path.Hope this helps.Bruce

The MRAI installer expects specific files to be included in a MRAI zip file. When someone submits these expected files to AVSIM as a single zip file, the librarian inserts the AVSIM comment file into the submitted MRAI zip file, which in turn causes the MRAI installer to become confused and crash.If you are submitting a schedule to AVSIM for upload, zip the MRAI files, and then create another zip file that acts as a "wrapper" around the original zip file. Think of it as a MRAI zip file stored inside another zip file. Then when the AVSIM comment is inserted, it goes into the wrapper zip file and does not disturb the original MRAI files.When users download the schedule and open the library zip file, they will see the AVSIM comment and a separate MRAI zip file. The MRAI zip file can then be extracted and used with the installer error free.Now if you are downloading a schedule that someone else uploaded and they did not follow this method, you can unzip the MRAI files, delete the AVSIM comment, and place the remaining files back into a zip file. Run the MRAI installer on the zip file you created and it should work (assuming the author created error-free files).Bruce

I checked out virtualearth and it has a ways to go to match the features and visuals of Google Earth. As for integrating the imagery into FS, I don't know many people that would elect to fly in a black and white world. (-: Bruce

Given Pee Wee's reputation for attending movie theaters, didn't you forget the "in" before famous? :-lol

I'm not seeing a problem with towering CBs. Ever since ASV came out I've been deviating around CBs. During my last flight at FL330, I encountered a line of CB's and had to deviate 15 deg left of course to dodge a buildup directly ahead of me. I'd estimate the tops were somewhere near FL400.It must the combination of option settings. I'm not in front of my home compute right now, but I do remember setting extended CB, no limit on cloud layers, and cumulus thickness at 15,000. Do you have a limit on the number of cloud layers? Perhaps ASV is trying to extend the CB height and it can't due to the restriction on the number of layers. Just a guess....Bruce

Check out this link, it might seem vaguely familiar ;-)http://forums.avsim.net/dcboard.php?az=sho...ing_type=searchRed1 only covers flights into and out of US airspace. Since you are interested in continental flights to and from the UK, FBOweb may be more to your liking. Realize that it will not show plans that do not pass over UK airspace.

Grant,I see that you are new to AVSIM, welcome aboard. Usually a request like yours can be easily answered by running a search. Topics like scenery and airports are posted all the time.For example, the following thread has been running for awhile and I'm sure you would have found it as one of the first responses to a search:http://forums.avsim.net/dcboard.php?az=sho...d=257120&page=9Hope this helps and try using the search function on the forums, you'll generally find lots of stuff that others may not feel like repeating.Bruce

>> If I'm correct on that assumption, then is it necessary to map a drive from the WideFS PC to the FS PC before loading ASV and planning the flight or will it simply do what it needs to do accross the normal network without going thru WideFS???. Before installing ASV, you must establish a normal windows network path between the computer running FS and the computer running WideFS. At the least you need to be able to have write access to the FS folder from the WideFS computer.Then when you install ASV, the setup routine will ask you to identify the path to the FS folder. Once this is completed, the setup program makes a complete backup of the FS texture folder across the network to the remote ASV machine, so you can restore the default textures (or any custom textures installed prior to using AE textures).If you want to use ICS, you must enter a flight plan (or for a local area flight enter the same airport for the starting and ending locations). Click refresh to process the WX stations at the starting airport and transfer the textures from the ASV computer to the FS computer via the Windows network.Then you are ready to start FS, which once running allows you connect the computers via WideFS. Once WideFS is established, the regular ASV wx updates will communicate with FS via WideFS.So in summary, the Windows network transfers the initial texture load to the FS texture folder and WideFS handles the wx updates to the FS wx engine. Two separate modes of transfer for two separate tasks.Hope this answers the question and clears up any confusion.Bruce

Victor,Your request seemed very familiar. :-)Here is a link with plenty of AAL 738 plans and some COA 737NG plans:http://forums.avsim.net/dcboard.php?az=sho...ing_type=searchDoing a search for B738 turned up all of these other replies to people wanting AAL 738 flight plans:http://forums.avsim.net/dcboard.php?az=sho...g_id=7443&page=http://forums.avsim.net/dcboard.php?az=sho...g_id=7205&page=http://forums.avsim.net/dcboard.php?az=sho...g_id=7241&page=http://forums.avsim.net/dcboard.php?az=sho...ing_type=searchhttp://forums.avsim.net/dcboard.php?az=sho...ing_type=searchConducting a search is a simpler approach... immediate data and someone doesn't have to go online to look up what has already been posted.Bruce

This doesn't sound like anything to do with ASV, but more likely has to do with corrupted pressure data. It would also explain why things settled down when you used an alternate data source.You are cruising at a constant 29.92 pressure level. Assume the pressure is 29.90 and the next update reads in an altimeter setting of 30.90 (should be 29.90), the aircraft will suddenly zip up in altitude to compensate for the drastic pressure level change.Bruce

This thread was cross-posted to the MS Flight Sim forum. I answered the question in the other forum.Cross-posting may get someone more exposure to a question, but certainly isn't a friendly way to meet the forum moderators.

Jerry,There was a complete texture backup made during the ASV install. The easy solution to keeping your original clouds and enjoy the new features of ASV (without the new clouds) was to restore the backup textures to your FS texture folder, then go into the ASV options and select Manual under the texture options. ASV will no longer change your cloud textures.Give that a try and see what you think.Bruce

Barry,I don't have FE, so I'll defer to someone that does. I can tell you that you have complete control over how the AE textures are loaded. You can select manual where you choose the textures or remain with the same textures, you can let ASV randomly select textures, and there is the Intelligent Cloud Selection system that will build a set of textures based on your enroute weather. Of course ASV ships with its own AE textures, but there is no reason one could not disable the AE textures and use FE textures .I keep reading on the forums how cumbersome the texture loading sequence is on ASV. People don't understand that flight plans are only needed prior to starting FS when one wants to simulate the best combination of textures for their route of flight. One can always start ASV, not use a flight plan, and textures will still get loaded (or not loaded depending on the ICS options). I've flown lots of flights without a going through the flight plan preloading process and the weather looks great.More importantly is your second question about WideFS. The program ships with a complete version of ASV, not just an upgrade. Whether you load it on your FS computer or a WideFS computer, ASV knows how to find your FS folder via the information it collects during the setup. The full texture set and ASV program are loaded onto your WideFS computer. You launch ASV prior to starting FS, and depending on the options enabled, textures are copied across the network to the FS folder. Then when you start FS, the copied textures are loaded into memory.The ASV program will conduct successive updates online or offline (depending on the options you've selected) and the FS weather will change accordingly. Following each update (mine is set to 10 mins), cirrus textures are copied across the network and appear in the sim. Cirrus textures are the only textures that can be changed dynamically. All other cloud textures are fixed in memory after FS loads.During the ASV setup, a backup is made of your current FS texture folder. This saves any custom textures and changes you have in effect. You are free to sample and experiment with the AE textures and if you wish, you simply copy the backup folder back to the FS texture folder to restore your original textures.If you are running FE, you'll want to set the ASV texture option to Manual. This disables ASV from copying AE textures over the network to your FS texture folder. You can then change your FE to suit your needs and ASV will not interfere with your selections.I think that Peter and Damian are planning to work together to integrate FE with ASV so a similar ICS routine can exist for FE textures. You'll need to check with Damian regarding this.Bruce

FSBuild does not need to be updated to handle ASV. Just make sure you have the latest beta build (FSB 2.2) and point your FSBuild AS2004 option to your ASV folder. The winds will be integrated into the planner.Bruce

I guess Ferdy isn't the only one that repackages freeware and sells it. At least people on eBay and other auction sites can be shutdown... Bruce

I see there are no responses over the past day, so I'll offer a tip.I suggest you do a search on this forum for the word B736 or the word B737. You'll be surprised the number of real flight plans you'll find.For example, using B736 in the search I just did yielded 10 topic hits and in the first topic returned, I found 39 real flight plans with the 737-600 and the 737-700 (there were even more if you include the 800 and 900 series).This should easily supply you with real world 737 plans. If you want specific airlines on specific routes, then just state which ones and there should be plenty of people on the forum to help out.Bruce

Frank,This is off topic for the message thread, but I'll attempt to answer and if you have questions, please ask on the FS Build forum at http://www.fsbuild.comI assume you have the FSBuild AS2004 option pointing to your ASV folder if you are reading the saved wx file and getting winds that are close.To plan fuel, you need to select the aircraft you are using from the FSB Aircraft folder. FSBuild ships with a selection of aircraft types. I'm using the PMDG 737 and I found the update for this aircraft at the FSBuild website. On the takeoff/landing_data tab (bottom of the aircraft folder selection) you'll see the drop down selection to choose your aircraft. Once that is done, you'll move to the right side and enter the payload weight. Normally, the program will automatically add alternate fuel if an alternate airport is listed in the plan. I have my reserve set at :45 to always add an extra 45 minutes of fuel to the plan. I also manually input either :10 or :15 into the Taxi Fuel box depending on how long I estimate the taxi phase will take (sometimes longer at busy airports). Once all of this data is entered, make sure the weight in FS matches gross weight in the aircraft tab of FSB.Now you are set to plan the flight. Enter the departure and Destination. I'll use EGLL going to EHAM. When I do this, I automatically get EBBR as the alternate. When I choose Auto Generate, a stored route is found and displays in the plan input box. I get EGLL BPK UR123 CLN UL620 REDFA EHAM. At this point nothing appears in the navlog since a plan has not been built. Click the Build button, and you'll see that the status box shows the Aircraft performance is loaded, the winds are loaded, then the plan is processed and crossing restrictions checked.Now the navlog is complete. This is what the top of my navlog looks like: FSBUILD FLIGHT PLANFLT REL IFR EGLL/EHAM MACH 78 A/C B737-700 W/ PMDG 737NG ADDON FUEL TIME CORR TOGWT LDGWT AVG W/CTAXI 000570 0015 . . . . 116540 113169 P030DEST EHAM 003371 0031 . . . .RESV 004718 0045 . . . .ALTN 001651 0015 . . . . ALTN EBBR DIST 84HOLD 000000 0000 . . . .EXTRA 000000 0000 . . . . ZFW 106800 PAYLOAD 023800TTL AT TO 009740 0131 . . . . DIST 0201REQD 010310 0146 . . . .CLB BIAS 0.0 % CRZ BIAS 0.0 % DSC BIAS 0.0 %EGLL BPK UR123 CLN UL620 REDFA EHAM/0031As you can see, my taxi, destination, reserve, alternate, total fuel at takeoff, and total required is listed in the fuel column. If I wanted to plan for holding time, I could have entered a time or fuel weight earlier in the aircraft config folder.FSBuild has taken the winds I saved from ActiveSky, the aircraft configuration based on payload, and computed fuel burn plus the other options I've provided. All you have to do is load the fuel listed on the REQD line.If you want to select the optimum cruise level, then you should take note of two things:DEST EHAM 003371 0031 (from the fuel column)and AVG W/C (upper right portion of the log)P030The first tells us that we are burning 3371 lbs of fuel to get to EHAM and flight time is 31 minutes. The second tells us the average wind component over the entire route is P030 (positive 30 knots), meaning a tailwind. This is all based on a cruise level of 21,000 feet.What you want to do is alter the cruise level and rebuild the plan, watching the two components listed. Try to find the best avg wind compenent in combination with the shortest flight time/fuel burn. The second term is tricky because sometimes you will find better tailwinds at lower altitudes, but this means slower true airspeeds and more fuel burn. Since this is a sim, fuel burn is probably the least of your concerns unless you fly for a virtual airline that tracks fuel burn. You'll probably focus more on min flight time and appropriate flight level (even vs. odd).Once the optimum flight level is known, the fuel categories will update on the next build.Another tip is you can do all of this (ASV + FSBuild) before launching Flight Sim. FSBuild writes the plan for Flight Sim, ASV then loads the plan and builds the ICS texture files. Then when you start flight sim, the textures are set and all you have to do is ensure the payload weight and fuel are correct.Hope this helps and if there are questions, ask at the FSBuild Forum on the FSBuild website.Bruce