Sign in to follow this  
Guest

Beta Blues

Recommended Posts

Trying out Beta 3.01 today... FS2K2, WinXP, PIC, ActiveSky wxRE, 2.95/5.3.Flight plan was KSFO.OAK.RBL.OED.EUG.UBG.LAKER.KPDXObservations:(1) I typically launch ActiveSky wxRE, then FS, and then RC. Before I launch RC, I position the a/c at the departure airport gate. When RC launches, it causes ActiveSky to switch to force destination wx (checks the box for me) and causes incorrect ATIS reporting at the departure point. If I watch ActiveSky and uncheck the box immediately then the ATIS is reported correctly.(2) All was fine on the route of flight until OED (aprox 200 miles out). Right after OED, I received a descent from FL390 to FL330. No problem. Aprox two minutes later I received a fly heading 005, descend and maintain 9,000 expect vectors for rwy 28L. Having flown a ~400 mile vector in real life, I found this odd, but not completely implausible. I requested rwy 28R. At aprox FL230, I was slowed to 250kts. Early, but again plausible. However, the vector was the Energizer bunny of all vectors (kept going, and going, and going...). Finally, passing Mt. Hood, I again requested rwy 28R and was told to expect vectors. It wasn't until I was nearing LTJ VOR that I received a reciprocal vector (190). Then I was turned 250 to intercept a 35-mile final. This seems very odd. Don't remember this type of problem before the beta. See below for vector image.(3) I know you're working on terrain awareness, but when I passed Mt. Hood (the first time) I was 3,000' below the summit and 5 miles east. Great view, but unrealistic for an airliner. The 190 vector aimed me right at it. I manually changed heading (notams checked) to avoid disaster.http://ftp.avsim.com/dcforum/User_files/3e3d624844eb7616.jpg

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

[This was also posted in the PIC forum.]Another problem I noted was a conflict between ADVdisp and the direct keyboard entry feature of PIC. This morning I was entering a bunch of different routes into the FMS while on the ground. I had clicked on the KA spot on the FMS for direct keyboard entry into the FMS. However, I noticed that some keystrokes were being passed on to the PIC panel. For example, the K would cause warnings to recall and the X would cycle the #2 engine display modes. Further investigation, shows that this only happens after RC3.01 is started and the ADVdisp is in use. If I launch just FS then this is not a problem. Once I have started RC the problem continues even after RC is closed.I'm running RC on a client using Wide FS. The problem occurs with FSUIPC 2.95/ WideFS 5.3 and with 2.96/5.4.I'm also going to post this in the RC3 forum to see if they have any ideas.FS2K2, XP, 2.95/5.3, PIC, RC3.01, ActiveSky wxRE

Share this post


Link to post
Share on other sites

1) i would suggest a different sequence at start up. i would do fs, and position the aircraft. then active sky, let it get the weather for your departure airport. then rc. when you load/start a flight plan, active sky will know where you are going, and set the destination airport for you. it is obviously an error to have the departure airport's weather set with the destination weather. i would be curious to see the .pln file you loaded into rc.2) also totally wrong. 200 miles out is about right for your initial descents. after reaching 330, you should have been switched to another center. you didn't mention that happening. did it? i'll have to fly it to see what is happening. never heard/seen such a thing in 2 years of testing.3) working on it is the key word

Share this post


Link to post
Share on other sites

who has a similar configuration can test your anomaly

Share this post


Link to post
Share on other sites

(1) The plan file was generated by FS Navigator, exported in .pln format and uploaded into RC3 it is as follows:[flightplan]title=KSFO to KPDXdescription=KSFO, KPDXtype=IFRroutetype=1cruising_altitude=35000departure_id=KSFO, N37* 37.14', W122* 22.49', +000009.84departure_position=28Ldestination_id=KPDX, N45* 35.32', W122* 35.85', +000029.53departure_name=San Francisco Intldestination_name=Portland Intlwaypoint.0=KSFO, A, N37* 37.14', W122* 22.49', +000009.84,waypoint.1=WESLA, I, N37* 39.86', W122* 28.82', +000000.00,waypoint.2=OAK, V, N37* 43.56', W122* 13.42', +000000.00,waypoint.3=RBL, V, N40* 5.93', W122* 14.18', +000000.00,waypoint.4=HANDY, I, N42* 14.11', W122* 50.47', +000000.00,waypoint.5=OED, V, N42* 28.78', W122* 54.78', +000000.00,waypoint.6=EUG, V, N44* 7.25', W123* 13.37', +000000.00,waypoint.7=UBG, V, N45* 21.19', W122* 58.69', +000000.00,waypoint.8=IA, N, N45* 32.47', W122* 27.75', +000000.00,waypoint.9=KPDX, A, N45* 35.32', W122* 35.85', +000029.53,(2) Somewhere (+/- 100 miles) I was handed off from OAK center to SEA. I wasn't troubleshooting at the time, so I didn't note the specific locale. The only handoff I specifically remember is tower at 5 miles. I don't remember being handed off to approach (should have been on 133.0), but agian, that doesn't mean it didn't happen. I was more focused on the vector problem.Thanks for your continued support.Dennis

