• 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.

SBuilderX not working

L

lingyuan.he

Messages
13
Country
china
Hi,

I ran SBuilderX for the first time, and all kinds of errors popped out.

Check your Bridge.txt!

There was an error related to <objects.txt>. Library objects were turned off.

Then, Global Exception: File already open.

I clicked yes to continue. At last, arithmetic operation resulted in an overflow. The program bailed out.

I am using Win7 64bit SP1.

Any suggestions?

Thanks
 
I have the same problem.

The first error pops up:
Check your Bridges.txt file
Click OK.

The second error:
There was an error related to <objects.txt>. Library Objects were turned off.
Click OK.

The third error:
File already open.
This was an unexpected error that can lead to unpredictable results. If
you press NO SBuilderX will shut down. If you press YES you can
continue to work at your own risk. Do you want to continue?
Click YES

The fourth (ultimate) error:
Arithmetic operation resulted in overflow.
This was an unexpected error that can lead to unpredictable results. If
you press NO SBuilderX will shut down. If you press YES you can
continue to work at your own risk. Do you want to continue?
Click YES

The final pop-up:
SBuilderX has stopped working
Windows can check online for a solution to the problem.
Whatever I click, this is the end of the story.

I try to run it on Win7 64.
 
LCSims said:
And you installed it where in Win7 64, ProgramFiles or ProgramFiles(x86)?

And your SDKs are installed where in Win7 64?
Click to expand...

c:\Program Files (x86)\SBuilderX313\
c:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\

Just in case (though probably obvious):
c:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\
 
99.9% sure it's a case of Windows protecting you from yourself.

Simple solution would be to uninstall the SDKs and SBuilderX and reinstall them outside of the \Program Files(x86) folders. If it isn't too painful of an issue, include FSX as an unistall/reinstall outside of \Program Files(x86).

If you don't want to do that, then you'll need to spend some time with Google and UAC for Win7, taking ownership of files/folders, run as Administrator and maybe some other, fun stuff.

Once SBuilderX can get access to some of the files it wants (needs) to copy over and can create some other files that it needs, it should then work.
 
LCSims said:
99.9% sure it's a case of Windows protecting you from yourself.

Simple solution would be to uninstall the SDKs and SBuilderX and reinstall them outside of the \Program Files(x86) folders. If it isn't too painful of an issue, include FSX as an unistall/reinstall outside of \Program Files(x86).
Click to expand...

OK, here is what I did:
Step 1
Uninstall SBuilderX
Uninstall SDK

Step 2
Install SDK from the DVD in c:\SDK\
Install SbuilderX in c:\SBuilderX313\
Run SBuilderX
Result: Same as before

Step 3
Install SDK SP1A
Run SBuilderX
Result: Same as before

Step 4
Install SDK SP2
Run SBuilderX
Result: Same as before

Step 5
Uninstall SBuilderX
Re-install SbuilderX in c:\SBuilderX313\
Run SBuilderX
Result: Same as before

