• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

shapelib.dll crash - SBX 3.14

bdf369

bdf369

Messages
258
Country
us-california
I added a golf course polygon to my scenery. Every time I try to compile the terrain vector scenery, SBX crashes. Is anyone else seeing this? Appcrashview details below.

Thanks,
Barry

Version=1
EventType=APPCRASH
EventTime=130503403445824771
ReportType=2
Consent=1
UploadTime=130503403446245210
ReportIdentifier=a9f8005f-101a-11e4-826a-54271e6b76a7
IntegratorReportIdentifier=a9f8005e-101a-11e4-826a-54271e6b76a7
NsAppName=SBuilderX.exe
Response.BucketId=34224718d1ce5b17cd85be20dce11223
Response.BucketTable=4
Response.LegacyBucketId=85934700282
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=SBuilderX.exe
Sig[1].Name=Application Version
Sig[1].Value=3.3.3.0
Sig[2].Name=Application Timestamp
Sig[2].Value=5393c5b0
Sig[3].Name=Fault Module Name
Sig[3].Value=shapelib.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=0.0.0.0
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=4d36f467
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=000000000000681d
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.3.9600.2.0.0.768.101
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=035b
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=035b64a3d6ff3d57bb5becfac8671735
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=5dda
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=5ddafec38730cb0635f62dc382f77a07
UI[2]=D:\Program Files (x86)\SBuilderX313\SBuilderX.exe
UI[3]=SBuilderX has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=D:\Program Files (x86)\SBuilderX313\SBuilderX.exe
LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\Windows\SYSTEM32\MSCOREE.DLL
LoadedModule[3]=C:\Windows\system32\KERNEL32.dll
LoadedModule[4]=C:\Windows\system32\KERNELBASE.dll
LoadedModule[5]=C:\Windows\system32\ADVAPI32.dll
LoadedModule[6]=C:\Windows\system32\msvcrt.dll
LoadedModule[7]=C:\Windows\SYSTEM32\sechost.dll
LoadedModule[8]=C:\Windows\system32\RPCRT4.dll
LoadedModule[9]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscoreei.dll
LoadedModule[10]=C:\Windows\system32\SHLWAPI.dll
LoadedModule[11]=C:\Windows\SYSTEM32\combase.dll
LoadedModule[12]=C:\Windows\system32\USER32.dll
LoadedModule[13]=C:\Windows\system32\GDI32.dll
LoadedModule[14]=C:\Windows\system32\IMM32.DLL
LoadedModule[15]=C:\Windows\system32\MSCTF.dll
LoadedModule[16]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
LoadedModule[17]=C:\Windows\SYSTEM32\MSVCR120_CLR0400.dll
LoadedModule[18]=C:\Windows\assembly\NativeImages_v4.0.30319_64\mscorlib\a20cafac04a2e9b3bcb5ec4d674775e5\mscorlib.ni.dll
LoadedModule[19]=C:\Windows\system32\ole32.dll
LoadedModule[20]=C:\Windows\SYSTEM32\kernel.appcore.dll
LoadedModule[21]=C:\Windows\SYSTEM32\CRYPTBASE.dll
LoadedModule[22]=C:\Windows\SYSTEM32\bcryptPrimitives.dll
LoadedModule[23]=C:\Windows\system32\uxtheme.dll
LoadedModule[24]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System\10e3367d9097070044e05c2825a4a1e9\System.ni.dll
LoadedModule[25]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Core\4c30ba993ce1f4d74c3fe26ffa9cd4a4\System.Core.ni.dll
LoadedModule[26]=C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.V9921e851#\b59fee046dfa048ec5f5180dc88f835d\Microsoft.VisualBasic.ni.dll
LoadedModule[27]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clrjit.dll
LoadedModule[28]=C:\Windows\system32\OLEAUT32.dll
LoadedModule[29]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Drawing\7b48e37359be1aebd4e9f302040d517d\System.Drawing.ni.dll
LoadedModule[30]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Windows.Forms\00d5b8fae6d70bea4fe037311f3ee7e6\System.Windows.Forms.ni.dll
LoadedModule[31]=C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_5.82.9600.16384_none_34a8918f959016ea\comctl32.dll
LoadedModule[32]=C:\Windows\system32\dwmapi.dll
LoadedModule[33]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Runt73a1fc9d#\7b307522da3019e7694bebdaa2da6734\System.Runtime.Remoting.ni.dll
LoadedModule[34]=C:\Windows\SYSTEM32\CRYPTSP.dll
LoadedModule[35]=C:\Windows\system32\rsaenh.dll
LoadedModule[36]=C:\Windows\SYSTEM32\bcrypt.dll
LoadedModule[37]=D:\Program Files (x86)\SBuilderX313\FSUIPCClient.dll
LoadedModule[38]=C:\Windows\WinSxS\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.9600.17056_none_932f2645474c8242\gdiplus.dll
LoadedModule[39]=C:\Windows\SYSTEM32\DWrite.dll
LoadedModule[40]=C:\Windows\SYSTEM32\WindowsCodecs.dll
LoadedModule[41]=C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.9600.17031_none_6242a4b3ecbb55a1\comctl32.dll
LoadedModule[42]=C:\Program Files\WIDCOMM\Bluetooth Software\btmmhook.dll
LoadedModule[43]=C:\Windows\system32\SHELL32.dll
LoadedModule[44]=C:\Windows\system32\PSAPI.DLL
LoadedModule[45]=D:\Program Files (x86)\SBuilderX313\TileServer.dll
LoadedModule[46]=D:\Program Files (x86)\SBuilderX313\Tiles\ArcGisServer.dll
LoadedModule[47]=D:\Program Files (x86)\SBuilderX313\Tiles\GLS_Server.dll
LoadedModule[48]=D:\Program Files (x86)\SBuilderX313\Tiles\GoogleServer.dll
LoadedModule[49]=D:\Program Files (x86)\SBuilderX313\Tiles\IrsGisLab_LandsatServer.dll
LoadedModule[50]=D:\Program Files (x86)\SBuilderX313\Tiles\NokiaMapServer.dll
LoadedModule[51]=D:\Program Files (x86)\SBuilderX313\Tiles\NokiaSatelliteServer.dll
LoadedModule[52]=D:\Program Files (x86)\SBuilderX313\Tiles\OpenStreetMapServer.dll
LoadedModule[53]=D:\Program Files (x86)\SBuilderX313\Tiles\VirtualEarthServer.dll
LoadedModule[54]=D:\Program Files (x86)\SBuilderX313\Tiles\YahooServer.dll
LoadedModule[55]=C:\Windows\system32\SHCORE.dll
LoadedModule[56]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Configuration\436bd23db5f3a6b8799945332afc0899\System.Configuration.ni.dll
LoadedModule[57]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Xml\a0f91cf4cae3b99bd02319f6a31fa079\System.Xml.ni.dll
LoadedModule[58]=C:\Windows\SYSTEM32\ntmarta.dll
LoadedModule[59]=D:\Program Files (x86)\SBuilderX313\shapelib.dll
LoadedModule[60]=C:\Windows\SYSTEM32\VERSION.dll
LoadedModule[61]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\diasymreader.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=SBuilderX
AppPath=D:\Program Files (x86)\SBuilderX313\SBuilderX.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=DB4493C3E4EB27B0BD82CC3E6326FD25
 
