SBuilderX Recognition problem

[falcon409]

I'm using the latest version (64bit) with P3D_V2.4. I no longer have FSX or FS9 Installed. When I load SBX, I get a message that it can't find FSX. I've looked at the cfg files and don't see any reference to a path it might be checking. Is there a way to get it to recognize P3D on startup?

 

[GaryGB]

Hi Ed:

Are you able to access this particular forum on the PTSIM / SBuilder web site ?

http://www.ptsim.com/forum/viewforum.php?f=30


If so, you may wish to review this thread:

http://www.ptsim.com/forum/viewtopic.php?f=30&t=2311



IIUC, SBuilderX may be looking for the Windows Registry entries of MS-FSX on the first start-up after installation.

I'm not sure if this is still the case, but SBuilderX may be looking for a Registry environment variable within Windows for the install location of FSX on the first start-up after installation of SBuilderX, to verify that certain default FS image texture files are physically present, so it can attempt to copy them for use as thumbnails displayable in the SBuilder GUI (just as prior versions of SBuilder did).


It is possible that you may be able work around this by first creating a 'dummy folder' for a FSX installation which is otherwise empty, aside from a 'fake' FSX.exe (re-named to a *.exe file type from a FSX.txt text file made in ex: Windows NotePad).


You may then try downloading & using Flight1's freeware FSX/FS9 Registry Repair Tool:

http://www.flight1software.com/files/FS_Registry_Repair.exe


Next, run that tool and browse to the location of the 'fake' FSX.exe placed into the dummy FSX installation at:

[FSX dummy install path]\FSX.exe.


NOTE: It is NOT required to actually have FSX physically installed in order for this tool to work.


FYI: FSX/FS9 Registry Repair Tool should then have simply restored the basic default FSX Registry entries back into Windows where SBuilderX expects to find them.


Hope this helps; let us know if this works for you.

GaryGB

 

[falcon409]

Thanks Gary,

Unfortunately while the registry tool seems to be fine with the dummy fsx.exe. . .and fixes the registry information. . .SBuilderX is not and will not accept it. No matter, I'll just take the time to type in my P3D path each time I open SBX. It's not worth wasting time with. Thanks!

 

[JRobinson]

Maybe you could put the dummy FSX.exe in the root P3D2 folder, then point the registry tool to that folder and claim it as the "FSX path" in the registry. Not sure what SBX looks for but with any luck at all there would be a P3D2 equivalent that would satisfy it so you didn't have to type the path each time.

 

[Andrew]

Thanks Gary,

Unfortunately while the registry tool seems to be fine with the dummy fsx.exe. . .and fixes the registry information. . .SBuilderX is not and will not accept it. No matter, I'll just take the time to type in my P3D path each time I open SBX. It's not worth wasting time with. Thanks!

This is also what I do. I can live with this for now. I am not going to try to solve anything. I am just happy I can use SB 314 for reference photos for ADE - and render a photoscenery or two. Thanks to Dick & Luis

 

[GaryGB]

Hi again:

Just to clarify the issues under discussion in this thread...


The SBuilderX v3.14x 64-bit update is intended to be un-zipped into a already installed and working folder of SBuilderX 3.13x 32-bit.




SBuilderX 3.13x 32-bit (aka "SBX_32-bit")

http://www.fsdeveloper.com/forum/threads/sbuilderx.5596/


"SBX_32-bit" 'full' installation required before applying 64-bit update - Download link:

http://www.ptsim.com/sbuilderx/SBuilderX313.zip



SBuilderX v3.14x 64-bit (aka "SBX_64-bit")

http://www.ptsim.com/forum/viewtopic.php?f=30&t=2306&sid=719423556431e9cb09929afeafd894b4


CAVEAT: SBuilderX 3.13x 32-bit must be already installed and working before applying the SBuilderX v3.14x 64-bit update


"SBX_64-bit" Update ONLY (requires 'full' and working install of "SBX_32-bit" before applying 64-bit update) - Download link:

http://www.ptsim.com/forum/download/file.php?id=224





So, IIUC, issues reported here may be due to problems seen when SBuilderX 3.13x 32-bit (aka "SBX_32-bit") ...is installed and run the 1st time.


AFAIK, During installation and/or on the first start-up after installation, SBuilderX 3.13x 32-bit may, (...at the very least):

1.) Look for a Registry environment variable within Windows for the install location of FSX of SBuilderX


2.) Verify that FSX.exe is physically present within the FSX root folder path specified by that Windows Registry environment variable


3.) Verify that certain default FS image texture files are physically present in the FSX sub-folder chain, so it can attempt to copy them for use as thumbnails displayable in the SBuilder GUI (just as prior versions of SBuilder did)


4.) Verify that Terrain.Cfg is physically present within the FSX root folder path, so it can:

a.) prompt the end user for a decision to:

(1) retain the FSX default copy of Terrain.Cfg
...Or:
(2) substitute the "Modified Terrain.Cfg" (by Richard Ludowise aka "rhumbaflappy" and Luis Feliz-Tirado)