Now, as far as the uninstalling/reinstalling of FSX is concerned, I'd rather not do that. I tried it once on my previous machine (also Win7 64), and it resulted in forfeiting the ability to use it at all. It simply didn't want to reinstall - it did start initially only to inform me at the end that there was some gameinst.dll error, which, as it subsequently appeared, is quite common among the MS games, and for which there seems to be no solution (MS states there is one, but many users state otherwise, including myself, after a few days' long attempts). As reinstalling Windows, as the only remedy to return to the status quo, is not an option, I'll simply not risk it (FSX without SBuilderX is still a more attractive proposition than neither of them).

To make things even more bizarre, yesterday I installed the whole bunch on an machine with WinXP SP3 32. The locations were C:\Program Files\Microsoft Games\Microsoft Flight Simulator X, C:\Program Files\Microsoft Games\Microsoft Flight Simulator X SDK, and C:\Program Files\SBuildrX313.
The results were exactly the same as on Win7 64.
If this helps, the FSX I use is FSX Deluxe with SP2 (no Acceleration).
 
Well, that's no good!

I'll look at what's on my HD(s), as I made the switch to Win7 a little over a year ago and haven't had any issues. What I'm thinking is there may be some older runtime files needed for SBX to function. If I recall correctly, it was done in an older version of Visual Basic and those supporting files need to be present. But I'll have to snoop around to see what I have and where it's hidden on the HDs.
 
Better late, than never?

Checked some of the older support files that I added when I moved from XP to Win7 64. A listing of them is attached.

From what I recall, SBuilderX was written in Visual Basic 6. That's old enough to where Win7 may not include any of the prior era's runtime to be included. So hunting down the files and getting them installed might clear things up and get SBuilderX working.
 

Attachments

I downloaded the suggested files, and, before I make more mess than I already have, I'd like to make sure place the library files in the right locations. I guess the best way is to follow your path (no pun intended). So where to copy the following:
- mfc 71 (3 files)
- mscomctl.ocx
- msvcr71.dll
- tabctl37.ocx ?
Since the other files on the list are executable, it seems self-explanatory (if there are any precautions, please let me know).
 
Updated the list. Make sure to set a system restore point, though I doubt any issues will occur. I think getting the Visual Basic runtime files installed will clear up past problems.
 

Attachments

SBuilderX is written in VB.net, and runs just fine in Windows7.

The problem may simply be the use of a "," as a decimal separator, rather than the required "."

dick
 
LCSims said:
Updated the list. Make sure to set a system restore point, though I doubt any issues will occur. I think getting the Visual Basic runtime files installed will clear up past problems.
Click to expand...

Thanks! I should know tomorrow.

rhumbaflappy said:
SBuilderX is written in VB.net, and runs just fine in Windows7.

The problem may simply be the use of a "," as a decimal separator, rather than the required "."

dick
Click to expand...

I'm not sure where to change it other than via Region and Language in Control Panel. It seems to fine here, though.
 

Attachments

  • dec separator.GIF
    dec separator.GIF
    36.5 KB · Views: 671
Sadly, there has been no difference, whatever I tried. I'm still going to try it on XP. That it doesn't work on Win7 is not so surprising, as quite a few people seem to have the same problem, but why it shows the same symptoms on XP is beyond explanation. It must be a piece of some recent software, but what is it?
 
The final pop-up:
SBuilderX has stopped working
Windows can check online for a solution to the problem.
Click to expand...

This means there is an error report in the Event Viewer. Can you get us the info from that report? It may give more info to what file caused the crash.


However the report may exist, I think its a permissions issue. You could reinstall outside of Program Files (you indicated you did), or you could set each executable to run as administrator.

Win7, Vista, and XP have the UAC built in; 32 and 64 bit versions, they all have it and it protects the program files folder.

review both posts below. Not directly SbuilderX, but the process is the same with all executable files.

http://fsdeveloper.com/forum/showpost.php?p=479039&postcount=4

http://fsdeveloper.com/forum/showpost.php?p=631524&postcount=5
 
Last edited:
The error report:

Description:
Stopped working

Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: sbuilderx313.exe
Problem Signature 02: 3.1.3.0
Problem Signature 03: 4a70d61e
Problem Signature 04: SBuilderX
Problem Signature 05: 3.1.3.0
Problem Signature 06: 4a70d61e
Problem Signature 07: 3
Problem Signature 08: 1ff
Problem Signature 09: System.NullReferenceException
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

As I said before, I installed SBuilderX and SDK outside Program Files (x86) folder, but not FSX (i.e. in Win7; in WinXP, everything is outside Program Files). I don't want to risk failing to reinstall FSX. It happened to me before, and it required reinstalling Windows, which I can't afford at my current situation (mainly time limitations - too much other soft to reinstall and finetune). In WinXp all the soft is outside Program Files and still no result.

Now, should I set ALL executables (including FSX) to run as administrator (you mentioned 'each')?
 
You dont have to reinstall FSX. You dont even really need FSX to open SbuilderX, but to use some aspects you do.

Your error report indicates a standard app crash. The problem lies in the SbuilderX files somewhere.

Now, are you able to at least open Sbuilder or does it not even open?

Now, should I set ALL executables (including FSX) to run as administrator (you mentioned 'each')?
Click to expand...

I run ALL my programs that interact with anything in program files directory as Admin. If the program does not interact with a program inside of Program Files, I dont worry about the run as admin. My SDK is installed in Program files. I set it to run as admin and I also set all programs that use the SDK compilers to run as admin so that way the program can start the sdk apps without the UAC saying the program initiating the control has not the permission needed to modify the file.


I don't want to risk failing to reinstall FSX. It happened to me before, and it required reinstalling Windows
Click to expand...

That is unusual and was probably something other than an FSX uninstall. This is a highly uncommon occurrence.
 
Last edited:
kevintampa5 said:
Now, are you able to at least open Sbuilder or does it not even open?
Click to expand...
No, it doesn't open. I explained how far I can get in my earlier post.

kevintampa5 said:
That is unusual and was probably something other than an FSX uninstall. This is a highly uncommon occurrence.
Click to expand...

Apparently not. Check error number 0x80040702 in google. MS tried to address it (http://support.microsoft.com/kb/968365) , but it's useless.
http://answers.microsoft.com/en-us/...ulator-x/c2d598e7-fce4-42cc-925d-a6eced15dbe3
 
holdenhk said:
No, it doesn't open. I explained how far I can get in my earlier post.



Apparently not. Check error number 0x80040702 in google. MS tried to address it (http://support.microsoft.com/kb/968365) , but it's useless.
http://answers.microsoft.com/en-us/...ulator-x/c2d598e7-fce4-42cc-925d-a6eced15dbe3
Click to expand...

That error is a common error that is thrown possibly when a dll is missing, common being that it is an error number associated routinely with missing or incomplete/corrupt files. It does not only apply to FSX. The error is not very common among FSX. A few hundred reports out of +250,000 installations of FSX, its a known issue but I wouldnt call it common unless we hit tens of thousands of instances. Common is defined as routine, fairly saturated, everyday thing. I did use poor judgement when I stated highly uncommon. This is besides the point, lets get back on topic.

Your SBX is having issues. I am looking over what I have done to mitigate these errors in the past.
If SBX is having an issue, it is not FSX causing it. You should not have to uninstall or reinstall FSX to resolve this.


double-check to make sure your VB6 files are updated. If you dont have VB6, then install VB6 and run windows update a couple of times to get the latest fixes.
SBX was written in Visual Studio 2005 with the .Net VB2005 runtime, per Luis Sa. VB2005 runtime is a CLR and requires .NET v2.0 Framework. Windows 7 includes .Net 2.5 and later; does not include 2.0 if I recall, but I am probably mistaken. its worth a shot to double check. I know I had to install something for SbuilderX to run, but it was 2 years ago and I have forgotten. I have thousands of shortcuts and notes on my installation troubles, but I can not find the file that contains what I did to fix it and what I did that didnt fix it.
 
Last edited:
You must log in or register to reply here.
Back
Top