rhumbaflappy

rhumbaflappy

Administrator
Staff member
Resource contributor
Messages
5,948
Country
us-wisconsin
If possible, you could save the pre-compilation as an SBX file, and zip that file and attach it to a post or a PM, so I could try to compile it on my computer?

Dick
 
bdf369

bdf369

Messages
258
Country
us-california
Thanks for the help, the zip file is attached here.

Regards,
Barry
 

Attachments

  • KGPI.zip
    1.3 KB · Views: 270
GHD

GHD

Messages
12,243
Country
england
I get "Not a valid SBX file" in both the 32 bit and 64 bit SBuilderX.

Edit. It was the copyright line, I changed it to SB313 and it compiles:



TmfViewer interprets it as a Park.

 
Last edited:
bdf369

bdf369

Messages
258
Country
us-california
Thanks George, that looks like the right GUID. I tried changing the copyright line and re-importing but SBX 314 still crashes when I compile.

SBX_GC_zps9c9d9b81.png
 
rhumbaflappy

rhumbaflappy

Administrator
Staff member
Resource contributor
Messages
5,948
Country
us-wisconsin
It loads and compiles fine on my system.

Confirming you have a Windows 7 or 8 64-bit operating system, I would try this:

https://onedrive.live.com/download?resid=F3950C5BBD2BCFA1!805