b.) Copy and process info from Terrain.Cfg chosen by end user, then populate pick-lists in the SBuilderX GUI with that info


5.) Install and update a "SBuilder.ini" file (located within the SBuilderX root install folder), with info derived from:

a.) info gathered during the installation sequence itself including user answers to prompts

b.) manually entered user preferences made during SBuilderX load-up for the 1st time, and all subsequent times


Thus, IIUC, to successfully install SBuilderX 3.13x 32-bit, one must have either a:

a.) full, real install of FSX with all associated sub-folder chains containing ALL files including those required SBuilderX 3.13x installer
...Or:
b.)"Dummy" install of FSX with all associated sub-folder chains containing ONLY the 'specified' files required SBuilderX 3.13x installer



I'm not certain about this, but perhaps this may merit testing by those installing SBuilderX 3.13x 32-bit without an actual full FSX installation.


SBuilderX 3.13x 32-bit installation with a "Dummy" or 'Minimal' install of FSX

Before attempting installation of SBuilderX 3.13x 32-bit, the "Dummy" or 'Minimal' install of FSX folder chain should contain, as a minimum:


* FSX Main 'root' top folder:

1.) "Fake" (...or actual MSFS executable file itself ?) FSX.exe

2.) Terrain.Cfg (FSX Default or 3rd party "Modified Terrain.Cfg")


* FSX sub-folder chain:

[TO BE DETERMINED]


I'd welcome input here by others to help put together an 'updated' guide to SBuilderX 3.13x 32-bit installation with a "Dummy" or 'Minimal' install of FSX.


Thanks in advance for any help posted here that may be used to put together all missing info to assist end users in successfully installing "SBX_32-bit".

GaryGB

 

[Andrew]

GaryGB,

First, thanks for your effort. But have you seen Dick's latest post about SB 314? There is now a full package available, as a folder structure.

Link: http://www.ptsim.com/forum/viewtopic.php?f=30&t=2315

In other words, don't update, clean all traces of old SB, then start using Dick's alternative.

And, with all respect for complicated solutions. Loved those before in times. But today, if an install becomes like a four-page description...then suddenly I want to do something else. As said before, I will not try to solve anything. I will wait for the original developer to solve it.

Andrew

 

[GaryGB]

Hi Andrew:

Thanks for the reminder about (temporary ?) availability of that awesome, very generous, and helpful post with linked download by rhumbaflappy.


As a heads-up for others looking into use of this download (while still available), it may require some work "under the hood" to get it configured for proper function on their "own" system.


It is possible that all which may be needed to use rhumbaflappy's "SBuilderX 3.14 full install folder chain" package ...is some edits to the folder (aka "directory") and/or "Dir" paths in his included SBuilder.ini file:

[Recent Files]
RecentFile1=
RecentFile2=
RecentFile3=
RecentFile4=

[RecentDirs]
SBPDir=
SBXDir=C:\Users\Dick\Desktop\GeoTrace\9035
SHPDir=C:\Users\Dick\Desktop\test shapefiles
SURDir=C:\Users\Dick\Desktop\GeoTrace\potrace
TEXDir=
BMPDir=
OBJDir=
RAWDir=
LIBDir=C:\Users\Dick\Desktop\jfar-vehicles-p3d
KMLDir=

[Main]
LonIniCenter=-9.136076
LatIniCenter= 38.7813203
DecimalDegrees=True
MeasuringMeters=True
BGLFolder=C:\MyPrograms\SBuilderX314\Scenery
OriginalTerrainCFG=False

[Edit]
BackUpON=True
BackUpSeconds=60
AskDelete=True
BorderON=True
ShowDonation=True
ShowLabels=True
SelectedPointColor=FF008000
UnselectedPointColor=FFFF0000

[Miscelaneous]
AutoLinePolyJoin=False
DisplayJoin=False
DirJoin=False
NameJoin=False
NoEndsSmooth=True
CornerSmooth=False
SampleDistance= 10
SmoothDistance= 50
DefaultLC=11
DefaultWC=12
Here_app_id=DemoAppId01082013GAL
Here_app_code=AJKnXv84fjrb0KIHawS0Tg

[Grids]
GridColor=FF008000
GridLODColor=FFFF0000
GridWidth= 1
ZoomOnQMID=True
CenterOnMouseWheel=False

[Aircraft]
ShowAircraftPeriod=5000
AircraftAltitudeOffset= .5
ExtraExtrusionAltitude=-20M

[Objects]
Rwy12Path=C:\MyPrograms\SBuilderX314\Rwy12
MacroAPIPath=C:\MyPrograms\SBuilderX314\API
MacroASDPath=C:\MyPrograms\SBuilderX314\ASD
LibObjectsPath=C:\MyPrograms\SBuilderX314\LibObjects

[Lines]
DefaultLineAltitude= 0
DefaultLineWidth= 50
LinePenWidth= 2
SelectedLineColor=FF008000
DefaultLineColor=FF0000FF
MakeClosedLineFromPoly=False

[Polys]
DefaultPolyAltitude= 0
PolyPenWidth= 2
PolyFILL=True
DefaultPolyColor=80FFFF00
PolyColorBorder=FF000000

