Running sBuilderX without FSX installed.

[jparnold]

I have sBuilderX installed on a PC which doesn't have FSX or SDK installed which I use simply to create 'projects' and also .BMP files of maps I use in other programs which have nothing to do with FSX.
(I also have it installed on a different PC which does have FSX installed where I create COMPILED .BGL files).

It works (on the PC without FSX) although it displays warnings etc that FSX etc can't be found which I can put up with (unless someone knows a way of changing a .CFG file or something else so that it won't 'look for' FSX and the SDK compiler etc) HOWEVER it continually displays a window advising that it is trying to "copy some bitmaps" so that "next time sBuilderX will start faster".

Does anyone know what bitmaps it is trying to copy and/or a setting (maybe in the .cfg file) which I can change so that sBuilderX 'thinks' that the bitmaps are copied?

 

[jparnold]

I ended up copying some of the (sBuilderX) folders from the PC which has FSX installed on to the other PC and also copied the FSX folders which sBuilderX uses for compiling etc and set the preferences to point to those directories. After doing that all warning windows disappeared except the "Can't find FSX" window which I can put up with (I guess I could figure out what registry entry is required but I can't be bothered going to that much trouble.

 

[kevintampa5]

After doing that all warning windows disappeared except the "Can't find FSX" window which I can put up with (I guess I could figure out what registry entry is required but I can't be bothered going to that much trouble.

Dont know if it uses the registry to check this after the initial setup. I think it uses an ini style file that stores the location, and the location is returning an invalid or not found result.

Update:
Found little information to support the reg check only on install, but more references to each startup. I have done some testing, and it does appear to check the registry to verify FSX location however it does not affect its use. (verified short of modifying registry to simulate the sim being in a dif location).

 

[jparnold]

Thanks Kevin
I put it into my "too hard" basket and just put up with the warnings.

 

[kevintampa5]

I have confirmed per Luis Sa's previous entries that it does indeed check the registry for FSX when installed, unsure if each time its started. If it does not see it, then it will return the error. You could add an entry to the registry and place a copy of the FSX.exe in that path then it wont throw errors.

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\IntelliPoint\AppSpecific\fsx.exe]
"Path"="C:\\Program Files (x86)\\Microsoft Games\\Microsoft Flight Simulator X\\fsx.exe"
@=dword:00000000

Just type the location you will place the FSX.exe after the path.
Example:
"Path"="C:\\USER\\Public\\Documents\\fsx.exe"

Just copy and past the quoted section into notepad and save as a .reg file then run as admin to add the entry.

Note:
I would backup the registry also just to be safe, outside of any windows or pc backup tools. A backup of the registry only. Google how to do it, its easily found. I have at-least 2 backups just in case I have an issue with my current. Ive had corrupted registries before, not a fun thing to fix and some backup tools wont allow you to just apply a backup registry, which is why I keep them separate.

Note 2: Do NOT do this if you have FSX already installed or you will have to find and remove the entry.

Again, I did not modify the registry to test this, but FSX is found based on that key entry and its the entry SbuilderX checks for, unless you type the path in the FSX Settings. It will check the registry each time its started if the entry is blank or FSX is not found.

UPDATE:
Upon further testing it doesnt matter where fsx.exe is, just ensure the path is set. See image. see no red entry, this was after modifying the change to simulate removal of fsx.
It did not throw an error.

 

[jparnold]

Thanks Kevin,
You have gone to a lot of trouble and I appreciate it.
I don't mind altering the registry and do manually modify it from time to time by adding/removing entries.
I used to be an analyst/programmer (even machine code) so the registry doesn't scare me although I am always very careful.

 

[kevintampa5]

Made some updates as testing has revealed it doesnt check the registry when started, and if it does it makes no difference and throws no flags. The reg entry matters not, neither does the fsx.exe location. As long as you set a path it doesnt care whether its right or not. If this was not Luis Sa's intent, then its a bug.
PS: When I took that screenshot, FSX was not where the path stated. Notice it wasnt red.
It will if you try to connect it to fsx, fsuipc connection error.

 

[jparnold]

Hi Kevin
Yes I have found that (it seems) the registry entry makes no difference too - although I feel that sBuilderX must check the registry at some point as setting the correct path does not 'stick' and needs to be done every time.
I will search for entries in the registry on the PC which does have fsx installed and duplicate those entries in the registry of the PC which does not have FSX installed.

I found that setting the path to the compiler changes to a path within sBuilderX after you set it (to the SDK location) so it (sBuilder) does some strange things. Maybe it copies the files from SDK. The location of those files within SDK then does not matter. Interesting.

 

[kevintampa5]

Hi Kevin
Yes I have found that (it seems) the registry entry makes no difference too - although I feel that sBuilderX must check the registry at some point as setting the correct path does not 'stick' and needs to be done every time.
I will search for entries in the registry on the PC which does have fsx installed and duplicate those entries in the registry of the PC which does not have FSX installed.

I found that setting the path to the compiler changes to a path within sBuilderX after you set it (to the SDK location) so it (sBuilder) does some strange things. Maybe it copies the files from SDK. The location of those files within SDK then does not matter. Interesting.

On install it checks the registry at first start. The above will trick it into thinking its there. You only need that one key to identify the program.

It copies the locations to an ini file it uses after that. If you manually modify the ini it may remember it. make a copy if you plan to modify.

 

[jparnold]

I meant to advise that I have updated the registry with the data you included earlier. It made NO difference.
Anyway lets move on as it's not all that inconvenient.

 

[kevintampa5]

I meant to advise that I have updated the registry with the data you included earlier. It made NO difference.
Anyway lets move on as it's not all that inconvenient.

interesting. I had a different result. It only checks on install btw. I uninstalled and reinstalled to change the sbx directory location. Program files was annoying. I simulated the removal of FSX and added just the one string and it recognized it.

However, I only simulated under current user, so it may have seen it on another users hive.