[V2 Pitch-Up and Other Quirks with Flaps]

10 hours ago, Coop said:

I'll note the pitch report and have it looked into. Regarding flaps, the Islander has 6° as the default for most flight conditions, and you can put it into the 0° bump position for low weight flight for improved cruise speed and altitude. 

Excellent. Thanks mate. 

[Islander BN-2B Sound]

14 hours ago, trago778 said:

Not sure if I've missed something but if I use the noise cancelling headphones it mutes all sounds including ATC, I cannot hear them or myself replying. I've tried adjusting the noise cancellation but it just turns everything up or down.

It would be good to be able to separate the background from the voice.

 

Using the latest Xplane 12 update (2.0)

 

Thanks

Yep. Me too. 

[V2 Pitch-Up and Other Quirks with Flaps]

Hi guys, thanks for the update.

Not sure whether this is accurate or not, but I appear to have excessive pitch-up when selecting Landing Flaps (from TO) - even the AP has difficulty correcting it. When hand flying, it takes significant forward yoke movement and then trim to correct it. It is also evident when transitioning from Clean to TO, but not as pronounced.  Is this normal - I don't recall this much pitch-up in the XP11 version (I don't have XP11 any more)?

Also there appears to be an extra flap position. After selecting 'flaps down 1 notch' from the UP position, the flap moves slightly and the flap indicator shows the flap indicator needle at the bottom of the upper-most flap position range marker. Another 'flaps down 1 notch' from that position then gives you the TO position. It's the same when moving the flaps back up from the Landing position to Clean. Is this correct?

Thanks

[[LOGGED 0002277] Three Monitor Checklist Issue]

Hi Guys,

I thought this may have been fixed in the XP12 update, but it still exists with multiple monitors (3) in native XP multi-monitor mode. It would be really helpful to have this one sorted.

Thanks

[AP randomly dissengages]

I noticed with my Honeycomb Bravo that if I just slightly nudge the Bravo trim wheel it will disconnect the AP - as it is supposed to. Make sure you don't have the trim wheel set to change the trim and just use the Yoke electric trim switches.

[CL650 GNSS difference]

10 hours ago, Tom Tom said:

Hey 

I own the CL650 version 1.6.1 and have a problem with the altitude display when flying online.
With the setting e.g. FL390 the Gnss shows me a FL420.
So I always get problems with the air traffic controller.
The selected QNH is on standard 1013 /29.92.
On the ground, the deviation is not so great. e.g. LSZS GNSS ALT 5600 FT and GNSS HT 5760FT.
Satellites 8 / SVC in use EGNOS 

Who can help me here?

• sincerely
• Tom
•  

If I recall correctly, there is a topic that covers this exact issue - I think you have to turn Temp Compensation off from the FMC Menu (2nd page).

[INSTALLED NEWS TBM 900 HOTSTART - WHEN I START TO SELECT AIRCRAFT TBM 900 - THE PC CRASHES COMPLETELY]

3 hours ago, garmin said:

 

INSTALLED NEWS TBM 900 HOTSTART - WHEN I START TO SELECT AIRCRAFT TBM 900 - THE PC CRASHES COMPLETELY 

ALL OTHER AIRCRAFTS WORK PERFECT ONLY TBM 900 CRASHES AFTER INSTALLING THE NEWES DOWNLOAD 1.3.

 

 

Hardware Overview:

 

  Model Name: iMac

  Model Identifier: iMac11,2

  Processor Name: Intel Core i5

  Processor Speed: 3.6 GHz

  Number of Processors: 1

  Total Number of Cores: 2

  L2 Cache (per Core): 256 KB

  L3 Cache: 4 MB

  Memory: 4 GB

  Boot ROM Version: 99.0.0.0.0

  SMC Version (system): 1.64f5

  S

  Hardware UUID: 3CCBA74D-5110-5B5C-8F7C-EFE6DFDD18D0

Mate - the first thing you need to supply is your XPlane log.txt file located in the XPlane root folder.

[Crash when Entering FMS Fix Data]

22 hours ago, Pils said:

That helps, thanks. But now we know that we need to know exactly what the flight plan looked like, as it sound like it crashed while determining the Lat/Lon of the intercept point.

Hi Pils , thanks for the quick response.

I was flying the DOSEL1 SID from RW16 at YMML direct to the RIVET3 STAR for RW25 at YSSY. I was either on the STAR or just before it when the crash occurred. I had no waypoints between the SID and the STAR as it was just a quick flight - didn't muck around with SimBrief.

Thanks - hope this helps.

[Crash when Entering FMS Fix Data]

2 hours ago, Pils said:

Please provide details of exactly what was entered prior to the crash. Thanks.

 

2 hours ago, Pils said:

Please provide details of exactly what was entered prior to the crash. Thanks.

Hi Pils,

I entered RW25 as the fix and I entered 070 degrees as the radial. I selected the LSK1L key to copy RW25 to the scratch pad to create a new fix as a 10nm circle around the fix, and it crashed just after I pressed LSK1L to copy the fix to the scratchpad.

Hope this helps.

CL650_Log.txt

[Crash when Entering FMS Fix Data]

Had another crash when entering fix data for RW25 at YSSY. Backtrace implicates the CL650 and Windows. Log attached.

Log.txt

[Collins Proline Joystick Functionality]

16 hours ago, Pils said:

