I thought I had it all clear to me but I'm still a bit confused about the relationship between the different Orbx products and how they compare.

 

My understanding is you have 3 categories - mesh which would be FS Global, textures which would be FTX Global and finally landclass which would obviously be OpenLC. Or if not using Orbx products it would translate into FSGenesis for mesh, GEX for textures and UTX/SceneryTech for landclass.

 

This makes me wonder where does FTX Vector come into the picture and how does that product compare to OpenLC? The line between those two products feel a bit blurry to me.

Vector is accurate roads - river - lakes - shorelines not having it would not be a great experience not to mention in August they are upgrading it and its day and night looks awesome

I thought I had it all clear to me but I'm still a bit confused about the relationship between the different Orbx products and how they compare.

 

My understanding is you have 3 categories - mesh which would be FS Global, textures which would be FTX Global and finally landclass which would obviously be OpenLC. Or if not using Orbx products it would translate into FSGenesis for mesh, GEX for textures and UTX/SceneryTech for landclass.

 

This makes me wonder where does FTX Vector come into the picture and how does that product compare to OpenLC? The line between those two products feel a bit blurry to me.

 

Hi Richard,

 

there's a difference between landclass information and vector information. The first one relates to the placement of different types of textures into FSX's terrain -- where goes the forest textures, field textures, desert textures etc. -- and this includes cities, villages etc. The second one, as the name suggests, relates to the placement of vectoring-based information, like roads, coastlines, rivers etc. 

 

UTX, for instance, provides both vector and landclass information. Orbx made all this separately. Good thing about the Orbx option is that, while vector information is limited to a region in UTX's case, FTX Vector covers the whole world. But landclass information, in Orbx's case, is still limited to a region -- like UTX. 

 

So actually that would be four layers: mesh (FS Global or FSGenesis); your set of textures (GEX or FTX Global); the placement of these textures (UTX or OpenLC); the placement of rivers, coastlines etc. (UTX or FTX Vector). 

Ok, got it. Thanks guys!

 

So now I just need to figure out if replacing what I already got with FTX Vector and OpenLC would be worth it and I realize that is a question I need to answer myself.

cvearl wrote:  "So it's only as necessary as you would feel UTX is. Like UTX, it adds missing lakes and rivers and other water bodies. Adjusts shorelines (shapes) to match Google Earth. Adds some main roads, railroads and things like that that are otherwise missing from a map standpoint."

 

Yes, but it´s way behind UTX concerning accuracy and detail!

 

Check the river going through Bangkok in Thailand, half is missing, and many other issues around the world.

 

They release the products not completed, and we end up with countless SP´s - I won´t pay for that, and def. not pay for their arrogant "customer service".

 

PS: Talking about Vector here, don´t know the LC yet...

 

Take a screenshot and post in their support forum so they can fix it in a patch. A program that covers the whole world will not be perfect and bug free.

Picture speaks but I cant find a single pic even on the ORBX forum. Anyone care to post the 4 layer effect?

Look in the P3D forum.....but with Global/Vector/OpenLC

Not sure I'll bother with this. Already have the FTX England, Wales and Scotland areas along with FTX Global coupled with UTX Europe. If I were to get this I'd have to also get FTX Vector too! All adds up I'm afraid. Only fly in Europe so no need for a global vector product and then buying landclass for EU.

 

And not only that......   As it looks now you can also kiss your precious FTX England/Wales/Scotland goobye....

 

