51

Re: ver 2.6 beta 2 WIN/MAC 64 bit

No problem with Navdata. Delete the navdata folder in A320 if present, and update the GNS430 using the information in first post.
For AirFMC try to download the updated plugin from their website and see if this is ok.

52 (edited by captbullett 2015-12-04 04:34:33)

Re: ver 2.6 beta 2 WIN/MAC 64 bit

good day,
I know this is going to make your day that there is a bug in that the display says one thing but the data is doing another..
i have detail screen shots of the file trees in my computer that show the Cycle 1512 but in the MCDU it show the original shipped version of data now I clicked on the "up-date" nav-data and it saved the data according to the MCDU and the route is working as intended ... so i would tend to believe that the display is just not catching up with the  data...

(I had server issues earlier today and just getting back here .. 11:34 PM  EST ... )

captbullett
 

Airbus.Italia wrote:

X-PLANE 10/Custom Data/GNS430/navdata/

The Cycle info of the folder navdata is 1509 , but , the Cycle in fmc is diferent. Why?

53 (edited by captbullett 2015-12-04 05:36:19)

Re: ver 2.6 beta 2 WIN/MAC 64 bit

the display is not matching what the data is saying ! see the post below...

Airbus.Italia wrote:

Hallo guys, yes, the NavaData cycle in GNS430, does not match the data cycle in the FMC.
How do I fix?

54 (edited by captbullett 2015-12-04 05:33:21)

Re: ver 2.6 beta 2 WIN/MAC 64 bit

good day,
this is how I know there is a bug up-dating the Navigraph data ... while Alpha testing it told me that the data is not there ...

/Users/brianhelip/Desktop/X-Plane/Resources/Plugins/DataRefs.txt not found
124thATC v2.0-a12 00:25:18 : OpenAL initialization function
124thATC v2.0-a12 00:25:18 : OpenAL device found
SoundSetPath=/Users/brianhelip/Desktop/X-Plane/Aircraft/A320neoJD_V2/320neo_JARDesign/plugins/sound3d/
VolumePath=/Users/brianhelip/Desktop/X-Plane/Aircraft/A320neoJD_V2/320neo_JARDesign/plugins/sound3d/volume.txt
3Dsound Engine by JARDesign
Gizmo64: OpenGL<->Physics Offset Default Init: -34149.414, -97.333, -12625.001
Gizmo64: Tried to use physics engine without loading an OBJ8 file. Ignored, can't draw!
SkyMaxx Pro: Location set to lat 37.612674 lon -122.387334 alt 8.867758
SkyMaxx Pro: Changing cloud conditions.
SkyMaxx Pro: Created cumulus congestus layer alt 3757.000000 size 108737.000000 density 0.321979
SkyMaxx Pro: Cloud conditions changed. Current target visibility is 100.000000
1 default data/apt.dat = /Users/brianhelip/Desktop/X-Plane/Resources/default scenery/default apt dat/Earth nav data/apt.dat
OPEN scenery_packs.ini FILE OK
124thATC v2.0-a12 00:25:41 : Airport to search in file: /Users/brianhelip/Desktop/X-Plane/Custom Scenery/GOLDEN_GATE+SOUTH_BAY_150_XP-10/Earth nav data/apt.dat ...
124thATC v2.0-a12 00:25:41 : /Users/brianhelip/Desktop/X-Plane/Custom Scenery/GOLDEN_GATE+SOUTH_BAY_150_XP-10/Earth nav data/apt.dat
124thATC v2.0-a12 00:25:41 : File opened: /Users/brianhelip/Desktop/X-Plane/Custom Scenery/GOLDEN_GATE+SOUTH_BAY_150_XP-10/Earth nav data/apt.dat
124thATC v2.0-a12 00:25:41 : found: 'SFO1'

