301 Reply by Bruns (edited by Bruns 2017-03-26 17:35:40)

  • Bruns
  • Member
  • Offline
  • Registered: 2017-01-20
  • Posts: 53

Re: ver.3.0 beta 2,3,4,5,6,7 for X-Plane 11

J.A.Romanov wrote:
Bruns wrote:

Also I found bug. I was flying from EDDF to LIPZ. Total distance 417nm. I tried to set FL340 but it automaticly just got into FL330 and there was text "new crz lvl" I wasn't able to get it higher than FL330

This is not bug. Real aircraft fork with the same way on lastest MCDU. Aircraft know DEP/ARR dist and trying  to build vertical profile - to get TOC and TOD. If your CRZ too hight for this distance - acf try to decrease CRZ FL to make vert profile normal.

As example if your lateral dist like 20 NM and you enter FL390, acf will recalculate it.

Anyway, you may turn On vertical profile using MCDU MENU and look at profile situation.

Well logics is there but implemention has to be bugged. First of all route is 400+ nm. There was over 100nm in cruise level 340. Instead it gave me FL180 at first which is way too low for such a trip.

To user ilankrt your description about flight levels to different directions is true (thanks for info). But does not explain that exaclty same thing was on my return trip (from Venice to Frankfurt). I entered FL340 and it was automatically lowered to FL330 so there has to be a bug and not a feature. And once again I would have well over 100+ nm at FL340 so telling me that flight level is too high for distance is not true.

I never had these problems before latest update of A320. So if you are developing something on FMC it has to be a bug even the idea behind feature might be correct.

302 Reply by Killerofwar

  • Killerofwar
  • Member
  • Offline
  • Registered: 2015-09-10
  • Posts: 63

Re: ver.3.0 beta 2,3,4,5,6,7 for X-Plane 11

Bruns wrote:
J.A.Romanov wrote:
Bruns wrote:

Also I found bug. I was flying from EDDF to LIPZ. Total distance 417nm. I tried to set FL340 but it automaticly just got into FL330 and there was text "new crz lvl" I wasn't able to get it higher than FL330

This is not bug. Real aircraft fork with the same way on lastest MCDU. Aircraft know DEP/ARR dist and trying  to build vertical profile - to get TOC and TOD. If your CRZ too hight for this distance - acf try to decrease CRZ FL to make vert profile normal.

As example if your lateral dist like 20 NM and you enter FL390, acf will recalculate it.

Anyway, you may turn On vertical profile using MCDU MENU and look at profile situation.

Well logics is there but implemention has to be bugged. First of all route is 400+ nm. There was over 100nm in cruise level 340. Instead it gave me FL180 at first which is way too low for such a trip.

To user ilankrt your description about flight levels to different directions is true (thanks for info). But does not explain that exaclty same thing was on my return trip (from Venice to Frankfurt). I entered FL340 and it was automatically lowered to FL330 so there has to be a bug and not a feature. And once again I would have well over 100+ nm at FL340 so telling me that flight level is too high for distance is not true.

I never had these problems before latest update of A320. So if you are developing something on FMC it has to be a bug even the idea behind feature might be correct.

Have you tried increasing cost index (as I posted earlier)? This fixed the issue for me.

303 Reply by dimkzr (edited by dimkzr 2017-03-26 22:02:58)

  • dimkzr
  • dimkzr
  • Member
  • Offline
  • Registered: 2017-03-20
  • Posts: 65

Re: ver.3.0 beta 2,3,4,5,6,7 for X-Plane 11

Killerofwar,

I've tried Bruns' route with the same results (FL180 instead of 340) and I'm always using either 30 or 50 CI. Even if it is a part of "weird and wonderful Airbus logic", how do you explain the fact it accepted 340 after I simply re-entered it?

Quite often FMC offered me complete nonsense - like FL020 for 600+nm flights. That's why I began to enter CRZ LVL at the very last step: it's still buggy and incorrect according to every A320 FCOM I know, but at least it works, kinda.

It looks like FMC can't properly calculate VNAV path based solely on FROM/TO fields, and require whole flight path and other data entered beforehand. And even then it's hit-and-miss.

So Mr. Romanov, like Bruns said: "it has to be a bug even [if] the idea behind feature might be correct".

