Nicholas G - 1397820
-
Posts
368 -
Joined
-
Last visited
-
Days Won
17
Content Type
Profiles
Forums
Calendar
Posts posted by Nicholas G - 1397820
-
-
Always a great guy both in and out of the sim. Enjoyed having a bit of banter, and he always gave as good as he got. Kind and patient when needed, absolutely wicked the rest of the time in almost as great a measure
Many years of experience, and much wisdom, all of which he was happy to give to me, and to many others here as well.
Thanks for keeping us in the loop Tracy. -
Yeah, generally you can apply the common sense test. If you're going to pop up within 10 minutes of another aircraft and create a conflict, probably don't do it. If you're planning to relog back in in the middle of a busy event, don't do it. If you're planning to log back in on or near a ruway that is active, don't do it. Especially if you haven't checked the status of online ATC, miss that tower is on and has nominated the opposite runway to what you are planning to use.
Conversely, logging on where there is no ATC is pretty much always fine. Logging on when there is ATC on and not another aircraft for 100 miles is almost always fine. In general, ATC will try to contact you anyway if you pop up in their airspace, and as long as you respond reasonably promptly you should be fine.
But baseline expectation is generally that you check the airspace you are operating in and who's there before you log in, not after.
Worth noting that if you are in a long sequence in an event (e.g Milk run), and you need to go and deal with RL but you plan to be back before something significant happens (i.e your descent), ATC will almost always prefer you actually stay logged in than for you to log off and then back in again when you get back to your keyboard. This is because while you're online, ATC can plan around you - they can't if you're logged off and will randomly reemerge again at some point. Always worth asking ATC if you can just step away if RL takes a hold.-
1
-
-
Quote
There are 5 ratings in VATSIM, P1 to P5. As I'm only a pilot /observer I don't get to engage ATC so I want to sign up with one of the listed training providers. I'm just having issues with that.
Having a little trouble following you here. To clarify, the pilot ratings have nothing to do with what you can do as a pilot on the network. You could not have any pilot rating and fly around and talk to as much ATC as you like. Pilot ratings do not in ANY way allow you to do anything on the network that you couldn't do without one.
I think most of the ATOs aren't really actively training atm because of a recent change to how the ratings work. There is is no ATO for Oceania Region anymore so if you really wanted to pursue pilot ratings your options will mostly be in Europe or NA. Which is fine, there'll just be some things that don't cross over.
Really, pilot ratings are only there if you want to pursue them for their own sake. Plenty of accomplished pilots don't bother, and most of what would be covered in those ratings you could probably gather from online tutorials, a bit of light reading and experience.
The only ratings that actually open up different kinds of things on the network are the controller ratings, which are entirely different to the pilot ratings and need to be earned seperately. You need to have various ratings to be allowed to act as ATC on VATSIM. You do not need any rating of any kind if you just want to fly. -
Does this happen in all aircraft or just some? Test in default c172, zibo, any payware third party aircraft that use their own navigraph datasets (eg Flight Factor).
If you have correct navdata and the CDG scenery it should all work, as I use it myself.-
1
-
-
The crossed icon deletes a reaction if you have put a reaction on a post.
-
Looking from the screenshot, I would have said assigned a push to talk, but it appears you've resolved your issue in any case.
-
You aren't running any other applications that may be taking exclusive control of your sound devices? Discord/TS in admin mode, DAWs, another pilot client, anything like that?
Can you post a screenshot of your audio settings page in xPilot?
Have you tried using it on VATSIM anyway to confirm you get no sound when tuning ATISs, ATC freqs, etc? -
Nice one!
Worth pointing out that these can also be imported as-is directly into Littlenavmap and will display in that. No modification required. -
1 hour ago, Pheonix Taylor said:
Brett, thanks for pointing me to the right spot to find what will become the offical charts, thanks.
They're already official and already in use real world, they just didn't make it in time for DAP 163. They did a similar thing with Hobart.
-
@Alan MallowsI think the initial problem we had was just getting Swift to connect, which iirc we resolved. The voice issue sounds different, but assuming you're using the current version of Swift you shouldn't need to configure anything to get voice to work. I think the other issue you had was model matching which I gave you some steps on, did you resolve that issue?
Feel free to resurrect the other thread you posted so we can keep troubleshooting there instead of in an unrelated thread. -
Most of the aerodrome display components of the prfs aren't actually reliant on the parts of TAATSMod that doesn't work in 3. I can go and open any of the prfs in 3.2 and they will open with all the correct colouring and display options, just not the TAATS menu and control features.
More likely if the aerodrome layouts aren't displaying correctly that there's something else askew in the settings config somewhere. -
Possible you still had another connection to Vatsim running while trying to connect 3.2 beta.
Anyway, you've solved it now, so that's good! You'll have to provide some photos of the finished setup with the curved screen for us all when it's done.
-
In terms of the tower view in sim? It's identical (apart from logging in as Tower into ES so you can own runways and edit flight planes). You can configure the placement of the tower cab in FSX (I assume also P3D), but that doesn't matter too much, as long as you can see the runways and manouvering area.
For tower controlling you'll also need to look at your scope in ES and VRC so you can see flight plans filed by pilots, but that's really the only difference. If you didn't have to worry about flight plans, you could just get your own strips and only look at the tower view. -
If you can't solve anything that way, all I could suggest is uninstall both euroscopes, clear out those dirs (should be able to leave the sector files alone), and reinstall 3.2 only, then reapply the beta patch, and see if that makes a difference.
-
Ok, the only thing I can think of is your shortcut for 3.2 is using 3.1d for some reason. I haven't updated es beta in months, but every time I've done it it's worked fine
I assume you still get the same debut output after running 3.2 beta then towerview in vpilot? And that you have restarted all clients since installing the beta and are now not opening 3.1d at all?
-
Ok, and you've copied all those files from that zip and pasted them wherever you installed euroscope 3.2 and overwritten as necessary (not 3.1d, and not wherever your sector files are). The euroscope program files should default to c:/program files or similar, the sector files should default to somewhere in my documents.
-
What beta version are you using. It will say in the zip you downloaded.
-
What beta version are you using? Are you connecting to vatsim with the beta client and NOT 3.1d?
-
No. You can just run 3.2 beta and then vPilot/whatever in towerview mode.
TLDR older versions of Euroscope don't pass on enough information in the correct format to other downstream applications. Newer ones do. So if you connect to VATSIM with most versions of Euroscope 3.2b that is fine, then if run in proxy mode (which you already are, otherwise you would be getting nothing when you try to .towerview) you get the information vpilot needs to display aircraft models (in this case, aircraft type) -
I just went and tested this again with 3.1d to be sure, I get the exact same debug output as you. Download and install the latest beta of 3.2 (although I think any beta from the last two years will work) and that should resolve your issue. You need to use a beta of 3.2, not vanilla 3.2
-
Make sure you've downloaded the most recent/a more recent beta version of Euroscope 3.2. I'm not sure the actual original 3.2 release supports towerview.
In your pilot client (vpilot is fine), once you have typed in .towerview, try typing both .aircraft and .debug, that will give us more useful information to help diagnose. -
I remember helping you out with a swift issue late last year, @Alan Mallows. Not sure if you replied, is your current issue the same one or is it a seperate one?
-
He was just feeling particularly welcoming at the time I think.
Consider yourslf priveliged
-
Right, but the main consideration is what freq people wlll be listening to. In gerneral, when occta people will be tuned to 122.8. Make your calls on whatever freq you like, but most people will go to unicom as default.
Many years of experience, and much wisdom, all of which he was happy to give to me, and to many others here as well.
06OCT | James Hennell
in ATC Feedback
Posted
Yes James, yes!