124thATC v2.0-a12 00:25:41 : Tower still zero, setting to 126.85!
124thATC v2.0-a12 00:25:41 : Tower frequency on leaving: '12685.000000'
124thATC v2.0-a12 00:25:41 : Total parkings found: 0
124thATC v2.0-a12 00:25:41 : Count ILS...
124thATC v2.0-a12 00:25:41 : Airport has 0 ILS/LOC runways!
124thATC v2.0-a12 00:25:41 : Disable AI for AI planes...
124thATC v2.0-a12 00:25:41 : No AI Planes!
124thATC v2.0-a12 00:25:41 : Count of planes: 1, count of parkings: 0
124thATC v2.0-a12 00:25:44 : Path: 'Macintosh HD:Users:brianhelip:Desktop:X-Plane:Resources:plugins:124thATC64:LastFlightPlan.txt'
124thATC v2.0-a12 00:25:45 : File flight plan window closed to apply...
124thATC v2.0-a12 00:25:45 : Airport not found to set runway height: .
124thATC v2.0-a12 00:25:45 : Flight Plan filed: KSEA 16C VA932 OTLIE RENBE RICHR TOMRE BANGR LKV BAARB HARTT PYRAM FMG TILTS SONNY TIOGA PINNI EHF BASET DOWNE REEDR VR170 VM2100 FEKIL TURKA RW07L KLAX
124thATC v2.0-a12 00:25:45 : Try to find: KSEA near lat 37.612782 and lon -122.387260
124thATC v2.0-a12 00:25:45 : Search as VOR...
124thATC v2.0-a12 00:25:45 : No VOR found!
124thATC v2.0-a12 00:25:45 : Search as NDB...
124thATC v2.0-a12 00:25:45 : No NDB found!
124thATC v2.0-a12 00:25:45 : Navaid not found: KSEA

124thATC v2.0-a12 00:25:45 : Try to find: 16C near lat 37.612782 and lon -122.387260
124thATC v2.0-a12 00:25:45 : Search as VOR...
124thATC v2.0-a12 00:25:45 : No VOR found!
124thATC v2.0-a12 00:25:45 : Search as NDB...
124thATC v2.0-a12 00:25:45 : No NDB found!
124thATC v2.0-a12 00:25:45 : Navaid not found: 16C

124thATC v2.0-a12 00:25:45 : Try to find: VA932 near lat 37.612782 and lon -122.387260
124thATC v2.0-a12 00:25:45 : Search as FIX...
124thATC v2.0-a12 00:25:45 : Navaid not found: VA932

