FSX (Can I) Combine multiple scenery BGL files?

[QVA70]

Guys I am installing a scenery project that contains all of its scenery objects as individual BGL files.
I would like to edit this scenery in ADE and import a scenery objects file as I would with other sceneries to allow me to do this.
Can I combine these multiple scenery object BGL files into one file, and if so how?

Cheers

Andrew

 

[scruffyduck]

https://www.fsdeveloper.com/forum/resources/library-creator-xml.86/ may be able to do this. I don't know if it needs mdl files rather than bgl files containing the object(s) Someone else may have a better answer. Also Arno is on vacation I think but is probably back soon

 

[QVA70]

Thanks Jon for that info. I have had a quick look at MCX but cant find anything so I'll await Arno's return from his holidays.

Cheers

Andrew

 

[RED COOL]

Turn everything into XML file and compile it into a big bgl file
The XML should contain infos such as Mdl files paths to make the library and scenery placement of these files.
Airports should be able to be included just fine (never tested this one )


PS. Some vector bgl files are not originally XML files so these won't be merge

 

[tgibson]

Why do you want to do this? It won't make any difference on how the sim runs.

 

[QVA70]

Hey Tom

I want to be able to edit the airport using ADE and import all the scenery objects as one file so they show instead of trying to figure out which objects are which.

Andrew

 

[scruffyduck]

Hey Tom

I want to be able to edit the airport using ADE and import all the scenery objects as one file so they show instead of trying to figure out which objects are which.

Andrew

Let's be clear that are you talking about adding the models (mdl files) from some other source to the main ADE project and compile them into the airport bgl file. Then place these objects using ADE? Assuming that you have the rights to extract mdl files from their original source and add them to your work? You can add mdl models directly into an ADE project.

It sounds a bit like the placement data for the objects are actually already in the ADE main project file.

 

[Tim Collins]

I believe MCX can create a library from a collection of mdl files, but it's much easier to use Library Creator (as linked to by Jon). LC does need the mdl files to work with, so you'll have to convert the bgls to mdl format. MCX can do that.

 

[QVA70]

Hi Jon

The project is a third party airfield that is rather well done, however the author has used a single BGL file for every single object so there are some 70 or so object BGL's. I have no way of seeing the objects or there locations unless I import each BGL into the object editor and then try to import them into the AD4 project file. I am only using the project for myself so I don't foresee a copyright issue. With previous projects I would simply import the objects.BGL (that contained all objects in the project) and manipulate them as I desired.

Andrew

 

[QVA70]

G'day Tim

I believed that MCX may be able to help me but I couldn't find a reference in Arno's manual to guide me with the process .

Andrew

 

[Tim Collins]

It’s very easy to convert bgl files to mdl in MCX. Library Creator will then compile the collection to a library bgl for you.

To convert the bgls to mdl, use the Batch Converter in Wizards (top toolbar in MCX). You can select all of the target bgls to be done in one go. No need to enter anything in the Operator box, just select your target folder and use the appropriate Writer (FSX, P3Dv2, P3Dv4 or P3Dv4.4). In Library Creator, select New to open a new library, use Add MDL to add all of the newly-created mdl files, then Save Library (where you can determine the name of your new library and its location). You will need to link the appropriate SDK files in both MCX and Library Creator, but this is a once-only job.

 

[Pyscen]

Hi Jon

The project is a third party airfield that is rather well done, however the author has used a single BGL file for every single object so there are some 70 or so object BGL's. I have no way of seeing the objects or there locations unless I import each BGL into the object editor and then try to import them into the AD4 project file. I am only using the project for myself so I don't foresee a copyright issue. With previous projects I would simply import the objects.BGL (that contained all objects in the project) and manipulate them as I desired.

Andrew

Hello Andrew

Just wondering if you have tried to contact the author on this matter. To be perfectly honest, if you are doing this for your private use, why are you asking "how to" do this in a public forum? Both members and non-members of this site can read it and learn how to change/disassemble any scenery they wish. Doesn't make it private any longer.

G'day Tim

I believed that MCX may be able to help me but I couldn't find a reference in Arno's manual to guide me with the process .

Andrew

There is 1 reason why it isn't referenced on "How to... " by Arno (this is true for all of his tools). Copyright is the main reason! The very same reason why Jon doesn't do so in regards to ADE.

 

[Tim Collins]

Let me make it clear in case there any misunderstanding. I do not condone or encourage copyright theft in any way. I do recognise that people modify others’ sceneries for their own purposes, and I think the compiling of several bgls into a library is a reasonable technique to advise on.

 

[Pyscen]

Let me make it clear in case there any misunderstanding. I do not condone or encourage copyright theft in any way. I do recognise that people modify others’ sceneries for their own purposes, and I think the compiling of several bgls into a library is a reasonable technique to advise on.

The point is: This is a Developer's site. Modifying 3rd party sceneries clearly isn't Developing one's own scenery. Modifying 3rd party sceneries without permission is clearly a violation of copyright. Private use should be kept private.

 

[Tim Collins]

I will keep my mouth (and keyboard) shut in future!

 

[tgibson]

Don't worry, some of use don't agree with that and will help you.

 

[Tim Collins]

Don't worry, some of use don't agree with that and will help you.

I’m fine - it wasn’t me asking for help. As this thread demonstrates, I develop my own scenery and I’m very happy for users to adapt it to their own needs as they see fit, as long as they don’t redistribute it.

 

[Pyscen]

Don't worry, some of use don't agree with that and will help you.

Hello Tom...

Does your statement have any legal foundation to it? Mine does. Or are you suggesting that both Jon's and Arno's intentions for their software were to be used in such a manner? I don't think they would agree with that.

 

[scruffyduck]

Can I remind everyone that this is not the right place to discuss legal matters. Also copyright law may differ by jurisdiction. I recently became the target of copyright infringement trolls (for images as it happens) I spent a lot of time in conversation with a very knowledgeable copyright lawyer based in the UK. This centered on the issue of tools that might enable the user to infringe copyright.

The topic exchange is here. I do not know if you need an account to read this. Also it is written on the basis of UK Law.

Tools the Enable Copyright Infringement - Copyright Aid

As it concludes I don't think my software puts me at any real risk of being accused of aiding or encouraging copyright infringement.

 

[Tim Collins]

Hi Jon - that's a very interesting discussion (no, it doesn't need an account to read), and I think you're quite right that neither your software nor Arno's puts either of you at risk, but both potentially enable copyright infringement. However, I think the warnings given by you both are quite sufficient and that modifications of software for limited personal use (in UK at least) are unlikely to generate any legal angst.

In the context of whether discussion of modifying third-party software should be allowed at FSD (as Doug appears to be concerned about), I think that's a slightly different issue and one which the admins of the site should think carefully about. But I think perhaps this should be a separate, new topic.