2 hours ago, B777ER said:

Someone in Discord said the LNAV still not working g correctly in 1.05. 

I intentionally saved the files from the community folder when updating, since I’ve had so many issues since release but just love the plane, so I’m back on 1.0.3. Looking forward to this being fixed, but I know from years of this not to be 100% trusting of a next day patch that’s supposed to fix such a critical issue (and one the devs apparently can’t recreate consistently). 

LNAV worked for me with 1.0.5, MTPP to KMIA, SAVA1G SID out of Port-au-Prince and VIICE2 STAR into KMIA, ILS27

I did notice I needed more N1 on short final than expected, but it's possible there was a light tailwind and I wasn't paying attention.  I also forgot to enable my LatinVFR KMIA scenery.  I just didn't have it together tonight.  At least the A300 performed well.

One of the developers said the following in Discord regarding this LNAV issue:

correct, but we have seen instances of errors with the navigraph package so we advise users to stick with the default data if possible. The default data is updated in realtime with the AIRAC cycle so while not as robust, it's still current

I’ve asked for the steps to get a refund. I think it’s absurd that all other developers of high end aircraft can use Navigraph without issue but iniBuilds cannot. I also think it’s absolutely necessary for them to put a disclaimer on their A300 sales page that Navigraph sim data will cause issues if used. I guess if this is their stance then I cannot purchase any more aircraft from them. I will hopefully get a refund for this as I am not uninstalling Navigraph for one plane.

Edited February 5, 20242 yr by B777ER

31 minutes ago, B777ER said:

One of the developers said the following in Discord regarding this LNAV issue:

correct, but we have seen instances of errors with the navigraph package so we advise users to stick with the default data if possible. The default data is updated in realtime with the AIRAC cycle so while not as robust, it's still current

I’ve asked for the steps to get a refund. I think it’s absurd that all other developers of high end aircraft can use Navigraph without issue but iniBuilds cannot. I also think it’s absolutely necessary for them to put a disclaimer on their A300 sales page that Navigraph sim data will cause issues if used. I guess if this is their stance then I cannot purchase any more aircraft from them. I will hopefully get a refund for this as I am not uninstalling Navigraph for one plane.

Did they say they won't try to fix it?

1 hour ago, B777ER said:

but we have seen instances of errors with the navigraph package so we advise users to stick with the default data

Now, they have kinda stepped back that statement. Not completely proven.

LNAV worked for me but VNAV or “profile” was doing some odd things.

1 hour ago, Adrian123 said:

Now, they have kinda stepped back that statement. Not completely proven.

Saw that. For those not on Discord:

further clarification that using navigraph data is totally ok. That is our official position. 

10 hours ago, Mace said:

LNAV worked for me with 1.0.5, MTPP to KMIA, SAVA1G SID out of Port-au-Prince and VIICE2 STAR into KMIA, ILS27

I did notice I needed more N1 on short final than expected, but it's possible there was a light tailwind and I wasn't paying attention.  I also forgot to enable my LatinVFR KMIA scenery.  I just didn't have it together tonight.  At least the A300 performed well.

That's a pilot nav departure though. Did you try going direct to any fix on the flight plan? That's been the issue.

 

I'm reticent to update given apparently people are still having issues, and 1.0.3 is doing just fine over here.

19 minutes ago, mspencer said:

That's a pilot nav departure though. Did you try going direct to any fix on the flight plan? That's been the issue.

 

I'm reticent to update given apparently people are still having issues, and 1.0.3 is doing just fine over here.

In a nutshell, no, with 1.0.5 I have not (yet) done a direct-to.  Instead, on the SAVA1G I used HDG mode at one point to orient the aircraft to where I felt I could safely turn on the autopilot (waiting to enter NAV mode).

So, in other words, what you're saying is that if I had instead opted to do a direct-to one of my uproute waypoints during my climbout, the plane would have bugged out?

26 minutes ago, Mace said:

In a nutshell, no, with 1.0.5 I have not (yet) done a direct-to.  Instead, on the SAVA1G I used HDG mode at one point to orient the aircraft to where I felt I could safely turn on the autopilot (waiting to enter NAV mode).

So, in other words, what you're saying is that if I had instead opted to do a direct-to one of my uproute waypoints during my climbout, the plane would have bugged out?

At least in 1.0.4, yes, which was why people were reporting it worked fine for them, but others had issues.

So far I haven't heard much about whether 1.0.5 has fixed the issue or if it's still a problem. Mixed reports.