124thATC v2.0-a12 00:25:45 : Try to find: OTLIE near lat 37.612782 and lon -122.387260
124thATC v2.0-a12 00:25:45 : Search as FIX...
124thATC v2.0-a12 00:25:45 : Found: OTLIE on lat 47.397823 and lon -122.311562, entering into flight plan as order 1!
124thATC v2.0-a12 00:25:45 :
124thATC v2.0-a12 00:25:45 : Try to find: RENBE near lat 37.612782 and lon -122.387260
124thATC v2.0-a12 00:25:45 : Search as FIX...
124thATC v2.0-a12 00:25:45 : Found: RENBE on lat 47.320366 and lon -122.311546, entering into flight plan as order 1!
124thATC v2.0-a12 00:25:45 :
124thATC v2.0-a12 00:25:45 : Try to find: RICHR near lat 37.612782 and lon -122.387260
124thATC v2.0-a12 00:25:45 : Search as FIX...
124thATC v2.0-a12 00:25:45 : Found: RICHR on lat 47.306690 and lon -122.437561, entering into flight plan as order 1!
124thATC v2.0-a12 00:25:45 :
124thATC v2.0-a12 00:25:45 : Try to find: TOMRE near lat 37.612782 and lon -122.387260
124thATC v2.0-a12 00:25:45 : Search as FIX...
124thATC v2.0-a12 00:25:45 : Found: TOMRE on lat 47.335457 and lon -122.516891, entering into flight plan as order 1!
124thATC v2.0-a12 00:25:45 :
124thATC v2.0-a12 00:25:45 : Try to find: BANGR near lat 37.612782 and lon -122.387260
124thATC v2.0-a12 00:25:45 : Search as FIX...
124thATC v2.0-a12 00:25:45 : Found: BANGR on lat 47.643902 and lon -122.914917, entering into flight plan as order 1!
124thATC v2.0-a12 00:25:45 :
124thATC v2.0-a12 00:25:45 : Try to find: LKV near lat 37.612782 and lon -122.387260
124thATC v2.0-a12 00:25:45 : Search as VOR...
124thATC v2.0-a12 00:25:45 : Found VOR in a distance of 305.27 miles
124thATC v2.0-a12 00:25:45 : Search as NDB...
124thATC v2.0-a12 00:25:45 : No NDB found!
124thATC v2.0-a12 00:25:45 : Found: LKV on lat 42.492851 and lon -120.507103, entering into flight plan as order 1!
124thATC v2.0-a12 00:25:45 :
124thATC v2.0-a12 00:25:45 : Try to find: BAARB near lat 37.612782 and lon -122.387260
124thATC v2.0-a12 00:25:45 : Search as FIX...
124thATC v2.0-a12 00:25:45 : Found: BAARB on lat 41.157604 and lon -120.113670, entering into flight plan as order 1!
124thATC v2.0-a12 00:25:45 :
124thATC v2.0-a12 00:25:45 : Try to find: HARTT near lat 37.612782 and lon -122.387260
124thATC v2.0-a12 00:25:45 : Search as FIX...
124thATC v2.0-a12 00:25:45 : Found: HARTT on lat 40.835869 and lon -120.021248, entering into flight plan as order 1!
124thATC v2.0-a12 00:25:45 :
124thATC v2.0-a12 00:25:45 : Try to find: PYRAM near lat 37.612782 and lon -122.387260
124thATC v2.0-a12 00:25:45 : Search as FIX...
124thATC v2.0-a12 00:25:45 : Found: PYRAM on lat 39.893276 and lon -119.755997, entering into flight plan as order 1!
124thATC v2.0-a12 00:25:45 :
124thATC v2.0-a12 00:25:45 : Try to find: FMG near lat 37.612782 and lon -122.387260
124thATC v2.0-a12 00:25:45 : Search as VOR...
124thATC v2.0-a12 00:25:45 : Found VOR in a distance of 172.24 miles
124thATC v2.0-a12 00:25:45 : Search as NDB...
124thATC v2.0-a12 00:25:45 : No NDB found!
124thATC v2.0-a12 00:25:45 : Found: FMG on lat 39.531265 and lon -119.656075, entering into flight plan as order 1!
124thATC v2.0-a12 00:25:45 :
124thATC v2.0-a12 00:25:45 : Try to find: TILTS near lat 37.612782 and lon -122.387260
124thATC v2.0-a12 00:25:45 : Search as FIX...
124thATC v2.0-a12 00:25:45 : Found: TILTS on lat 38.634720 and lon -119.526878, entering into flight plan as order 1!
124thATC v2.0-a12 00:25:45 :
124thATC v2.0-a12 00:25:45 : Try to find: SONNY near lat 37.612782 and lon -122.387260
124thATC v2.0-a12 00:25:45 : Search as FIX...
124thATC v2.0-a12 00:25:45 : Found: SONNY on lat 38.335747 and lon -119.484528, entering into flight plan as order 1!
124thATC v2.0-a12 00:25:45 :
124thATC v2.0-a12 00:25:45 : Try to find: TIOGA near lat 37.612782 and lon -122.387260
124thATC v2.0-a12 00:25:45 : Search as FIX...
124thATC v2.0-a12 00:25:45 : Found: TIOGA on lat 37.932922 and lon -119.428024, entering into flight plan as order 1!
124thATC v2.0-a12 00:25:45 :
124thATC v2.0-a12 00:25:45 : Try to find: PINNI near lat 37.612782 and lon -122.387260
124thATC v2.0-a12 00:25:45 : Search as FIX...
124thATC v2.0-a12 00:25:45 : Found: PINNI on lat 36.797825 and lon -119.272026, entering into flight plan as order 1!
124thATC v2.0-a12 00:25:45 :
124thATC v2.0-a12 00:25:45 : Try to find: EHF near lat 37.612782 and lon -122.387260
124thATC v2.0-a12 00:25:45 : Search as VOR...
124thATC v2.0-a12 00:25:45 : Found VOR in a distance of 203.61 miles
124thATC v2.0-a12 00:25:45 : Search as NDB...
124thATC v2.0-a12 00:25:45 : No NDB found!
124thATC v2.0-a12 00:25:45 : Found: EHF on lat 35.484554 and lon -119.097298, entering into flight plan as order 1!
124thATC v2.0-a12 00:25:45 :
124thATC v2.0-a12 00:25:45 : Try to find: BASET near lat 37.612782 and lon -122.387260
124thATC v2.0-a12 00:25:45 : Search as FIX...
124thATC v2.0-a12 00:25:45 : Found: BASET on lat 33.978706 and lon -117.978539, entering into flight plan as order 1!
124thATC v2.0-a12 00:25:45 :
124thATC v2.0-a12 00:25:45 : Try to find: DOWNE near lat 37.612782 and lon -122.387260
124thATC v2.0-a12 00:25:45 : Search as FIX...
124thATC v2.0-a12 00:25:45 : Found: DOWNE on lat 33.964302 and lon -118.123726, entering into flight plan as order 1!
124thATC v2.0-a12 00:25:45 :
124thATC v2.0-a12 00:25:45 : Try to find: REEDR near lat 37.612782 and lon -122.387260
124thATC v2.0-a12 00:25:45 : Search as FIX...
124thATC v2.0-a12 00:25:45 : Found: REEDR on lat 33.949043 and lon -118.275879, entering into flight plan as order 1!
124thATC v2.0-a12 00:25:45 :
124thATC v2.0-a12 00:25:45 : Try to find: VR170 near lat 37.612782 and lon -122.387260
124thATC v2.0-a12 00:25:45 : Search as FIX...
124thATC v2.0-a12 00:25:45 : Navaid not found: VR170

