[ Closed ] v.3.0 beta 1, 2, 3, 4, 5, 6 public tests (Page 8 of 13)

I hate people crying like a baby and thinking they're always right just because they've posted 590 times and think of theirselves that they're godlike.
Oh @ilankrt, did you think I meant you? That would be funny, but you aren't godlike. Go and report me. I'll find another way into this page - and if I need to hack it I will do so... A webpage without SSL encryption. Haha.

And your typo is crap. The past participle and the simple past form of "to read" are spelled r-e-a-d but pronounced "red".
I think you should carefully watch what your big mouth is blurting out. Just a suggestion.

And by the way: you're completely right about the dry operation weight, that was my mistake!

EDIT: Hacking that page was a bad joke...

@MrGeeBee right. Not more to add. "Dung throwing party"

Beta 4 is posted now. Please use link at first post to download it.

What new:
+ bug fix

Need reinstall it. Not mix with old versions.

Thanks a lot for all your reports (good and not good) - it is very useful info for debug.

I really understand Latin, but you just should keep out of this (by the way closed/ended) argument between me and @ilankrt.
I personally think that JARDesign is doing a good job on developing XP-ACFT and I found a wrong source for information regarding the dry operation weight. If you wanna leave, then do so.

Yep, back to business as usual.
I wanted to make a flight starting at EDDF with beta 4, but this happened (see screenshot):

So, this is not a beta related thing, it occured also in v2. Reloading the complete ACFT helps. Maybe a log.txt. is useful.
I don't consider that as an important bug, but if you should have too much time (I guess your constantly improving your Airbus fleet to make it even better) you could have a closer look.

Hi there!
V3 really looks great! FPS wise, she performs very nicely! The FBW seems to be much improved, only during approach, it became quite sluggish for me on several occasions so far. Especially when there is some crosswind. Then, I needed some serious control input to keep her on the path.
Just a few more observations I’ve made so far:
-Lower ECAM doesn’t change the page automatically, according to the phase of preflight or flight. (engine page when ignition is set to start, wheel page after f/ctrl check and during the taxi phase, no cruise page after take off, etc.)
-Define a waypoint as overfly waypoint doesn’t work. The button on the MCDU is present, but I can’t use it.
-flight plan entering: only one airway - exit waypoint pair can be entered on the airways page, actually it should be possible to create the whole flight plan there before you activate it via TMPY FPLN, and so on...
-on a short base pattern like test circuit, I put in CRZ FL of 90 on the INIT A page and dialed in the altitude on the FCU, both was accepted. During the flight, the plane levelled off at FL70 and accelerated to 293 IAS. On the INIT page, the CRZ ALT had reset itself to FL70 as well. I could manually overwrite it and the aircraft climbed to FL90. I could replicate this behaviour multiple times
-windshield is blocked by a magenta curtain if rain effect is turned on

Not sure which of these points are already known and possibly being worked on, I just wanted to give a quick feedback. Keep up the great work! :-)

Hi
I noticed something that's seem not present in V2 :
In the MCDU on the F-PLN page we have waypoint and pseudo waypoint for exemple (LIM) (T/D) (DECEL) etc.
It appears to me that when you reach the last waypoint before a pseudo waypoint this pseudo waypoint disappear from the F-PLN page.
I am pretty sure of this because I used to look at this to know how many NM I have before engaging the descent at the TOD pseudo waypoint.

Also if I have understand correctly, the Approche phase should engage automatically when you reach the (DECEL) pseudo waypoint, and as it has disappear this did not happen.
On the EGLL - LSZH flight I made today the decelerate phase did not engage even when I engaged it manually and the speed brakes where inoperative. The plane catch the G/S but I was too fast so I use the flap to slow down the plane with of course numerous overspeed alert as I deploys the flaps at a speed too high. So I put the auto brake at max, touchdown at 170 knts, engage the reverse to finally succeed with my landing, but with brakes red hot.

As was the case in older versions of both the A330 and the A320, the MCDU does not include all the waypoints that belong to an ILS. The ILS of KDTW04R has 8 waypoints. The JAR A330 V3 beta 4 only includes 2 of them i.e. JELLY and ETALE.

Also, the ILS of KMCO 17L starts with KAKEY and HERVI; the JAR implementation does not include them. They're not to be found.

As I mentioned: this has always been the case. Can it be fixed?

I created a flightplan for a trip from PAJN - PHNL, this loads perfectly in the JD A320 - but not in the current A330 b4 where I get an error message.  I have attached the  flightplan file so that you can try this.

On a flight from KDTW04R to KBOS22L, the lateral RNP got worse and could not be altered in the FMGS. The aircraft was not able to stay on the NAV line (see screenshot). Also a DIR TO was not possible, giving the feedback "MISSED DATA".

The beta 4 of the V3 corrected itself after 20 - 30 minutes. The NAV line got captured again.

I noticed this: The pitch of the aircraft changes abruptly. There's no subtle change between holding steady at an altitude restriction and the subsequent descent to the next waypoint. It's a split second thing and it feels uncomfortable.

Thank you very much JAR for your work! I'm really glad to see the A332 evolving.

I cannot delete the Route discontinuity after selecting a departure runway, no sid, no transition, see pics.
The message "not allowed" makes sense if there's no runway selected. but with one selected I should be able to clear the DISCO.

Luke

EDIT: the NAV page tune for ILS and VOR and it's course works now,very nice!