Jump to content

pbrad74

Member
  • Posts

    28
  • Joined

  • Last visited

Posts posted by pbrad74

  1. Quote

    The MCDU SID/STAR restrictions are shown correctly, but the next waypoint altitude would be very weird and not logical at all

    The most recent version fixed this problem for me. I've done at least a dozen flights since v1.0.9 was released and is performing much better. Do you have the latest version or did you buy from the MS Marketplace?

    • iniBuilds 1
  2. Figured I would make another post about this. After filling out INI A, then FPL pages, the SID's and STAR's have the correct speed and altitude constraints. However, after completing INIT B page, altitude assignments in between the constraints are crazy. See below. There is an altitude restriction of FL220, then it wants me to climb again before reaching the next altitude restriction of FL140. Not sure if iniBuilds is aware of this or not.

    Microsoft Flight Simulator Screenshot 2024.02.24 - 15.23.38.13.png

  3. 5 hours ago, Azlog said:

    I should probably have clarified that I’m on Xbox. I forget that the builds of the aircraft are different between the two platforms

    I might be mistaken but, the most current version for xbox hasn't even been released yet, that would make it a MS issue. As PC users who bought the aircraft directly from iniBuilds and not the marketplace, we get the most current version immediately upon release. Marketplace users have to wait until Microsoft decides to update the marketplace. Xbox version is V1.0.7, check to see which you have.

  4. Gobbly gook, nice! Didn't think anyone used that term besides me and Matthew Colville. Yes, I am using Navigraph and the current AIRAC 2402 cycle. I haven't done a flight with the A300 stateside in quite some time though so I will try tomorrow and see how that works. It might just be messed up for that region? I don't know, just taking a guess at it.

  5. For the TOGA:

    Just assign to whatever button you like. Long press sets TOGA and short press disconnects auto throttle.

    TOGA.jpg

  6. spad.next can be difficult to get around. Couple of hints: watch some video tutorials on youtube by LesOreilly. If asking questions, be specific, there are a couple of really grumpy SME's on Discord that seem to dislike questions but most everyone else is friendly.

    On the left hand side of SPAD.neXt, click on the profiles icon, then click on ONLINE PROFILES. Search "A300" without the quotes and you'll see results for the A300. The profile by .errandil is pretty good. That's the one I built mine off of.

    Lastly, for AP disconnect:

     

    AP disconnect.jpg

  7. 1 hour ago, Crabby said:

    Have you flown this?  If you have, does the aircraft follow those altitudes in Prof mode?  If you have not flow it, see if they change in the course of the flight.  

    Yes, I have flown it multiple times as it is a scheduled route for me and flying it right now. Indeed, in Prof mode, the aircraft will follow those altitudes. So I have to take it out of Prof mode. If I change the altitudes in the MCDU, sometimes it will follow and sometimes not. I don't know if this is an error with simbrief or an error with iniBuilds.

  8. Im thinking this must be an iniBuilds problem as I have not had this issue with other aircraft. I just loaded up another flight and still having problems where I have two waypoints with mandatory altitude restrictions with waypoints between those two points that have much higher altitudes assigned. This isn't making any sense. It's always happening with  STAR's. SID's and the rest of the route is as it should be.

  9. Here is what I am talking about. You can see that FM758 is at 9000, not above or below and FM764 is at 9000 as well. The waypoints in-between in the MCDU are somewhere above 9000, can't remember. But similar to what I described in the post above. So my question is, is this simbrief's fault, something I'm doing wrong, or is it the A300 itself that is the problem?

    Desktop Screenshot 2024.02.24 - 08.51.13.58.png

  10. I did a flight today to LTFM with INBE2B arrival. I loaded my flight plan from simbrief into the MCDU through the ACARS option. At FM758 there is an altitude restriction of 9000, then the next flight restriction is at FM764 at 9000 also. The question is, why does the MCDU automatically assign higher altitudes in-between those two flight restrictions? Like 9700 ft then to 10200 ft? Is it normal to have to go through and change each waypoint in the MCDU?

  11. Not sure if this is just user error or what, but I cannot seem to get any tone (NDB station morse identifier) from any of the NDB's that I've tuned in. Well, this goes for ILS too, haven't tried VOR's yet. 

    My steps taken:

    1 Tune the NDB on ADF panel.

    2 TFR switch to correct ADF

    3 Set Tone to on

    I have also tried pulling the #1 ADF knob to up position and rotating that knob fully closck-wise.

     

    So, is this an error on my part is is it not yet functional?

     

  12. Yes, I have to agree here. I will never buy from them again unless it's absolutely necessary. If possible, though highly unlikely, see if MS will do a refund. If so, come back and buy directly through iniBuilds. I hope it works out for you as the A300 is my #1 right now.

    • Like 1
  13. On 1/24/2024 at 5:43 AM, allexsaraujo said:

    The performance of this particular aircraft is terribly poor. It's a shame an aircraft of this price comes with such a problem that makes it impossible to fly. Frankly, it's embarrassing for a company like this.

    What's embarrassing is for someone to make a statement like this. If everyone was having this issue, then yes, I could understand that statement. But as I am running this on an old laptop, see above post for specs, and I am having nothing but fun with it. Not to mention how fast the devs were with the most recent set of patches. You need to check your settings, in sim and graphics, especially when flying near big cities and extremely detailed airports. Tons of videos on YT.

    • Like 2
×
×
  • Create New...