124thATC v2.0-a12 00:25:45 : Try to find: VM2100 near lat 37.612782 and lon -122.387260
124thATC v2.0-a12 00:25:45 : Navaid not found: VM2100

124thATC v2.0-a12 00:25:45 : Try to find: FEKIL near lat 37.612782 and lon -122.387260
124thATC v2.0-a12 00:25:45 : Search as FIX...
124thATC v2.0-a12 00:25:45 : Found: FEKIL on lat 33.913155 and lon -118.638573, entering into flight plan as order 1!
124thATC v2.0-a12 00:25:45 :
124thATC v2.0-a12 00:25:45 : Try to find: TURKA near lat 37.612782 and lon -122.387260
124thATC v2.0-a12 00:25:45 : Search as FIX...
124thATC v2.0-a12 00:25:45 : Found: TURKA on lat 33.925541 and lon -118.519257, entering into flight plan as order 1!
124thATC v2.0-a12 00:25:45 :
124thATC v2.0-a12 00:25:45 : Try to find: RW07L near lat 37.612782 and lon -122.387260
124thATC v2.0-a12 00:25:45 : Search as FIX...
124thATC v2.0-a12 00:25:45 : Navaid not found: RW07L

124thATC v2.0-a12 00:25:45 : Try to find: KLAX near lat 37.612782 and lon -122.387260
124thATC v2.0-a12 00:25:45 : Search as VOR...
124thATC v2.0-a12 00:25:45 : No VOR found!
124thATC v2.0-a12 00:25:45 : Search as NDB...
124thATC v2.0-a12 00:25:45 : No NDB found!
124thATC v2.0-a12 00:25:45 : Navaid not found: KLAX

124thATC v2.0-a12 00:25:45 : Adding flight plan to FMS now...
124thATC v2.0-a12 00:25:45 : No actual FMS entries yet...

124thATC v2.0-a12 00:25:45 : Enter FMS entry with known type. Get NavAid...
124thATC v2.0-a12 00:25:45 : Enter NavAid as FMS entry...
124thATC v2.0-a12 00:25:45 : Set!

124thATC v2.0-a12 00:25:45 : Enter FMS entry with known type. Get NavAid...
124thATC v2.0-a12 00:25:45 : Enter NavAid as FMS entry...
124thATC v2.0-a12 00:25:45 : Set!

124thATC v2.0-a12 00:25:45 : Enter FMS entry with known type. Get NavAid...
124thATC v2.0-a12 00:25:45 : Enter NavAid as FMS entry...
124thATC v2.0-a12 00:25:45 : Set!

124thATC v2.0-a12 00:25:45 : Enter FMS entry with known type. Get NavAid...
124thATC v2.0-a12 00:25:45 : Enter NavAid as FMS entry...
124thATC v2.0-a12 00:25:45 : Set!

124thATC v2.0-a12 00:25:45 : Enter FMS entry with known type. Get NavAid...
124thATC v2.0-a12 00:25:45 : Enter NavAid as FMS entry...
124thATC v2.0-a12 00:25:45 : Set!

124thATC v2.0-a12 00:25:45 : Enter FMS entry with known type. Get NavAid...
124thATC v2.0-a12 00:25:45 : Enter NavAid as FMS entry...
124thATC v2.0-a12 00:25:45 : Set!

124thATC v2.0-a12 00:25:45 : Enter FMS entry with known type. Get NavAid...
124thATC v2.0-a12 00:25:45 : Enter NavAid as FMS entry...
124thATC v2.0-a12 00:25:45 : Set!

124thATC v2.0-a12 00:25:45 : Enter FMS entry with known type. Get NavAid...
124thATC v2.0-a12 00:25:45 : Enter NavAid as FMS entry...
124thATC v2.0-a12 00:25:45 : Set!

124thATC v2.0-a12 00:25:45 : Enter FMS entry with known type. Get NavAid...
124thATC v2.0-a12 00:25:45 : Enter NavAid as FMS entry...
124thATC v2.0-a12 00:25:45 : Set!

124thATC v2.0-a12 00:25:45 : Enter FMS entry with known type. Get NavAid...
124thATC v2.0-a12 00:25:45 : Enter NavAid as FMS entry...
124thATC v2.0-a12 00:25:45 : Set!

124thATC v2.0-a12 00:25:45 : Enter FMS entry with known type. Get NavAid...
124thATC v2.0-a12 00:25:45 : Enter NavAid as FMS entry...
124thATC v2.0-a12 00:25:45 : Set!

