Re: objects disappear/ changes don't seem to 'save'

[bmoat]

Hi, all!

I have been working on a scenery for some time now, testing it in both fs2k2
and fs2k4, and all seemed to be fine.

Then, for no apparent reasons, airport for windows (3.0 build 188) balked at
installing an API macro into the scenery. As I continued to try to get it to
install the macro, AFW seemed to stop saving the changes I made, or both
versions of the simulator stopped recognizing the changes from AFW.

I have checked the preferences/paths on both AFW and FSDSpro v1.5, and
eventually went so far as to completely remove/uninstall AFW, FSDS, and fs2k4,
deleting any remaining folders, plus the shortcuts on the desktop, re-starting
the computer, and re-installing all three programs, only to find myself in
either the same, or worse shape. At some point, a sudden 'peak' appeared in
the scenery, attempting to create a flatten area to force it down does no good.

Finally, as my attempts to fix have gone on, (trying known good working apis
in place of the one in question, etc...), I found that eventually, huge
sections of my scenery no longer show up, and once again, my attempts to change

don't seem to change anything... unless for the worse.

Has anyone got an idea what could be causing this wide ranging wierdness? I'd
appreciate any input anyone has to offer.... ;P

Thanks,

Brian Moat

I thiiiiiink I have found the problem, or at least a solution. Let's see if
anyone else has run across this one...

I was going through the scenery in AFW looking for any signs of a problem,
especially where my most recent changes took place. In doing so, I happened to

look at the list of 3-D objects in the 'sections' area, and I noticed that the

last 10 buildings or so had no number called out in the 'comments' column,
which apparently AFW had created numbers associated with the objects up to a
point, and then it stopped creating them. I went through and edited each of
these items, adding an appropriate number to each one.

I decided to check other 'sections', and found that several flatten areas,
buildings, and excludes didn't have numbers in the 'comment' area, so I
repeated the above procedure for each of these 'un-named' objects, and at this
point, my scenery returned to 'almost normal' condition. I'm still having
trouble placing the object that I was originally trying to place, although I
got it to show up, it just absolutely refuses to show up where I want it to.
Must be quicksand.... I can move it a couple of blocks from where it should
be, and it shows up, but not right where it should be. I'll leave it as it is,
for now, I doubt anyone will notice it should be a block or two to the East...

Anybody having these kind of troubles with the newer builds of AFW???

Brian

[wsieffert]

Brian,

The API probably has a LAT/LON set internally in the API. Open the API and
look for lat/lon instead of the %1, %2 place holders.

Bill Sieffert

Hi, all!

I have been working on a scenery for some time now, testing it in both fs2k2
and fs2k4, and all seemed to be fine.

Then, for no apparent reasons, airport for windows (3.0 build 188) balked at
installing an API macro into the scenery. As I continued to try to get it to
install the macro, AFW seemed to stop saving the changes I made, or both
versions of the simulator stopped recognizing the changes from AFW.

I have checked the preferences/paths on both AFW and FSDSpro v1.5, and
eventually went so far as to completely remove/uninstall AFW, FSDS, and fs2k4,
deleting any remaining folders, plus the shortcuts on the desktop, re-starting
the computer, and re-installing all three programs, only to find myself in
either the same, or worse shape. At some point, a sudden 'peak' appeared in
the scenery, attempting to create a flatten area to force it down does no good.

Finally, as my attempts to fix have gone on, (trying known good working apis
in place of the one in question, etc...), I found that eventually, huge
sections of my scenery no longer show up, and once again, my attempts to change

don't seem to change anything... unless for the worse.

Has anyone got an idea what could be causing this wide ranging wierdness? I'd
appreciate any input anyone has to offer.... ;P

Thanks,

Brian Moat

I thiiiiiink I have found the problem, or at least a solution. Let's see if
anyone else has run across this one...

I was going through the scenery in AFW looking for any signs of a problem,
especially where my most recent changes took place. In doing so, I happened to

look at the list of 3-D objects in the 'sections' area, and I noticed that the

