Eoin M - 1315348
-
Posts
522 -
Joined
-
Last visited
-
Days Won
6
Content Type
Profiles
Forums
Calendar
Posts posted by Eoin M - 1315348
-
-
-
Just a note, if you manually overwrite the sectorfiles, the new configuration for DOS/CVN will not be fully implemented.
Ie: Incorrect ground layouts will be available
Default screen settings will not be correct
And Login templates will also not be correct.
There is also a huge risk of not showing the changes because the views are all pre-configured for each AIRAC, so when you manually overwrite, you will still have the previous AIRAC display settings, which could be out of date (New things won't show, old things will still be available).-
1
-
-
AccuMap v1 and 2 have been taken care of
-
Brb, buying a Vive.
Rip social life.
-
The error is just VRC saying it can't download the servers from the internet, which is a common issue, and i've never found a fix.
Doesn't mean it can't find the aforementioned servers.txt file
-
VRC tends to do that with servers. I've attached the server file to this post. Try downloading that into "C:\Users\[username]\Documents\VRC"
-
14 hours ago, Joshua Micallef said:
Eoin.
First off, great post!
However, it should be noted 122.1 will not show up as an "Active" Controller in your Connection Client (Vpilot Etc.), I am not sure if we are supposed to open a 'Text' Frequency where we just listen to the text conversations, however, i assume 122.1 is never used on VATSIM, but is in the Real World.
Not sure how, but I've managed to get 122.1 working as a second frequency when online. Only ever worked once, but I do monitor it for text transmissions.
12 hours ago, Kirk Christie said:Good post, I see that you are writing ETA's in the scratch pad, that is good, and often something I suggested to enroute controllers during the exam, but here is a question for you,.
The aircraft is estimating the next fix at 0930z, but what time did it pass the last fix?
But before you ask, why should you care? let me ask you, how do you know if the aircraft behind is catching up to the aircraft in front if they have not passed the fix the preceding aircraft already passed? How do you know you still have 10 minutes?
I suggested to my students using minutes to write in the scratch pad TOP>ETA (time of passing > ETA) so something like 54>28.
You bring up a good point, will remember to note the TOP
-
1
-
-
When I control on Oceanic positions, I can't help but notice that not many pilots, old and new, know much about oceanic control. Some smash it all our with their position reports, requests, complying with ATC instructions, etc. Others request vectors, give incorrect reports, mistake the phraseology, etc.
Consider this a bit of an in-depth explanation for pilots on how Oceanic ATC works from the pilots perspective.
Warning: This post is quite long...
Let's get this out of the way:
What's the difference between normal ATC, and Oceanic ATC?
Normal ATC throughout Australia (Brisbane Centre, Melbourne Centre, Sydney Approach, etc.) rely on radar to determine where an aircraft is in the air. This could be through ADS-B, MLAT, or good ol' SSR.
Over the ocean, it's not as easy to place a radar down and hope that it doesn't float away... Therefore, there is no radar. This non-radar airspace is controlled by oceanic ATC.
In short, normal ATC has radar and covers over land (Sometimes referred to as Domestic ATC). Oceanic ATC, doesn't have radar and rely on other methods to depict where aircraft are in the world.
Where does Oceanic ATC cover?
In Australia, the OCA (Oceanic Control Area) is where all oceanic ATC takes place. This area is covered by multiple sectors:
In the Brisbane FIR (YBBB), we have BN-TSN_FSS (Tasman) covering the Tasman Sea up to the Coral Sea:
This during special events, this standard sector splits further into BN-COL_FSS (Coral) covering the northern part of the Coral Sea, BN-FLD_FSS (Flinders) covering the southern part of the Coral Sea, and BN-HWE_FSS (Howe) covering the Lord Howe Island area (Which is equipped with ADS-B, will touch on later)
In the Melbourne FIR (YMMM), we have ML-IND_FSS (Indian) covering the Indian ocean and all south of Australia down to Antarctica:
This during special events, this standard sector splits further into ML-INE_FSS (Indian East) covering the north west of Port Headland and Karratha, up to the southern part of Jakarta, and ML-INS_FSS (Indian South) covering south of Australia down to Antarctica.
Now that we know where they are, how do you communicate to Oceanic ATC:
First things first; The all OCAs in Australia are controlled from Brisbane, so all oceanic controllers in Australia are called "Brisbane Radio", there is no "Melbourne Radio", so yes, ML-INx_FSS is called "Brisbane Radio".
Now that that's out of the way, let's get down to business.
When domestic ATC hands you off to an Oceanic controller, the handoff will sound similar to this:
BN-MDE_CTR: "Qantas 151, crossing PLUGA, identification terminated, report your position to Brisbane Radio on 128.6, g'day"
Or, if you are using CPDLC:
BN-MDE_CTR: "Qantas 151, continue with Brisbane on Datalink, monitor VHF primary 128.6, g'day"
So what does this mean?:
"Crossing PLUGA, identification terminated": Once you've reached the waypoint "PLUGA", you are no longer within range of radar, and we can no longer identify you.
"Report your position to Brisbane Radio on 128.6": Once you've reached the waypoint "PLUGA", provide Brisbane Radio with a position report on frequency 128.6.
"Continue with Brisbane on Datalink": Remain in CPDLC contact with Brisbane (YBBB) and do not log off.
"Monitor VHF primary 128.6, g'day": Monitor frequency 128.6, you are not required to transmit any position reports.
Now, communicating to oceanic:
When making initial contact:
QFA151: "Brisbane Radio, Brisbane Radio, Qantas 151 with position." Note: It is good practice to state the callsign of the station you are calling twice.
At this point, Brisbane Radio will respond in one of two ways:
BN-TSN_FSS: "Qantas 151?" Note: When a controller says your callsign alone, it's either an acknowledgement of a previous transmission or an indication for you to go ahead. In this case, it's "Go ahead."
Or
BN-TSN_FSS: "Qantas 151 Brisbane accepts primary guard this frequency. Secondary 122.1, standby for a SELCAL check"
So what does this mean?:
"Brisbane accepts primary guard this frequency": This frequency can be used in place of the standard guard frequency, 121.500.
"Secondary 122.1": If you are unable to reach me on this frequency, then try again on 122.1.
"Standby for a SELCAL check": Please wait before transmitting, I am about to test your SELCAL system.
If your SELCAL check is okay, meaning you have received the SELCAL alert, then you should respond with:
QFA151: "Brisbane Radio, Qantas 151 SELCAL check okay." Meaning you have received the SELCAL alert.
After this point, Brisbane Radio should be ready for a position report:
BN-TSN_FSS: "Qantas 151, go ahead with position."
Now for the hard part, the position report...
What are position reports?
Position reports are how ATC can determine where you are. Position reports contain estimates for waypoints, speeds, altitudes and any other information. Because there is no radar over the ocean, ATC relies on time-based separation and reports from the pilots. ATC has no way of determining where you are unless you specifically tell them.
The standard format is:
Current/Previous waypoint name and the time which you crossed that point.
Current flight level.
Mach number if assigned by ATC.
Your next waypoint and estimate for that point.
The waypoint after that.
VATPAC provides a nice tool for pilots to help put together position reports: https://vatpac.org/pilots/pilot-tools/oceanic-reporting-tool/
Let's look at some examples:
Example 1:
QFA151 (Qantas 151) from Sydney to Wellington enters oceanic airspace at waypoint PLUGA. Not using CPDLC and equipped with a SELCAL code of CP-RS.
BN-MDE_CTR: "Qantas 151, Crossing PLUGA, identification terminated, report your position to Brisbane Radio on VHF 128.6, g'day"
QFA151: "Report position to Brisbane Radio on 128.6, Qantas 151, g'day"
QFA151 tunes to 128.6
QFA151: "Brisbane Radio, Brisbane Radio, Qantas 151 with position."
BN-TSN_FSS: "Qantas 151 g'day, Brisbane accepts primary guard this frequency. Secondary 122.1, standby for a SELCAL check"
Brisbane Radio broadcasts the CP-RS SELCAL code over the frequency.
QFA151s radio alerts the pilot that a SELCAL was received.
QFA151: "SELCAL check okay, Qantas 151."
BN-TSN_FSS: "Qantas 151 go ahead with position?"
QFA151: "Qantas 151 is position PLUGA at time 0627, flight level 380, estimating VELKU at 0655, SASRO next."
BN-TSN_FSS: "Qantas 151." Note: Unlike other FIRs, Australian ATC (YMMM and YBBB) are not required to read back your position report.
Qantas 151 will continue to provide position reports each time they reach a new point along the route until back within radar coverage and identified.
Brisbane Radio can use your position report to build an image of where you are. The image below is from BN-TSN, the circles are aircraft identified on Mode-C, and the boxes are approximate positions based on the pilots' position reports:
Example 2:
QFA151 (Qantas 151) from Sydney to Wellington enters oceanic airspace at waypoint PLUGA. Using CPDLC and equipped with a SELCAL code of CP-RS.
BN-MDE_CTR: "Qantas 151, continue with Brisbane on Datalink. Monitor VHF primary 128.6"
QFA151: "Continue with Brisbane on Datalink, monitor 128.6, Qantas 151, g'day"
QFA151 tunes to 128.6 and monitors that frequency.
QFA151 and YBBB remain in contact through CPDLC and ATC can obtain automatic position reports through CPDLC. The pilots must monitor the frequency for SELCAL alerts and are not required to provide position reports through voice.
Brisbane Radio can now use CPDLC/ADS-C to retrieve your position through ACARS. Triangles are aircraft whose position is sent through CPDLC using ADS-C:
Example 3:
QFA151 (Qantas 151) from Sydney to Wellington has entered oceanic and is requesting a step climb to FL400.
QFA151: "Brisbane Radio, Brisbane Radio, Qantas 151."
BN-TSN_FSS: "Qantas 151?"
QFA151: "Brisbane Radio, Qantas 151, request climb to FL400"
BN-TSN_FSS: "Qantas 151 climb to FL400, requirement to reach FL400 by VELKU, report reaching." Note: QFA151 must reach FL400 at or before VELKU. This prevents conflicts when in the middle of an altitude change over a point. They are also asked to report reaching FL400, so ATC can determine when they are level at FL400
QFA151: "climb to FL400, requirement to reach FL400 by VELKU, will report reaching, Qantas 151"
QFA151 reaches FL400.
QFA151: "Brisbane Radio, Brisbane Radio, Qantas 151."
BN-TSN_FSS: "Qantas 151?"
QFA151: "Brisbane Radio, Qantas 151, reaching FL400"
BN-TSN_FSS: "Qantas 151."
Example 4:
BN-TSN_FSS detects a conflict between QFA151 (Qantas 151) and ANZ132 (New Zeland 132). QFA151 is using CPDLC, ANZ132 is not and is using the SELCAL code FS-CH.
Brisbane Radio broadcasts the FS-CH SELCAL code over the frequency.
ANZ132s radio alerts the pilot that a SELCAL was received.
ANZ132: "Brisbane Radio, New Zeland 132 answering SELCAL."
BN-TSN_FSS: "New Zeland 132 climb to reach non-standard FL360 by VELKU, report reaching."
ANZ132: "Climb to reach non-standard FL360 by VELKU, will report reaching, New Zeland 132"
Or:
Brisbane Radio sends a message QFA151 via CPDLC, telling the pilots to descend to FL350 and report when reaching.
QFA151 receive and acknowledge the message on their FMC. They then begin their descent.
Once QFA151 have reached FL350, they send a message to Brisbane Radio via CPDLC stating they have reached FL350.
How can I help ATC when flying?
- Fly with the correct UTC time set in your simulator. Since ATC rely on your estimates, they must be in the correct UTC time. Before connecting to VATSIM, make sure your time of day and your aircrafts UTC clock are set to the correct UTC time. You can find the current UTC time on Google, vPilot (Flight plan window), or even on your phone's clock!
- Prepare your position reports beforehand. Before you cross your next position, have your position report ready and prepare to give it to ATC. You can use VATPACs oceanic tool (https://vatpac.org/pilots/pilot-tools/oceanic-reporting-tool/), or if you're flying Boeing, you can go to your FMCs PROGress page, and then to the POS REP page.
- Use CPDLC. CPDLC (Controller Pilot DataLink Communication) is a form of communication between pilots and controllers which uses ACARS and satellite data. ATC can use CPDLC to issue instructions through the onboard flight computers. The messages are in plain text and are easier to read than a radio transmission. It can be much easier to manage than a cluttered frequency and can save time when making requests to ATC both domestic and oceanic. VATSIM doesn't support CPDLC natively, but the VATPAC TAAATS simulation supports the Hoppie ACARS/CPDLC system. The pilot client can be found here: http://www.hoppie.nl/acars/prg/air/
- Find your SELCAL code. Each aircraft has a unique SELCAL (Selective Calling) code assigned to it. SELCAL is used to "Ping" a pilot when ATC needs them, so they the pilots don't have to listen to the poor quality of the radio throughout their oceanic crossing, they can just wait for the SELCAL alert from ATC, then start paying attention to the radio. You can use http://www.airframes.org/ to find the SELCAL code for your aircraft. You can enter your SELCAL code when connecting using vPilot, or if you're using X-Plane, you can use xSelcal: https://forums.x-plane.org/index.php?/files/file/35528-xselcal/
- Make sure ATC is ready for your position report. When providing a position report, make sure ATC is ready by saying "Brisbane Radio, Brisbane Radio, Qantas 151 with position." then wait for Brisbane Radio to give you the go-ahead for the report. This makes sure Brisbane Radio is ready to take the report.
- Tell ATC when your ETAs update by more than 2 minutes. If your ETA changes by more than 2 minutes from the time you told ATC with your position report, you must provide ATC with a "Revised Estimate". Eg:
QFA151: "Brisbane Radio, Brisbane Radio, Qantas 151."
BN-MDE_CTR: "Qantas 151?"
QFA151: "Brisbane Radio, Qantas 151, revised estimate for VELKU 0502z"
BN-MDE_CTR: "Qantas 151."
Identification near Lord Howe Island (LHI):
Lord Howe Island has an ADS-B receiver based on the Island. This means that any aircraft within range can be identified, and are not required to pass position reports. ATC will indicate this by telling you whether or not you are identified.
The grey circle around Lord Howe Island is the ADS-B range of the receiver.
When BN-HWE_FSS ("Brisbane Radio", Howe), they will cover most of this area.
Non-radar in Domestic Airspace:
The BN-TRT_CTR sector (Territory), BN-ARA_CTR sector (Arafura) and BN-KIY_CTR sub-sector (Kimberly) lack radar coverage in their northern areas towards the WAAF FIR (Ujung Control). This results in a control service similar to Oceanic ATC, however, there are no SELCAL checks or procedures, secondary frequencies, or guard override frequencies. The red line depicts where radar coverage may be lost/regained:
CPDLC can still be used and the controller callsign will remain as "Brisbane Centre".
More info:
CPDLC: Controller Pilot DataLink Communication: A text-based communication system between pilots and ATC utilising ACARS. Typically accessed through the MCDU/DCDU or MFD.
https://en.wikipedia.org/wiki/Controller–pilot_data_link_communications
ADS-B: Automatic Dependent Surveillance-Broadcast: Highly accurate radar data containing much more information than standard Mode C transponders.
http://www.airservicesaustralia.com/projects/ads-b/how-ads-b-works/
ADS-C: Automatic Dependent Surveillance-Contract: A CPDLC position reporting system set up by ATC. Sends aircraft position and altitude details to ATC depending on their requirements.
https://www.skybrary.aero/index.php/Automatic_Dependent_Surveillance_-_Contract_(ADS-C)
SELCAL: Selective Calling: A unique tone assigned to each aircraft, which when broadcast over the currently tuned radio frequency, will alert the pilots.
https://en.wikipedia.org/wiki/SELCAL
Radar images from EuroScope/TAAATS and AccuMap-Project .
-
3
-
2
-
Just getting better and better!
-
2
-
-
GA Madness
in Events
What time zone Is the roster using?
-
Date changed to 22/03/2018, 22nd March, 0800z.
Unfortunately Grammarly can't spell as good as it says...
-
Happy to help!
Being VATPACs EuroScope expert and a developer has it's advantages :cool:
-
Here is the issue
Josh, Callum and I have done some testing and we think this is the issue:
The issue originated originates in TAAATSMod.dll, and is to do with TFMS.
The quick fix:
[*]Load EuroScope with your desired profile.
[*]On the TAAATS HMI (The big grey bar on the top of the screen), click the button labelled TFMS.
[*]Click on the airport ICAO code. By default, it's set to YMML.
[*]A small menu will pop up, click the button labeled "Switch to offline mode".
This will prevent TAAATSMod from making requests to the URL, thus stopping the exceptions. I've spoken to IT and they are on top of the issue.
Note to Jake for the new TAAATS client
: >try{}catch(){} -
Hi everyone,
The AccuMap team will be holding a public meeting on Thursday the 22nd of March (22/03/18) at 0800z.
This conference will be held on a temporary Discord server: https://discord.gg/PyZyN2X'>https://discord.gg/PyZyN2X
As many of you know, AccuMap is in the stages of a complete redesign for v2. As we strive to make the best application available, we need community input.
We'll be discussing features, design problems and solutions, as well as community suggestions.
What: Public discussion and problem solving for the benefit of AccuMap and all VATSIM users. A chance to give suggestions directly to the developers and help them solve new design problems coming with v2.
When: 22/03/18 0800z
Where: https://discord.gg/PyZyN2X
If you're unable to make it, feel free to comment your suggestions on this thread, or leave your suggestions on the server.
We hope to see you there!
-
Ok, so it's something on my end then, and I've mucked up the install somewhere. What would cause the ATIS Generator to spit out the wrong ATIS files (I have 2018 INTAS loaded in ES's ATIS page). I am manually copying the url from ATIS Generator into the ES pane, if that makes any difference.
UPDATE: I've actually just gone to test it again now, with YBCG now it doesn't seem to actually connect with the generator at all, but it does with, say, YBBN.
This is the extracted string for YBCG:
>http://localhost:3000/?info=A&metar=YBCG%20080630Z%20AUTO%2017011KT%209999%20%2DSHRA%20SCT037%20BKN052%20BKN066&callsign=BN%2DMDE%5FCTR&freq=133.000
The ATIS Generator does not update, it just says waiting for Euroscope ATIS request. I am clicking test url and have new ATIs ticked.
As you can see, it is extracting some metar information from somewhere, but I don't know where. It doesn't match the METAR from VATSIM for YBCG
if I change the aerodrome in Voice ATIS to YBBN it works fine. I haven't touched either of the files since yesterday.
Anyway, happy to ignore if it's just something weird that's happened somewhere on my install. I can assure you I am using the new ATIS files, tho, as shown in screenshots. The second one is taken immediately after the first, only change is getting the METAR for YBBN and then pressing test URL, all in ES (I also scrolled down in the voice files to confirm I had the expecteed ones) I did not touch the Generator.
EDIT2: I just tested it again on another station, loaded up YPAD fine, put YBCG it loads up the correct metar info but generates incorrect voice files.
Below is the Generator after receiving the request from ES.
If you want to take this to email or something, instead of doing troubleshooting on the forums, let me know
I have a feeling there has been a datafile conflict during the installation. It's happened before with AccuMap on certain computers. I've attached the correct datafile which is working completely fine for me. Place this in
>%appdata%/VATPAC/ATIS
and replace the current airports.json.
I apologise for the inconvenience. Still waiting on IT to help out with the automatic updater
-
The ATIS Generator is designed for the new INTAS ATIS package only and not the old packages.
Thought you might say that, which is why I tried to be as clear as I could be. ;D If I was using the old voice files I would not have had this problem. I'll just pull up the important bits:
Some of the things that the Generator spits out don't seem to correspond to the voice files. EG today, I put an ATIS on YBCG. the Voice file is "[ON FIRST CONTACT WITH CG TWR OR BN APP, NOTIFY RECEIPT]" but the generator spits out " [ON FIRST CONTACT WITH CG_TWR OR CG_APP NOTIFY RECEIPT]" I would guess there may be more than this example.If you want to go test it, or if you want me to send you screens, I can. In any case, the issue is the file in the new 2018 INTAS (that mentions BN APP, good job on fixing that btw!) says one thing, but the one the ATIS Generator spits out is what I assume is the OLD voice file from the OLD package. I don't think I'm doing anything wrong, on other airports like YSSY It spits out the correct adjusted sound files in normal usage (i.e DO NOT PASS THROUGH... instead of opaque old CL), but it's always possible. I am definitely using the 2018 female INTAS, tho, with the generator. This is the only such issue I've noticed so far tho.
Not a big deal in the grand scheme of things, in relation to what is a wonderful step forward, so I don't want to harp on about it. Just wanted to be crystal clear, and figured it would be something you'd want to know about.
Glad to hear the other things I posted about are on the roadmap. Look forward to it!
Thanks nick, I have just tested it on the Gold Coast and it works perfectly fine for me. All the files are there, mapped correctly and in working order.
Just to make sure, the files you must use are the ones that came with the ATIS generator in the zip file. I can jump on TeamSpeak later on today if you’re still having issues, but I can assure you, the ATIS files that are packaged with the generator do work and I’ve just checked it myself.
-
Some of the things that the Generator spits out don't seem to correspond to the voice files. EG today, I put an ATIS on YBCG. the Voice file is "[ON FIRST CONTACT WITH CG TWR OR BN APP, NOTIFY RECEIPT]" but the generator spits out " [ON FIRST CONTACT WITH CG_TWR OR CG_APP NOTIFY RECEIPT]" I would guess there may be more than this example.
The ATIS Generator is designed for the new INTAS ATIS package only and not the old packages.
You can change the descriptor at the top of the "Voice ATIS Setup Dialog" in EuroScope.
Click "Browse", then navigate to wherever you've unzipped the ATIS package.
Once you've found it, go to the "Female (INTAS)" folder, and load the "AtisFiles.txt" file.
That will then import the new ATIS files into EuroScope and you'll be all set!
Second, is there a way somehow to have another field that just spits out the changes? EG, those items apart from letter than were changed from the last iteration? That would help for reading out changes to aircraft, the only downside to using this software.
Working on it for the next update :cool:
Finally, not sure if this generates XW components for the major rwys, but it definitely doesn't for ones where you need to specify the actual rwy number (i.e CG
). Is it possible to add something so it does this for custom rwy numbers?Also working on it for the next update too :cool:
Cheers!
-
Yeah got it working now. Just had no guidance whatsoever on where the files should be installed and referenced. I believe Quigs is working on that.
I'm the one with the manual ;D
They're vague because the ATIS files and generator are pre-configured with the EuroScope Package, meaning the only reason most people should need to read the manual is if they're trying to figure out how to use it.
If you're running a custom setup, it's assumed you know how to setup the ATIS, seeing as you can set up the rest of the entire scope. The ATIS is relatively easy compared to all the other setup components of EuroScope.
Will look into it though
-
Yeah I had to rename MAX to MX, GT 10KM to GREATER THAN 10KM and NOTIFY RECEIPT to NOTIFY RECEIPT OF. That's so far.
Is that normal?
BTW....awesome work!
No, because as the instructions say, it's designed for the 2018 ATIS file set that's included, and not for the old files provided in previous packages
Aaaannnd, pretty sure I'm using that. Although with the very sparse instructions... it's pretty hard to tell.
That's very strange, because the provided files use GREATER THAN 10KM, and not GT 10 KM
Are you sure you're not using the depricated files? HAS to be the INTAS files only
-
Yeah I had to rename MAX to MX, GT 10KM to GREATER THAN 10KM and NOTIFY RECEIPT to NOTIFY RECEIPT OF. That's so far.
Is that normal?
BTW....awesome work!
No, because as the instructions say, it's designed for the 2018 ATIS file set that's included, and not for the old files provided in previous packages
-
Eoin,
When dealing with people who are not programmers you have to be much more specific. You must lay things out in a Step 1,2 & 3 fashion. Otherwise it all gets too hard when one has to go back and forth to compare visual images in order to determine whether or not the " marks are to be removed. You must TELL me not to use them AND also to remove them!
Also, Tristan, what for those of us who might be uninitiated, is a 'file descriptor'?
Very good point. I'll admit, i'm not the god of manual developing. Will improve with coming updates :cool:
As for the file descriptor:
It's the text file that "imports" and "maps" all of the recorded sound files to the [text boxes] inside of EuroScope.
You can change the descriptor at the top of the "Voice ATIS Setup Dialog" in EuroScope.
Click "Browse", then navigate to wherever you've unzipped the ATIS package.
Once you've found it, go to the "Female (INTAS)" folder, and load the "AtisFiles.txt" file.
That will then import the new ATIS files into EuroScope and you'll be all set!
Sorry to steal your spotlight Tristan but I thought i'd practice on my instruction writing
-
Right! We got it up & running with a little help from Tristan. The above notes should be included in the pdf manual. It helps old, slow buggers like me.
Funnily enough, it actually is in the manual
See section 3 (EuroScope connection)
Image attached
-
Not sure if this is exactly what Zach is talking about, but sometimes if METARs have SPECIs, TEMPOs, etc, it breaks the ATC Assist generator requiring manual addition of values for QNH, T, etc. I think this might be a VATSIM issue, sometimes the full metar exists online at BoM but not in VATSIM. I'd imagine that might also break something in this new generator, unless it was getting data from the BoM?
The data is being sent from EuroScope directly to the application, and its new METAR decoding engine will account for any remarks, TEMPOs, SPECIs, etc.
-
Does it work for ES 3.2? And the installation instructions need to be a bit more detailed if so.
It works with all versions of EuroScope and does not rely on any plugin or EuroScope specific code what so ever.
It's a completely separate application to EuroScope (could theoretically be run on another computer in the same or even a different house and still work 100%).
The installation and configuration are 100% the same for all versions of EuroScope.
[*]Launch EuroScope and the ATIS Generator
[*]Copy the URL from the ATIS Generator into the EuroScope ATIS menu's "ATIS Maker URL" section.
[*]Tick the "Automatically generate new ATIS using the URL" checkbox at the bottom.
[*]Click the "Test" button.
Done!
Your ATIS will now automatically update when the METAR changes.
You can adjust the ATIS parameters in the ATIS Generator application.
You can press the "Test" button to re-fetch the current ATIS from the generator.
Is it time for me to move to P3D?
in Flight Simulators
Posted
I started in FSX back in 2009, started using P3d in 2016. Was well worth the extra cost!