[Shapes]
ShapeLineGuid={89ABCDEF-EDCB-A987-6543-210FEDCBA000}
ShapeLineAltitude= 0
ShapeLineWidth= 50
ShapeLineColor=FF0000FF
ShapePolyGuid={CB2D5672-CCBC-429B-BA43-2EA24E37EF4C}
ShapePolyAltitude= 0
ShapePolyColor=7400FFFF
AddToCells=True

[Tiles]
ActiveTileFolder=ArcGisStreetMap
ReprojectMercatorTiles=True
SummerVariations=July,August,September
SpringVariations=April,May,June
FallVariations=October,November
WinterVariations=December,February,March
HardWinterVariations=January
CompressionQuality=85

[BLN]
BLNSeparator=,
BLNPolyGuid={9ABCDEF0-FEDC-BA98-7654-3210FEDCB000}
BLNPolyColor=FFFF9D00
BLNLineGuid={89ABCDEF-EDCB-A987-6543-210FEDCBA000}
BLNLineColor=FFFF0000
BLNIsPolyAlt=False
BLNIsLineAlt=False
BLNStartWidth= 35
BLNEndWidth= 35
BLNLineFromPoly=False
BLNExportAltitudes=True

However, this again may be confusing to some newcomers unfamiliar with SBuilderX, and indeed, those unfamiliar with Windows itself.

Thus, I had advocated the intended guide above in an effort to help 'would-be' users of SBuilderX achieve a successful 'full' install on their own Windows platform that would function properly on an individual stand-alone basis, which IIUC, was intended by author / original developer Luis Sa'.


One of the other anticipated results of my ongoing efforts here, would be that we can publicly clarify how folks can use SBuilderX with not only a "dummy" install of FSX, but with Prepar3d (aka "P3D") version 1.4 and version 2.x, which IIUC, each require separate installations of their own.


[EDITED]

And, with all respect for complicated solutions. Loved those before in times. But today, if an install becomes like a four-page description...then suddenly I want to do something else. As said before, I will not try to solve anything. I will wait for the original developer to solve it.

Andrew

Indeed: "An ounce of prevention is worth a pound of cure"...

I believe we share the same sentiments, as I also have limited available time and patience, especially as I endeavor to balance real life commitments with increasingly complex technical demands of producing add-on content for flight simulation.

So I do hope the developer(s) of software which, IMHO, is essential to the present and future of ex: MSFS, MS-Flight! and the P3D platform will 'go the extra distance' < PLEASE ! > in their efforts as programmers to assist the FS Community with getting past the many outstanding and un-resolved issues with documentation and complexity of installation or use of their software.

This would seem preferable, instead of making it necessary for end users to search all over multiple web sites for answers and solutions to problems (which might otherwise have been un-necessary were it not for errors, omissions, and perhaps even purposeful limitations of intended effort on the part of those developers with programming and/or documentation for their software).

Hopefully, if 'original developers' and well-intended FS Community members continue allocating their time to making installation / configuration / use of flight simulation software less complex, more end users might be able to spend their time enjoying flying, learning new skills, and creating new add-on tools or content for flight simulation.

[END_EDIT]


Hope this and my effort above (which requests further input ! ) may help more folks successfully get SBuilderX 64-bit running.

GaryGB


PS: Here's a copy of Dick's "SBuilderX314 complete zip" post at PTSIM regarding his "complete SBuilderX314 folder" package:

http://www.ptsim.com/forum/viewtopic.php?f=30&t=2315

Hi all.

Until Luis returns from sailing, I'm going to make available a zip file of a complete SBuilderX314 folder. It contains everything. Just unzip it to the harddrive location of choice, and it should run on any 64-bit Windows7 or Windows8. Make a shortcut of the SBuilderX.exe and place that on your desktop, if you like.

When Luis returns, he'll decide if a full 314 installer is a good option, and I'll remove this zip from the cloud.

This should end installation problems a few users are still having.

Here's the link:

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

Dick

 

[JRobinson]

Maybe you could put the dummy FSX.exe in the root P3D2 folder, then point the registry tool to that folder and claim it as the "FSX path" in the registry. Not sure what SBX looks for but with any luck at all there would be a P3D2 equivalent that would satisfy it so you didn't have to type the path each time.

I just tested this by removing my FSX registry key, putting a blank txt document in my P3D2 folder and renaming it fsx.exe, and then using the registry repair tool to insert the dummy reg key. SBuilder starts and works fine without typing or browsing to find fsx.exe. How hard is it to do that?

 

[GaryGB]

Excellent info, Jim !

GaryGB

 

[Andrew]

I just tested this by removing my FSX registry key, putting a blank txt document in my P3D2 folder and renaming it fsx.exe, and then using the registry repair tool to insert the dummy reg key. SBuilder starts and works fine without typing or browsing to find fsx.exe. How hard is it to do that?

Done - but it still doesn't work here. I guess it is because I use the full 314 version which comes as a folder structure. But no problem, I can still start and use SBX as described before. Only for photos and photoscenery that is; polygons and objects doesn't work since I use P3D only.