304 Reply by rajo

  • rajo
  • Member
  • Offline
  • Registered: 2015-04-24
  • Posts: 25

Re: ver.3.0 beta 2,3,4,5,6,7 for X-Plane 11

CTD short After T/D while requesting vectors in x-life atc

Post's attachments

Attachment icon LSZHEDDL.txt 230 b, 188 downloads since 2017-03-26 

Attachment icon X-Plane_2017-03-27-012829_rajo24.crash 75.7 kb, 201 downloads since 2017-03-26 

iMacPro, xplane11, ToLiss A319/A321, FF A320/A350, JD A320/A330/AN148, Carenado DO228/B1900/PC12/SR22/BE35-REP/PA46, Alabeo M20R/C177, RW-Design DHC6/A330, dmax P92/Blackshape Prime, aerobask DA42/DA62/EA55, Heinz Comanche 250, JRollon CRJ200/F260-REP, STMA DA40/DHC3, xhangar DA20, FlyJSim Q400 Legacy, LES 340A, Thranda-Kodiak-Quest-REP

305 Reply by Vertical807

  • Vertical807
  • New member
  • Offline
  • Registered: 2017-03-27
  • Posts: 3

Re: ver.3.0 beta 2,3,4,5,6,7 for X-Plane 11

Is anyone having trouble with the APU just randomly shutting off?

I'm following proper procedure:

1. GND PWR ON
2. BAT 1 & 2
3. EXT PWR ON
4. APU & APU START On

Then, when about a minute after I disconnect EXT PWR the APU just randomly shuts off.

306 Reply by sandmantt

  • sandmantt
  • New member
  • Offline
  • Registered: 2017-03-27
  • Posts: 1

Re: ver.3.0 beta 2,3,4,5,6,7 for X-Plane 11

Is anyone else blacking out? Around FL20 I started to black out, no warnings for cabin pressure. It's set to auto. I even went and I did the reset on all systems in the x plane menu but no results.

307 Reply by dimkzr (edited by dimkzr 2017-03-27 10:08:41)

  • dimkzr
  • dimkzr
  • Member
  • Offline
  • Registered: 2017-03-20
  • Posts: 65

Re: ver.3.0 beta 2,3,4,5,6,7 for X-Plane 11

sandmantt, no warnings on ECAM? Both Packs and Eng.Bleeds on? Cabin press "mode sel" on auto (no light)?

308 Reply by Bruns

  • Bruns
  • Member
  • Offline
  • Registered: 2017-01-20
  • Posts: 53

Re: ver.3.0 beta 2,3,4,5,6,7 for X-Plane 11

dimkzr wrote:

Killerofwar,

I've tried Bruns' route with the same results (FL180 instead of 340) and I'm always using either 30 or 50 CI. Even if it is a part of "weird and wonderful Airbus logic", how do you explain the fact it accepted 340 after I simply re-entered it?

Quite often FMC offered me complete nonsense - like FL020 for 600+nm flights. That's why I began to enter CRZ LVL at the very last step: it's still buggy and incorrect according to every A320 FCOM I know, but at least it works, kinda.

It looks like FMC can't properly calculate VNAV path based solely on FROM/TO fields, and require whole flight path and other data entered beforehand. And even then it's hit-and-miss.

So Mr. Romanov, like Bruns said: "it has to be a bug even [if] the idea behind feature might be correct".

Yeh I've tried cost index change as well. I usually always use company routes so plan is there when I enter my flight level. And happens to be true that with 2-3 tries it finally puts desired altitude.

Another thing I've told many times but not got single answer is IRS align time. Well it is way too fast to be real. It takes maybe 1-2 mins to align. Still timer on upper ECAM always starts from 7min. So usually at the point when IRS is "aligned" upper ECAM still shows 4-5min left in timer.

Also I want to ask about weather radar and terrain on nd features? At least I've not even once seen anything on weather radar. Also terr on nd seem to work sometimes and sometimes it don't?

I don't want to seem like unsatisfied customer. I do love this aircraft and fly it most of my flights. I just think good response will help development. Or at least I hope our comments will be noted.

309 Reply by Totti

  • Totti
  • Member
  • Offline
  • Registered: 2016-12-25
  • Posts: 23

Re: ver.3.0 beta 2,3,4,5,6,7 for X-Plane 11

