hey dude,

the last post sounds like the run time libraries again - follow deathwalkers advice same as before to see if it helps.

the li01_01 thing is the code freelancer uses to identify the bases (id assume they have to be unique for your new system but i may be wrong).theres a link to a list of them and many more usefull things in the compilation thread at the top of the tutorials forum and in chip's own newbie help thread in this forum.
you get to know what they all look like in several ways - you can look for pics or (my fave) fly there and have a looksee - has the advantage of fights and loot if its in one of the exiting sectors

the crash may be related to the above

not sure about adding patrols and things - think it has something to do with defining zones and encounters but its bin a while since i read anything about it so anal vocalisation cant be ruled out here

the names thing is controlled by the dll and you will need to have unique id numbers for the call ( not sure but i thought the prog set that up for you) and then entering the text in the correct format.

all in all im gonna echo the advice chips gave you - its far better to know how to do these things manually by reading the tutorials as it makes fault finding and debugging a lot easier.

stick at it though - its a nice feeling flying in your very own sector in your own ship.

as a side point anyone ever try putting a space station on a planet to see what happens? erm sorry im starting to think professional help may be needed here - luckily i still have her phone number


dr del


you know why you never get a fortune cookie that says "your about to catch an embarassing disease"? its not because of your fine taste in women ...its just that they want to keep on selling fortune cookies

Are you sure FL explorer works on XP?

But the worst happened when Bargib started singing Campfire songs!-----Baptism of Fire

Yes - Freelancer Explorer works on Windows XP - that is certain

FL Explorer was designed for XP if I understood his page correctly

FLE is good for a few things, I use it while manually editing a system because it's a quick way to get a basic visual map of the system to make sure everything is falling into place where I want it. I also use it to place patrol paths since it's a lot easier than trying to figure out the dimensions for each leg on your own, the paths do require a bit of cleanup work afterwards but the time it saves me in placing, rotating and sizing the path zones is worth the few minutes of cleanup. It also has a nice little feature to preview the wireframe of many objects, I find that helpful when I can't remember exactly which station archetype I wanted to use.

When all is said and done however it's still good to know how to do most or all of that by hand. That knowledge is essential when you're debugging things and there are better ways to setup the zones that what FLE will do for you, especially when it comes to encounters.

I whole heartedly agree there. Knowing what each feature in Explorer can do by hand as well is a vaulable asset. I use it just to check that zones are correctly place is all. There is nothing better to use than checking your calculations don't have certain zones overlapping each other than by actually seeing those zones on FL Explorer - as well as that where you just put them is actually where you want them. It certainly helps me when i don't have a calculator to hand and have lost my diagram of the system i am making.

Victor - do your patrol paths appear on the map as patrol paths for you system?