jmoss

UPDATE Feb 3, 2022: Sorry for not posting an update sooner as I haven't had a chance the past several days. I've successfully loaded the challenger twice since several days ago without a hitch So my hunch on a botched graphics drivers I believe was on point. I've yet to try career mode since I've purchased the CL650. I still want to test that too, but have a feeling all should be good as well there as well. If anything changes, I'll post another update of course. I need to look at which version I have installed right now. I think it's the optimized for 6gig vram vs 8 and above. It still looks great. I still may try the threading performance shortcut just to compare, but hyperthreading is off in my bios, so don't know if this will override that setting or not? I know process lasso won't. Best, Jeff

UPDATE: Please hang in with me here as it may help others with this specific loss of Vulkan device errors, not other CTD's. Off topic a bit, but since the Challenger was the only plane with Vulkan crashes, I just wanted to be helpful here. First, I got the Challenger to load and in the middle of a short hop. (hopefully not jinxing myself) Below are my findings and possible reasoning with explanation and a windows 10 users warning for those that ever have to do what I did and avoid issues. Today I decided that there must be a graphics driver issue. I noticed every time a flight would load, default plane or not, especially daytime, there was a huge lag with shadows loading right away and low FPS for up to 40 plus seconds, then it would go up to normal, plus stuttering when panning. When I updated the drivers yesterday, stupid tech savvy me did not use add/ remove programs like I used to do in Windows7. It's been so long, I forgot that step. I just did clean install on top of it and it didn't help any. Plus xplane would crash every time I go to quit since then. For what it's worth, it was causing issues before that as I used to have reshade installed and that really botched things up... that's for another forum and another day. Anyway, I tried booting into safe mode for the first time since changing to Windows 10, to use a DDU uninstaller of remnants files to insure a clean installation of the graphics driver. Hang in with me here as this is very important! I then got no display but a black screen after attempting to boot into safe mode....and the computer was completely useless for hours of troubleshooting and almost a meltdown after reading what could have gone wrong, but nothing I attempted worked. If you're using a pci express graphics card on windows 10, MAKE 100% SURE that if you have an integrated card on your MB... ( I think most have it if I'm not mistaken ) ...and that it as NOT disabled before doing anything. If nothing is hooked up to to the integrated port, and using the high end card instead that is hooked up, there apparently is no issues or conflicts. Thankfully, I did not have it disabled!! Otherwise, you can't see anything and completely dead in the water. After many, many hours of searching the web and lots of dead ends, I turned the system off and moved my monitor to the integrated port and was able get the display back. Huge sigh of relief! Im sure it doesn't happen to everyone, but you never know. Anyway, I reinstalled the latest driver again. After rebooting and loading Xplane, I successfully loaded the Challenger! I noticed marked performance improvement...FPS 40's to 62, no stuttering overall. and loading doesn't have that lag like before now with Shadows or FPS loading at first. I strongly believe the Vulkan was messed up due to a lag when first loading an aircraft before all of this, timing out and causing a crash as the drivers were messed up. I'm in the middle of a short flight... I will see what happens. I will report back. I was so mad at myself as I should've known better. Plus windows 10 is a different animal and does what it wants that's completely unexpected. Always do your due diligence and make certain that the info you get is spot on from those who are in the know or troubles will get worse. Sorry a bit off topic, but I got a flight loaded. if it continues to work, I'll be grateful over and beyond. I just think due to the complexity of this product and the loading of so many items is why it wouldn't give Vulkan a chance due to the corrupt driver conflicts in windows. I will report back as I said when I have time to test perhaps tomorrow sometime. Thanks for reading and to the support staff. Off to hopefully land at KTPA soon without issue. Apologies for the long post. Best, Jeff

This evening I tried what you had suggested. First removed the CL650 folder from the xplane output folder. Result: same error messenger I then installed latest version. Optimized for 8gig or over as I have a TitanX Nividia 12gig GPX card. Result: it loaded, but horrible stuttering when panning with all systems off. So I preceded to installing the 6gig or under to see. Result: same error message upon loading that version. I also ran the xplane 11 installer to update to see if anything was missing. It only asked to overwrite some runway textures. I've also removed: fluwithlua / better pushback / sky max pro/ real weather connector / 3j cabin sounds ( not used in your product) I don't use many plugIns otherwise. I reloaded xplane and same result, but the log shows basically the same message. I really need to upload that tomorrow. Maybe you'll see something I missed? Very frustrated after many hours of trying. I'm sure there will be a solution at some point. Why it loaded ok once is strange since I follow the same routine every time. Thanks in advance for all you guys do to help everyone. If it was a $30.00 product, it would be easier to let it go, plus the fact, this release is over the top for X-Plane11. I'll wait to hear more suggestions. I may install a vanilla install on an external drive and see what happens, but I am skeptical for now. If it does work, I shuttle that over and reinstall all the add on aircraft and one plugin at a time. Best, Jeff

Thanks much for the reply. I'll give it a go. I also installed new updated Nvidia drivers a today to see if that was part of the issue. I'll test this evening and report back results. This one is puzzling to me for sure. Best, Jeff

Hi Gents, After installing the new version 1.1.0 today, all of a sudden I get CTD's either after the start up screen for the product comes up ( where I choose career or cold and dark) the X-plane background behind Greys out. ... then I just keep get an error box that says vulkan has lost connection and xplane will close. Otherwise, it just CTD's See screen shot is below I did turnoff vulkan and got the plane to load , but the performance lacks so can't use the product smoothly. I tested my other hot start products TBM900 and also the Saab340. They load perfect without issue with Vulkan turned on as well as all of my add ons after testing all evening. I am at a loss. I also reinstalled the original release version of the CL650 and let it do it's uninstall / reinstall. That version also now CTD's every time. I miss her and would to get her back in the air again. Incredible product and so well designed. It's late so I can perhaps upload my log tomorrow. Thanks in advance for any help you can provide. I hope this is a bug that reared it's ugly head that wasn't picked up before the update came out. Best, Jeff

Hi gentlemen, I installed the hotfix, then reloaded the aircraft. I did a different flight than before when I had issues from KFKL- KMCO not following the LNAV. I flew KPDX - KSEA tonight as time was tight. The FMC followed my plan perfectly, even though it was simple... No SID from KPDX, just the STAR going into KSEA. Also handled the ILS 34R at KSEA flawlessly! Only went up to FL125 as it was a short hop. Logic seems much improved. I will try the KFLL-KMCO flight I originally had issues with tomorrow. Guys, keep up the great, fantastic, incredible work that you are doing! The amount of things that you squeezed into this hotfix is much more than anyone would expect in such a short period of time since release. I'm sure there are more issues out there, but what a great start. I immensely enjoyed my flight this evening. Thank you guys! Sincerely, Jeff

i am noticing this as well. When on the ground, evertime i move the throttles up and back down it happenes. When in the air ( I have FPS counter on... example...it fluctuates from 70 and drops to low 60's, high 50's, then back to 70 every two seconds. Actually depends what area I'm in as far as the higher fps is concerned. Best, Jeff

Philipp, Just saw your reply now. Thanks much for the info. Much appreciated! Best, Jeff

Hi Rydent1, Would you be so kind to tell me what you did? What file did you have to open, and what dater editor did you use?? I would love to fix things as they are driving me nuts! Thanks in advance. EDIT: I figured it out part of it. Downloaded Dataref editor, placed into my plugins folder, loaded the CRJ200 then opened the plugin, then scrolled until I found the avionics "EQ=0 and changed to a 1. All is good, only except when I reload the CRJ, it defaults back to off again. Is there a way of permanently saving the setting? Best Jeff