124thATC v2.0-a12 00:25:45 : Enter FMS entry with known type. Get NavAid...
124thATC v2.0-a12 00:25:45 : Enter NavAid as FMS entry...
124thATC v2.0-a12 00:25:45 : Set!

124thATC v2.0-a12 00:25:45 : Enter FMS entry with known type. Get NavAid...
124thATC v2.0-a12 00:25:45 : Enter NavAid as FMS entry...
124thATC v2.0-a12 00:25:45 : Set!

124thATC v2.0-a12 00:25:45 : Enter FMS entry with known type. Get NavAid...
124thATC v2.0-a12 00:25:45 : Enter NavAid as FMS entry...
124thATC v2.0-a12 00:25:45 : Set!

124thATC v2.0-a12 00:25:45 : Enter FMS entry with known type. Get NavAid...
124thATC v2.0-a12 00:25:45 : Enter NavAid as FMS entry...
124thATC v2.0-a12 00:25:45 : Set!

124thATC v2.0-a12 00:25:45 : Enter FMS entry with known type. Get NavAid...
124thATC v2.0-a12 00:25:45 : Enter NavAid as FMS entry...
124thATC v2.0-a12 00:25:45 : Set!

124thATC v2.0-a12 00:25:45 : Enter FMS entry with known type. Get NavAid...
124thATC v2.0-a12 00:25:46 : Enter NavAid as FMS entry...
124thATC v2.0-a12 00:25:46 : Set!

124thATC v2.0-a12 00:25:46 : Enter FMS entry with known type. Get NavAid...
124thATC v2.0-a12 00:25:46 : Enter NavAid as FMS entry...
124thATC v2.0-a12 00:25:46 : Set!

124thATC v2.0-a12 00:25:46 : Enter FMS entry with known type. Get NavAid...
124thATC v2.0-a12 00:25:46 : Enter NavAid as FMS entry...
124thATC v2.0-a12 00:25:46 : Set!

124thATC v2.0-a12 00:25:46 : Enter FMS entry with known type. Get NavAid...
124thATC v2.0-a12 00:25:46 : Enter NavAid as FMS entry...
124thATC v2.0-a12 00:25:46 : Set!

124thATC v2.0-a12 00:25:46 : Set destination to first FMS entry...
124thATC v2.0-a12 00:25:46 : Display first FMS entry...

124thATC v2.0-a12 00:25:47 : Btn rqst IFR clearance...
124thATC v2.0-a12 00:25:47 : RequestIFRClearance...
124thATC v2.0-a12 00:25:47 : Count of planes: 1, count of parkings: 0
124thATC v2.0-a12 00:25:47 : cannot find center frequency in acc.dat for SFO1
124thATC v2.0-a12 00:25:47 : generating dummy center frequency: 12555.000000
124thATC v2.0-a12 00:25:47 : Check departure runway now...
124thATC v2.0-a12 00:25:47 : Set matching runway...
124thATC v2.0-a12 00:25:47 : Take parser object
124thATC v2.0-a12 00:25:47 : Get wind data...
124thATC v2.0-a12 00:25:47 : Departure, take plane position as reference
124thATC v2.0-a12 00:25:47 : Reference point: Lat 37.612782 Lon: -122.387260
124thATC v2.0-a12 00:25:47 : Wind less than 10 knots. Get runway by location...
--=={This application has crashed because of the plugin: 124thATCV2}==--

55

Re: ver 2.6 beta 2 WIN/MAC 64 bit

Speed brakes not setting on the ground until I fully extend them first!

When preparing for departure, I set the Speed Brake (Spoilers) to armed but there is no corresponding feedback from the co-pilot and I don't think the spoilers are in fact Armed.  I have to select Full Spoilers before I get audio feedback from the co-pilot, I then have to then select half spoilers then retracted before I get a positive response that the Spoilers are Armed.

This issue may have been introduced in v2.6b1.

Cheers Mike
iMac 27" Mid 2011, MacOS Sierra v10.12.1, i5 Intel 3.1Ghz, 16GB RAM, AMD HD 6970M 1024MB - Logitech Extreme Pro, X-Plane 10.51

56

Re: ver 2.6 beta 2 WIN/MAC 64 bit

So to keep the work for Jar and Slava easy and structured, I would kindly ask all users to use a standardized bug reporting.