last 10 buildings or so had no number called out in the 'comments' column,
which apparently AFW had created numbers associated with the objects up to a
point, and then it stopped creating them. I went through and edited each of
these items, adding an appropriate number to each one.

I decided to check other 'sections', and found that several flatten areas,
buildings, and excludes didn't have numbers in the 'comment' area, so I
repeated the above procedure for each of these 'un-named' objects, and at this
point, my scenery returned to 'almost normal' condition. I'm still having
trouble placing the object that I was originally trying to place, although I
got it to show up, it just absolutely refuses to show up where I want it to.
Must be quicksand.... I can move it a couple of blocks from where it should
be, and it shows up, but not right where it should be. I'll leave it as it is,

for now, I doubt anyone will notice it should be a block or two to the East...

Anybody having these kind of troubles with the newer builds of AFW???

Brian

[bmoat]

Hi, Bill!

I checked that, the api was ok, and I couldn't only place it in one place, I
could place it all over, there was one place I couldn't place it (where it
belonged, of course!) Anyway, I had another odd problem with a rectangular
elevated patch in the center of the scenery that I couldn't remove for love nor
money, so I finally broke down and reverted back to AFW 2.95 build 166 and
re-compiled the scenery, and it all returned to normal.

Thanks for the tip, if nothing else, it will come in handy should I need to
decompile and import a scenery in the event I lose the AFW working files..
I've had to do that, and was just changing the LAT/LON in the scasm to move the
re-generated apis, a real pain...

Thanks for replying,

Brian

Brian,

The API probably has a LAT/LON set internally in the API. Open the API and
look for lat/lon instead of the %1, %2 place holders.

Bill Sieffert

Hi, all!

I have been working on a scenery for some time now, testing it in both fs2k2
and fs2k4, and all seemed to be fine.

Then, for no apparent reasons, airport for windows (3.0 build 188) balked at
installing an API macro into the scenery. As I continued to try to get it to
install the macro, AFW seemed to stop saving the changes I made, or both
versions of the simulator stopped recognizing the changes from AFW.

I have checked the preferences/paths on both AFW and FSDSpro v1.5, and
eventually went so far as to completely remove/uninstall AFW, FSDS, and fs2k4,
deleting any remaining folders, plus the shortcuts on the desktop, re-starting
the computer, and re-installing all three programs, only to find myself in
either the same, or worse shape. At some point, a sudden 'peak' appeared in
the scenery, attempting to create a flatten area to force it down does no good.

Finally, as my attempts to fix have gone on, (trying known good working apis
in place of the one in question, etc...), I found that eventually, huge
sections of my scenery no longer show up, and once again, my attempts to change

don't seem to change anything... unless for the worse.

Has anyone got an idea what could be causing this wide ranging wierdness? I'd
appreciate any input anyone has to offer.... ;P

Thanks,

Brian Moat

I thiiiiiink I have found the problem, or at least a solution. Let's see if
anyone else has run across this one...

I was going through the scenery in AFW looking for any signs of a problem,
especially where my most recent changes took place. In doing so, I happened to

look at the list of 3-D objects in the 'sections' area, and I noticed that the

last 10 buildings or so had no number called out in the 'comments' column,
which apparently AFW had created numbers associated with the objects up to a
point, and then it stopped creating them. I went through and edited each of
these items, adding an appropriate number to each one.

I decided to check other 'sections', and found that several flatten areas,
buildings, and excludes didn't have numbers in the 'comment' area, so I
repeated the above procedure for each of these 'un-named' objects, and at this
point, my scenery returned to 'almost normal' condition. I'm still having
trouble placing the object that I was originally trying to place, although I
got it to show up, it just absolutely refuses to show up where I want it to.
Must be quicksand.... I can move it a couple of blocks from where it should
be, and it shows up, but not right where it should be. I'll leave it as it is,

for now, I doubt anyone will notice it should be a block or two to the East...

Anybody having these kind of troubles with the newer builds of AFW???

Brian