Hello,
This is my 4th attempt to post a reply, keep getting bumped off when I switch to a different view to look at a file.
The main problem with Atlas on Win 7 is the path ways with spaces in them.
So use " , at the begining of a path way the has spaces and end it with " . example= "C:\program files\flightgear\data" Ok?
The switches --Atlas --palettes --airplane do not need the above.
I do not use the GUI's or the supplied atlas.cmd file. (Even with FGCOM, the gui's for this program work fine in XP, but not WIN7)
When you get involved you will see encoded errors that show path ways that don not contain spaces and start at the root of the C drive.
Smart way and an OLD way dating from DOS days. Or dinosaur days. No nested \directories to weed thru, quick and faster etc.
Not more than one space between --switches.......... ok?
Get the 0.5.0 version which has the added version switch. ( and when invoked shows 0.4.9)
I also got the version to compile also, and used the fonts and default.ap etc......
Get the updated 0.5.0 version of Atlas and the the version to compile to rape and pilage etc
Unpack and put the EXE's in the flightgear\bin\win32 thats all the Atlas and Map exe's.
Make a new directory : Atlas, example: C:\program files\flightgear\data\Atlas
Under the Atlas directory make also a Fonts dir and Palettes dir. (these are where you put the files you took from the build version)
I also for general purpose put some of em in the root of the Atlas dir. like default.ap
Now to build your scenery files with the MAP command.
Same rules about spaces exactly in pathways names.
Map will make 4 more directories in the Atlas directory, consisting of different resolution png's or peg's (you pick), for zooming when usin Atlas.
Map will either work fine or make only so many scenery png's and error out. Not sure the exact cause, lets just say, I won't need a barber for a year tryin to get this to work.
But I fudged it and worked around the problem area here. Seems some of the scenery files Map just don't like...... So, ok, don't use em. I tried downloading new ones
and still, Map does'nt want them. Just errors out. --force helps here, like OB-WAN told me.
So, I fired up Atlas and looked at what I had and what I don't have.. Then slowly but surely I copied what I did'nt have (scenery files) to another directory and edited my
Map.cmd file to reflect where, what pathway wise etc and had Map build the pngs from that point till I filled up 90% of Atlas's World.
And it works just fine for me. Atlas is a work in progress and is a must have if you like Flightgear or serious about it. The graphics and bells and whistles are out of this
world!!!
When it don't work right go to the Dos command window and read it to find out why........ syntax, pathways, to many spaces
I still get errors and complaints about airplane and default.ap etc, but Atlas works fine..
One last part.
When fired up minimize the command window for Atlas and the graph window. Maximize the Atlas main window. click on accept and ok for the port, then deselect and then
accept/select again and ok for port to get you zeroed in on where you are in Flightgear. Make sure you cfg flightgear wizard menu localhost 5500 and add the atlas prop also in advance properties.
I have seen no loss of power with flightgear using both at the same time at all.
But their are the butts also.
And do like Luke did, use the FORCE!!
Prime example of what happens when you put a monkey in a capsule full of buttons and switches...Now, wheres that damn banana?...