4 hours ago, BrammyH said:

Search for "v2" and it will be there

wish everything is so easy. thx

Well, he's giving it another try

 

10 minutes ago, Tuskin38 said:

Well, he's giving it another try

 

Let's see if it turns in circles again...

Maybe I just haven't been doing very complicated flights, but the three flights I've done so far have been fine flying wise.

I have experienced the MCDU/Screen freezing, and some airports not auto filling the ILS frequency. But the actual flying, I've had no issue with the aircraft following the plan.

For those also on the beta, can you go to LEMD and see if trying to select a departure runway also freezes your aircraft?

Edited March 25, 20242 yr by Tuskin38

1 hour ago, Tuskin38 said:

Well, he's giving it another try

Didn’t see that coming. His closing remarks:

Quote

You can see with a little bit of fiddling with it, with a little bit of um… pilot intervention. Well a little bit uh is kind of an understatement. But with quite a bit of pilot intervention it is sort of flyable. 

 

confirmed on the ini Discord, the reason they didn't include the terrain radar on the A320N is because it's too performance heavy

There were about 50 posts in his last video, telling him how to get the plane working with VATSIM.   His response was "I shouldn't have to press that button".  😄   He's obviously decided to give it another go.....

13 minutes ago, JYW said:

There were about 50 posts in his last video, telling him how to get the plane working with VATSIM.   His response was "I shouldn't have to press that button".  😄   He's obviously decided to give it another go.....

It was a video. Not a live stream. Hindsight is always easy. The problem is: He is right. It's just wrong what they implemented, let alone that no other plane in MSFS needs a fictional button to be pressed to be able to contact VATSIM. Of course inibuilds would have known that, had they done testing.
I'll give you an example: Your A320 doesn't capture the glideslope and you don't know why. It turns out you have to open the cockpit door to capture the glideslope. Is the error on your side now?
Please don't let them get away with such nonsense.

Quote

I do think some people are missing the point of a beta release. I would point out that the neo V2 went through our entire testing process, along with Microsoft's, ours at least including pilots from across the aviation spectrum including pilots typed on the real thing. The purpose of a beta is to get a wider testing input. Its not for people to fly the finished product "early"; it is for people to provide their feedback on issues they're seeing that didn't crop up during internal testings. So for those that are engaging in the beta testing process in good faith and providing constructive feedback and engaging with us, I thank you.

We have been working through the weekend to resolve appropriate issues. I cannot speak on the timing of release, as that is down to Microsoft

 

 

Josh

inibuilds Community Manager

From their discord. I totally agree with what he's saying. People are missing the point and aren't even asking if issues will be fixed.

6 minutes ago, Krakin said:

From their discord. I totally agree with what he's saying. People are missing the point and aren't even asking if issues will be fixed.

BS. SU15 will release in a few days. The A320neo will be just the same on full release of SU15! Only because it appears two days before the end of the Su15 beta doesn't mean it's a beta release and they can get away with anything.

46 minutes ago, Fiorentoni said:

BS. SU15 will release in a few days. The A320neo will be just the same on full release of SU15! Only because it appears two days before the end of the Su15 beta doesn't mean it's a beta release and they can get away with anything.

Spoke too soon there, bud. SU15 is now releasing sometime in April.

https://forums.flightsimulator.com/t/sim-update-15-delayed/635719?fbclid=IwAR0W8FuCLHY-_x_lgjb2U5wrUCri78-MX-cyVXeyirHOC68opcDSxEge2uU

1 hour ago, Krakin said:

From their discord. I totally agree with what he's saying. People are missing the point and aren't even asking if issues will be fixed.

and this is why first impression videos are pointless during a beta. Helps no developer by complaining constantly via a video instead of communicating directly.

Edited March 25, 20242 yr by carlanthony24

2 hours ago, Fiorentoni said:

It was a video. Not a live stream. Hindsight is always easy. The problem is: He is right. It's just wrong what they implemented, let alone that no other plane in MSFS needs a fictional button to be pressed to be able to contact VATSIM. Of course inibuilds would have known that, had they done testing.
I'll give you an example: Your A320 doesn't capture the glideslope and you don't know why. It turns out you have to open the cockpit door to capture the glideslope. Is the error on your side now?
Please don't let them get away with such nonsense.

They always said it was wrong they just had to do it that way because of MSFS default ATC or what ever. If I remember correctly they were pointing them to the MSFS forum to discuss it since it out of their hands. You trying to compare a door being open to make a glideslope work is nonsense. 9 out of 10 times its user error who can't capture the glide and don't check the box properly or seem to use charts to help them out. Evidently saw this last couple of days in the server, on a flight I am on currently people not even using charts, asking a busy ground for help at a busy airport. when it does goes wrong they spend time just complaining that it did not capture, you should be helping me instead of flying the aircraft or even taxiing. Aviate Navigate Communicate. 

Edited March 25, 20242 yr by carlanthony24