A better way inside the Map linker to call the main feature

MoveTo method to field state group

This is gonna be scary, but if it works we got one of the most important Kthura issues tackled

Before I got to work on Star Story today, the cockroaches I had to deal with here kept me away from working on Dyrt, so that comes first!

#9 Should be fixed now

I need a break now, so I'll get back to this later!

Issued as #9

Nope

Well, does it work?

I've replaced the actor picture files with jpbf files

Briggs was looking the wrong way

The reason why this happens is still

I think... I think the altframing is bugged

Now the actors are still in mini form, so the bugfixing is not over yet, but my most pressing matter at had has been fixed at least

Take L

Now I did undummy the actors, but I forgot to rebuild the game resource

the TiledAreas show now

Take XLIX will have to confirm all this!

It was just a typo in the loading function.... Since the starfield was modified manually that bug was bypassed in Lovejoy's story

KLABAMMO! Just as I suspected

Well, if you eliminate all the impossible, whatever remains, however improbable, must be the truth!

Actors undummied

Take XLVIII

Temp dummy on the actor generation...

Checked the entire chain and the only error I found was a scale defintion not in order... This could indeed be why i got the feeling my actors look so "flat", but that doesn't seem likely

Given the state of the error I now must find out if the actors are to blame for all this or not.

There's indeed something wrong with the Tiled Area.... According to my log the height of all TiledAreas is 0

Take XLVII

The Annoying line I likely no longer need

It is now heavily implied it's only the tiled area that is to blame

It appears I made assumptions too soon

MOAR DEBUG!

Take XLVI

Well?

The core drawer does seem to address it all... or at least the logs say so

Take XLV

Another annoying debug line has been put in place

But what then?

Visibility does at least not appear to be the problem

Take XLIV

Syntax error

Take XLIII

Visibility verification!

They confirm though that only the actors are drawn and that the rest is ignored.... Why!

Take XLII

Very annoying debug lines

The results confirm everything the computer does regarding this matter is bullshit

Take XLI

Dominance experiment

The log confirms that all stuff should be present

Nothing relevant

Cosmetic output error....

Take XL

run barf script

Ref error

Take XXXIX

Code typo

Take XXXVIII

Rebuild

Added to the game script

Links it all

Neil link up

I'e added an API routine which may give me some ansers (I hope)

Take XXXVII

I've deactivated the actor scaler as it does not appear to work the way it should

Other closure routines still got issues, though, so there's still work to do

Well it appears I got the lua closure fixed

Take XXXVI

I am required to do rebuild the game itself for that, though

I need to find out if the animator is what causes things to turn invisible

I've put in an extra precaution that should make sure all Kthura Maps are unloaded (this because Lua is on the rampage here and I don't want more trouble than I already got).

Take XXXV

An extra debug line should confirm if indeed most of the map was killed (for no apparent reason)

Now the question is, of course, why this all happened

CWRITE> ____________XXX___XXX_________________X
CWRITE> ___________XXX_____XXX________________X
CWRITE> __________XXX_______XXX_______________X
CWRITE> XXX______XX__________XXX___XXXX______XX
CWRITE> ______________________________________X
CWRITE> ______________________________________X
CWRITE> ______________________________________X
CWRITE> ______________________________________X
CWRITE> ______________________________________X
CWRITE> ______________________________________X
CWRITE> XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Half of the blockmap is gone, which may indicate half of the map is gone as well

At least the actors appear, but now we do have some other bones to pick... They are shown far too small, and their environment has gone.... I'd like to know why that happened.

Take XXXIV

Syntax Error

Take XXXIII

Kind

The destructor should be obsolete now

Constantly All objects are being destroyed, I see

Now I do have a few ideas to make the destructor obsolete, but still I need to check things out!

Now the destructor is called while it shouldn't be (causing a crash in the process).

Take XXXII

!= is not the same as ==, Jeroen!

It KEEPS insisting not not working!

Take XXXI

Whatever causes this bug, it's persistent!

Fucked it all up AGAIN!

I am not definitely pissed off!

Even now that the actor could contain nothing but the correct data I get garbage

Take XXX

I hope

I think I solved the case! (or is that wishful thinking?)

Elementairy, my dear Watson!

This can only mean that the parent layer is somehow not properly set in the Actor record, which should have happened... The question is, of course, why...

Aha... Now the log makes more sense.... The layer for dominance remapping is declared a null pointer....

Take XXIX

I do need to re-test as a few things in the IDE went wrong

Ah... C++ placed the error marker on the wrong spot (what else is new?)