We used that in the alpha/ beta phase and it was quite well because you clearly could see which bug was fixed, if there is a discussion about bug and so one.
So my suggestion are:
1.Search the forum before you open a new topic. Your bug might be already reported.
If your bug is already reported:
Post your findings to this existing topic.
If your bug wasn't reported before:
2. Open a new topic
3. Choose a Topic subject which describes your bug in the most shortest form and use one of the following to identify your problem in front of your topic subject:
[sys] for bugs concerning the aircraft's systems
[fpln] for bugs concerning flight plan
[vis] for bugs concerning the outside/ inside look of the 3D objects
[other] if you can't put your bug into one of these categories
4. Describe your bug precisely as possible in the write message field.
5. Attach X-Plane Log.txt and A330 bb_log.txt.
6. If possibile add sources from FCOM, POH, AMM proving JarDesign's A330 is wrong.
And last the most important point for a fast fixing of bugs is that you please post only one bug into one topic

To my mind if we all spent the time to do our bug reporting like that way, JarDesign could easily work through the reported bugs
Best Regards
Lukas



mruane wrote:

Speed brakes not setting on the ground until I fully extend them first!

When preparing for departure, I set the Speed Brake (Spoilers) to armed but there is no corresponding feedback from the co-pilot and I don't think the spoilers are in fact Armed.  I have to select Full Spoilers before I get audio feedback from the co-pilot, I then have to then select half spoilers then retracted before I get a positive response that the Spoilers are Armed.

This issue may have been introduced in v2.6b1.

57

Re: ver 2.6 beta 2 WIN/MAC 64 bit

Good day,
This is when the Navigraph data is set-up right yet the display still dod not change in the MCDU the data is right. but the page display is not. https://youtu.be/woIo6-YGwpU
captbullett

58 (edited by mruane 2015-12-05 09:30:54)

Re: ver 2.6 beta 2 WIN/MAC 64 bit

Lukas

Are you proposing that the bug reports be added to the general feedback section of the Forum and not the Beta Version (Download and Discussion)?  If so, then there will be a problem implementing your good suggestion. Quite simply, the structure of the Forum currently does not support this approach. To implement this, JAR would need to add a new section so that new topics can be created. Currently, the Beta forum does not allow for new Topics in relation to the Beta's. The only place available to add bug reports is inside the Release thread, which does not allow for Topic descriptions.

Cheers Mike
iMac 27" Mid 2011, MacOS Sierra v10.12.1, i5 Intel 3.1Ghz, 16GB RAM, AMD HD 6970M 1024MB - Logitech Extreme Pro, X-Plane 10.51

59 (edited by Homer.Simpson 2015-12-05 11:42:22)

Re: ver 2.6 beta 2 WIN/MAC 64 bit

Hej, when I wrote the text there were no betas available to public. So this procedure was set for released versions and the general discussion forum to keep that structured. For me it's okay to post bugs which are related to betas directly in the topic of the beta. Because it's a beta and no release version.
But the bug report here in this forum also should be structured and contain all the necessary data like log.txt bb_log.txt and so on..

Lukas

60

Re: ver 2.6 beta 2 WIN/MAC 64 bit

Hi !

I've made a flight from Lima to Cuzco, interesting landing with 300 Miles :-)

1) Graphic error on the map on approach to Cuzco:

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

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


2) The plane did not follow the flight path:

http://jardesign.org/forum/img/m/552/t/p1a5p55spv3dci0a1g2se6b1t1bm.jpg
http://jardesign.org/forum/img/m/552/t/p1a5p56as41sjpjlr18pgca2ekvo.jpg
http://jardesign.org/forum/img/m/552/t/p1a5p56ens1g7g16kvh8r1prg1urpq.jpg


3) but then decided to turn around: I did not do anything, so the plane decided itself to turn....

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


4) Yes, on final approach: No speed 250 markers, no speed 220 markers, no approach mode, that means
    the plane was willing to land at 300 miles :-)

    Ok, the airport is over 10000 feed high ....

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

best regards,

Thomas

61

Re: ver 2.6 beta 2 WIN/MAC 64 bit

Good day,
thank-you I thought I knew how to follow directions ...
brian

Homer.Simpson wrote:

Hej, when I wrote the text there were no betas available to public. So this procedure was set for released versions and the general discussion forum to keep that structured. For me it's okay to post bugs which are related to betas directly in the topic of the beta. Because it's a beta and no release version.
But the bug report here in this forum also should be structured and contain all the necessary data like log.txt bb_log.txt and so on..

Lukas

62

Re: ver 2.6 beta 2 WIN/MAC 64 bit

Good Day,
yes, we can't have are cake and eat it too, the graphic errors you speck of I have seen also, the fix is to change your range knob and you will be ok this will also, fix the behavior of when your aircraft makes the turn to final so, it is in the way you make the adjustments in the aircraft that either make or break the flight on the simulator that is when your skill come in and i can't teach that...
captbullett   



thomas_99 wrote:

Hi !

I've made a flight from Lima to Cuzco, interesting landing with 300 Miles :-)

