Jump to content

Nicholas G - 1397820

Members
  • Posts

    368
  • Joined

  • Last visited

  • Days Won

    17

Posts posted by Nicholas G - 1397820

  1. One down, one to go. Might be worth checking other important web apps you use on that install still work as expected, including web browsing. This settings could be there to facilitate some application or another. It could also, less likely, be a result of malware, but either is worth checking. Its possible WPAD services are a fringe case for Swift and it hasn't been programmed to support it.

    Open up swift data (i said swift core erroneously before) and clear out everything in the first tab (named something like model set). Then go to I think the Second tab (haven't got a machine with swift open in front of me, so bear with me). Its the tab that should be listing every single aircraft and model it can find in your XP directory, even if it doesn't know what it is.

    Right click, go to the option that says filter (i think you can also get there with ctrl +f). There's a field call distributor, type bb, a drop down should also appear where you can select BB (can also add x-csl later, but let's keep it simple for now). This will filter out everything but known BB models which will work.

    Then, select everything left (should all have ticks in the db field and an airplane with a small green plus in the mode field), and add to model set through right click menu. Then go back to the first tab, find a button down the bottom right a button that says something like “save ‘xplane’ set”. Click that. Close swift data. This should give you a usable model set for now, then we can sort through any other models you may want to set later.

    If no good, when I have access to a comp with xplane and swift again I'll try and give you a step by step a screenie guide to what I do.

  2. On 26/12/2019 at 4:03 PM, Peter Story said:

    Could be done, the only issues I'm aware of is you don't get a choice of voice and the experience to date has been unreliable in activating the bot voice...and it doesn't work for VRC

    For what it's worth, the voice bot seems to have an aneurysm every second week or so anyway regardless of what software is being used - I generally just type out the ATIS manually for everywhere except Sydney, and even then it still spits the dummy more often than not. For me personally, selecting a different voice from the one we get is much less an issue than that one which appears to mostly be serverside.

    Only real issue is that the generator to which I refer spits out text that isn't understood by whatever VATSIM is using for text to speech. I seem to vaguely remember looking through the files in the Generator at some point (was it using JS?) and some elements seemed to be  'soft' and configurable in the data files, a few others seemed hardcoded, but I never delved in deeply.

    I think most people are really just looking for something that will quickly generate bot readable text based on current METAR and put it in a correct format for our region using the current synthesis system (particularly somewhere with Sydney that often includes a lot of operational info). Everything else is an extra. I'll have a look at the Generator files tomorrow probably and see if it's something that can be easily modified and come back with any results.

    • Thanks 1
  3. Is there any reason we can't just reconfigure Eoin's Generator? It would simply be a matter of changing the items from their shortened versions to human readable versions, and removing all the brackets (though even that is probably not necessary). Not sure how hardcoded all that is, but seems it would potentially be easier than trying to wrangle vATIS  - at the very least almost all of the formatting work for Australian ATIS has been done.

  4. Can you triple confirm you are not using a proxy at all? System pref > Network > Advanced > Proxies > automatic proxy conf. That should be DISABLED. Also, dumb question, but you can browse the internet on that Mac OS install fine, I assume? No other internet related errors?

    As fo the models, it's not enough to point it at the directory. Swift should automatically be able to work out what directory your models are in, but you need to tell it which models to use (not every model in your XP directory can be used for multiplayer aircraft,). You can do this in the setup wizard, but I find it's a bit more transparent if you do this process in swift core. Have you gone into Swift Core at all to build model sets? This guide with screenshots on the swift website may be of assistance.

  5. I mean, you could staff up all 3, people can do what they want between them. Short hop MElbourne to Adelaide return, or they can go YPPH to YPAD, or they can do the mammoth leg if they want to mark the end of the decade. Why not be a little crazy for the last Spilled MRM of the decade (it's not quite end of the decade, not really, but roll with me here :D)

    But if you were going to pick one option, sure, Perth to Adelaide.

    • Like 2
  6. When you set up the mode set, I would recommend using the filters. I haven't been able to flight sim recently, but Swift was my main client and I know when I was using it it would basically cease to function if you fed it uncorellated or invalid models.

    The model set in Swift is basically a handbook used by the sim itself. It looks in this handbook (the model 'set') to find what AI models to display when it encouters certain callsigns and aircraft types on the network. Using model sets allows users to add or remove models they want to see appear online, especially useful if you have 5 versions of one specific livery but only want one to appear.


    Vpilot does most of this automatically (and can be overriden using a specially made file), but Swift asks you to import those models you wish to use. at setup One of Swift's strengths is the consantly update online database that compares unique 'vendor' IDs for specific models with its lists of model 'identifiers' online categorised in all sorts of ways - aircraft type, airline, alliances, even dominant livery colour. This allows the sim to intelligently give a 'close enough' match even when a 100% match can't be made.

    Easiest way around this initial setup learning cliff is to use the filters in swift core. Filter out everything that doesn't have a db entry (that is, everything that isn't recognised by the swift database and therefore swift has no idea what to do with. if it has no db entry there's either a blank or a big fat X there), put it into the model set, make sure no non-db models are in the saved model set for xplane, and you should have something that works. I think you can also click the db column, and it will sort into db ---> non db, so you can just select manually if needed. If you have no 'weird' models in the model set, it should work fine, and I think that might fix your model string problem, which sounds like a generic model set error.

    But in terms of your general qustion - right now AFV is only officially and fully supported (via the standalone client) on Windows. The only pathway to MacOS support at this point is Swift because they have native AFV support in the pipeline (AFV Standalone ONLY works in Windows and will remain so for the moment afaik), but that native support is still in development and not available on the main beta builds. You HAVE to use the alpha builds (0.9.3 and up) in order to use AFV in MacOS, but you may run into other issues becuase you are using alpha software.

    Only other options are using a non-supported method like Parallels or CrossOver (no idea if CrossOver works).Or use Windows.

  7. Hmm, definitely sounds like an issue then on the discord.vatpac side. 

    I expect that the site should be giving you a Discord Invite URL or something similar to connect you to the server (I don't know because I have a seperate issue with SSO currently so I haven't even gotten as far as you :D ). But it doesn't sound like it is (it definitely hasn't connected you if you haven't got the server in your list). 

    Sorry I can't be of anymore help. 

     

    • Thanks 1
  8. 3 hours ago, Tom Grozev said:

    Could you please try again and if it doesn't work let me know the approximate time you made the request. Maybe also try clearing your browser cache.

    Time would have been about the time I made that post. so roughly 7pm AEDT

    Just tried again, got a slightly different error:

     

    Quote
    
    {"request":{"result":"failed","message":"Not allowed by CORS","type":"Error"}}

    I tried clearing cache, no dice. I could try signing out of SSO on VATSIM side and signging back in, but the error seems to be in VATPAC Core, not on the VATSIM SSO side (which works fine, and is handled correctly still on other sites that ask for SSO). The URL seems to have a valid Oauth token in the string, so it's getting something back from Cert?

  9. I seem to be having an issue with permissions. I go to discord.vatpac.org, get as far as confirming my login with VATSIM Cert, then it spits me to :

    dEKAzDg.jpg.7c0659e66790cf0b16d58dc8b43798c4.jpg

     

    I still have the old VATPAC Discord Server in my list on Discord, but only see the welcome channel and announcements. Nothing else. 

  10. The generator should still produce an output that the synthesiser can read, it might just not be understandable to humans :D

    I've experienced again the earlier issue with ATIS tonight on CB_APP. YSCB_ATIS (127.450) is connected, the frequency is set correctly in voice comms, but zero audio plays when I attempt to listen. This is the second time I've noticed the issue on this particular station.

    EDIT: Actually, turns out all the Australian ATIS's were not working (Sydney, Melbourne and Canberra). I did check some other ones through AFV, and had no trouble picking up voice ATIS in the US, Europe and Singapore. Figure it's probably just whatever does our regional voice synthesis.

  11. I've seen this gremlin, no rhyme or reason to it. I've sat on SNO, put an ATIS on one station and had no audio play, then immediately change the ATIS to another aerodrome in Euroscope and listen to the new in AFV, works fine. I don't think the issue is client end - afaik it should just read the text off the station info as long as you have a primary freq set. None of the voice channel stuff in Euroscope should matter now if you are using current AIRAC, cause all of the voicerooms have been stripped from the profiles and nothing audio related is being handled by ES anymore at all except maybe if we can still use Overrides etc in the client (haven't tried yet).

    To confirm it's not some kind of user error, is this happening to you on ANY ATIS, or just a particular one? What happens if you log on ENR somewhere and just try planting exactly the same text but change the aerodrome to something (so YSCB to YMML, etc)

    • Like 2
  12. Ah, cool, I'll give that a go next tme I'm on. Last time I tried ARRS and DEPS it was pronounced oddly, and CAVOK was being pronounced as one word rather than CAV OK, but they're still tweaking. Giving there was no documentation for the initial release of the ATIS functionality, let alone the constant tweaking, it's a little hard to keep up with what works and what doesn't without experimenting. :D

  13. It seems the ATIS reading stuff is now saying the zulu time at the end of the ATIS (at least on Launceston ATIS)? I gather that's going to annoy a lot of divisions which either don't put ATIS time in the ATIS (us) or who put it elsewhere other than at the end (most other jurisdictions). It also appears to be reading the wrong time (was getting 0730z today even though time was actually 0630z)

    EDIT: Also seem to be other new oddities. The input "CLOUD FEW 4 THOUSAND FEET" will read it over the frequency as "CLOUD. FEW CLOUD 4 THOUSAND FEET". I get it interpreting how to say words based on context (A is ay, but Information A is information alfa for example), but wholesale adding words based on context seems excessive and takes the ability away from controllers to actually make their ATIS work according to divisional standards.

  14. I've consistently had this issue on YSSY ATIS. The freq is set correctly, no voice room set, but it doesn't play. Confirmed ATIS is ticked, the correct freq displays on afv-map.vatsim.net but it says (TXT Only). Pilots have confirmed they can get the text ATIS. If I then just go back to YMML ATIS, for example, it works fine. Works without having to go into comms setup. 

    If controllers are using the current sector files and have installed using the Euroscope updater, all the voice rooms should be removed, so that's the easiest way to eliminate that as a potential issue.

  15. There have been numerous instances I've seen since launch where an ATIS will be live but not listenable. You can still get the text, but sometimes voice will just not work. There's no apparent rhyme or reason to when this happens, although they will display on AFV Map as (text) only. There's nothing that can be done client side it seems, because it's some server side thing that reads the text ATIS, not something in ES anymore. So you can set everything up correctly client side, connect the ATIS (no multi playback, XMT an RCV all ticked off but ATIS freq still tuneable), and sometimes it will just not work.

    Not a biggie, I assume it's something that will be worked on, but it has happened, and also seems to occur more often the more active ATIS and active connections there are.

×
×
  • Create New...