August 30, 201015 yr Author Yea, I stay away from the ground call buttons now . . . all you can do for now I suppose, don't imagine LVLD will spend much time looking for the issue after all of these years . . . Joe Porter
September 18, 201015 yr Hello,I am having CDT issue as well, yet quite reproducable. Each time I click on Ground Crew button after I initiated FS2Crew (first click on VSI - when it says that speech recogintion engine started) FSX crashes without warning. I have never had a crash when using Ground Crew button before I initiate FS2Crew.Here is the Event Viewer entry:Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3Faulting module name: ntdll.dll, version: 6.1.7600.16559, time stamp: 0x4ba9b29cException code: 0xc0000374Fault offset: 0x000cdc9bFaulting process id: 0xf3cFaulting application start time: 0x01cb5064394c72c5Faulting application path: D:\Microsoft Flight Simulator X\fsx.exeFaulting module path: C:\Windows\SysWOW64\ntdll.dllReport Id: eea3bd1f-bc57-11df-a598-001d6057ca62It doesn't look like FS2Crew is the faulting module, however as I said without initiating FS2Crew, Ground Crew Call works flawlessly.Can anybody confirm that? I am using Windows 7 64-bit and FSX SP2 (without Acceleration).And taking the opportunity: Bryan, I love your software. I have been flying recently no other plane, but my LD 767 with voice control.ThanksSebastian Cheers Sebastian
September 19, 201015 yr Commercial Member Hi Sebastian,The faulting module is 'ntdll.dll'. That's not an FS2Crew file, but rather a systems file.Did you read the previous replies in this thread.This is a known issue with the LDS 767 that also affects FSPassangers it seems.The solution appears to be this from another user, in quotes: Have you tried the uiautomationcore.dll fix by chance?I used to get CTDs with FSPax.And could get the Level D 767 to crash like clockwork with the Ground Call button.But then the HIGHMEMFIX was discovered, and I did the uiautomationcore.dll fix to stop random CTD when you try to access new windows or menu items. Have flown from Chicago to LAX and back again a few times with FSPax and FS2Crew Voice, with no crash.Cheers, B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
October 2, 201015 yr Hi Bryan,sorry for not responding for such a long time - been very busy at work.I know about these issues you mentioned:1. uiautomationcore.dll solved the problem with CTD when clickin/opening FSX top menu items too many times. I have it applied of course and since then have no issues with opening menus.2. HIGHMEMFIX solves the problem with disappearing textures when loading complex aircrafts on complex sceneries - FSX somehow seemed to be running out of memory and stopped loading some textures and eventually ended up with crash. I also have this tweak applied.Both of them have nothing to do with what I experience.Please do not get me wrong: I can finish all my flights without any problems and FS2Crew works perfectly for me (I never had mentioned "check, check" for example) as long as I do not touch overhead ground crew button.What I mean is that FS2Crew somehow seems to trigger the CTD when clicking Ground Crew: without FS2Crew initiated I never had a crash after click on ground crew, with FS2Crew initiated I always have a crash after click on ground crew.I just thought this might be reproducable by anyone else and then solution could be found easilyI also have completely different question: it is written in the documentation (page 57), that one of the captain duties during cruise is to inform Flight Attendants the aircraft is in cruise. How can I do this? Is there an appropriate voice command?Thanks a lotSebastian Cheers Sebastian
October 3, 201015 yr Commercial Member Hello Sebastian,The Ground Call CTD button appears to be a Windows 7 - Level D 767 issue, not an FS2Crew one.Please see this thread on the Level-D Support forum for more info:http://www.leveldsim.com/forums/forum_posts.asp?TID=21297&KW=ctd&PID=153741&title=solutiOn-ctd-ground-menu-windows7#153741Informing FA about being in cruise: It's a mistake in the manual. Please ignore it.Cheers, B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
December 6, 201015 yr Commercial Member Sorry to drag up an old thread, but...The error message quoted in this thread - as Bryan stated - is related to the ntdll.dll and fsx.exe, not the Level-D 767.I am running Win 7x64 and do not have any problems with CTD when using the GND CALL button.That leads me to believe this is system related.The link to ******* Altuve's fix is for those that may encounter the CTD when accessing the GND CALL button (again: if it was a LDS767 issue, then EVERYONE would encounter the problem, which is NOT the case).Hope you don't mind my intrusion, Bryan: just want to make sure users understand that the error is not universal and - all appearances and anecdotes to the contrary - not a specific LDS767 problem. The SUPPORT FORUM for Level-D Simulations products: http://www.leveldsim.com/forums
January 9, 201115 yr I speak English very little I have to run Win7 FSX Level D 767 .Problems engine plane to get an external electrical system shuts down when I press the button gorund reguest.What I can do about it I would be glad if you help me.
January 10, 201115 yr Commercial Member I speak English very little I have to run Win7 FSX Level D 767 .Problems engine plane to get an external electrical system shuts down when I press the button gorund reguest.What I can do about it I would be glad if you help me.Ozgurzorlu,I suggest asking/checking the Level-D support forum. It's not an FS2Crew issue.Best, B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
August 10, 201411 yr My solution was simple. I had the same problem with the ground request in Level D 767 and FS2Crew voice for Level D, it crashed my FSX every time. What I did was the following steps: 1- Uninstall fsx_sp2_ENU 2- Reinstall fsx_sp2_ENU 3- Uninstall FS2Crew for Level D voice 4- Reinstall FS2Crew for Level D voice, Run as administrator. That's it, my FSX is working fine. I hope this can work for every one.
Create an account or sign in to comment