[ Closed ] v1.1b5.2 distributive mostly the same b4 + new base SASL plugin (Page 5 of 6)

Another crash, this time I tried the stable A330 windows version. I have also tried this aircraft before without any problems. Again, very weird. No changes to my system (as far as I can remember anyways..).

CTD.

(Regarding the log file: This might be the wrong log file, unfortunately I started up xPlane again before publishing this log file. I guess this log won't say much..)

Good Day,
I have had no luck with this version and went to the stable 1.1...
then you might get one CTD on the third flight but after that you should be ok and since I went to 10.40b3 I have had no CTD's yet so don't start the ball rolling Please ...LOL
captbullett

note: try to disconnect the :

XSB: Loading package: /Applications/X-Plane 10/Resources/plugins/X-IvAp Resources/CSL/A320/xsb_aircraft.txt
XSB: Loading package: /Applications/X-Plane 10/Resources/plugins/X-IvAp Resources/CSL/AIRBUS/xsb_aircraft.txt
XSB: Loading package: /Applications/X-Plane 10/Resources/plugins/X-IvAp Resources/CSL/AN/xsb_aircraft.txt
XSB: Loading package: /Applications/X-Plane 10/Resources/plugins/X-IvAp Resources/CSL/AVROLINER/xsb_aircraft.txt
XSB: Loading package: /Applications/X-Plane 10/Resources/plugins/X-IvAp Resources/CSL/B738/xsb_aircraft.txt
XSB: Loading package: /Applications/X-Plane 10/Resources/plugins/X-IvAp Resources/CSL/B742/xsb_aircraft.txt

and see if this is the issue.... X-ivAp has been known to be able to cause issues ...

Capbullett, good day.
You are right about X-Ivap plugin.
I got many problems with it.
So, I will follow your instructions and see what happens.
Alessandro

Another problem that I might have heard mentioned by other users, but I cant locate that thread..:

I input the FP first, then departure rwy with SID. Everything works fine and the plane has implemented some waypoints called "speed limit" and the "TOD". Depending on the distance between the last waypoint and put into the FP and the landing AD, these waypoints can be before or after my last real waypoint.

1 - Do these extra waypoints (spd lim, TOD. e.g.) contain coordinate information, or should they follow the flightplan if the FP changes, and only contains distance data from AD depending on crz level etc.?
2 - What happens to these waypoints (TOD, spd lim e.g.) if I change some en-route airways/waypoints to lets say enter the destination AD from opposite angle? Will new TOD e.g. waypoints be calculated and replace the old waypoints?

Ive come to notice a couple of times that when I am enroute, and enter an arrival (STAR) for my destination AD, that the flight plan is completely messed up, with zigg zagg 180-degree turns between these "spd lim" waypoints the plane added by itself, and the new waypoints in the STAR. I have the feeling that if the "spd lim" or "spd 220" waypoints is (lets say) 50 nm from the AD, and the STAR contains a waypoint 60 nm from the AD, the flight will first fly to the "spd lim" waypoint, THEN turn 180 degrees back to catch the first STAR waypoint, and again turn 180 degrees to follow the remainder of the STAR. Do you understand what I mean?

3 - is this "normal" in this plane?
4 - is there a way to stop this from happening?

Most of the time I do not encounter this problem, and as mentioned before I think this has to do with the fact that usually the STAR waypoints (that I enter en-route) appear at the end for the flightplan, after the "spd lim" e.g. waypoints automatically added by the aircraft.

Thanks

Captbullet,
Thanks for the explanation, you may very well be correct. I will keep this in mind next time it happens.

So this means that these extra waypoints (spd lim, TOD etc.) That appear in the flight plan, they are not bound to coordinates, and thus will change if the STAR/rwy changes? I guess they do...

Thanks again

reproducable (everytime) CTO while loading.

if have "not enough memory" error, may try place a330 direct to Aircrafts folder. This may help.

CTO, last line Log.txt: SASL ERROR: Error loading panel: not enough memory

I can't believe, but  "place a330 direct to Aircrafts folder" helped. So its the SASL Memory for the Path Names?

CTO short after starting descend. Xplane 10.40b3

Wow, this is indeed a surprise: Had constant CTDs on my iMac every time when loading the plane and did not quite believe in the root folder theory. But well, I must admit, it seems to work for me. Immediately after moving the folder, I was able to load the plane for the first time.

Alex

Crash to desktop during descend without touching anything in that moment.

X-Plane version was 10.40 Beta 5 running on my iMac with OS X Yosemite 10.10.4. Aircraft is placed in the root aircraft folder.

Alex

PS: However, managed to do a full flight from Lagos/Nigeria to London Heathrow yesterday, so I am more than happy.

Hi guys,

I just recently bought the A332 and I'm pretty much enjoying it. Great work JARDesign!!!
I do have a few bug reports / suggestions based on my beta testing of FF A350 and QPAC's FBW/Avioncs suite, but I'm not (yet?) allowed to create new toppics. Maybe an admin can create/move this to the appropriate place.

Versions tested were 1.1b5.2 and the latest stable version (MCDU says VER 12 and 04.15) should be v1r2.

FBW:
-  This is a difficult and highly subjective issue but I feel that especially the roll command is dampened to much. It kind of feels like the A/C is flying on rails and you have to first get the A/C out of it's track to establich any roll movement.

-  Yaw dampers seem to be inop? Even in light turbulences the A/C suffers from massive roll-yaw oscillations (dutch-roll anyone?) and the wind is able to deflect the rudder. (Impossible in r/l as there are several thousand psi of hyd. pressure counteracting

-   flare law seems to be a bit too agressive as well?! Upon touch down I almost need to apply full back stick to smooth the landing and avoid smashing onto the rwy. This stand in hard contrast to the necessary movements during approach or short final. In this flight regime I have to barely touch the sidestick to cause quite the change in pitch or roll.

ECAM:
- The ECAM is completely missing the auto display mode (FCOM Vol I 1.31.20 p2-3). When no specific ECAM page is selected (no button is illuminated) the auto mode will show different ECAM pages depending on the phase of the flight. I.e when I'm checking the flight controls the F/CTL page should automatically display and remain displayed for 20 second after the last flight controls input. Other pages that are displayed automatically in certain conditions are WHEEL, ENG, APU and CRUISE pages. (FCOM Vol I 1.31.20 p3; Indicating/Recording Systems, Indication on SD)

MCDU:
-  on the F-PLN page it's not possible to enter speed and altitude restrictions directly. I.e. if I set 220/5000 and click on a RSK button the waypoint in that line should immediately accept this input an set a speed restriction of 250 kias and an altitude restriction of 5000ft. In the current model this input (250/5000) takes me directly to the VERT REV subpage where I can enter the restriction. Combinations of speed and altitude restriction should also be possible i.e. 250/ and /5000 for speed or altitude restrictions only. (FCOM Vol IV 4.05.10 p12)

Flight dynamics/FBW: (Climb Energy Sharing)
-   when reaching acceleration altitude Airbus aircraft use 70% of the established thrust to accelerate and 30% to climb. Right now the A320neo and A332 use 100% of thrust to accelerate resulting in a complete level off near the accel altitude. This is kind of unpleasent and disrupts a smooth climb and normal ops. Interestingly, I haven't yet observed that behavior at FL100 when accelerating further. (A330 Flight deck & Systems Briefing for Pilots, 10.31)

These are my observations and apart from those your model is first rate. I especially looooooove the wing flex and ground movement dynamics, this A/C taxies so realistically, wow. And everybody knows that textures and 3D-modelling are next to nothing. Really great job JARDesign.

Should you have any follow up questions, I'd be happy to answer them. Skype is also possible.

Greetings

Michael