crisk73 wrote:
Totti wrote:

I checked the dataref for AP1. It's the same in 330 and 320. In 330 it works for me. But in 320 the dataref value doesn't switch from 0 to 1.

Reinstall the plane or delete xp11 prefs. For me AP is working fine with pb17.


I deleted my logitech joystick, because I have read, that Laminar changed something with it. I configured it new and now it works.

310 Reply by dimkzr (edited by dimkzr 2017-03-27 10:58:00)

  • dimkzr
  • dimkzr
  • Member
  • Offline
  • Registered: 2017-03-20
  • Posts: 65

Re: ver.3.0 beta 2,3,4,5,6,7 for X-Plane 11

Crash while taxiing for take-off.
XP11pb17, JAR beta 7
EGPH-EHAM
Log:

https://drive.google.com/open?id=0B-5ha … UJyMEMzOUE

311 Reply by FIREBLADE103

  • FIREBLADE103
  • New member
  • Offline
  • Registered: 2016-01-20
  • Posts: 4

Re: ver.3.0 beta 2,3,4,5,6,7 for X-Plane 11

I'm getting lines going across the cockpit windows from the external view of the beta 7 aircraft... has this been recognised by Jar?

312 Reply by ilankrt

  • ilankrt
  • Member
  • Offline
  • Registered: 2015-10-20
  • Posts: 772

Re: ver.3.0 beta 2,3,4,5,6,7 for X-Plane 11

Is anyone having trouble with the APU just randomly shutting off?

I'm following proper procedure:

1. GND PWR ON
2. BAT 1 & 2
3. EXT PWR ON