Not sure if this was posted before, but caught up on Into the Blue's review of the A300, always love his content.

His final thoughts start here: https://youtu.be/oKx0KkplCiA?t=4018 .. keep in mind it's from a month ago so before the fixes/updates. Some of his quotes:
- externally looks great, modelling depth is excellent, cockpit modelling excellent, nice texures & materials look realistic
- one of the most detailed passenger cabins
- pretty decent flight model overall, taxis nicely, maintaining directional control is easy, easy to trim for pitch
- hand flying feels nice and pretty stable
- one of ini's nicer flight models to date
- very much on par with the competition
- systems wise is very good, depth is there for a study level aircraft
- lnav pretty flawless, vnav is a mixed bag
- failure systems: would be good to flesh out more
 

 

Edited February 5, 20242 yr by lwt1971

7 hours ago, mspencer said:

At least in 1.0.4, yes, which was why people were reporting it worked fine for them, but others had issues.

So far I haven't heard much about whether 1.0.5 has fixed the issue or if it's still a problem. Mixed reports.

I have a report, v1.0.5

So I flew the GLADZ2 departure out of KMIA, bound for MMMX.   I do use Navigraph.  I decided to test the DIR TO function with this SID.  The SID calls for GLADZ-->MARCI-->SHAQQ.  I decided to save a little time/virtual fuel and skip MARCI, so after passing GLADZ I inputted DIR to SHAQQ and inserted.  Plane initiated the turn and performed as expected.

That wasn't a very radical course change, but, it worked, at least for me on that particular SID.

Then later on after passing SHAQQ and nearing NATLE I decided to test it again, by skipping the next three waypoints, NATLE, BUUOY and MINOW...by going direct to CCUDA.  Once again this worked perfectly, although it wasn't a big turn either.

If you have 1.0.3 I'd keep it around though, at least until things shake out a bit as 1.0.3 worked pretty well for me and I am good at breaking things.  I wish I would have kept 1.0.3 but I'm not smart enough to have done that I guess.  Anyway, I'll keep flying 1.0.5 and try to break it as well.

this really stinks, the plane flies well with 1..0.3, now u give updates, and really messes up a beautiful plane.  I'm starting to think with Inibuilds they rush  to release products just to make some money. I got burned with KJFK, like so many others, this does not set a good image or brand for this developer.  Would PMDG put out a plane with such major issues, that it can't follow a course  ? Never Ever.!!!

 

11 hours ago, Sunshine13 said:

this really stinks, the plane flies well with 1..0.3, now u give updates, and really messes up a beautiful plane.  I'm starting to think with Inibuilds they rush  to release products just to make some money. I got burned with KJFK, like so many others, this does not set a good image or brand for this developer.  Would PMDG put out a plane with such major issues, that it can't follow a course  ? Never Ever.!!!

 

V1.0.5 was a hotfix and done over the weekend, so tell me which other Devs are working over the weekend - and have a look at how many updates was out until now so they do a lot to fix all the bad stuff for us the costumers..

Shure for first release the plane was rushed out, probably because of Christmas..

But at the moment they are always hard at work on bugs, never seen it like this from other developers so what you want more ??

The "Fall out of the sky" bug is still there but over the forum inibuilds say they working hard to investgate this somehow critical bug and hope they get over it until V.1.0.6 or latest for V1.0.7 update, so my hope is big for this to get fixed for ever and all the time !!

cheers 😉

 

Edited February 6, 20242 yr by pmplayer

23 minutes ago, pmplayer said:

V1.0.5 was a hotfix and done over the weekend, so tell me which other Devs are working over the weekend - and have a look at how many updates was out until now so they do a lot to fix all the bad stuff for us the costumers..

Shure for first release the plane was rushed out, probably because of Christmas..

But at the moment they are always hard at work on bugs, never seen it like this from other developers so what you want more ??

The "Fall out of the sky" bug is still there but over the forum inibuilds say they working hard to investgate this somehow critical bug and hope they get over it until V.1.0.6 or latest for V1.0.7 update, so my hope is big for this to get fixed for ever and all the time !!

cheers 😉

 

the "fall out of the sky" and the "CTD at start up" reports have completely disappear after the suggestion of deleting all the wasm files in the package folder of the Aircraft. by doing that the sim will regenerate those wasm files again with the latest version.

for some reason it was not automatically done before, but I have been doing the same for every aircraft I own after every update. never had a CTD.

https://discord.com/channels/535246634448191499/1190091090892705802/1203099790355734589

Edited February 6, 20242 yr by ttbq1