• 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 problems, Vista64

HolgerSandmann

Resource contributor
Messages
392
Country
ca-britishcolumbia
Hi guys,

I'm setting up a new computer with Vista64 and I'm having difficulties getting SBuilderX to run properly.

I've installed FSX (Acceleration), the SDK, and SBuilderX onto a separate drive (E), with folder names

E:\FSX
E:\Microsoft Flight Simulator X SDK
E:\SBuilderFSX

I've checked the registry entries for FSX and they point to the correct location; other add-ons with auto-installers find FSX without problems.

Upon first loading SBuilderX I get a warning "FSX could not be found in this computer" and then crashes because it can't find the folders to copy files from.

So I manually copied the SDK tools and bitmaps into the required folders (using my working SBX environment on my previous computer as a guide) and that lets me start SBX (though the initial error message remains) and work with projects. Moreover, when running FSX, SBuilder properly connects to FSX and everything seems OK.

However, every time I try to compile a project I get the error message window as below and SBX crashes.

Given Vista's hyperactivity about security I've double-checked that I have full access to the FSX and SBX folders; also, Vista's UAC is off.

Any idea how I can get SBuilder to work? Also, what specifically is SBX looking for to recognize FSX if not the registry entry?

Cheers, Holger
 

Attachments

  • SBX_error_Vista64_2.jpg
    SBX_error_Vista64_2.jpg
    93.2 KB · Views: 1,385
I will check tonight Holger. I had similar issues and can't remember off the top of my head if I fixed it or not.

...will get back here later!:D
 
Hi guys,

thanks for the quick responses and the links. I double-checked and both registry entries (FSX and SDK) already have the trailing slashes.

According to Luis the search key code is:

FSPath = My.Computer.Registry.GetValue("HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Games\Flight Simulator\10.0", "SetupPath", Nothing)

and my FSX reg key is just that:

"HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Games\Flight Simulator\10.0\"


What is a bit odd is that according to Luis' code the trailing "\" isn't actually searched for. So I experimented with removing it. Didn't make a difference.


Also, according to Luis the search key for the SDK should be

"HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Games\Flight Simulator X SDK"

However, the default folder name is actually "...\Microsoft Flight Simulator X SDK".

So I changed my folder name to "Flight Simulator X SDK" and edited the reg key accordingly. Again, still the same error messages.


Looks like a fat fingers issue but I can't figure out what it is :(


Cheers, Holger

P.S.: attached my system specs as a signature
 

Attachments

  • FSX_folder_setup.jpg
    FSX_folder_setup.jpg
    40.3 KB · Views: 1,201
  • FSX_registry_entry 2.jpg
    FSX_registry_entry 2.jpg
    31.4 KB · Views: 1,124
  • FSX_SDK_registry_entry.jpg
    FSX_SDK_registry_entry.jpg
    33.4 KB · Views: 1,036
Last edited:
OK, the first one didn't work, how about this one;

http://www.ptsim.com/forum/topic.asp?TOPIC_ID=1360&SearchTerms=vista

This is getting too geeky for me and I'm glad to say I'm sticking with XP until FSnext!:D

Edit: Checking some older posts show that Jim Dhaenens had the sme problem as you, Holger. Same error message with Vista 64. Nothing I can really find that explains how or if he got things working, but maybe a PM or email to him will help you along?
 
Last edited:
Hello Lance,

full points for you! :)

The link to jasons' post was the key. After applying the 32-bit flag to SBuilderX.exe using CorFlags.exe both the initial "can't find FSX" message and the compilation crash went away!

BIG phew! :o

Many thanks to you and to jasons! I actually had suspected a 32/64-bit issue and tried running SBuilderX in XP2-compatibility mode (Vista provides that option). It appears though that this only affects the OS mode not the 32 vs 64-bit stuff. Not that I know anything about it...

Cheers, Holger

P.S.: btw, anyone else have display issues with the PTSim forums? None of the icons show and I had trouble getting a search to work on either of my computers.
 
Me again,

it's getting better :D

I tried the same corflags tweak on Rhumba's TcalcX because it refused to run in Vista 64. Works like a charm now!

I believe there was a thread here about that issue. Will hunt it down and post the solution.

Cheers, Holger
 
Last edited:
Hi Holger

Did you manage to get rid of the annoying SbuilderX cannot find FSX in the registry box? I have got everything to work, compiles, photoscenery etc, but every time I fire up SBX Iget this message. I have added a \ to the registry entry but that hasn't worked.