4 PUMPS on - you need fuel for APU ! (The left fuel feed line supplies the APU in real aircraft, I didn't try out how it works in the JARA320 model)

4. APU & APU START On

5 APU BLEED on
6 PACKS off

X-Plane 11.30r3 | iMac27 OSX Mojave 14.10.4, | Samsung ultra-wide screen 49-inch | Saitek equipment | MFG pedals |Gladiator Joystick | Plugins: GndHandling, RWC, SMP, SoundM, X-Life, BetterPushback, AutoGate, SoundMaxx, X-ATC-chatter, X-Camera | iPad 12.9, iPad Air 9.7  | Airliner: JAR A320/A330, FF A350XWB, FF B767, SSG B747-8 inter, Epic1000 new, TBM900  http://ilankrt1.blogspot.co.il

313 Reply by Vertical807

  • Vertical807
  • New member
  • Offline
  • Registered: 2017-03-27
  • Posts: 3

Re: ver.3.0 beta 2,3,4,5,6,7 for X-Plane 11

ilankrt wrote:

Is anyone having trouble with the APU just randomly shutting off?

I'm following proper procedure:

1. GND PWR ON
2. BAT 1 & 2
3. EXT PWR ON

4 PUMPS on - you need fuel for APU ! (The left fuel feed line supplies the APU in real aircraft, I didn't try out how it works in the JARA320 model)

4. APU & APU START On

5 APU BLEED on
6 PACKS off




I did try that though hmm, I have 9500kg of fuel on board too. Like it just shuts off, I'll try a re-install.

314 Reply by dimkzr (edited by dimkzr 2017-03-28 01:46:35)

  • dimkzr
  • dimkzr
  • Member
  • Offline
  • Registered: 2017-03-20
  • Posts: 65

Re: ver.3.0 beta 2,3,4,5,6,7 for X-Plane 11

FIREBLADE103 wrote:

I'm getting lines going across the cockpit windows from the external view of the beta 7 aircraft... has this been recognised by Jar?

Discussed a couple of pages ago. They're not gonna fix it until after XP11 release.

315 Reply by rsd99

  • rsd99
  • Member
  • Offline
  • Registered: 2015-04-27
  • Posts: 17

Re: ver.3.0 beta 2,3,4,5,6,7 for X-Plane 11

Having an odd issue here.  I use a Saitek X-55 Rhino, and have the flaps assigned to switch 1 and switch 2 on the throttle side, when i go to raise/lower the flaps, all i hear is "Flaps 0" and the lever or flaps never move.  Let me know what logs i need to attach.

XP 11pb17
Latest 320 Beta
Mac OSX 12.4.3
32GB Ram
1TB SSD
Nvidia GTX-970


Thanks.

Rob

316 Reply by hdespres

  • hdespres
  • hdespres
  • Member
  • Offline
  • Registered: 2015-12-02
  • Posts: 73

Re: ver.3.0 beta 2,3,4,5,6,7 for X-Plane 11

rsd99 wrote:

Having an odd issue here.  I use a Saitek X-55 Rhino, and have the flaps assigned to switch 1 and switch 2 on the throttle side, when i go to raise/lower the flaps, all i hear is "Flaps 0" and the lever or flaps never move.  Let me know what logs i need to attach.

XP 11pb17
Latest 320 Beta
Mac OSX 12.4.3
32GB Ram
1TB SSD
Nvidia GTX-970


Thanks.

Rob

You have engines running? No engines ~ no hydraulics.

i5 8600K OC@ 5.0Ghz, 16 GB DDR4-RAM
ASUS ROG STRIX GTX 1070 - X55 Saitek Pro Rhino Stick, X55 Saitek Rhino Throttle
Windows 10 64 Bit - X-plane 11.11 - X-Enviro 1.07 - X-Ivap - XCamera - GHD - EFASS NG

317 Reply by laohu314

  • laohu314
  • Member
  • Offline
  • Registered: 2016-01-03
  • Posts: 677

Re: ver.3.0 beta 2,3,4,5,6,7 for X-Plane 11

Well, some pumps also run on electricity. So you need the APU on and the electrical pumps. The Yellow pump might be sufficient by itself but I'm not sure.

iMac5K 27” (2015), i7 4GHz, OSX 10.14.6, 32GB, AMD M395X 4096MB, Saitek X52, TPM, Radio, Switch & Multi, TM MFD, XP11.35r1, FFA320v0.11.2-2305, ToLiSs A319 v1.3.3, JDA320 v3.4r1, JDA330 v3.2r1, XL v4_250719, FM v2.6r2,  GndHdg v.4.010719, Air Plugin v4.8.3,  FWL 2.7.19, 3jFPS-wizard, PI v2.73.06, NOAA v2.4.4, XSPs v2.75, XCL v1.37, BPB v0.47, SAM 1.1.0

318 Reply by Totti

  • Totti
  • Member
  • Offline
  • Registered: 2016-12-25
  • Posts: 23

Re: ver.3.0 beta 2,3,4,5,6,7 for X-Plane 11

If you want to land with A320 V3 B07at EDDN, rwy 10, ils 109.55, crs 097, you can't put in the right course of 097 in the FMC. It flickers. I only noticed this problem at EDDN, standard scenery of XP11.
Anybody checked it? Same problem?

319 Reply by thomas_99

  • thomas_99
  • Member
  • Offline
  • Registered: 2015-05-04
  • Posts: 235

Re: ver.3.0 beta 2,3,4,5,6,7 for X-Plane 11

Hi !

At the moment I have problems getting ILS-Landings / Diamonds to work. (A320 B7, XP11RC1)

Last Flight from EDLP to EDDL. So far so good, but the ILS-landing does not work (FMC Managed mode).
Neither GS was captured nor ILS diamonds are displayed.

At the end I found the problem: The ILS frequency was wrong. In the Image it's set to "110.95",
but this does not belong to EDDL nor EDLP.


http://jardesign.org/forum/img/m/552/t/p1bcdh0rcq1v8q15so1arh1jmnf3c3.jpg

[SASL INFO] "bbox"    >>> zulu 16:52:2
[SASL INFO] "bbox"        baro alt=721 / rad alt=0
[SASL INFO] "bbox"        air spd=-3 / gnd spd=0 / mach=0.01
[SASL INFO] "bbox"        GW=52713 / FOB=5213 / CG=28
[SASL INFO] "bbox"    new fpln full = 1 EDLP (APT) >>> 2 06 (DEP_RWY) >>> 3 CA1100 (CA) >>> 4 LP101 (WPT) >>> 5 LP102 (WPT) >>> 6 LP105 (WPT) >>> 7 DOMEG (WPT) >>> 8 BABUV (WPT) >>> 9 DL505 (WPT) >>> 10 DL556 (WPT) >>> 11 DIKMI (WPT) >>> 12 FI05L (WPT) >>> 13 RW05L (ARR_RWY) >>> 14 EDDL (APT) >>> DIST=122.79779

During Landing:
[SASL INFO] "mcdu_fpln"    --> Switch active WPT from FI05L to RW05L by internal FMS
[SASL INFO] "mcdu_fpln"    --> Set active WPT to RW05L for DetectActualWaypoint reason
[SASL INFO] "bbox"   
[SASL INFO] "bbox"    >>> zulu 17:18:6
[SASL INFO] "bbox"        baro alt=1610 / rad alt=1463
[SASL INFO] "bbox"        air spd=133 / gnd spd=151 / mach=0.2
[SASL INFO] "bbox"        GW=51924 / FOB=4424 / CG=29
[SASL INFO] "bbox"    active wpt = 19 RW05L
[SASL INFO] "bbox"    vert wait = ALT
[SASL INFO] "bbox"    vert mode = DES
[SASL INFO] "bbox"    vert wait = G/S
[SASL INFO] "bbox"    thr  mode = THR IDLE
[SASL INFO] "bbox"    thr  mode = SPEED

320 Reply by holman.donald

  • holman.donald
  • Member
  • Offline
  • From: Owen Sound, Ontario, Canada
  • Registered: 2015-06-04
  • Posts: 22

Re: ver.3.0 beta 2,3,4,5,6,7 for X-Plane 11

Regarding AB320 V3.0B7.. It seems fine.. I flew a 700 NM+ trip and everything worked super.. sid stars.. wp everything..
on XP 11/RC 1
You are geniuses!
I am using:
iMac (Retina 5K, 27-inch, Late 2015
4 GHz Intel Core i7
32 GB 1867 MHz DDR3
AMD Radeon R9 M395X 4096 MB
mac os 10.12.3
Xplane 11.RC1 (64 bit)
X55 Saitek Pro Rhino Stick
X55 Saitek Rhino Throttle

321 Reply by thomas_99

  • thomas_99
  • Member
  • Offline
  • Registered: 2015-05-04
  • Posts: 235

Re: ver.3.0 beta 2,3,4,5,6,7 for X-Plane 11

Hi !

I think i found the problem...... my fault....

Seems that the "NAV Switch" was on, which means that the autotuning was switched off.....

thomas_99 wrote:

Hi !

At the moment I have problems getting ILS-Landings / Diamonds to work. (A320 B7, XP11RC1)

Last Flight from EDLP to EDDL. So far so good, but the ILS-landing does not work (FMC Managed mode).
Neither GS was captured nor ILS diamonds are displayed.

At the end I found the problem: The ILS frequency was wrong. In the Image it's set to "110.95",
but this does not belong to EDDL nor EDLP.


http://jardesign.org/forum/img/m/552/t/p1bcdh0rcq1v8q15so1arh1jmnf3c3.jpg

322 Reply by ilankrt (edited by ilankrt 2017-03-30 11:35:29)

  • ilankrt
  • Member
  • Offline
  • Registered: 2015-10-20
  • Posts: 772

Re: ver.3.0 beta 2,3,4,5,6,7 for X-Plane 11

That is a good example for Beta Tests. Before claiming bugs, check your activities as pilot and aircraft system configuration and then you will nearly always find out that you are the one that have made mistakes.

Beside this some more hints:
1 landing speed too law <125 kt (arrow to down)
2 ALT manage mode (!) prohibit catching G/S
3 ILS radio freq check always
4 ECAM: IGNITION stayed on !
             Spoilers not in ARM pos
             APU BLEED ON ! (since TO?!)

Hint: Before and After TO always check AICAS (using the Co Pilot checklist will help you avoid such failures)


Hi !

I think i found the problem...... my fault....

Seems that the "NAV Switch" was on, which means that the autotuning was switched off.....



At the moment I have problems getting ILS-Landings / Diamonds to work. (A320 B7, XP11RC1)........

X-Plane 11.30r3 | iMac27 OSX Mojave 14.10.4, | Samsung ultra-wide screen 49-inch | Saitek equipment | MFG pedals |Gladiator Joystick | Plugins: GndHandling, RWC, SMP, SoundM, X-Life, BetterPushback, AutoGate, SoundMaxx, X-ATC-chatter, X-Camera | iPad 12.9, iPad Air 9.7  | Airliner: JAR A320/A330, FF A350XWB, FF B767, SSG B747-8 inter, Epic1000 new, TBM900  http://ilankrt1.blogspot.co.il

323 Reply by ilankrt

  • ilankrt
  • Member
  • Offline
  • Registered: 2015-10-20
  • Posts: 772

Re: ver.3.0 beta 2,3,4,5,6,7 for X-Plane 11

holman.donald wrote:

Regarding AB320 V3.0B7.. It seems fine.. I flew a 700 NM+ trip and everything worked super.. sid stars.. wp everything..
on XP 11/RC 1
You are geniuses!
I am using:
iMac (Retina 5K, 27-inch, Late 2015
4 GHz Intel Core i7
32 GB 1867 MHz DDR3
AMD Radeon R9 M395X 4096 MB
mac os 10.12.3
Xplane 11.RC1 (64 bit)
X55 Saitek Pro Rhino Stick
X55 Saitek Rhino Throttle


BTW: laohu314 you and I have the same hardware configuration. We should keep an eye about similar occurrences while testing JAR aircraft models.......

X-Plane 11.30r3 | iMac27 OSX Mojave 14.10.4, | Samsung ultra-wide screen 49-inch | Saitek equipment | MFG pedals |Gladiator Joystick | Plugins: GndHandling, RWC, SMP, SoundM, X-Life, BetterPushback, AutoGate, SoundMaxx, X-ATC-chatter, X-Camera | iPad 12.9, iPad Air 9.7  | Airliner: JAR A320/A330, FF A350XWB, FF B767, SSG B747-8 inter, Epic1000 new, TBM900  http://ilankrt1.blogspot.co.il

324 Reply by ilankrt

  • ilankrt
  • Member
  • Offline
  • Registered: 2015-10-20
  • Posts: 772

Re: ver.3.0 beta 2,3,4,5,6,7 for X-Plane 11

holman.donald wrote:

Regarding AB320 V3.0B7.. It seems fine.. I flew a 700 NM+ trip and everything worked super.. sid stars.. wp everything..
on XP 11/RC 1
You are geniuses!
I am using:
iMac (Retina 5K, 27-inch, Late 2015
4 GHz Intel Core i7
32 GB 1867 MHz DDR3
AMD Radeon R9 M395X 4096 MB
mac os 10.12.3
Xplane 11.RC1 (64 bit)
X55 Saitek Pro Rhino Stick
X55 Saitek Rhino Throttle


BTW: laohu314 you and I have the same hardware configuration. We should keep an eye about similar occurrences while testing JAR aircraft models.......

X-Plane 11.30r3 | iMac27 OSX Mojave 14.10.4, | Samsung ultra-wide screen 49-inch | Saitek equipment | MFG pedals |Gladiator Joystick | Plugins: GndHandling, RWC, SMP, SoundM, X-Life, BetterPushback, AutoGate, SoundMaxx, X-ATC-chatter, X-Camera | iPad 12.9, iPad Air 9.7  | Airliner: JAR A320/A330, FF A350XWB, FF B767, SSG B747-8 inter, Epic1000 new, TBM900  http://ilankrt1.blogspot.co.il

325 Reply by thomas_99

  • thomas_99
  • Member
  • Offline
  • Registered: 2015-05-04
  • Posts: 235

Re: ver.3.0 beta 2,3,4,5,6,7 for X-Plane 11

Hi !

Yes, mistakes happen :-)

ilankrt wrote:

Beside this some more hints:
1 landing speed too law <125 kt (arrow to down)
2 ALT manage mode (!) prohibit catching G/S
3 ILS radio freq check always
4 ECAM: IGNITION stayed on !
             Spoilers not in ARM pos
             APU BLEED ON ! (since TO?!)

1) That's in a way interesting.... have not noticed that... A/THR on, AP1 on, AP2 on, speed is set to 135kt by managed mode
    -> hmmm, I don't know why speed is too slow and decreasing....

2) Yes, after I saw that it's not working I tried changing height...., spoilers and so on :-)

3) I saw that it was wrong, but did not know why and could not set it manually.
    Now I know why....

4) Ignition was on since "hot start". I always forget to set it back.
    Is ist forbidden to let APU and APU Bleed on ? I thought it was only wasting fuel....