[ Closed ] JD330 Airliner ver 2.0r1 WIN/MAC 64 bit (X-Plane 11) (Page 2 of 5)

Hi,

First of all I would like to say hello. Recently bought this plane and I find some error(?):

Due to gust winds I needed to go around and reengage auto-throttle. I've set up throttle position to CL and pushed A/THR button. Unfortunatelly it did not went to designated speed. I've tried it few other times and this error is repeative.

I've also noticed that despite AP1 on + A/THR on + heading knob pulled plane does not follow designated heading.

Is this some kind of error? It seems AP and A/THR has difficulties to reengage full funcitionality when turned off and then on in flight.

Please be so kind to help.

First test flight....very nice performance, better framerates than previous version...speedbrakes work fine, all systems were good.

One thing I noticed and will test again today....wind was 12 knots from the left...on ILS capture, the aircraft started moving the nose left and right constantly...was almost making me motion sick....on external view I could see the rudder moving full left and full right constantly. I disengaged the autopilot to fly manually but the rudder continued to move left and right so the yawing was non stop until I touched down.

That's not entirely unrealistic. I have experienced that in RL but if you want to get rid of it, turn off Camera Shake in the FMGS menu

I don't need to calm down as I am not nervous nor angry. I just feel a bit disappointed as I have bought 3 Airbuses (A320neo, A330 from JAR and A350 from FF) and none of them works the way they should. As for a320neo, I have not tested the new release yet, so it might be ok. In case of A350 I knew it has serious issue with FMC but I wanted to help a friend who was struggling with it, but that's another story. So, I just don't t undertand this behavior when someone is complaining about an issue and then others come and say their plane works ok. I have no doubt theirs work ok but that won't solve my and others issue.

I can talk only for myself. Look at my profile (text in gray underneath), you and especially JAR can recognize if problems occurred by some user occurs (or not) are connected to a special hard and software configuration. This is a crucial information for developers!

Unfortunately some guys are posting only occurrences without any further detail. That is good for the garbage can !!

Generally spoken, we all are in the same boat. You are right, the models have yet some failures and bugs. The good news are that JAR is working on it constantly ! (the bad news are that FF Group is doing nothing ...). To your knowledge, under XP10.51 the corresponding JAR models at least are flying perfectly and this also after a long way of trial and error...

Hi !

Well, I'm very sorry, it's not. It could be a hint in some very rare cases (in your case: 32 GB 1867 MHz DDR3, but what does it mean ?? Is the RAM overclocked, and if yes, is ist stable ?? Or is it unstable even if not overclocked ?? nobody knows...) but in most cases
there is not much information you can get.

Same with the logs. There could be some hints in the logs regarding to wrong usage of a function, but that's it. There is nearly no information for debugging purposes inside.

What would for the first step help to get a better view inside some problems is a xplane dataref recorder and player which is able to log all datarefs from xp and the A320/A330 every frame.

This would open a wider view inside some internals of the plane and you (well, not exactly you but JAR)  would be able to see
some of the problems.

Unfortunatelly, a dataref recorder/player does not exist a at the moment......think about it.

best regards,

I am not going to open a philosophic dispute, but I'll give you Two simple examples. Someone described on this thread a certain  SASL problem simulating under WIN10. On my iMac I'll never be able to reproduce same situation because of different operating system. We Mac user had a specific problem with XP that resulted through change from OSX El Capitan to Sierra. If someone would present this problem without further information, he will never get the solution that we find out.... Think about ....

BTW how do you know if you are reading a declared bug that it concern the latest r1 version? Maybe someone stuck in b8.....

My hardware config is included in the log.txt, but it is: Win10, i7-7700, 32Gb RAM, Zotac GTX1080, XPlane 11 r1, A330 is up to date, V2.0R1. All on an 1TB Samsung Pro SSD. I doubt if the hardware would cause any of my issues.
In the meantime I purged all the plugins I don't use often, assuming they might cause some disturbance in the force

In middle of my first flight with the XP11 A330.  First thing I noticed is the higher quality of the textures compared to the A320.  Secondly, it's far more frame rate friendly.  With my struggling GPU, I get around 25 FPS in the cockpit of the A320 with medium settings.  I'm getting 35 FPS in the A330 with better looking textures.  Can we have the A320 updated according?

I'd also like to see the knobs in the A330 updated so we can use the mouse wheel as with the A320.

Very nice job guys!

I hope that after 20+ years of flight simming, 15 real world flying and 5 years of flight instructing I would recognize difference between camera movement and actual "dutch roll" like effect during landing

Had the same issue that i've faced before in Beta version.

Durring the flight from LCLK to HEBA , After passing RASDA intersection and start the descend as per the TOD mark.

suddenly Found my self on ground in a remote airport not even in the same area, i think airport is E46

attached Log.txt for analysis

This is 2nd time to happen