This is a link to a zipped folder containing the complete SBuilderX314. Put it anywhere, copy a shortcut to SBuilderX.exe, and you should be good to go. I'm guessing your update was not right, somehow. I see you updated to the original 313 folder. Luis did this to avoid an installer. But it has given some problems. This zip is the whole enchilada. Nothing to add. ( I would uninstall the 313, or at least delete the folder, to avoid any cross contamination ).

Dick
 
bdf369

bdf369

Messages
258
Country
us-california
Thanks Dick, I uninstalled my SBX install and used your complete zip file but I get the exact same crash. Maybe it's something to do with Windows 8. I'll try it on a Windows 7 machine later today.

Regards,
Barry
 
rhumbaflappy

rhumbaflappy

Administrator
Staff member
Resource contributor
Messages
5,948
Country
us-wisconsin
Does it crash on any poly compilation? Just the golf course?

Quite a mystery. We've had Windows8 testers without having problems. Most, if not all issues have been related to installation. If you find the shapelib.dll, right-click on it, select properties, and UnBlock...press OK. That might be it.

Dick
 
bdf369

bdf369

Messages
258
Country
us-california
Did some additional testing. FYI I'm running Windows 8.1 with latest updates. I checked that all files in SBuilderX are unblocked, and I added an exclusion in Win Defender for the SBuilderX folder:

- Same crash occurs regardless of terrain vector: I tried Landclass, shorelines and hydro polys
- On my Win7 machine there is no crash -- so I can do compiles there as a workaround
- On Win 8.1 I have been able to compile rasters: Photo and landclass

Anything I can do to help debug?

Thanks,
Barry
 
rhumbaflappy

rhumbaflappy

Administrator
Staff member
Resource contributor
Messages
5,948
Country
us-wisconsin
When you used my zipped folder with 314, did you place that folder in the Program Files (x86) folder? If so, you could move it to somewhere else... worth a try.

Also, do you have an option to run a program as Windows7 or WindowsXP? Again, worth a try.

The problem is specific with your Windows8 setup somehow. Shapelib.dll is a 64-bit native code DLL. I'd have to look into Luis' code, but I don't see how Shapelib is involved with the compilation of vectors. I thought it only read the shapefile when it translated it to SBuilderX' internal poly array.

Dick
 
bdf369

bdf369

Messages
258
Country
us-california
Nope, the zip is not in any Program Files directory, I'm using D:\FSX Files\Development\SBuilderX314. I tried the compatibility modes but it still crashes.

I wonder if it matters that I have .NET framework 4.5.2 installed?

Here's the last stack trace from event viewer:

Application: SBuilderX.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
Stack:
at SBuilderX.moduleSHAPE.DBFAddField(Int32, System.String ByRef, DBFFieldType, Int32, Int32)
at SBuilderX.moduleSHAPE.DBFAddField(Int32, System.String ByRef, DBFFieldType, Int32, Int32)
at SBuilderX.moduleSHAPE.MakeSHPPolys(System.String, System.String)
at SBuilderX.frmBGL.MakeBGLVector()
at SBuilderX.frmBGL.cmdCompile_Click(System.Object, System.EventArgs)
at System.Windows.Forms.Button.OnMouseUp(System.Windows.Forms.MouseEventArgs)
at System.Windows.Forms.Control.WmMouseUp(System.Windows.Forms.Message ByRef, System.Windows.Forms.MouseButtons, Int32)
at System.Windows.Forms.Control.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.ButtonBase.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.Button.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.NativeWindow.Callback(IntPtr, Int32, IntPtr, IntPtr)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG ByRef)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG ByRef)
at System.Windows.Forms.Application+ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr, Int32, Int32)
at System.Windows.Forms.Application+ThreadContext.RunMessageLoopInner(Int32, System.Windows.Forms.ApplicationContext)
at System.Windows.Forms.Application+ThreadContext.RunMessageLoop(Int32, System.Windows.Forms.ApplicationContext)
at System.Windows.Forms.Form.ShowDialog(System.Windows.Forms.IWin32Window)
at SBuilderX.frmStart.BGLMenuItem_Click(System.Object, System.EventArgs)
at System.Windows.Forms.ToolStripMenuItem.OnClick(System.EventArgs)
at System.Windows.Forms.ToolStripItem.HandleClick(System.EventArgs)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(System.Windows.Forms.MouseEventArgs)
at System.Windows.Forms.ToolStrip.OnMouseUp(System.Windows.Forms.MouseEventArgs)
at System.Windows.Forms.ToolStripDropDown.OnMouseUp(System.Windows.Forms.MouseEventArgs)
at System.Windows.Forms.Control.WmMouseUp(System.Windows.Forms.Message ByRef, System.Windows.Forms.MouseButtons, Int32)
at System.Windows.Forms.Control.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.ToolStrip.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.ToolStripDropDown.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.NativeWindow.Callback(IntPtr, Int32, IntPtr, IntPtr)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG ByRef)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG ByRef)
at System.Windows.Forms.Application+ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr, Int32, Int32)
at System.Windows.Forms.Application+ThreadContext.RunMessageLoopInner(Int32, System.Windows.Forms.ApplicationContext)
at System.Windows.Forms.Application+ThreadContext.RunMessageLoop(Int32, System.Windows.Forms.ApplicationContext)
at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnRun()
at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.DoApplicationModel()
at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.Run(System.String[])
at SBuilderX.My.MyApplication.Main(System.String[])


