Jump to content

Problems with GeoLock program


hjwalter

Recommended Posts

Hi all,

 

There are many FS9 scenery objects, which can only be positioned within a confined/specified geographical area because they are so called "Geo-Locked". If one tries to position such an object, e.g. via the Abacus EZ program, anywhere outside that geographical area, an error message is displayed and the objects concerned will/can not be positioned there.

 

This GeoLock program should be able to remove these Geo Locks or even to create new ones ..... BUT ...... it somehow does not seem to work, so I hope one of you experts out there has some more experience with this program and can point me to something I may be doing wrong.

 

In the GeoLock manual it states that one of the default FS9 BGL files (e.g. Orlando.bgl) has all it's scenery objects Geo-locked to that specific area and when the GeoLock program is (test-)pointed to this file it displays the geographically locked co-ordinates correctly for each scenery object, either in bulk or selectively. When these are then unlocked by pressing the "unlocked" button, the co-ordinates concerned disappear correctly and a new BGL file is created with the name: "Orlando-unlocked.BGL". The original "Orlando.BGL" file must then, for safety reasons be de-activated and be replaced by the new one in the same position.

 

However, when trying to re-position any of the objects from the new "Orlando-unlocked.BGL" file elswhere, e.g. via the Abacus EZ object placement program, an error message is displayed saying that the objects concerned are still locked in their original area. Shutting FS9 down and re-starting makes no difference.

 

HELP !! ------ Please.

 

Regards and thanks in advance for any ideas.

 

Hans

Link to comment
Share on other sites

Tom,

 

Thanks for your reaction but when the EZ program produces the error message, there is no choice or possibility to disregard it and to somehow place/position the object concerned anyway.

 

Yes, it now seems that the problem must be attributed to the EZ program, which somehow cannot handle ex-GeoLocked models and/or their related Guids. Great pity.

 

Hans

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...