Jump to content

Nabeel

Administrators
  • Posts

    8141
  • Joined

  • Last visited

  • Days Won

    38

Posts posted by Nabeel

  1. The entire thing is now working flawlessly. I fixed a few bugs, and I will make sure this is solid, and release it either on Friday or over the weekend.

    A few notes:

    Pilot Number: FULL number, INCLUDING the code (so VMA434). This is because FSACARS does not send me the CompanyICAO field, only the pilot ID field. I need both to lookup who you are.

    Flight IATA: FULL number, INCLUDING the code (VMA654654). I can't look up a route without that code. The CompanyICAO field is not sent to me here either, and I don't know what airline a route belongs to without the code.

    Registration: REQUIRED, or else I don't know what aircraft you used. Now that there are multiple aircraft of the same type, I can only look up the registration number reliably.

    To send the PIREP, you click "Stop Log". It will ask to Accept or Decline. Click Accept. Then, click the "Flight Log" tab, then click "Send Log". It will ask to confirm; say yes, and it will send.

    I'll have a patch over the weekend to fix errors which prevent the flights from showing, and to upload the code to use the registration data, and properly parse the Flight IATA. If you forget the code, I can "guess" which airline is it, but if it doesn't find the correct flight, then I can't do anything about it. There will be a "Edit PIREP" option, but it might not make this weekend's release, most probably the next one after (depends how much time I have this week).

    Also, FSACARS loves to spontaneously stop working (properly). Deleting the fsacars.ini file and reinstalling (the latest 4.0.15 version) fixes the problems. You NEED to use the 4.0.15 because they have changed how data is send between the versions. Their documentation doesn't match either version, so I've picked apart how they send it in 4.0.15 since it is the latest.

  2. Hey,

    A few critical patches in this one, run the update.php

    I had stopped manually doing patches, and replaced it with a build script (automatically checking versions, patching files, and just using test-cases), leaving bugs in there for the last update. There were a few database changes as well, so this was not completely checked in the auto build. The first releases were tight in how they handled data, but now with all your feedback, that needs to be loosened a bit, so it's just going through growing pains...

    Stay tuned this week and next since I'm issuing patches fairly quickly with bug fixes as soon as I find them. There's going to be quite a bit more Q&A from now on.

    Sorry about all this trouble.

  3. You can define it as icao or iata, it doesn't have to be either. When you enter a flight number or airline code, you can enter it either way. I'm not expecting a ICAO or IATA. That's much more confusing.

    In the flight IATA field it is the easier, just enter the airline code (icao or iata, however it is entered in phpvms), and then the flight number. It's written in the documentation clearly.

  4. I changed the page encoding to ISO-8859-1 (in Firefox, goto View->Character Encoding). Try changing the meta encoding from UTF-8 to that, see if it works. I don't think I have a character encoding specified in the admin skin, if not, try setting it in admin/lib/layout/header.tpl, see if that works.

    The reason I did not set an encoding was because it changes, but I'll add a config option to change this, and have it set to that

  5. Well you're supposed to add the code in the IATA field, since there are multiple airlines. I use the code in that field to map it to a scheduled flight. It's more reliable. But can you try blanking the CompanyICAO and adding the code to the IATA field? Does that work as well?

  6. If you're having problems with FSACARS (including double'd flight codes (VMAVMA1100)), you need to create a log and send it to me:

    In version 1.1.430 and later, in your local.config.php, there is a value:

    Config::Set('ACARS_DEBUG', false);

    Set this to true, and also, create a "log.txt" in /core/modules/ACARS. Make this 777. After a flight, post that file to this page (in a zip file, as an attachment)

  7. Ok. Thanks for the information. I think it is to difficult to use this system. When I, a virtual pilot with over 1000 logged hours can register a flight with errors and I'm not able to change it afterwards. Strange system.

    What about new pilots and unexperienced pilots, do you really think they can use this system without submitting errors? Don't think so. I think you should work towards that the bids imports directly into FSAcars, and then you take down the perecent of error submittings.

    Difficult to submit a PIREP? Or difficult to use FSACARS?

    I have no control over FSACARS or importing data into FSACARS. If they don't have functionality to import a bid or even a flight, then I have no way of doing it. It does some things in a strange way, so the instructions are to make sure errors are minimized, and to work around some of those problems.

    What do you mean by change it afterwards?

×
×
  • Create New...