Share this post


Link to post
Share on other sites

2) other than not checking arrival notams and slamming into the side of a mountain, the flight was flawless@oed i was 390then i was d&m (descend and maintain) 350then i cc (contact center)then i was d&m 240then i ccthen i was given a pd (pilot discretion) d&m 14000then @ 35 from UBG i was given a nxr (new crossing restriction) to be level at 10000 in 30 miles of lessthen i was handed off to approachdon't see the problem.

Share this post


Link to post
Share on other sites

That is entirely different than what I experienced. What did I do wrong?

Share this post


Link to post
Share on other sites

hard to say. did you even get switched at 350?maybe you are missing some files and/or whole directoriesdo you have winwood2, 3, 4, 5, 6, 7, 8, 9, 10, 11?same number of files in each?here is the plan i flew, based on your original post[flightplan]title=KSFO to KPDXdescription=KSFO, KPDXtype=IFRroutetype=0cruising_altitude=18000departure_id=KSFO, N37* 36.82', W122* 21.46', +000011.00departure_position=28Rdestination_id=KPDX, N45* 35.69', W122* 37.25', +000030.00departure_name=San Francisco Intldestination_name=Portland Intlwaypoint.0=KSFO, A, N37* 36.82', W122* 21.46', +000011.00, waypoint.1=OAK, V, N37* 43.56', W122* 13.41', +000010.00, waypoint.2=RBL, V, N40* 5.93', W122* 14.18', +000320.00, waypoint.3=OED, V, N42* 28.77', W122* 54.78', +002080.00, waypoint.4=EUG, V, N44* 7.25', W123* 13.37', +000360.00, waypoint.5=UBG, V, N45* 21.19', W122* 58.69', +001440.00, waypoint.6=LAKER, I, N45* 32.48', W122* 27.74', +

Share this post


Link to post
Share on other sites

If you get the problem solved, then you might what to try the real route flown between SFO and PDX:KSFO.CUIT2.RBL.J1.OED.MOXEE5.KPDXThe waypoints are:KSFOREBASRBLHANDYOEDMOXEEPORTLVANTZOCITYKPDXATC will start your descent between OED and MOXEE, then further descents to VANTZ. You should get vectors to the final approach course before OCITY.I've flown this route many times and I have never had a problem like the one described.

Share this post


Link to post
Share on other sites

I had filed for 350, but PIC showed 38X as being optimal, so I requested (and received) 390. From 390, I was given 330, then the vector, then (I think) 230, then 90.I have windwood2

Share this post


Link to post
Share on other sites

Thanks Bruce! I've been looking for some good RW plans, especially those with realistic DP's and STAR's. I'm going to try jd's plan first for troubleshooting and then I'll save yours. What planning tool do you use?

Share this post


Link to post
Share on other sites

Dennis,Fly it again. Save a dat when just before you get the first descent instruction. Make sure you do everything the same (including requesting higher).Also save a dat before requesting higher.

Share this post


Link to post
Share on other sites

Just tried jd's flight plan and it worked flawlessly. Handed off to ZSEA 64 mi south of OED at 390. Down to 350 70 mi south of EUG, 240 51 south of EUG, pd 140 20 south of EUG, etc.I'll try the plan that gave me trouble again later this week to see if I can duplicate the problem. My guess is that the LAKER fix is somehow confusing RC, however I really have no evidence for that other than a hunch.Thanks again for your help in sorting this out. I've been kind of a problem child for support haven't I? First the client lockup problem and now this. If it can be broken, then I'm your guy...

Share this post


Link to post
Share on other sites

Dennis,I use several planning tools. No single tool is all inclusive, so it's helpful to have a range of resources.Try clearanceunlimited.com. That site has many routes listed between major cities.I also use FSBuild 1.4.0. It doesn't always give realistic routing when the program builds its own routes, but it has a fantastic set of saved routes. http://ourworld.compuserve.com/homepages/a...er1/fsbmain.htmYou can also use the NFDC preferred routes site. Rather than guessing what routes are available, click on the download routes link and keep a copy in your spreadsheet for planning.http://www.fly.faa.gov/Products/Coded_Depa...s_database.htmlThere is also the routes forum here on AVSIM that can give you plenty of tips.Bruce

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this