Hello:
SBuilder's "start location" defaults to Portugal where the author,
Luís Vieira de Sá, resides, and for which he developed "
SceneryBuilder" (aka "
SBuilder") to assist with making his own
Portugal FS scenery years ago.
http://www.ptsim.com/
http://www.co.it.pt/~luis/
BTW: The author of SBuilder is to be distinguished from
Luis Feliz-Tirado, noted creator of numerous tutorials for SBuilder, co-creator of the "
Modified Terrain.Cfg" file with Richard Ludowise, as well as having been moderator of the AVSIM scenery design forum for many years, and now of SBuilder support forum at PTSIM (to mention only few of his many outstanding and very generous contributions to the FS Community).
FYI: Although manually entering the
"Go To Position" coordinates and/or using SBuilder when 'connected' to a live FS flight session via FSUIPC can certainly help in many cases, IMHO, it is preferable to also change the Geographic coordinates of that default "start location" in the SBuilder "initialization" file, as that helps SBuilder to 'manually' zoom / pan / scroll
properly when working with displayed scenery content within its work-space.
Otherwise, the Geographic extent to which one is able to successfully 'manually' zoom / pan / scroll is
limited when working with displayed scenery content within SBuilder's work-space, and the requested area one attempts to visualize may not stay in view, as the work-space "background" keeps shifting back to a position closer to the default Geographic coordinates for a "
central start location" specified within the SBuilder.Ini file.
To do this, one must edit the pertinent lines in the
SBuilder.Ini file to set the center of the Map background at the Geographic center of your own project area rather than the default one in Portugal via:
SBuilder Menu > Edit > Preferences > click [INI File] button < file opens in Windows NotePad >
[Main]
LonIniCenter=-9.136076
<-- Your project's central Longitude goes here
LatIniCenter= 38.7813203
<-- Your project's central Latitude goes here
DecimalDegrees=True
MeasuringMeters=True
BGLFolder=C:\MyPrograms\SBuilderX314\Scenery
<-- Your project's compiled BGL 'active' \Scenery folder path goes here
OriginalTerrainCFG=False
1.) When configuration of your
SBuilderX project is completed via editing "
SBuilder.ini" in
Windows NotePad:
.....a.) In
Windows NotePad Menu > File > Save As... > "Save as type" field, set to "
All Files (*.*)" (
do not click OK yet)
.....b.) In NotePad Menu > File > Save As... > "
Save In" field, browse to [
SBuilderX install path] folder; double-click to select it
2.) Back in NotePad Menu > File > Save As... browse dialog, click "OK"
.....a.)
When prompted to over-write Sbuilder.ini, click "YES" to save your edits to that file.
3.) Exit and re-start
SBuilderX (...or the above changes will
not yet take effect)
PS: Regarding the Help file freezes, be certain that FS, FS SDK, and SBuilder are all installed properly with Windows Administrative permission levels for the current Windows User account profile to the physical
local computer in sub-folder locations below the root of (any) physical hard drive letter (not "copied" or 'linked' from another User Account folder chain or computer on a LAN).
Also, the SBuilderX shortcut must be edited to "
Run as Administrator" on either the Compatibility or Security tab to elevate the intended /required User permission level.
NOTE: 'Some' images and sections on pages in the Help CHM file are not
local to that file, and are instead linked to
remote content on web pages at the PTSIM site, portions of which may now be offline; thus it is possible a search may be taking place for a 'dead' URL before the Help engine internal browser fails or (rarely, if ever) ...reports missing content.
Additionally, IIUC, one must be certain that on the computer running SBuilder, that application has full access to the internet via the Windows Firewall rules for the Help CHM file to work when it is launched as a child process of SBuilder via the "Help" Menu system.
Ideally, FS, FS SDK, and SBuilder would each be installed (for "all" Windows Users) to the physical local computer in sub-folder locations below the root of (any) physical hard drive letter, rather than in the Windows Program Files (x86) sub-folder chain ...to minimize the number of "gotchas" incurred by Windows over-protective restriction on file reads / writes arising from separate security mechanisms above and beyond UAC (even when UAC is already disabled).
Hope this helps a bit more !
GaryGB