FSX Can't place custom objects

[lordofwings]

Just noticed an omission in SBX. While one can use the Object Tool to place virtually anything, if one has a custom object in a custom library (I do), then one cannot use SBX to place that custom object on the SBX project by stating its GUID.

 

[rhumbaflappy]

SBuilderX allows you to place a MDL directly.

To place an object that is compiled to a self-made library, you need to go through a few steps.

Find the C:\Program Files\SBuilderX313\LibObjects folder. In that folder, open the objects.txt file in notepad.

; This file should only be used with:

; SBuilderX 3.04 or later
; ***********************

; Lines started by ; are comments and are ignored
; Lines enclosed in [] are category designators.
; You can have more objects references in secondary files
; using the include directive in the "objects.txt" file.
; The secondary files should exist in the SBuilder/Tools/
; folder and they are processed after the processing of
; the primary - "objects.txt" - file.

; You can enter your objects in any of the following 3 forms:

; 6dc7e21e4f0c4d7395488dac102499a1 0 38 14 1 ag_barn
; 6dc7e21e4f0c4d7395488dac102499a1 1 38 14 1 ag_barn
; {6dc7e21e-4d73-4f0c-ac8d-4895a1992410} 2 38 15 1 ag_barn

; In the 1st case the object is placed using FS8 techniques
; and you can control some extra visibility parameters. In the
; 2nd case it will be placed via SCASM exactly in the same way
; as BGLComp from the FS2004 SDK. In the 3rd case the object
; be placed with FSX' BGLComp.

; SBuilderX 3.13 or later
; ***********************

; 1 - This file and all included (secondary) files have moved to the
; SBuilderX/LibObjects/ folder. It is required that each Category
; should be defined in a single secondary file and that the Category
; Name should match the name of the corresponding secondary file.
; 2 - All object definitions should be moved to secondary files
; 3 - Thumbnails need to be JPEG type. All that is needed is to place
; them in the SBuilderX/LibObjects/NewJpegs folder.
; 4 - The folder containing the thumbnails should have the same name
; as the Category.

include=FSX_airport_objects.txt
include=FSX_animals.txt
include=FSX_autogen.txt
include=FSX_bridges.txt
include=FSX_buildings.txt
include=FSX_gameobjects.txt
include=FSX_generic.txt
include=FSX_hazards.txt
include=FSX_landmark.txt
include=FSX_missionobjects.txt
include=FSX_vegetation.txt
include=FSX_vehicles_aircraft.txt
include=FSX_vehicles_airport.txt
include=FSX_vehicles_land.txt
include=FSX_vehicles_water.txt
include=FSX_waterobjects.txt
include=FSX_MyObjects.txt


Note I have added the bolded line to set up my own objects for placement. Save the objects.txt with the appropriate include name added as above.

In the C:\Program Files\SBuilderX313\LibObjects folder, create a new text document... FSX_MyObjects.txt ( mine looks like this) :

[FSX_MyObjects]
{d43fffe2-e15a-4c9f-82da-815c2be92ce2} 2 10.0 10.0 1 WeirdCube


The format is GUID TYPE X Y SCALE FriendlyName

Save the appropriate lines as above.

Now SBX, when restarted, will allow the group FSX_MyObjects, which contains all the custom GUIDs you typed into the FSX_MyObjects.txt file. You can make a FSX_MyObjects folder, and place thumbnails of the object, and SBX will give you a preview of it.

Unless you want to place lots of these objects, you might want to just place the MDL, and save the extra steps.

If you had lots of library objects, you'll spend a day typing them in.

Dick

 

[lordofwings]

But isn't this double work? I have already several custom libraries I created with FS9/FSX Library Creator which I use to compile with MDLs. So I simply include the library BGL and the corresponding textures.

With FSX my custom library is more or less rendered useless unless I add the model, right? although I am getting the impression that if I add my custom "include" as you showed above, then I can use my own library provided it is deployed in the scenery folder and that the right object GUID from the library is put in the TXT file you indicated. Or... am I wrong? just to make sure I don't do double work.