The location where the crash is noted (a debug line just containing a "cout" and a constant string, is what surprises me the most , though.

Apparently.... no work at all! I guess fate is against me after all!

I can at least confirm that normal objects appear to be working under the new code

Well We're still counting on... test XXVIII

I needed a break before the great test would commence

And now it even deems the compilation succesful? Is it really done?

Hmm, it has stopped giving me errors in the Kthura library and now wans the adaptions for the API

That's only half the work, though!

I think the core part of the operation is done....

DUMBLE-ROLLED!

:-P

With C++ desperately trying to get EVERYTHING in a bad manner, there is only one thing left for me to do... I'm gonna fuck up the Kthura library ENTIRELY!

That experimental line was exactly where C++ didn't like me, at all

As expected

Take XXVII

I've tried something but I expect not much from it...

Take XXVI

MOAR stuff

Things appear to go wrong when the actors are being called.... It was to be expected, yet, I wonder what the fuck is going on here!

Take XXV

I've added a debug line in the iterator... Hopefully it answers a few questions

Is the iterator still broken?

The data in the debugging screen doesn't make sense at all.... What the fuck is going on here?

Returning a string is reason to crash?

I see now that the system does follow a different traceback route though, so that is a bit odd

I've ruled out possibilities for memory conflicts now, so NOTHING and I repeat NOTHING could have caused anything here.... Yet it still happens.... and the computer will have to clear up why!

With no more reason to crash, it still crashes

Take XXIV

That was take XXIII btw

Will backspace is a handy key, but still

Why did an identifier get cut in two over two lines?

The blockmap builder has NOT been done. It would a) be too much hassle and b) Actors were ignored by the blockmapbuilder even before this update because c) including actors in the blockmap builder is in 99% of the cases beyond stupidity to do anyway.

Labelmap builder updated

Tagmap builder updated

Dominance regenerator has been updated

But first a natural break

This will NOT yet affect the mappers, that will be the next step

The Kill All has also been set to clear both lists

And the killer will already respond to the correct vector in order to remove actors if they should be.... This should happen automatically

I've put the actors in their own vectors

And while I was in bed I realized why I've been stupid with the object list... After all, and I should have realized that, C++ is primitive, and so a memory conflict in using the way I used vectors was only bound to happen.... Since the listing system in both C# and BlitzMax only store the pointers and have a completely automated memory system around that I never realized this... C++ is, of course,a different story....

Take XXII

ALthough as an intelligent person, I don't understand how this could happen

I've forced the actor spawner to rebuild the ID map though

On Crystal the system crashes on being unable to find the object ID, on Wendicka this didn't bother the system

Take XXI

Internal fixups

Take XX

I hope I got it now

The actor IDs remain 0

texture ""?

Take XIX

This should prevent it

The bug that happened now should not be possible, but did happen

Take XVIII Confirmed

Well I fixed it!

I guess that's Microsoft for ya!

VisualStudio complained about bugs in strings, while the fault was made in my vector usage....

The error gets picked up in the xstring library on the tag of Wendicka's actor... Why this is happening is something I cannot tell, as the traceback only limits itself to the function where the fatality happens, but it doesn't tell me which function called the fatal function.

Take XVII

Inside visual studio then and hopefully that produces some useful insights

Stuff gets even stranger now as the game now crashes without any notice

Take XVII

Compile

Part II done

Part I done

I see my API has a few advancements that now work against me, so I need to experiment on a bit

Take XVI

Adapted API to this experiment

I think my entire approach may be faulty and if I'm right I guess I may be lucky I didn't get a segmentation fault

XV

Can't be it, but here goes nothing

I wonder what happens if.....

Take XIV

Why the tags do not change I cannot tell though

I've at least fixed the ID...

a few more things

A few issues do arise here.... First of all not the correct object ID(), which should happen... But I guess that's only natural, and second NO TAG!

Take XIII

Done

Forgot to compile and that debug line was in the C++ code

Take XII

Ultimate debug line and let's see if this provides some answers!

The forcing didn't help and the created output by the tag list confirms the actor is not listed in the tagmap

Take XI

Extra debug line

I've forced the system to always rebuild the tagmap whenever actors are being created, regardless of underlying configuration settings

So far the logs confirm the entire claim is nothing more but bullshit

Take X

Let's see

Extra debug line

Take IX

Field name != Object tag

That at least covers the issue of having no actor with the specific tag

Take VIII

But I think I got it now

Nope!

Take VII

?

No this has NOTHING to do with corona... I am just traumatized about things that happened over the entire course of my life, and that is getting onto me.

My stress is really getting the best of me