I have posted the winds aloft that I entered into the Corridor for my trip from KSFO to KAUS. The winds that were indicated on the NAV display were constantly from the west and northwest for the trip. When I started my descent into KAUS from FL390 the winds were still from the NW and as I passed FL240 they started moving in a slow counter-clockwise circle. This condition continued until on final at KAUS. Needless to stay this made speed control a challenge.
When I purchased the NG upgrade I had hoped the speed issues would be alleviated. There are times when it works very well and others it doesn't. I am not sure what I am doing wrong or how to fix this issue.
Bode
(CLIMB) JSICA ILC BCE
FL360 183/036 -46 FL410 185/036 -54 FL410 186/039 -53 FL410 190/039 -52
FL290 171/030 -30 FL390 185/036 -54 FL390 186/039 -53 FL390 190/039 -52
FL220 204/013 -14 FL370 183/032 -48 FL370 185/035 -48 FL370 192/036 -48
14000 202/010 +2 FL350 181/027 -43 FL350 185/030 -43 FL350 194/033 -43
7000 148/009 +18 FL330 181/023 -38 FL330 185/026 -38 FL330 194/030 -38
KD39Q CNX CME HOB
FL410 191/029 -52 FL410 102/021 -52 FL410 090/025 -52 FL410 084/027 -52
FL390 191/029 -52 FL390 102/021 -52 FL390 090/025 -52 FL390 084/027 -52
FL370 190/027 -47 FL370 100/019 -47 FL370 090/022 -47 FL370 082/024 -48
FL350 188/025 -43 FL350 097/018 -43 FL350 089/020 -43 FL350 080/022 -43
FL330 187/022 -38 FL330 092/015 -38 FL330 087/017 -38 FL330 076/019 -38
(DESCENT)
FL360 069/034 -45
FL290 072/030 -28
FL220 076/022 -13
14000 073/015 +2
7000 146/008 +20
On the Corridor page, did you select this checkbox?
[x] Special wind & OAT corridor embedded in planet weather model
|-|ardy
Quote from: Hardy Heinlin on Fri, 5 Aug 2022 20:39
On the Corridor page, did you select this checkbox?
[x] Special wind & OAT corridor embedded in planet weather model
|-|ardy
Yes.
Can you provide a situ file? Otherwise I can't analyse the reported problem.
This is the first time in 2 years a user is reporting the corridor isn't working. I've no idea what could cause such a problem ...
Quote from: Hardy Heinlin on Sat, 6 Aug 2022 01:50
Can you provide a situ file? Otherwise I can't analyse the reported problem.
This is the first time in 2 years a user is reporting the corridor isn't working. I've no idea what could cause such a problem ...
I can fly the flight again. How do I make a stu file for the whole flight?
Bode
I answered this on the other thread, but pressing REC EVENT is a quick way to save a snapshot of the simulator's state. It's a slice in time, not a movie, so you can't record a whole flight. But if the winds aren't what you expect at a given moment, you can create a situ (snapshot) of that moment and then post it here for analysis.
You can also save a situ using the "Save" function, but the REC EVENT button is always right there in front of you, easy to press in the moment if you ever want to return to that simulated instant in time.
Regarding the wind corridor, are you using the slider called "Wind & OAT random deviations"?
Quote from: Bluestar on Sat, 6 Aug 2022 03:27
I can fly the flight again.
So do you already have a situ file (situation) for the start of this flight, with all weather and route data set? If so, please post this situ file.
|-|ardy
How do I attach a situation file?
Bode
Three alternatives.
1. Upload the file to the hosting service of your choice, such as dropbox, and link to it.
2. Upload your situ here: https://aerowinx.com/board/index.php?topic=1744.0 and link to it in a forum post.
3. Copy & paste it into a forum reply, surrounded by the "Insert Code" tags, like this:
Sample sample
Sample sample
Sample sample
Sample sample
Sample sample
Sample sample
Sample sample
Sample sample
Sample sample
https://www.hoppie.nl/forum/var/2022-08-06_18.11.14_kaus.situ
This is the situation file for KSFO-KAUS. After I land I delete the payload. I can provide the route file and flight plan if that will help.
Bode
One more question, to be sure your PSX nav database has found your corridor waypoints: On your Corridor page, do you see the message "9 corridor points are set"?
When you use this airline text format that has no lat/lon data but just waypoint names, PSX needs to find the related lat/lon data in the sim's nav database. This problem cannot occur when you use an airline text format that has lat/lon data. If any lat/lon data cannot be found in the database, there'll be an error message and the entire corridor will be removed from the simulation.
When the corridor is OK and embedded in the simulation, you can see the corridor (magenta clouds) on the Instructor's map when "Met" is selected.
|-|ardy
I just flew along your corridor points (partially with time acceleration), and my wind data on the aircraft agreed with the corridor data within circa 1% (which is perfect) during cruise, and within circa 3% during descent (also fine).
Are you using any add-on that might be injecting weather data into PSX?
I just checked and it said "9 corridor points are set".
I am using Active Sky, but I am not connecting it to PSX. I just use it for visual weather when taking off and landing.
I don't use Acceleration, maybe that is a contributing factor.
Bode
Quote from: Bluestar on Sun, 7 Aug 2022 02:24
I don't use Acceleration, maybe that is a contributing factor.
No. Certainly not :-)
QuoteI am using Active Sky, but I am not connecting it to PSX. I just use it for visual weather when taking off and landing.
So you connect it for takeoff and landing? Are you sure it is permanently disconnected during cruise?
|-|ardy
Quote from: Hardy Heinlin on Sun, 7 Aug 2022 03:07
Quote from: Bluestar on Sun, 7 Aug 2022 02:24
I don't use Acceleration, maybe that is a contributing factor.
No. Certainly not :-)
QuoteI am using Active Sky, but I am not connecting it to PSX. I just use it for visual weather when taking off and landing.
So you connect it for takeoff and landing? Are you sure it is permanently disconnected during cruise?
|-|ardy
If I were using Active Sky during cruise, the winds aloft in P3d would be the same as the winds displayed on the PSX Nav display. When I don't use the Corridor and use WidePSX and Active Sky, the winds in PSX and P3d are the same except when below FL200. What I do find interesting is when below FL200 (no corridor) there are times when there is a significant difference in the winds. For whatever reason, the Planet winds seem to dominate and at times incorrectly. In the U. S. during the summer months there is normally a high pressure ridge that covers most of the country where the winds are out of the East and the jet stream is pushed up north of Chicago.
Because I fly long flights at real time with PSX I see a lot of things that do not agree with Active Sky or the forecasted winds that were loaded into the Corridor from my PFPX flight plan. I still have those flight plans and the situation file that was present when I shut down at the destination airport. Since Steve provided the aircraft templates for PFPX, I have been using it l along with Active Sky to build my Corridor. I should be able to rebuild almost every flight I made with PSX over the last month.
For whatever reason I am doing something to the Weather page and Planet/Corridor that from time to time is causing wind discrepancies.
Bode
Quote from: Bluestar on Sun, 7 Aug 2022 15:05
What I do find interesting is when below FL200 (no corridor) there are times when there is a significant difference in the winds. For whatever reason, the Planet winds seem to dominate and at times incorrectly. In the U. S. during the summer months there is normally a high pressure ridge ...
The Planet page provides global aloft weather data and
global surface weather data.
Which of the datasets dominate is controlled by a simple and clear logic:
The global surface weather data is in use when none of the 7 local zones is active. When the nearest local zone center is more than 320 nm away, the sim uses the
global surface weather data from the Planet page.
So, the interpolation with aloft data always depends on which of the 8 surface datasets are in use (7 zones + rest of the planet).
PSX doesn't know anything about U.S. specific weather effects. It just provides to the user 8 freely configurable datasets for the surface and one global dataset for aloft weather (and a corridor if installed).
The interpolation always uses the global aloft data (or corridor) and the currently active surface data.
The surface data may change when the aircraft moves from zone to zone, or when METARs are updated from the Internet.
|-|ardy
Hardy,
This is the autosave from a KSFO-KAUS that we talked about. I tried the flight again today.
https://www.hoppie.nl/forum/var/2022-08-07_19.50.43_-Autosaved[B].situ
Notice at the start the winds are out of the north. The winds should be out of the east or southeast.
I'm not sure what to do.
At this point all I need to know is can I get accurate winds on descent and landing? If so how?
Bode
I can't reproduce this problem. When I start your situ (2 nm to UTEEE) my wind is 163°/10 MAG.
Yes, the ND arrow points down from the "north" so to speak, but the ND compass rose is at 145°. So I'm actually seeing a headwind from the south, and this agrees with the corridor data.
Are you focussing on the wind arrow angle or on the wind numbers?
You may also check the wind data on the FMC PROGRESS 2 page.
|-|ardy
Bode,
I have been using the PSX NG update since it was released as follows...
Psx.net.externalsim which doesn't do any P3D to PSX wind injections for the visual link to p3d
BACARS and Simfest dispatch which updates the PSX wind corridors with those from the flight plan.
SIGMETS enabled
And have never had issues with the winds being wildly different from the flight plans.
I wonder if this approach might be better for you? (However we don't support MSFS as the injections are just not smooth enough on a wrap around visual yet)
Obviously you can carry on using widePSX if you find it easier to setup but disable the windows aloft injection?
Cheers
G
Quote from: Gary Oliver on Mon, 8 Aug 2022 01:22
Bode,
I have been using the PSX NG update since it was released as follows...
Psx.net.externalsim which doesn't do any P3D to PSX wind injections for the visual link to p3d
BACARS and Simfest dispatch which updates the PSX wind corridors with those from the flight plan.
SIGMETS enabled
And have never had issues with the winds being wildly different from the flight plans.
I wonder if this approach might be better for you? (However we don't support MSFS as the injections are just not smooth enough on a wrap around visual yet)
Obviously you can carry on using widePSX if you find it easier to setup but disable the windows aloft injection?
Cheers
G
Gary,
I'm only using the Network/SceneryGenBridge/TrafficRadioXpndr tabs. For whatever reason the wind data is getting corrupted.
The main thing I want to do is be connected to Vatsim through vPilot. If Vatsim had a way to connect directly to vPilot I would gladly not use the scenery. I'm a P3d guy and will not be going to MSFS.
On long flights do you update the winds aloft since they are updated every 6 hours?
Thanks for trying to help. As you know this whole deal with PSX has been a struggle for me with issues that Hardy has never seen. 🤣 PSX is a great sim and I really want to get it to work for me in the environment that I enjoy.
Bode
Bode,
I have been using PFPX Wind data in the tabulated format examples as detailed in the Aerowinx PSX NG FMS Manual flawlessly since it was released.
I dont want to crash into the discussion here but I would like to offer my own opinion on ActiveSky wind data output versus PFPX wind data & how it interacts with PSX.
If you are flight planning prior to any PSX flight with PFPX then its probably best to insert that data into PSX for the flight.
ActiveSky is best used for eye candy - ie making the scenery generator look pretty.
I have provided a diagram of my PSX & p3D integration below to illustrate how all the various accessory/ancillary software addon programmes that the fantastic group here in the the PSX community have created interact within my setup to make my PSX experience run flawlessly (and very realistically).
You will note that the PSX environment uses PSX downloaded weather below 20000ft & also PFPX wind data (from my PFPX OFP) within its own PSX 'ecosystem'. AdaptPSX runs alongside PSX sends ACARS print to a thermal printer. Obviously a myriad of USB controls are also interfaced with PSX.
My scenery generator gets visual weather simulation from ActiveSky which is installed on the scenery generator PC.
And neither of these two weather products interact with each other across my network.
I access BACARS & PSX.NET software via 3 iPads which are connected to PSX & run a piece of software which simulates the CDUs, thus I have 2 CDUs for the Capt & FO & the third running BACARS & PSXControl software.
Secondly - my scenery generator receives PSX positional information through my network from PSX via WidePSX
- this runs on a third PC.
This 'ancilliary PC' also hosts my remote ATC client & my ATC communications device & the BACARS, PSX.NET & PSXControl software.
(https://i.imgur.com/WyW3NGyl.jpg)
I really do have hassle free PSX flying this way. I fly PSX a lot, I mean a lot.
ActiveSky upper wind data is not accurate to real world wind data, whereas PFPX upper wind data is generally within a 5-10% margin when compared to the real deal used commercially.
Hope this helps.
I hope this helps
EDIT - Feel free to insert your preference of flightplanning software wherever I have stated " PFPX".
QuoteI dont want to crash into the discussion here but I would like to offer my own opinion on ActiveSky wind data output versus PFPX wind data & how it interacts with PSX.
Steve,
Thanks for joining the discussion. :)
I'm obviously getting things confused. but I just don't understand where. I am looking at winds from one direction on the Nav Display and looking at entirely different winds from the those I loaded into the Corridor from PFPX.
Where is your PFPX getting it's wind data?
I was going to use PSX.Net today, but I could not get the frequencies for Vatsim to change.
Bode
Quote from: Bluestar on Mon, 8 Aug 2022 17:52Where is your PFPX getting it's wind data?
My PFPX uses the native annual weather subscription which it (PFPX) periodically downloads. I use the wind data output from my PFPX flight plan & insert this into the wind data entry in the relevant Weather Page in my PSX Server/Boost instance. I do this as follows:
1. Once I have created a PFPX flightplan & exported it into the PSX Routes Folder in the correct format.
2 And ONLY AFTER this flightplan is loaded from the PSX database, activated, EXECuted & ONLY once the relevant COST INDEX & FLIGHT LEVEL is entered on the PSX PERF INIT Page ... as would be the minimum for real world operations. Some flight plan outputs also create DES WINDS, I usually manually input these during the preflight sequence if time allows, or after the TOC when time allows.
Once again, just emphasize - my choice (which has always worked for me) is to keep the scenery generation weather engine (just producing 'eye candy' & the PSX upper wind data (from PFPX) entirely separate.
WidePSX is the application I am using that has a tick box in one of its tabs to actively take control of the ATC client VHF frequencies & synchronize them to the VHF frequencies you select on the PSX Radio tuning heads on the centre pedestal.
I hope this helps.
I hope this helps.
Thanks Steve, every little bit helps. :)
Bode
Bode,
I saw you asked if WidePSX can 'override' PSX "downloaded" METAR below 20000ft in another part of the fora.
To the best of my (limited) knowledge this is not possible.
From my personal experience (a lot) of flying my set up as I have illustrated & described .... I have never had any issues or anomalies with the PSX METAR downloads. They appear to me to originate from a very similar source to the data used by PFPX & the popular online flying environments (VATSIM etc).
This could be completely gratuitous at this point... I don't mean to be too basic, so forgive me. But...
1. PFPX gets wind forecasts from its current weather servers.
2. These are presented at the end of the operational flight plan (OFP).
3. These are cut & pasted by the user into PSX, to make the wind corridor.
Therefore...
4. The wind corridor always agrees with the OFP, because they have exactly the same data.
5. Wind data is only given for select waypoints.
Therefore...
6. Wind is interpolated for both the OFP and the FMC. Therefore one again...
7. The wind corridor always agrees with the OFP.
If you ever have a situation where you look at the ND and the wind direction and speed vary from what you expect, you should save a situ file for closer examination. The following should always agree:
A. Wind on the ND
B. Wind on the FMC: Find it on PROG > POS REPORT
C. Wind on the OFP
D. The wind corridor
If these four don't agree, then the error is most likely in setting up the wind corridor. Make sure you cut & pasted properly, make sure the wind corridor is active, check the magenta "blobs" on the map (Instructor > Situation > Position), make sure you have magenta blobs, make sure your aircraft is close to or within one of the blobs.
Also:
8. From the surface vertically up to the corridor, PSX uses local real-world surface weather and smoothly changes the winds as the altitude increases, until you reach the corridor. This means:
9. If you spend a very long time in cruise below the corridor, you may have wind predictions that don't match your experience.
Therefore...
10. Also check that your OFP (that you cut & pasted into your corridor) is giving you wind data at the altitudes you need.
Even with PSX-native, real-world weather injection into PSX(*), only the surface stations will get updated. So real-world weather affects METARs and local airport winds, but the corridor will always match your OFP. This is important: what's on your OFP will be in PSX.
*) Add-ons by third parties may inject weather in different ways. PSX itself only imports surface weather.
(I typically fly trips that are over 10 hours long, but I break them into several days. Each day, the OFP still agrees with PSX, because the wind corridor isn't overwritten by anything. It remains fixed until you update it or cancel it.)
In numerous trips lasting 10+ hours each, the time and fuel agreements between the four things above (the ND, the FMC, and OFP, and the corridor) are in such constant agreement that I purposefully change the slider called "Wind and OAT random deviations" to something other than zero, otherwise the winds are too perfect. As we know, the real world doesn't match the forecast by 100%, so it's more fun (for me) to have some randomness mixed in.
But that's just because the agreement is otherwise so perfect.
Example: I just ended a flight from SBSN to FMCH, with PFPX as the flight planning tool, using real-world weather in PSX and a wind corridor. The trip was planned for 11 hours, 29 minutes, and at takeoff the FMC predicted I would land with 64,100 lbs of fuel. The trip actually took 11 hours, 35 minutes, and I landed with 61,100 lbs of fuel. That feels pretty good, considering I had the wind slider set for some random deviations and there was some vectoring at the destination. Planned contingency fuel was 8000 lbs, so even the difference between predicted and final was within the anticipated window--no need to sweat the discrepancy, and no need to dip into extra fuel or FMC reserves.
Final summary: If the winds on the ND seem off, make a situ and post it. Also compare the ND, the FMC, the corridor, and the OFP for that waypoint and you should see agreement.
Best of luck.
What Will so elloquently said ....
Oooops, I forgot to say two things.
First, your flight planning software doesn't have to be PFPX. You could use Simbrief or anything else that generates an OFP with a wind forecast table.
And second, the ND winds may not match the corridor if you are using an add-on that injects winds aloft into PSX. The corridor itself remains static (based on your original OFP) until you cancel it or change it, so the corridor will obviously become out of synch with the PSX weather if there is something else injecting external winds aloft into PSX. If this is what is happening, there are two solutions. Either request an updated OFP with an updated wind table from your virtual dispatch office, and use it to update your wind corridor, or else just live with it, as the OFP always contains forecasts anyway, and forecast winds don't always match what you see when you get airborne.
Will,
Thanks for the explanation.
QuoteEither request an updated OFP with an updated wind table from your virtual dispatch office, and use it to update your wind corridor, or else just live with it, as the OFP always contains forecasts anyway, and forecast winds don't always match what you see when you get airborne.
Can the OFP be run again, say 6 hours into a 10 hours flight, and the winds aloft created by the "new" OFP be pasted into the Corridor?
Bode
QuoteCan the OFP be run again, say 6 hours into a 10 hours flight, and the winds aloft created by the "new" OFP be pasted into the Corridor?
Hi Bode,
The answer is: certainly. You can run your OFP as many times as you want, say every 6 hours when new forecasts come out. Then you can cut & paste the new OFP wind table into your wind corridor as needed. Thus, you can update the wind corridor as often as you update your OFP.
Another application here is that if you divert to an alternate, and if your original OFP doesn't include winds for the route between your present position and the alternate, then you can run a new OFP to the alternate and update the corridor with those winds as well.
Whether this is "realistic" depends on operational considerations with your company.
Some long-haul companies update the winds during the trip, others fly the whole flight with the wind forecast created at the time of dispatch. After all, even the best forecasts can be off, so the pilots always need to look at actual fuel consumption and update their planning accordingly, no matter what their OFP says, and no matter how current their forecasts are. The whole reason for carrying extra fuel and for having alternate airports is for things like this, when the real world doesn't match your predictions.
But there are actually two issues here: creating a new OFP, and updating PSX with a new corridor based on updated wind data. You can do both, or neither. But if you wanted, you could do just the latter... you could use your flight planning software to generate an updated wind table and copy that into your PSX wind corridor, without going as far as replacing the original OFP that you're using for navigation.
But to your question: yes, you can update the wind corridor in PSX as often as you update your OFP.
It's just "redispatch" basically. Fly up to point (X) using reasonable but not pessimistic data, and at (X) figure out whether you can still make it to the original destination. Most of the time you can, and you save tons of fuel. Sometimes you cannot, and you deviate to a known fuel alternate and swallow the loss.
Hoppie