No word about that on the FTX  OLC page. Was wondering about it because i have FTX England/Wales/Scotland/N-Ireland too ( and like 'em very much). Program is called ' FTX:Global OpenLC Europe', right. When i open up my FTX Central i have two buttons there : FTX Global and FTX Europe. Can only select one...... 

 

Obviously FTX Global OLC Europe will work with FTX Global but will it work with FTX Europe, i.e. England/Scotland/Wales/N-Ireland ? .....

 

Seems like the answer is no......  

 

So now what.....  Was on the verge of buying because i love what i see in the screenies but now i'm not so sure anymore. I don't want to loose my precious FTX/UK.....

 

Remarkable, isn't, Both FTX add-ons have Europe in their name but you can't use them together...

 

And there's another thing : what about if UK with FTX Global OLC Europe looks as good ( or maybe even better.... ) as FTX/England/Wales/Scotland/N-Ireland all together ??....

 

Then i can just throw away the latter 4 editions...  :o

 

Cheers,

Dilemma Peel 

You don't need to use them together.  Your specific regions, like England, already have the correct landclass and special textures, so the Open LC Europe doesn't add anything to it.  Your Orbx regions are even better than the Open LC Europe is what I'm saying.  Of course you can use hybrid mode if you're flying into or out of a special Orbx region from or to another European destination.  You seem to be frustrated over nothing.  What Orbx has done all makes perfect sense.

You don't need to use them together.  Your specific regions, like England, already have the correct landclass and special textures, so the Open LC Europe doesn't add anything to it.  Your Orbx regions are even better than the Open LC Europe is what I'm saying.  Of course you can use hybrid mode if you're flying into or out of a special Orbx region from or to another European destination.  You seem to be frustrated over nothing. 

 

Aha,Ok. 

 

So you did buy OpenLC Europe and tried it with FTX/England/Wales/Scotland/N-Ireland with FTX Europe selected in your FTX Central, right ?....

 

Actually i don't think so because then you would've seen misplaced textures and other anomalies all over the place....

 

It is not called Global OpenLC Europe for nothing, you see. It will work with FTX Global only, not with FTX Europe.

 

And frustrated i am not, my young padawan.

So you did buy OpenLC Europe and tried it with FTX/England/Wales/Scotland/N-Ireland with FTX Europe selected in your FTX Central, right ?..

 

You cant use them together you pick one or the other - thats how it works combining the two is impossible or maybe the hybrid mode works not sure as I do not have yet but plan on getting it tomorrow

Hope my wife will not find out

every time i spend more than 100 sim related i have to take the wife out shopping , if she ever finds out how much has gone into fsx alone ill have to move next to the mall ...

You cant use them together you pick one or the other 

 

Yup, that's what i said, " with FTX Europe selected " ... ( not FTX Global ) 

Anyone know how to uninstall LC Europe? I get this unhandled exception when I try to open FTX Central now.

 

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
   at System.ThrowHelper.ThrowKeyNotFoundException()
   at System.Collections.Generic.SortedList`2.get_Item(TKey key)
   at FTXCentral.FTX_Environment.CopyBuildRestoreBat()
   at FTXCentral.FTX_Environment.ApplyRegionChanges()
   at FTXCentral.FTXC.InitSystem()
   at FTXCentral.FTXC.InitAll()
   at FTXCentral.FTXC.Timer1_Tick(Object sender, EventArgs e)
   at System.Windows.Forms.Timer.OnTick(EventArgs e)
   at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5477 (Win7SP1GDR.050727-5400)

----------------------------------------
FTXCentral
    Assembly Version: 1.0.4.3
    Win32 Version: 1.0.4.3

----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 8.0.0.0
    Win32 Version: 8.0.50727.5420 (Win7SP1.050727-5400)

----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)

----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5468 (Win7SP1GDR.050727-5400)

----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)

----------------------------------------
System.Runtime.Remoting
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400)

----------------------------------------
System.Configuration
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5476 (Win7SP1GDR.050727-5400)

----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5476 (Win7SP1GDR.050727-5400)

----------------------------------------
ivy8i8xv
    Assembly Version: 1.0.4.3
    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)

----------------------------------------
System.Core
    Assembly Version: 3.5.0.0
    Win32 Version: 3.5.30729.5420 built by: Win7SP1

----------------------------------------
b92rcsne
    Assembly Version: 1.0.4.3
    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)

----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

 

Try running the latest ORBX libraries again. Usually fixes problems with FTX Central.

I thought I had it all clear to me but I'm still a bit confused about the relationship between the different Orbx products and how they compare.

 

My understanding is you have 3 categories - mesh which would be FS Global, textures which would be FTX Global and finally landclass which would obviously be OpenLC. Or if not using Orbx products it would translate into FSGenesis for mesh, GEX for textures and UTX/SceneryTech for landclass.

 

This makes me wonder where does FTX Vector come into the picture and how does that product compare to OpenLC? The line between those two products feel a bit blurry to me.

 

 

Ok, got it. Thanks guys!

 

So now I just need to figure out if replacing what I already got with FTX Vector and OpenLC would be worth it and I realize that is a question I need to answer myself.

 

Ofcourse it is explained clearly in the manual, page 15  ^_^

For all those wondering about how Orbx products work exactly download and read the PDF in the provided link.On  page 17 you can read all about the relation between regions and global products It really is quite simple  :wink:

 

http://www.orbxsystems.com/forum/topic/74345-the-definitive-guide-to-ftx-products-the-go-to-source-of-ftx-information/