Mandretti

And I’ve stopped using this product as I’m tired of spending 30-45 prepping a flight only to have it CTD every time.

Yeah the log file is exactly the same every time. Mrogers0547 has the last log entry - waas related. I’ve never seen another problem with a CTD where the last set of log entries are exactly the same. Not only for me, but others as well. The fact that the developers dismiss that clue as coincidental does not make any sense. I understand that it doesn’t provide a lot of info but it seems like a good place to start.

Warning - rant coming. Abandoning CL650 - too many CTDs and other issues. Just really tired of spending hours setting up flights only to CTD at some point. Yes - pulled plugins, yes reverted NVIDIA driver, yes updated NVIDIA driver, yes posted on Discord, yet posted on X-Pilot, yes pulled custom scenery etc, no - nothing in XP log, no - nothing in Windows Event Viewer etc. This is a very expensive aircraft, and very well modeled, extremely realistic blah blah. Yes to all that - and bottom line - its not any fun with this ever-present issue. Spending way too much time troubleshooting. Really disappointing and frustrating. And given that this was about the only aircraft I was using on a regular basis in XP - probably done with XP too. Back to MSFS which has it's issues as well - but not like this. OK - done with rant. Feel much better.....

Yes. I'm trying a different NVIDIA driver, and removed all plugins. We'll see - but I'm interested if there was a solution for this. Be nice not to have to experiment for weeks trying different configurations.

I am having the same exact issue with every flight. Was there any resolution on this.

I removed plugins and scenery and still getting the same CTDs with the same ending WAAS data download in the log.

Here's another CTD log. Again, WAAS weather updating is the last thing. Log.txt

I've had two CTDs in the last couple of days, and looking at the xp12 logs they have similar endings - with the last processes related to Vulkan handling new WAAS downloaded weather. At the time of the crashes I've been in the FMC setting things up - I believe this last time was working with PERF INIT, flight plan entered, things pretty much ready to go. I have not yet removed all the plugins as I thought this information could be useful in and of its own. I am using ORBX NoCal TrueEarth HD scenery for this flight. I will remove the custom scenery and see if that resolves the issue. I think my previous CTD flight was also in an ORBX TrueEarth scenery area. CurFlow: Lighter Aircraft SW wind NewFlow: Jets+Larger NW wind 2023-06-11 17:18:35 CL650[waas_api.c:193]: WAAS API data download successful 0:12:07.601 I/RWX: WEATHER UPDATE at zulu-time 1686528531 0:12:59.934 I/GFX/VK: Surface formats for surface: 0:12:59.934 I/GFX/VK: VK_FORMAT_B8G8R8A8_UNORM 0:12:59.934 I/GFX/VK: VK_FORMAT_B8G8R8A8_SRGB 0:12:59.934 I/GFX/VK: VK_FORMAT_R16G16B16A16_SFLOAT 0:12:59.934 I/GFX/VK: VK_FORMAT_A2B10G10R10_UNORM_PACK32 0:12:59.934 I/GFX/VK: VK_FORMAT_A2B10G10R10_UNORM_PACK32 0:12:59.934 I/GFX/VK: Surface 0000021BEBFDABA0: 0:12:59.934 I/GFX/VK: minImageCount 2: 0:12:59.934 I/GFX/VK: maxImageCount 8: 0:12:59.934 I/GFX/VK: supportedUsageFlags 9f: 0:12:59.934 I/GFX/VK: supported modes: 0:12:59.934 I/GFX/VK: VK_PRESENT_MODE_MAILBOX_KHR: 0:12:59.934 I/GFX/VK: VK_PRESENT_MODE_IMMEDIATE_KHR: 0:12:59.934 I/GFX/VK: VK_PRESENT_MODE_FIFO_KHR: 0:12:59.934 I/GFX/VK: VK_PRESENT_MODE_FIFO_RELAXED_KHR: 0:12:59.934 I/GFX/VK: Created swapchain for 0000021B4B292850 with size { 663x883x3 }. Mode: VK_PRESENT_MODE_MAILBOX_KHR 0:12:59.934 I/wmgr: Re-building fbos for window 0000021B467BDF20 using pool 6 0:13:04.127 I/GFX/VK: Cleared memory pool 6, allocations: 1, block bytes: 4759552 Log.txt

