|
Post by Travis on Dec 24, 2013 1:24:06 GMT -5
Thanks Captains.
If this continues to occur for anyone, I would suggest a three step process.
1. Make a backup of your externals.cfg file (literally just go to Windows Explorer and do a copy / paste as "Copy of....." 2. Load your externals.cfg file into a text editor and remove the text lines for the weather engines that you do not own/use. 3. Post or email us with the lines that you removed, along with any improvement or adverse effects that you observed after making the edits in #2.
I'm thinking there's a reference in some version of Windows that is "okay" for some, but which causes a CTD for others. It's odd, but with your help we can track it down.
|
|
|
Post by Tjeuten on Dec 24, 2013 10:45:11 GMT -5
Doesn't work for me either. It CTD.
Have tried to put a semicolon in front of all lines in externals.cfg, doesn't work.
Have deleted all lines but ASNext (ASNext is installed on client laptop, not on FSX gaming "server"), still CTD.
Using Windows 7 64, English.
This is my event viewer log:
Faulting application name: Admin.exe, version: 0.7.0.11, time stamp: 0x52b0d760 Faulting module name: USER32.dll, version: 6.1.7601.17514, time stamp: 0x4ce7ba59 Exception code: 0xc0000005 Fault offset: 0x000385c4 Faulting process id: 0x1ff8 Faulting application start time: 0x01cf00bda0eb4117 Faulting application path: D:\Games\FSX\FSCaptain\Bin\Admin.exe Faulting module path: C:\Windows\syswow64\USER32.dll Report Id: fa715315-6cb0-11e3-9534-002683144921
|
|
|
Post by Travis on Dec 24, 2013 11:41:49 GMT -5
Wow. And I have the same version of USER32 and everything. So that blows my last theory right out of the water. I can tell that you're not running FSX inside of a "protected" folder such as Program Files, so asking for you to run as an administrator likely wouldn't matter. Until Dutch or I can make this happen (to give Dutch a target to code against) I can only recommend that if pressing the Weather Options button causes a CTD... then don't press it. Here are the corresponding lines in your profile.cfg that are tied to that dialog - just take care when hand-editing: METARTYPE=Opus METARDATA=C:\OpusFSX\Themes\OpusWeather.txt METARFORMAT=2 METARSOURCE=0 METARSHOW=1 METARSTALE=2 HAZARDICE=1 HAZARDRWY=1 HAZARDCB=1 HAZARDDEICE=1
|
|
|
Post by Dan on Dec 24, 2013 23:17:11 GMT -5
I tried:
- emptying the file, - commenting out lines - leaving only ASN in - leaving only OPUS in (that's what I use) with the correct path to the weather file - running the Admin binary as administrator
Nothing worked for me so far.
Dan
|
|
|
Post by pracines on Dec 25, 2013 2:50:40 GMT -5
Well I can add that the weather options work fine from my FSX directory but it CTD's from my P3DV2 directory. I did place the ; in front of all the weather apps I don't use, and I corrected the directory entries of the programs I do use- this method worked fine in FSX but not in P3D. The fact that there are no current weather programs that correctly function in P3D V2 may be the reason why this happens to me(?). I have a habit of running everything as ADMIN and I have UAC totally off.
ActiveSky 2012,%appdata%\HiFi\AS2012\Weather\current_wx_snapshot.txt,AS2012,0 ;ActiveSky 6.5,%fs%\Modules\ASv6\current_wx_snapshot.txt,ASV6,0 ;ActiveSky Evolution,%appdata%\HiFi\ASE\Weather\current_wx_snapshot.txt,ASE,0 ActiveSky Next,%appdata%\HiFi\ASNFSX\Weather\current_wx_snapshot.txt,ASN,0 FS Global Real Wx,C:\FSGRW\data\exchange\common\current_weathercomplete.txt,FSGRW,0 ;FS Real Wx,(enter pathname to FSRealWx METAR file here),FSRealWX,0 ;Opus,%programfiles%\OpusFSX\Themes\OpusWeather.txt,Opus,0 ;Real Environment Extreme,C:\REX\METAR,REX,1 REX Essential Plus,C:\REX Essential Plus\MetarXML\metar_report.xml,REXe,0
description Faulting Application Path: C:\Prepar3D v2\FSCaptain\Bin\Admin.exe
Problem signature Problem Event Name: APPCRASH Application Name: Admin.exe Application Version: 0.7.0.11 Application Timestamp: 52b0d760 Fault Module Name: USER32.dll Fault Module Version: 6.1.7601.17514 Fault Module Timestamp: 4ce7ba59 Exception Code: c0000005 Exception Offset: 000385c4 OS Version: 6.1.7601.2.1.0.256.1 Locale ID: 1033 Additional Information 1: 0a9e Additional Information 2: 0a9e372d3b4ad19135b953a78882e789 Additional Information 3: 0a9e Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
Windows Ultimate 64 bit SP1 FSX ACC w/ FSUIPC 4927b Prepar3D V2 (2.0.9448.0)
Processor Intel(R) Core(TM) i7-3970X CPU @ 4.30 GHz Memory (RAM) 32.0 GB Graphics NVIDIA GeForce GTX 690 Total available graphics memory 4096 MB Display adapter driver version 9.18.13.3193
|
|
|
Post by Travis on Dec 25, 2013 14:56:12 GMT -5
The fact that there are no current weather programs that correctly function in P3D V2 may be the reason why this happens to me(?). Opus seems to work fine with P3D - no awful OAT temps or anything. This is still awfully puzzling. I know Dutch has moved this to the top of the list as far as bugs go. I've come up with one other daffy idea... could you ZIP and email us your externals.cfg file. I need it Zipped so it's as pristine as it is on your system. Merely posting it directly won't do. It's a long shot to be honest, but since we apparently have similar systems, I have to look for what could even remotely possibly be different.
|
|
|
Post by pracines on Dec 25, 2013 16:36:29 GMT -5
Hi Travis,
I just sent you an email.
Paul
|
|
|
Post by Travis on Dec 26, 2013 12:48:53 GMT -5
Just updating everyone that we're ruling out more and more things. Paul's files work well on my system, so there's less and less straws to grasp.
|
|
|
Post by okupton on Jan 2, 2014 23:28:13 GMT -5
Ok I am in Ecuador, have windows 7 Ultimate which was originally in Spanish, but I have it set to English format United States now using a windows language pack. Your suggestion of using the semicolon in front of the different weather engine lines in the externals.cfg didnt work for me. Im using ASN. I also tried eliminating all lines except the ASN line with no luck. Here's my externals.cfg
ActiveSky 2012,%appdata%\HiFi\AS2012\Weather\current_wx_snapshot.txt,AS2012,0 ActiveSky 6.5,%fs%\Modules\ASv6\current_wx_snapshot.txt,ASV6,0 ActiveSky Evolution,%appdata%\HiFi\ASE\Weather\current_wx_snapshot.txt,ASE,0 ActiveSky Next,%appdata%\HiFi\ASNFSX\Weather\current_wx_snapshot.txt,ASE,0 FS Global Real Wx,%programfiles%\FSGRW\data\exchange\common\current_weathercomplete.txt,FSGRW,0 FS Real Wx,(enter pathname to FSRealWx METAR file here),FSRealWX,0 Opus,%programfiles%\OpusFSX\Themes\OpusWeather.txt,Opus,0 Real Environment Extreme,C:\REX\METAR,REX,1 REX Essential Plus,C:\REX Essential Plus\MetarXML\metar_report.xml,REXe,0
The crash report Im getting is: Faulting application name: Admin.exe, version: 0.7.0.11, time stamp: 0x52b0d760 Faulting module name: USER32.dll, version: 6.1.7601.17514, time stamp: 0x4ce7ba59 Exception code: 0xc0000005 Fault offset: 0x000385c4 Faulting process id: 0x1d24 Faulting application start time: 0x01cf083ad0a0418e Faulting application path: D:\FSX\FSCaptain\Bin\Admin.exe Faulting module path: C:\Windows\syswow64\USER32.dll Report Id: 1060f6d2-742e-11e3-9a5e-e840f2c1fe15
|
|
|
Post by okupton on Jan 3, 2014 9:16:13 GMT -5
Ok figured it out. Had recently reinstalled FSC from scratch and had forgotten to register the product in the ADMIN. All running fine now. So, for me in Demo mode, the ADMIN crashes upon selecting weather options, but works once registered. Hope this info helps someone
|
|
|
Post by Travis on Jan 3, 2014 9:21:19 GMT -5
For me, switching back to the demo mode didn't affect my Admin, but thanks for providing another odd piece of this puzzle - as well as thanks for hanging in there!!
|
|
|
Post by okupton on Jan 3, 2014 11:17:05 GMT -5
Happy to help. Flying now from paris to philly and FSC is working perfectly.
|
|
|
Post by Marco Manieri on Jan 4, 2014 18:55:09 GMT -5
Hi there,
exactly the same issue. Brand new purchase of FSCaptain and download.
Windows 7 Home Premium 64 Bit - Italian
Kept crashing putting the semicolon in front of each line in the Externals.cfg, leaving only the ASN line and also leaving it empty and with all line prefixed with the semicolon!
This is a crash report from the utility "AppCrash View":
Version=1 EventType=APPCRASH EventTime=130333526776981121 ReportType=2 Consent=1 ReportIdentifier=2b833c11-759a-11e3-812b-08606e87f286 IntegratorReportIdentifier=2b833c10-759a-11e3-812b-08606e87f286 WOW64=1 Response.type=4 Sig[0].Name=Nome applicazione Sig[0].Value=Admin.exe Sig[1].Name=Versione applicazione Sig[1].Value=0.7.0.11 Sig[2].Name=Timestamp applicazione Sig[2].Value=52b0d760 Sig[3].Name=Nome modulo con errori Sig[3].Value=USER32.dll Sig[4].Name=Versione modulo con errori Sig[4].Value=6.1.7601.17514 Sig[5].Name=Timestamp modulo con errori Sig[5].Value=4ce7ba59 Sig[6].Name=Codice eccezione Sig[6].Value=c0000005 Sig[7].Name=Offset eccezione Sig[7].Value=000385c4 DynamicSig[1].Name=Versione SO DynamicSig[1].Value=6.1.7601.2.1.0.768.3 DynamicSig[2].Name=ID impostazioni locali DynamicSig[2].Value=1040 DynamicSig[22].Name=Informazioni aggiuntive 1 DynamicSig[22].Value=0a9e DynamicSig[23].Name=Ulteriori informazioni 2 DynamicSig[23].Value=0a9e372d3b4ad19135b953a78882e789 DynamicSig[24].Name=Ulteriori informazioni 3 DynamicSig[24].Value=0a9e DynamicSig[25].Name=Ulteriori informazioni 4 DynamicSig[25].Value=0a9e372d3b4ad19135b953a78882e789 UI[2]=E:\FSX\FSCaptain\Bin\Admin.exe UI[3]=Adminstrator for FSCaptain ha smesso di funzionare UI[4]=Windows: รจ possibile ricercare online una soluzione al problema. UI[5]=Cerca una soluzione online e chiudi il programma UI[6]=Cerca una soluzione online in seguito e chiudi il programma UI[7]=Chiudi il programma LoadedModule[0]=E:\FSX\FSCaptain\Bin\Admin.exe LoadedModule[1]=C:\Windows\SysWOW64\ntdll.dll LoadedModule[2]=C:\Windows\syswow64\kernel32.dll LoadedModule[3]=C:\Windows\syswow64\KERNELBASE.dll LoadedModule[4]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.18201_none_ec80f00e8593ece5\COMCTL32.dll LoadedModule[5]=C:\Windows\syswow64\ADVAPI32.dll LoadedModule[6]=C:\Windows\syswow64\msvcrt.dll LoadedModule[7]=C:\Windows\SysWOW64\sechost.dll LoadedModule[8]=C:\Windows\syswow64\RPCRT4.dll LoadedModule[9]=C:\Windows\syswow64\SspiCli.dll LoadedModule[10]=C:\Windows\syswow64\CRYPTBASE.dll LoadedModule[11]=C:\Windows\syswow64\GDI32.dll LoadedModule[12]=C:\Windows\syswow64\USER32.dll LoadedModule[13]=C:\Windows\syswow64\LPK.dll LoadedModule[14]=C:\Windows\syswow64\USP10.dll LoadedModule[15]=C:\Windows\system32\WSOCK32.dll LoadedModule[16]=C:\Windows\syswow64\WS2_32.dll LoadedModule[17]=C:\Windows\syswow64\NSI.dll LoadedModule[18]=C:\Windows\syswow64\WININET.dll LoadedModule[19]=C:\Windows\syswow64\api-ms-win-downlevel-user32-l1-1-0.dll LoadedModule[20]=C:\Windows\syswow64\api-ms-win-downlevel-shlwapi-l1-1-0.dll LoadedModule[21]=C:\Windows\syswow64\shlwapi.DLL LoadedModule[22]=C:\Windows\syswow64\api-ms-win-downlevel-version-l1-1-0.dll LoadedModule[23]=C:\Windows\system32\version.DLL LoadedModule[24]=C:\Windows\syswow64\api-ms-win-downlevel-normaliz-l1-1-0.dll LoadedModule[25]=C:\Windows\syswow64\normaliz.DLL LoadedModule[26]=C:\Windows\syswow64\iertutil.dll LoadedModule[27]=C:\Windows\syswow64\api-ms-win-downlevel-advapi32-l1-1-0.dll LoadedModule[28]=C:\Windows\system32\WINMM.dll LoadedModule[29]=C:\Windows\syswow64\COMDLG32.dll LoadedModule[30]=C:\Windows\syswow64\SHELL32.dll LoadedModule[31]=C:\Windows\system32\IMM32.DLL LoadedModule[32]=C:\Windows\syswow64\MSCTF.dll LoadedModule[33]=C:\Windows\syswow64\ole32.dll LoadedModule[34]=C:\Windows\system32\Secur32.dll LoadedModule[35]=C:\Windows\system32\profapi.dll LoadedModule[36]=C:\Windows\system32\api-ms-win-downlevel-advapi32-l2-1-0.dll LoadedModule[37]=C:\Windows\syswow64\api-ms-win-downlevel-ole32-l1-1-0.dll LoadedModule[38]=C:\Windows\system32\mswsock.dll LoadedModule[39]=C:\Windows\system32\uxtheme.dll LoadedModule[40]=C:\Windows\System32\wship6.dll LoadedModule[41]=C:\Windows\system32\IPHLPAPI.DLL LoadedModule[42]=C:\Windows\system32\WINNSI.DLL LoadedModule[43]=C:\Windows\system32\dwmapi.dll LoadedModule[44]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\comctl32.DLL LoadedModule[45]=C:\Windows\system32\NLAapi.dll LoadedModule[46]=C:\Windows\system32\napinsp.dll LoadedModule[47]=C:\Windows\system32\pnrpnsp.dll LoadedModule[48]=C:\Windows\system32\DNSAPI.dll LoadedModule[49]=C:\Windows\System32\winrnr.dll LoadedModule[50]=C:\Windows\System32\fwpuclnt.dll LoadedModule[51]=C:\Windows\system32\rasadhlp.dll LoadedModule[52]=C:\Windows\System32\wshtcpip.dll LoadedModule[53]=C:\Windows\syswow64\OLEAUT32.DLL FriendlyEventName=Ha smesso di funzionare ConsentKey=APPCRASH AppName=Adminstrator for FSCaptain AppPath=E:\FSX\FSCaptain\Bin\Admin.exe
|
|
|
Post by Travis on Jan 4, 2014 18:58:45 GMT -5
Thanks,
I think Dutch has a good handle on what's happening here. He's been busy the last few days on bug fixing - and we should expect a new build by mid next week to address this and a few other issues.
|
|
|
Post by Marco Manieri on Jan 4, 2014 19:03:28 GMT -5
Ahhhh...
I've manually edited my profile.cfg as per previuso post:
METARTYPE=Opus METARDATA=E:\OpusFSX\Themes\OpusWeather.txt METARFORMAT=2 METARSOURCE=0 METARSHOW=1 METARSTALE=2 HAZARDICE=1 HAZARDRWY=1 HAZARDCB=1 HAZARDDEICE=1
And now no more CTD!
|
|