[ Closed ] JD320 v.3.4 public beta (Page 4 of 8)

Regarding the bss sounds, the jar a320 and the clicking, the hdg knob seems to rotate during pushback and flight when autopilot alters the course, hence in my belief the problem seems to be with the plane and not the sounds? Watch the triangle on the hdg knob.

For people using the bss sounds, just turn Down the cockpit volume and the clicking goes away

Also the speed knob rotates when autopilot adjusts speed

Thanks Sir for answer, for ILS I thinks that put automatical insert, but no problem. For point example I depart on LOWW with IRGOT1A RWY11 but there's the SID. I put point in to MCDW WW361 WW362 etc. but not allowed

Thanks Sir I solve it on follow a SID Charts and use HDG. I thought that it's an error of plane

Hi Team,

a good week went very well. The old problems (autopilot simply turns off, and the speed control) were fixed. Perfect!

Yesterday, however, there were again 2 problems:

1. Autopilot 1 can not be reacktivieren.
2. On the flight from EDDH to ESSA the aircraft remained constant at a cruising speed of 280 Ktn.

Otherwise, I am very satisfied and wait for the official release.

A message in XPlane11 showed that I should send a log.txt to JARDesign.
Where do I find the file?

many greetings
FullThrottle

Hi! I have no sounds at all using the BSS PW version....engine sounds and system sounds not playing...any tip?
Not working even with default sounds

I do have it...Even with Default 3.4 installation the aircraft has no sounds

Hi, i'm using the beta version for 1 month and just noticed this: after a go around, autopilot don't follow the SIDs planned at the FMGS. It can be fixed by re-entering the destination airport but the landing configuration does not activate a second time
(With the non-beta all works nice)

Hi Eugeny,
I was going thru the new features of the MCDU MENU to manage the handling / fuel / tow /settings / screenside toolbars, and I think that in order to improve the VR compatibility for this beautiful aircraft you should add these features instead of the screen widgets:

1) you could make this MCDU MENU page only available when powering the aircraft with batteries on. It has no sense for me that I have to run the APU first, in order to have then the ability to turn the GPU on from the MCDU when on VR. Or alternatively, make the GPU available by default when starting the aircraft "cold and dark".

2) make it possible to load fuel, pax and payload via the MCDU, it is impossible to use the screenside toolbars while on VR.

I appreciate a lot the improvements like the automatic route scrolling update when passing each route fix, the ability to generate flightplan or load presaved from FlightPlan folder etc.

Here are a few problems I noticed instead:
1) I noticed an acceleration in managed descend that exceeded 6000fpm during a descent, and I had to revert it to V/S descent.
2) I've never been able to access to STS page on the ECAM.
I thought beta 2 corrected these issues
3) By pressing any ECAM button twice (or STS twice) during a cruise (when passed STD baro press) I should be able to see the CRUISE page, but I have only seen it sometimes while ALL button was pressed.

I have never seen ECAM actions like in the real related A320 for abnormal situations or malfunctions, and I am wondering if those are, or will be simulated in the future.

Besides the other issues noticed by everyone, (Metar still not working, etc.) I found this version is gonna be a huge improvement!
Thank you Eugeny!
Giulio

that is what Magknight did for his crappy B787. And it took a lot of flak and bad pr. If the product isn't up to current standard, I don't see why the user should pay more money for things that should be included in the first place. I am not afraid to say that in my honest opinion, the price tag for the JAR wasn't correct until this recent update, that brought a lot of needed features. Donations? Of course! Asking money for updates? No way, it sets a bad precedent that the whole industry could follow. Personally, I'd gladly leave some euros to this awesome project to help progressing to advanced features (like separated systems for captain and f/o), but absolutely not if required. Maybe, this could work for people that bought the plane ages ago with XP10, but as a lot of people bought this right before the FF came out I don't see why they should pay again after this little time.

During a flight from SABE to SAZS, FMGC only allow to input FL370. If I select another FL it says NEW CRZ FL and then MISSED DATA

It does for me, 11.32r2

Check frequence ILS in NAV/RAD button