Thank you!

I've been away from this ac for several months and coming back into it there are some issues. First, I'm immediately in the cockpit - skipping the FBO. I'm getting an audio warning on start up to check the script quarantine, and a visual message about a sound file. And nothing is operational in the cockpit. I'm thinking a re-install is in order for this XP12 version. If so, can someone provide a link to info about the correct way to reinstall the product. And of course if there's a solution without requiring a reinstall I'm all ears... Edit: Looks like there are a lot of LUA scripts disabled, and a 650 script in quarantine. I'm concerned that I just delete the CL650 Aircraft directly and re-run the install that this will not get cleaned up. But perhaps I will be enlightened in a reply to the post. Thanks in advance!

Thank you!

That wasn't the issue. In fact I never figured out what was going on and haven't had the problem for a while. I suspect it had something to do the the A/T. And in this AC the difference between V1 and Vr is very small in my experience and by the time you actually get some lift from pulling on the yoke, you're well past Vr even if you start at V1.

No - but I haven't looked at this in a bit. I'll check it out again.

Thank you!

Thanks for your help. Yeah I've poked around the cockpit looking for another light control and haven't found anything that makes a difference for that. It's not visible during the day without zooming in within a few inches of the display. At night it's better.

No problem! So none of the three rotary knobs there increase the brightness of the ATS annunciator/indicator.

Once again I'm unable to properly execute a takeoff. Previously I had ice conditions that prevented a proper takeoff, this time TAT is 18 degrees so that's not it. V speeds are set and N1 TO. Takeoff starts normally, but my speed never gets beyond Vr and eventually I sink back onto the runway. I'm attempting to follow the FD pitch. You can see in the pic that the speed is set for 200. What's wrong with this picture? At takeoff the ATS indication is N1 TO - at the point I'm sinking it's N1 HOLD. I notice that in the Thrust Limit page there's nothing for climb or cruise. Is that the issue - and if so how do those get set. Thanks in advance!

I'm following the checklists so I believe so. But I'm working off of saved configurations so it's possible I'm not depending on which config I'm using. I'll check that. I'm assuming you're asking because if they are on they will shut off after start?

Thanks! Let me know if I should post separately - but when I'm getting ready to taxi the Gen 1 and Gen 2 CAS warnings come on. The switches are in the on position, so to clear CAS I turn off then on again. Not sure why this is happening. Also where do I config inHg/ hPa? How can I make the ATS indication brighter.

Poked around the FMC quite a bit, and the forums, and cannot find it. I remember seeing it in a video but don't want to watch hours of video to refresh my memory.

Ok - you are right. When I crashed the last time XP gave me a message that the aircraft was carrying ice at time of impact. When I look more closely at flight surfaces I do see ice now. And when I de-iced I was able to take off normally. Actually never seen ice before - now I know!

I do not see ice. There's no precipitation anywhere, the temp has been between 4-9 degrees. and its the afternoon. I cannot see any ice on the wings. And if I click the leading edge, I do not see a message on CAS, if that's where it's supposed to be. So you see any ice? Would ice account for the speed staying around 135 even with full throttle. I changed the XP weather to 15 degrees, no precipitation, still have the problem.

How do you check for ice contamination? And with an OAT of 4 degrees C on the ground how would you get ice?

OK I'm back...trying this once again.. At V1 call out I pull back on the yoke and the ac begins to climb but it never achieves the full climb and shortly falls back to the tarmac. The ATS indicator is live. The V speeds have disappeared, that may be normal. The PERF pages are all completed as far as I know, and the flight surface configuration looks good for TO and CAS show TO config OK. The ac speed never goes much above V1. I've attached a pic of the cockpit before initiating takeoff, and then a pic when I've crashed into the runway. Also Gen 1 and Gen 2 switch CAS indicators change to off either during taxi or on the runway. Not sure what that's about. The GEN switches are on. I do turn those back on before takeoff. I also am having an issue periodically when the ac is configured for TO, everything looks good, throttles forward, engines rev up, brakes off, and the ac will not move. EDIT: looks like my rudder brake pedals were somehow perceived as depressed even though they were not. Along these lines, my Honeycomb Alpha yoke is calibrated.