You are not logged in. Please login or register.
JARDesign Group Board → Beta-versions (Download & Discussions) → ver.3.0 beta 2,3,4,5,6,7 for X-Plane 11
Thank you for the update.
Thank you 
Hi,
thank you for the update. I have a problem, after activation and reloading of the aircraft (also tried restarting the sim) I get a error message in the bottom left saying:
ERROR: a320 plugin not loaded propertly
- Please check aircraft installation!
- Please contact support.jardesing.org if no luck!
I tried reinstalling the aircraft a couple of times (with Beta 2) and even changed the folder name of the whole XP11 installation (Now it is D:\X-Plane11 (removed a whitespace)). With the Beta 3 I still have the issue.
I did notice a error message in the log.txt -> D:\X-Plane11/Aircraft/320_JARDesign/plugins/320/win.xpl : Error Code = 182 : The operating system cannot run %1.
Please find attached a screenshot of the issue and the log file.
/EDIT I forgot to mention that I successfully finished a flight despite the fact that I constantly received this error 
Are we supposed to re-enter the license serial on each beta update? Won't this consume all of the serial activations?
So I flew the A320 Beta 3 today..or tried to.
The FMC would not let me clr anything. Allos.. the B key on the keyboard..shuts off all electricity to the plane.. it is suppose to toggle the brakes at normal pressure.
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.11 (64 bit)
X55 Saitek Pro Rhino Stick X55 Saitek Rhino Throttle
Is this an x-plane 11 bug where the reflected sun is visible in the shadowed portion of the cockpit?
I think it should only been visible where the sun is shinning... comments.
Here's a quick video of the troubles.... https://youtu.be/XknI3--MCHA
Cheers Hervé
I don't seem to be able to use BSS sound pack with latest beta.
All ok with V3b2
I've installed it into A320 v3.0b3 with no issues. I actually just copied the sound3d-1 from the beta2 install and removed the old sound3d folder. The sound pack for some reason only works if the plane is loaded once. If I change aircraft and go back to the A320, I get no sound...
Hi Guys can you use a keyboard to put in entries into FMGC like aerosoft airbus - thank you
No, not in the Jar airbuses
Thank you Buddy - do you think I will be ok to load this new version ? your post on sounds is not a big deal for now
Anything to write home about in this new version ?
Biggest visible change was the cockpit reflections have been toned down a bit. In he air right now on IVAO from CYVR to CYYZ... no issues.
Thanks again
Heads up zek0 paints need tweaking to use - great repaints and thankfully there is a fix for the new A320 beta3 - you need to delete the _NML image files or your aircraft will be all chrome
The file names are
engines_NML
fuselage_NML
wings_NML
his glass files can stay or even be used in other liveries if you want
Engines inlet rings now look excellent well done Jardesign - what a great aircraft
BBS sounds working again now after removing Jar's Ground Handling Plugin.
Also was blocking another programme from working with the A320.
Tell me please.Are we supposed to re-enter the license serial on each beta update? Won't this consume all of the serial activations?
Hi,
thank you for the update. I have a problem, after activation and reloading of the aircraft (also tried restarting the sim) I get a error message in the bottom left saying:
ERROR: a320 plugin not loaded propertly
- Please check aircraft installation!
- Please contact support.jardesing.org if no luck!I tried reinstalling the aircraft a couple of times (with Beta 2) and even changed the folder name of the whole XP11 installation (Now it is D:\X-Plane11 (removed a whitespace)). With the Beta 3 I still have the issue.
I did notice a error message in the log.txt -> D:\X-Plane11/Aircraft/320_JARDesign/plugins/320/win.xpl : Error Code = 182 : The operating system cannot run %1.
Please find attached a screenshot of the issue and the log file.
/EDIT I forgot to mention that I successfully finished a flight despite the fact that I constantly received this error
One of your installed X-Plane plugin can block plugin run. You can temporary remove your plugins one-by-one and check is activation window appear.
Tell me please.Are we supposed to re-enter the license serial on each beta update? Won't this consume all of the serial activations?
no problem with this
Hi !
Tell me please.Are we supposed to re-enter the license serial on each beta update? Won't this consume all of the serial activations?
Yes, you need to reactivate the plane every beta. I allways do a clear and new install of every update.
Usually no problem, if you ran out of activations, send an email to jar, you will receive a couple of new activations
within a short time.
best regards,
First test flight with version b3: Summa summarum: I could end this flight only after go-arround and manually landing.
1. This is in my opinion very important. The Pilot cabin view (perspective) was changed since version b2. The view is too narrow !! Trying to change it with XP11 "Graphics" only distorted the view perspective. I recommend warmly to change the parameters back to b2. (It was for me dreadfully to correct all the time the perspective during flight. )
Attached 2 images of pilot view (after opening) of b2 and b3
2. AP disconnected during climb without any known reason.
3. TC was reached too early ( MCDU works normally)
4. HpA knob scrolled at first in wrong direction
5. Smoke looks better but it should be less dark gray and more dilute
I had also problems with the MCDU, but I am now going to make the same flight again to check the occurrences .....
First test flight with version b3: Summa summarum: I could end this flight only after go-arround and manually landing.
1. This is in my opinion very important. The Pilot cabin view (perspective) was changed since version b2. The view is too narrow !! Trying to change it with XP11 "Graphics" only distorted the view perspective. I recommend warmly to change the parameters back to b2. (It was for me dreadfully to correct all the time the perspective during flight. )
Attached 2 images of pilot view (after opening) of b2 and b3
2. AP disconnected during climb without any known reason.
3. TC was reached too early ( MCDU works normally)
4. HpA knob scrolled at first in wrong direction
5. Smoke looks better but it should be less dark gray and more dilute
I had also problems with the MCDU, but I am now going to make the same flight again to check the occurrences .....
Hi
I confirm the three first points above mentionned with version3 b3
jcdp
Tried to load departure on FMS (MCDU) at 2 different airports, LFPO & KSFO. Can't get the departing airport to be white (destination airport fine). So unable to get SID.
Rgds
Paul
MKJS-KMIA crash during approach
Log copy.txt 447.05 kb, 234 downloads since 2017-02-23
Just noticed QNH on the FMS adjustment knob is not equal to the MFD value???
a320neo_8.png 1.31 mb, 158 downloads since 2017-02-23
Had several of these SASL errors in the Log.txt
[SASL INFO] "mcdu_fpln" --> Switch active WPT from DISC to (T/C) by internal FMS
[SASL ERROR] Error updating avionics: [string "/mcdu_prf_to.sec"]:0: attempt to compare nil with number
[SASL INFO] "mcdu_fpln" --> Set active WPT to VEBIT for APT_DEP/DEP_RWY reason
[SASL ERROR] Error updating avionics: [string "u//mcdu_fpln.sec"]:0: attempt to index a nil value
[SASL INFO] "bbox" active wpt = 2 VEBIT
[SASL ERROR] Error updating avionics: [string "du//mcdu_int.sec"]:0: attempt to perform arithmetic on a string value
Best regards
chillicrab
JARDesign Group Board → Beta-versions (Download & Discussions) → ver.3.0 beta 2,3,4,5,6,7 for X-Plane 11
Powered by PunBB, supported by Informer Technologies, Inc.