They’re basically used for creating Place-Bearing-Distance waypoints in your flight plan. Or for getting the GPS coordinate of a location (press down one of the knobs if I remember correctly) to create a custom data base waypoint in the FMS.

Your spot-on. If you draw the vector with the joystick and then go to the Pilot Waypoint Database you can enter the Co-ords, give it a name and then use it as any other waypoint.

Thanks again

[Collins Proline Joystick Functionality]

8 hours ago, Pils said:

They’re basically used for then creating Place-Bearing-Distance waypoints in your flight plan. Or for getting the GPS coordinate of a location (press down one of the knobs if I remember correctly) to create a custom data base waypoint in the FMS.

Thanks mate. I’ll give it a go. 

[Multiple FMOD errors]

1 hour ago, wakevortex said:

I have recently been getting the x plane log filling up with FMOD errors when flying the current update  of the challenger -like below ,but many more 

0:04:07.079 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel.
0:04:07.100 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel.
0:04:07.116 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel.
0:04:07.131 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel.
0:04:07.146 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel.
0:04:07.160 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel.
0:04:07.175 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel.
0:04:07.191 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel.
0:04:07.207 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel.
0:04:07.223 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel.
0:04:07.237 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel.
0:04:07.252 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel.
0:04:07.267 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel.
0:04:07.282 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel.
0:04:07.297 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel.
0:04:07.311 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel.
0:04:07.326 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel.
0:04:07.340 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel.
0:04:07.355 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel.
0:04:07.369 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel

Is this connected to the challenger or is it coming from something else?
Its only there when the C650 is loaded... 

any help appreciated

Bill P

 

I have also had these errors on a CL650 crash. 

[Collins Proline Joystick Functionality]

HI guys,

I am aware that the Collins Proline joystick can be used for manipulating the Charts, but does anyone know of uses for the vectors it can draw on the MFD - see screen shot?

Thanks

[Xplane freezes with the CL 650]

4 hours ago, ois650 said:

Thanks for your feedback, Cam. 

Your most welcome. 

[Xplane freezes with the CL 650]

On 6/24/2022 at 10:03 AM, max4life said:

After reaching altitude or a little ther after Xplane Freezes. Its the only plane that freezes xplane that I have 

Log.txt 2.86 MB · 1 download

I was having the same issue, and for me it was the custom mesh I was using from Alpilotx. I have removed them and it seems ok so far. I also disabled SAM in Traffic Global as suggested in another topic.

[[LOGGED 0002277] Three Monitor Checklist Issue]

On 6/23/2022 at 9:49 AM, N330CT said:

Frustrated to see now three updates later this still has not been addressed.  While I would never claim to know what it takes to fix or program anything on this amazing plane it is hard to understand why “implementing GPS jamming simulation” is more important then customers with more then one monitor not being able to read the menus.  I can’t even put oil in the plane without turning off my other monitors so the menus and click spots work. This was logged in January. 

I have the same issue as well. Also have an issue with Avitab in the WFB using multiple monitors and the passenger lighting screen in the galley. 

[MFD Plan View Anomaly]

4 hours ago, Cam said:

 

Ok thanks. I’m about to fly now so will give it a go. 

Yep. All good now. That worked. Thanks. 

[MFD Plan View Anomaly]

3 hours ago, Pils said:

Looks like you’re still in PLAN mode and it’s centred on a waypoint or airport from an earlier part of the flight plan? It doesn’t automatically follow the plane unless you manually centre it on the plane with the MFD ADV page on the CDU.

 

3 hours ago, Pils said:

Looks like you’re still in PLAN mode and it’s centred on a waypoint or airport from an earlier part of the flight plan? It doesn’t automatically follow the plane unless you manually centre it on the plane with the MFD ADV page on the CDU.

Ok thanks. I’m about to fly now so will give it a go. 

[MFD Plan View Anomaly]

On 6/20/2022 at 6:53 PM, Cam said:

I was flying along checking my Summary pages on the pilot's MFGD, and when I reverted back to Plan view I noticed that the MFD showed the aircraft symbol way off center - outside the outer range ring. Copilot's MFD and Pilots PFD were ok, as shown in the pic.

Hi guys, does any one know whether this is something I am doing wrong or its a bug?

[PFD Artifact/Anomoly]

On 6/21/2022 at 9:29 PM, rjb4000 said:

Ahh - great. The FPV is half off the field of view so I couldn't work out what it was. Given I had a 105kn cross wind I can understand why. Thanks heaps for the clarification.

[PFD Artifact/Anomoly]

I noticed this strange artifact on the PFD the other day. Not sure how or when it got there, as I didn't notice it immediately. It hasn't reappeared yet.

[[FIXED? 3138] fctl_get_hinge_torque]

13 minutes ago, ois650 said:

Interesting backtrace, just cruising and it crashed or were you doing anything in particular?

 

Just cruising I think, although I could have been checking the summary pages or FMS progress page. 
I added 2 more logs (total of 4) and I was actually just cruising on the exact same flight plan (I was having dinner). 

[[Intended Behaviour] TCAS ALT LIMITS]

11 minutes ago, ois650 said:

This is intended and most operators use ABV/BLW mode. 

Ahhh. Interesting. Thanks mate. 

[MFD Plan View Anomaly]

I was flying along checking my Summary pages on the pilot's MFGD, and when I reverted back to Plan view I noticed that the MFD showed the aircraft symbol way off center - outside the outer range ring. Copilot's MFD and Pilots PFD were ok, as shown in the pic.