Oh yes I am using Vista 64bit and FSX sits on a separate drive to the OS (E drive)

Cheers

Paul
 
Hi Paul,

actually, both the initial "cannot find FSX" and the compile crash went away as soon as I applied the CorFlags.exe "hack". So you're saying the same isn't true for you?

Cheers, Holger
 
Yes thats exactly it. The odd thing is everything works, I can compile Polygons, Photosceney et. it puts them in the folder I have designated, its just the message as soon as I load up. I can select okay and SBX loads up, very odd. I have also got TCalc_2 working as well using the Corflags.exe, no problems at all.
 
I have tried all these corrections mentioned aerly in this thread without luck. My FSX path is C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\. I attach pic of my regeditor. The error msg still apears ( I am using Vista 64bit and FSX SP2):

FSX could not been found in this computer.
 

Attachments

  • SBuilder_Error 4.jpg
    SBuilder_Error 4.jpg
    41.7 KB · Views: 1,085
Last edited:
Hi guys, for me, SBuilderX isn't working as well. However, I seem to have a different problem. I have attached the error warning I get when I try to start SBuilderX.

Thanks in advance for the help
Florian
 

Attachments

  • problemsbuilder.jpg
    problemsbuilder.jpg
    79.6 KB · Views: 971
I would try uninstalling and reinstalling somewhere other than inside the \Program files directory structure. I don't have Vista, will not get Vista, ever! But so many problems are seen where people are installing FSX and other stuff within \Program files and having accessability problems. Lovely UAC!

Others have success right-clicking and running things as Administrator and so forth.

I love my WinXp! :D
 
Hello,

At this moment I am installing Vista on a computer with the (only) purpose of investigating the installation of SBuilderX on that OS.

I also made some minor changes and I expect to release an update in the near future. I will make a post here when it is apropriate.

Kind Regards,

Luis
 
Hi Luis.

I would suggest the next version of SBuilderX NOT be placed in 'Program Files' for Vista... it is the cause of many problems because 'Program Files' in Vista has extra 'protection'.

I believe 'Program_Files" would be just fine.

Dick
 
Hi Dick,

I use Visual Studio 2005 and I have 2 projects in the "SBuilder solution". One is the SBuilderX project. The second project is the Setup project. I do not have it here with me to check it out, but I assume that I have assigned the installation folder in the properties of the Setup project to be "Program Files". I am not really sure because in my case it installs in "Programas". In my system (portuguese) all the applications that I have go to the "Programas" folder. So I am not sure if it only suffices to change a parameter of the Setup programme. When I get home I will check that. I will only have Vista available tomorrow, though.

Thanks,

Luis
 
Hi Dick,

I use Visual Studio 2005 and I have 2 projects in the "SBuilder solution". One is the SBuilderX project. The second project is the Setup project. I do not have it here with me to check it out, but I assume that I have assigned the installation folder in the properties of the Setup project to be "Program Files". I am not really sure because in my case it installs in "Programas". In my system (portuguese) all the applications that I have go to the "Programas" folder. So I am not sure if it only suffices to change a parameter of the Setup programme. When I get home I will check that. I will only have Vista available tomorrow, though.

Thanks,

Luis

I have just installed SbuilderX 3.10 on Vista 64 and run into the errors that it can't find FSX, the tools and then it dies can not find file 301b2su1.bmp. I've gone through the forums and made sure the proper registry entries for FSX, the FSX SDK are in place and that FSX\scenery\world\textures contains the 301b2su1.bmp. Still get the FSX can't be found and neither can the tools.

Is there a fix for this that I've missed.

Thanks.

Followup on this.

* I uninstalled - via the control panel. Then deleted the SBuilderX directory (D:\xxxx\yyyy\SbuilderX.
* Reinstalled - first made sure all the registry entries were there
* Used CorFlags to set 32 bit
* Ran and got an error telling me it thought FSX was at xxx but couldn't find it. Program did come up though.
* Checked - added trailing \ to end of FS setup path.
* Now it runs/

Some suggestions. If the program can't find FSX and the tools allow us to tell it where they are either on a startup dialog for through options and then save the results. Frankly, after as much time as I've spent working with the registry (I used to write install/uninstall routines) the best thing that could happen is for MS to get rid of the registry. It's a potential single point of failure and relying on it causes problems. I would do a registry search but if I couldn't find it I then asked the user and stored that in a cft or ini file in my program directory!

Now to learn how to use this program.

*
 
Last edited by a moderator:
Back
Top