AR196 Project in AD2K

[Ivan]

Hi Smilo,

Perhaps you have a different method, but I believe you should consider using the same scale across all the Fuselage Components which means the Tail Cone you just created probably isn't going to be the limitation that sets the scale for all the other Fuselage Pieces.

Hey Hubbabubba,

Whadyamean about overkill??? I try to work within AF99 for the most part which is hardly gonna be overkill cuz there aren't enough resources to really do that.

- Ivan.

[hubbabubba]

Hi Smilo,

Perhaps you have a different method, but I believe you should consider using the same scale across all the Fuselage Components which means the Tail Cone you just created probably isn't going to be the limitation that sets the scale for all the other Fuselage Pieces.

Hey Hubbabubba,

Whadyamean about overkill??? I try to work within AF99 for the most part which is hardly gonna be overkill cuz there aren't enough resources to really do that.

- Ivan.

Hey Ivan, you know that we are both a bit, shall we say, compulsive when it comes to over-doing it. We go into modifications that only us see. If it ain't overkill, then what is it?

When I was working within AF99 boundaries (I was tempted to say "chains"...), I would over-do some parts intentionally, using them as reserve-sorta for the future. This way I was less frustrated when being in a pinch for polygons.

smilo, it does look like a derrière de bébé, but the color suggest a good dose of Zincofax or Desitin is in order!

[smilo]

smilo, it does look like a derrière de bébé, but the color suggest a good dose of Zincofax or Desitin is in order!

now, that's funny!
thanks H, i needed a chuckle.

in self defense, i used a 256x256 bmp
that came from the ad2k tutorial ugly100 project.
next, maybe i'll drop in the grid you sent me.
but first, i need to clean up that tail section.

[smilo]

just to let you know,
my daughter has been visiting
for the past week or so.
needless to say,
i haven't spent a lot of time on the 196.
although, i did mess with it a bit yesterday
and plan on giving it some time today.

i have redone the tail cone area
and spent an inordinate amount of time
on the junctions with the cone area
and the vertical and horizontal stabilizers.

ad2k has a feature to do this in the wing area,
but it won't work in the tail area.
i won't go into the bloody details,
unless someone really wants to know.

now, i need to put the all pieces together
and then, the fun part, work on the coding
in order to get everything to work visually in cfs.
as i've said before, this is the key to the whole project.
until i can get this process down pat,
the parts are just a jumbled mess.
that is, unless i want to use the project in fs2000,
then it's accomplished automatically....dang

i need some coffee and then it's off to work.

[smilo]

arrrgh...
after spending hours in a futile attempt
at trying to figure out the visual coding,
i was treated to this wonderful visual display.

suffice to say, the program froze
and all work was lost.
note that all menu items
and the buttons are grayed out.

fortunately, when i began work today,
i made a file backup and moved it to another machine.
the bad news is, i didn't make backups
as i went along today,
so all is lost from this session.

i would be really pissed
if i had been successful today,
but as it is,
nothing of importance is gone,
just time.

[Ivan]

Darn. That must hurt.

- Ivan.

[No Dice]

Well what we do down here in the South, IS SHOOT OUR COMPUTER, KICK THE DOG, PUT THE OLD LADY TO BED,OPEN YOUR MOST FAVORITE BOTTLE OF RIPPLE PINK, and then start kicking some@#$% why that showed up in blue I have no idea?

Dave

[smilo]

yup, it was mildly annoying,
but like i said,
there was nothing of great worth lost.
just time, and i did get something out of the deal.
if nothing else, i'm learning to save
and stash the main file early and often.

it's like any learning experience,
trial and error....mostly error.

i only wish i knew what i am doing wrong
so i could stop whatever it is
that seems to irrate the program.

i actually took a break and then,
went back at it for a few more hours.
still no luck with the coding sequence.

i guess i'm just a glutton for punishment.
or not.
i'm done for the night.

[Ivan]

The format looks to me like "Access Violation at address 0x0????? in module <Something or Other>

Keep in mind that I don't know French and am only guessing.

I get those fairly often but usually they are from CombatFS itself.

- Ivan.

[hubbabubba]

The format looks to me like "Access Violation at address 0x0????? in module <Something or Other>

Keep in mind that I don't know French and am only guessing.

I get those fairly often but usually they are from CombatFS itself.

- Ivan.

That's pretty much it, Ivan.

Access violation at address 004CFC84 of 'AD 2000.exe' module. Writing of the address 00000004.

That's all it says. The address itself is basically at the very beginning but, beyond that, I'm powerless. I'm curious to know, smilo, how your work is preserved. In AF99, for example, parts are written in XYZ.afp, components in XYZ.afc and assemblies in XYZ.afa. How does AD 2000 stores work in progress?
Now that No Dice has convinced Abacus to re-sell AF99, it could be a good alternative, don't you think?

[smilo]

as far as i can tell,
ad2k work is stored in a .3DM file
within the specific project folder.
for extra security, i copy it
and move the copy to another computer.
what i need to learn to do
is make copies more often.
there are no parts, components,
or structures as in af99,
only chains and lines,
which are a series of points.

i am having a problem understanding
this address access violation business.
i had just created a new sub assembly
and attempted to move a part,
or group of chains into it
from another sub assembly.

i have taken this action
on several occasions with no problems.
it is a standard procedure
that even has a menu listing.

as for purchasing af99,
no need, i already own a copy.
my past experiences with it
have left me less than ecstatic.
i may be a glutton for punishment,
but reached the line with it long ago.
i decided to leave it to you guys.
i just didn't have the patience
to fight with it anymore.
i'm actually amazed that i've stuck
with ad2k this long.
heck, this is even my second go round with it.
truly amazing.

[Ivan]

Hi Smilo,

Basically what is happening is that most likely there is a bug either in your application (AD2000) or one of the library routines it is calling. An address is most likely getting corrupted and the result is that the computer tries to access (write) to an area of memory that is not writable or is a secure part of the computer's system software.

It is a bug or corruption of some type.

I don't know there is a proper fix.

- Ivan.

[No Dice]

I really do not have a clue, but can you try the 2K2 fix for the hell of it.

Dave

[smilo]

about all i can say is, so it goes
and keep making back ups.
lots of them.

also, i am able to build individual sections,
each as a master project, such as the tail,
the wings, floats and so on.
then later, when it's time to put it all together,
i can import the individuals into the main project.
this should be more secure and save space.
but that's way down the road.

i don't know about the ad2k2 fix
or if it can be used in ad2k.
i will check it out this weekend.

[Ivan]

Hey Smilo,

How are things coming? With the discussion of AIR files, if you send me the visual model, I can try to slap together something for you to start tuning.

- Ivan.