1) Graphic error on the map on approach to Cuzco:

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

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


2) The plane did not follow the flight path:

http://jardesign.org/forum/img/m/552/t/p1a5p55spv3dci0a1g2se6b1t1bm.jpg
http://jardesign.org/forum/img/m/552/t/p1a5p56as41sjpjlr18pgca2ekvo.jpg
http://jardesign.org/forum/img/m/552/t/p1a5p56ens1g7g16kvh8r1prg1urpq.jpg


3) but then decided to turn around: I did not do anything, so the plane decided itself to turn....

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


4) Yes, on final approach: No speed 250 markers, no speed 220 markers, no approach mode, that means
    the plane was willing to land at 300 miles :-)

    Ok, the airport is over 10000 feed high ....

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

best regards,

Thomas

63

Re: ver 2.6 beta 2 WIN/MAC 64 bit

Hi !

captbullett wrote:

Good Day,
yes, we can't have are cake and eat it too, the graphic errors you speck of I have seen also, the fix is to change your range knob and you will be ok

Sorry, but this is not true. As you can see here:
http://jardesign.org/forum/img/m/552/t/p1a5pncn5bug01t9ovldnpu134l3.jpghttp://jardesign.org/forum/img/m/552/t/p1a5pncr3g138s1g7b1fil2ks1cv25.jpg

I've marked the ranges. So changing the range does all but not fixing any/this error. As you see I have changed the range knob but the error does not vanish.


captbullett wrote:

this will also, fix the behavior of when your aircraft makes the turn to final so, it is in the way you make the adjustments in the aircraft that either make or break the flight on the simulator that is when your skill come in and i can't teach that...
captbullett

Sorry, but this is also not true. Jesus, I have to mark everything....

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

1) On the PFD, you see: THR IDLE, ALT DES, AP1, A/THR engaged.
    But you also see: Speed is above 300 miles, hight is about 14700 feet, which is about 4000 feet over ground.
    On the secondary display, ok, the snapshot is too late, but I have another one:

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

So please tell me where the speed markers are ?? I can't see them, and so the plane goes 300miles/h in the ground....

best regards

64

Re: ver 2.6 beta 2 WIN/MAC 64 bit

hello guys, but because the aircraft does not follow the flight plan loaded sull'FMC?
This version continues to have the same problems as the front ones, Plane: exit off course by itself, does not follow the flight plan entered and I have to correct with the HDG manually.
This bug continues over time since the first version. It will be solved once and for all?

65

Re: ver 2.6 beta 2 WIN/MAC 64 bit

I've never had that problem. I had the a320 from v1
Win8 and XP10.42

Airbus.Italia wrote:

hello guys, but because the aircraft does not follow the flight plan loaded sull'FMC?
This version continues to have the same problems as the front ones, Plane: exit off course by itself, does not follow the flight plan entered and I have to correct with the HDG manually.
This bug continues over time since the first version. It will be solved once and for all?

66

Re: ver 2.6 beta 2 WIN/MAC 64 bit

personally and 'a problem that in the past had shown with screenshots, and if I remember correctly, there were others with the same problem, I repeat, as the plane follows a route point and joins him, he loses the point route next and follow the right instead of heading towards the next one.
All this does not always happen, but occasionally, I can not understand why.
Let's see what he says the Jardesign

67

Re: ver 2.6 beta 2 WIN/MAC 64 bit

My Baro reads 0000 and cannot be changed!

Intel i5 3570K, Gigabyte G1 Gaming GTX 970 4GB, 16GB Ram

68

Re: ver 2.6 beta 2 WIN/MAC 64 bit

Hi !

It's even worse!

What we have here:

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

-> Speed is 280, but the SPD220 marker is just 3 NM away.....
-> in the MFD, there even is no SPD220 marker...

So let the plane go 4 miles result in this:

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

-> No SPD220 marker, but next waypoint is selected.
-> Speed is +280..

And that's the flight plan:

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

White: URC is selected and next point.
Green: SPD220, ignored...


thomas_99 wrote:

Hi !

captbullett wrote:

Good Day,
yes, we can't have are cake and eat it too, the graphic errors you speck of I have seen also, the fix is to change your range knob and you will be ok

Sorry, but this is not true. As you can see here:
http://jardesign.org/forum/img/m/552/t/p1a5pncn5bug01t9ovldnpu134l3.jpghttp://jardesign.org/forum/img/m/552/t/p1a5pncr3g138s1g7b1fil2ks1cv25.jpg

I've marked the ranges. So changing the range does all but not fixing any/this error. As you see I have changed the range knob but the error does not vanish.


captbullett wrote:

this will also, fix the behavior of when your aircraft makes the turn to final so, it is in the way you make the adjustments in the aircraft that either make or break the flight on the simulator that is when your skill come in and i can't teach that...
captbullett

Sorry, but this is also not true. Jesus, I have to mark everything....

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

1) On the PFD, you see: THR IDLE, ALT DES, AP1, A/THR engaged.
    But you also see: Speed is above 300 miles, hight is about 14700 feet, which is about 4000 feet over ground.
    On the secondary display, ok, the snapshot is too late, but I have another one:

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

So please tell me where the speed markers are ?? I can't see them, and so the plane goes 300miles/h in the ground....

best regards

69

Re: ver 2.6 beta 2 WIN/MAC 64 bit

ND flash fixed for beta 3.

Please read a FAQ before you post a bug http://support.jardesign.org

70

Re: ver 2.6 beta 2 WIN/MAC 64 bit

Airbus.Italia wrote:

personally and 'a problem that in the past had shown with screenshots, and if I remember correctly, there were others with the same problem, I repeat, as the plane follows a route point and joins him, he loses the point route next and follow the right instead of heading towards the next one.
All this does not always happen, but occasionally, I can not understand why.
Let's see what he says the Jardesign

No example? No screenshots? No tmpyfpln? No bbox_log? Do you think that there is a psychic, please? I am not, sorry smile

Please read a FAQ before you post a bug http://support.jardesign.org

71

Re: ver 2.6 beta 2 WIN/MAC 64 bit

Thanks so much

J.A.Romanov wrote:

ND flash fixed for beta 3.

72

Re: ver 2.6 beta 2 WIN/MAC 64 bit

J.A.Romanov wrote:

ND flash fixed for beta 3.


Great !!

73

Re: ver 2.6 beta 2 WIN/MAC 64 bit

Hello. Since you are working on mcdu, its possible for you to update the estimated time from a short interval instead of doing it
only when passing a waypoint? This is because i sometime enter oceanic atc on vatsim, and its no possible to pass estimated time
because the time is static on every waypoint until i pass the next one.

Regards.

74 (edited by captbullett 2015-12-11 02:17:45)

Re: ver 2.6 beta 2 WIN/MAC 64 bit

Good day,
Hay you missed a spot with your marker  LOL come on man ease-up.
As you see it will be re-worked on the next Beta but i have seen the issue get fixed by changing the range on the AP and in your case it did not... "why" is my question to myself?
captbullett

thomas_99 wrote:

Hi !

It's even worse!

What we have here:

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

-> Speed is 280, but the SPD220 marker is just 3 NM away.....
-> in the MFD, there even is no SPD220 marker...

So let the plane go 4 miles result in this:

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

-> No SPD220 marker, but next waypoint is selected.
-> Speed is +280..

And that's the flight plan:

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

White: URC is selected and next point.
Green: SPD220, ignored...


thomas_99 wrote:

Hi !

captbullett wrote:

Good Day,
yes, we can't have are cake and eat it too, the graphic errors you speek of I have seen also, the fix is to change your range knob and you will be ok

Sorry, but this is not true. As you can see here:
http://jardesign.org/forum/img/m/552/t/p1a5pncn5bug01t9ovldnpu134l3.jpghttp://jardesign.org/forum/img/m/552/t/p1a5pncr3g138s1g7b1fil2ks1cv25.jpg

I've marked the ranges. So changing the range does all but not fixing any/this error. As you see I have changed the range knob but the error does not vanish.


captbullett wrote:

this will also, fix the behavior of when your aircraft makes the turn to final so, it is in the way you make the adjustments in the aircraft that either make or break the flight on the simulator that is when your skill come in and i can't teach that...
captbullett

Sorry, but this is also not true. Jesus, I have to mark everything....

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

1) On the PFD, you see: THR IDLE, ALT DES, AP1, A/THR engaged.
    But you also see: Speed is above 300 miles, hight is about 14700 feet, which is about 4000 feet over ground.
    On the secondary display, ok, the snapshot is too late, but I have another one:

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

So please tell me where the speed markers are ?? I can't see them, and so the plane goes 300miles/h in the ground....

best regards

75

Re: ver 2.6 beta 2 WIN/MAC 64 bit

Airbus.Italia wrote:

hello guys, but because the aircraft does not follow the flight plan loaded sull'FMC?
This version continues to have the same problems as the front ones, Plane: exit off course by itself, does not follow the flight plan entered and I have to correct with the HDG manually.
This bug continues over time since the first version. It will be solved once and for all?


I have deleted  the x plane preference folder, so x plane rebuild it  , remap my joystick setting  and  that  fix it

cheers