• 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.

change txt code for SBX?

shedman51

shedman51

Messages
79
Country
australia
When I create the text code for the library in SBuilderX. the text code still calls the object as an FS9 object and I have to change one number from 1 to 2. Is it possible in future versions to have to text creation options, one for FS9 and one for FSX objects? This way I could copy and paste the whole file instead of editing the line and pasting it into the file at SBX.
CDF4D5794EE9845302EC7E8C709CCFE1 1 5 24 1 aeb_FSX_Windmill_10m
{cdf4d579-8453-4ee9-8c7e-ec02e1cf9c70} 2 4.01 2.05 1 AEB_Windmill_10m
 
Last edited:
Hi,

I did not realize SBuilderX updated its TXT format. I guess it would make sense to use the FSX notation for FSX libraries and the old one for FS2004 libraries. I'll put it on the todolist.
 
I have release a new version that can export FSX GUIDs for SBuilderX as well now.
 
Hi Arno, the SBX format needs to insert the filename in the first line of the text file otherwise SBX can't see it. Can you please add this to your todo list for the next version. I added [aeb_FSX_lib1] into the first line of the text file and and it worked fine.
Alan
 
OK, I will add that. I'll see if I can make a small update of the release soon for this.
 
Arno, it would be remiss of me to add that I am one of the many people who have watched the work you have done over the years as a service to the SIM community and used your resources but have not taken the opportunity th publicly thank you. I am one of the great unwashed who has had only the slightest training in basic programming and without your software, I would have given up years ago. Your work is much appreciated.
 
Hi,

I have updated the file. So if you download it again it should work now.
 
Hi Arno

I am finding SbuilderX does not like the change in format of the GUIDs in the txt file being produced for FSX.
The previous format is acceptable ie 1234ABCD1234ABCD etc and not {1234ABCD-1234ABCD- etc.

Iain
 
Hi Iain,

Humm, the thread starter indicated the opposite. I am a bit confused about that :confused:

But you can always use the option to export the TXT files as for SBuilder (not SBuilderX), they should still contain the FS2004 style GUIDs.
 
Hi Arno

I have failed to replicate the error message I got last night with SBuilderX, so I appear to have been hasty in my assumption, so my apologies.

However one thing the original poster asked was that the first number that follows the Guid in the txt file for FSX objects be changed from 1 to 2. With that change in place SBuilderX will then show the objects are coming from a FSX library rather than a FS2004 library which is what is happening at the moment.

Iain
 
Hi,

Sorry, I missed that part. I will add that change as well.
 
Hi,

I have uploaded another small fix.

The behaviour is now as follows. If you export a SBuilder TXT file you always get the FS2004 style GUID and type 1.

If you export a SBuilderX TXT file you get a FSX style GUID and type 2 for a FSX library, for a FS2004 library you still get a FS2004 style GUID and type 1. The SBuilderX TXT has the library name defined at the top between [].

I hope this fixes all problems :). Just download again from the downloads section.
 
Hi Arno

The library name added at the top of the FS2004 txt would also be welcome. The format is the same as for FSX.

Iain
 
OK, if both versions of SBuilder can handle that it would be good to add indeed.
 
You must log in or register to reply here.
Back
Top