Thanks,
Barry
 

Attachments

  • SBX_crash.txt
    19.3 KB · Views: 669
arno

arno

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
32,886
Country
netherlands
Hi Dick,

Shp2vec expects shapefiles as input, so it doesn't sound weird that shapelib is used when exporting terrain vectors as well.

In the last error stack it seems that the shapelib library is being called, but something goes wrong when adding fields to it. From what I know from the library that might be related to a dbf file not being created correctly.
 
rhumbaflappy

rhumbaflappy

Administrator
Staff member
Resource contributor
Messages
5,948
Country
us-wisconsin
Hi Arno.

That makes sense. Luis had problems with the reading of the DBF of the shapefile, so he handled the DBF with his own routine. I don't know if this included writing the DBF as well. But, the problem is still lying with Barry's system. Both George and I were able to use his example. And no one else has complained of the program crashing while compiling vectors.

Barry, lets try this...

Here's a link to an x86 version of SBuilderV314:

https://onedrive.live.com/download?resid=F3950C5BBD2BCFA1!812

This is also a folder structure, so nothing needs to be added, overwritten or registered. See if the x86 version can compile your vectors without crashing.

Dick
 
Last edited:
arno

arno

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
32,886
Country
netherlands
Could the location where sbuilderx is installed matter? This error seems to happen when creating the dbf, but maybe the file could not be created due to permissions on folders.
 
rhumbaflappy

rhumbaflappy

Administrator
Staff member
Resource contributor
Messages
5,948
Country
us-wisconsin
Hi Barry.

I fixed the link. You could try it again.

Arno has a good idea. But I don't know why Windows8 permissions would be different. Are you logged in with administrator priviledges?

Dick
 
bdf369

bdf369

Messages
258
Country
us-california
Thanks I really appreciate all the assistance here.

Yes, I have administrator privileges and UAC is disabled. The target folder on my D:\ drive and from what I can tell I have full control permissions.

I downloaded the x86 version and with that one I can compile the terrain vector and the BGL is copied to my destination folder, but the "show background" menu item is disabled regardless of which tile server I choose.

Thanks,
Barry
 
rhumbaflappy

rhumbaflappy

Administrator
Staff member
Resource contributor
Messages
5,948
Country
us-wisconsin
Hi Barry.

In the Preferences popup, there is a checkbox that asks if you really want to use the tile server ( as I recall from memory ). That should be checked to activate the background tiles of choice.

Now I'm suspecting your .NET 4+ installation might be corrupted. The x64 and the x86 are identical programs... with the CPU type targeted differently. The x86 should be fine to use, but may have issues with extremely large maps (photoreal), just like version 313 had.

Same routines, same dlls ( although they are 64-bit dlls ), same everything.

Dick
 
arno

arno

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
32,886
Country
netherlands
Hi Dick,

If the x86 and x64 are the same exe, I do assume that each version has a different shapelib.dll included? Because that DLL would need to be 64 bit compiled for the x64 version.
 
rhumbaflappy

rhumbaflappy

Administrator
Staff member
Resource contributor
Messages
5,948
Country
us-wisconsin
Hi Arno.

I believe we borrowed the same 64-bit shapelib.dll you use in your projects for the x64 version 314. It hasn't been a problem for any other users. Have you had issues with it for Windows8 users?

Dick
 
You must log in or register to reply here.
Top