And I think I've prevented it from happening again... At least in this particular instance.

I think I fixed some code typos

RIght-o

Let's fire up a test then....

Will nothing happen? Then I must take it as "good"

If I got an error, then I guess something's not right....

Help me, Weniaria!

Please note that I can only trust on it that everything works the way it's intended if no crashes take place.... Other than that, I got nothing...

I've linked the character data for Young Irravonia to the New Game initiator...

I made changes based on these calculations, and tell ya what it DOES look better

I made a few recalculations hoping I can make things look esthetically better.

Ah, it was nothing

HMMMMM.....

I have forgotten my self

(that space is not a typo)

Code typo

Forgotten )

Case Error

Irravonia's face should now appear in the first box

A quick linkup routine to quickly access BoxPics

#15

Irravonia's portrait aliased for Young Irravonia... This is a dirty method and totally not friendly on the memory I know, but this was the easiest way to go and in the longer run also more efficient

And Kirana too, also a playable character despite her being an important enemy.

Shanda has been done too as she is also playable

Added tag SPOILER

And the other main heroes too

Brendor Main Potrait

Irravonia main portrait

Party member wrong tag

Time for a break!

Fixed tiling bug?

Nope that didn't do anything

Swapping some parameters, and see what happens :-/

Well that fixes a part of the problem

So that's fixed

Of coruse I should not forget that the back boxes need to be drawn as well...

Coordinate editting

In game screensize checker

it was stupid.. that suffices!

I don't wanna talk about it

A forgotten ) (sigh)

This debug line should answer a few things....

The width of each box should be fixed now....

there's a lot NOT right, but let's first get into a the coordinates of the boxes

Illegal function calls

I should be almost there now... At least when it comes to parse errors

Link errors

Code typo

I think I fixed the unclosed group

Well let's get back to business

I'll sort this out later, first to the store to make sure I've enough bread to get through the upcoming days.

A group scope not properly ended?

"." and ":" on arrays and function followup crashes fixed... well... sort of!

NIL didn't know the empower operator

And again

Not a fix, but a bug in NIL voided (for now).

Another test!

And now that everything is properly embedded the error (which was also stupidity, first class) became visible, and it has been fixed.

Running compile script

The embedding issue

Something went wrong in embedding the SysFont after I relinked that, I see

The latter I understand least of all

The game does start, but the status bar does not show, and trying to open the debug console even ends the game abruptly

And let's resume the test, shall we?

Running the compilation script

I did add a "lines" function to JCR6, but I shouldn't have forgotten I need to recompile NALA due to that! (sigh)

Another missing declaration

Not really a fix, but worked around a bug that is still being nasty in NIL

Missing declaration

MOAR of those

Code typo

Forgoteen "self"s

Not sure what I did to fix this, but mysteriously the computer has enough memory now (it was never clear why it hadn't in the first place)

More #say tags must provide an answer

?

I wonder if qff is to blame... But I also wonder why it was imported in the first place

The code crashes almost immediately after the first #say marker... This is really odd

One code typo

Placed in some #say markers so I can see what is happening

The error pops up while NIL is still translating the party sub

"Out of memory"?

Let's see what happens now

Regenerated Anyway.nil

Conflict prevention

No parse errors in the linker, but we're not there yet!

Written the link code to make the bar always available from all sections of the game (where needed).

Before I get onto the textboxes I've decide to do the boxes of the character bar which will always be below the screen first... Since these boxes will always have the same size and are not dependent on scenario data they are easier to script, and yet, the routine creating and drawing them is the same. So if they work on that bar, they'll work on the textboxes too, and then I only get to worry about the coordinates, and scenario parsing... The textboxes will then at least not go wrong, and that can be one issue to many at the time....

The textbox generator should be ready now, however, as always the case in these things... Testing is not yet possible :-/

I've tried to make cool "shade borders", however these can be terribly messed up... The downside is also that MonoGame has no line instruction. So I just just hope this'll work... :-/

"The little girl would be missing her doll. We should return it!"

ITile

Constructor set up for the boxes which can be used to display text in

Of course you realize a new backup is in order now.... :-/

Due to my time being wasted on the OpenGL mysterious incompatibility issue, I could not move on to the BoxText routine as originally planned... I hope I'll be forgiven...

Leeroy Jenkins and over 9000 are now just kills achievements, as the original requirements were too obscure

It's over NINE THOUSAND

#14

It is!

Let's see if the fix is real now.... :-/

Leerooooooooooy Jennnnkins

I think I got it!

Let's expand the error message, shall we?

The music stopper is declared absent.... that should not be possible so what is going on here?

Well on the bright side... With DirectX the communication with the Windows UI is now a lot better.... So I guess I have to take it or leave it... :-/

Yeah, if MonoGame didn't pop errors that were no issue, I would have done that this morning and not have suffered like this... GRRR!

#14 should have been taken care of now

(perhaps it was because this were pages 1300-1399... You know unlucky number... that this had to happen to me)....

And now I can FINALLY get back to setting right #14 what I actually wanted to have done in less than an hour... THANKS A LOT!

Appears to be working....

Testing building script with the new engine build

in order to prevent conflicts I've removed the original release folder (easy to recreate thanks to my builder)

AT LAST!

MapScript doesn't produce results though, and I know there's metadata here!

Poor Lua code generator in Kthura data outline

I know why the private was not accepted.... Due to a complicated metatable construction NIL was not able to understand that privates should be accessible, and there is by the way no way to fix that... at least not with the way NIL's been set up now....

ID in Kthura no longer private, but I did set it to readonly

It works?

But now I got the error that I tried to call a 'nil' value, and I wonder what's wrong here....

Well I found out what's wrong

Let's run it again, shall we?

true for a microschoft product VisualStudio crashed

Let's try a different road here

I don't see where it could possibly go wrong, though, so this is gonna be a though ride, since the system doesn't tell me anything...

Exception thrown

taking forever, I see

seems not very good

I'm waiting?

Final step, the key table former

THAT WORKED TOO!!!!

And now with Data read-out link

Very well, when I uncomment the Data definition link the game just starts up... good!

Let's do this now STEP BY STEP, and see what'll happen....

The menu runs again.... FINALLY!

Of all the issues in the world.... I HAVE TO DEAL WITH WINDOW'S BEING OVER PROTECTIVE OVER FILES IN A "DIFFERENT (non-existent) PROCESS"!!!

And now a general error, without any form of information at all... I am really beyond furious now!

Okay, that's because of a code typo in the Kthura link script, but due to not everything being loaded at the time that results to an error that doesn't make it through... Somehow...

And now nothing happens when I run the engine...

Well I fixed that

Well, I got the Blue Screen of Death (which I took very very literally), but that at least indicates the engine runs at all... In OpenGL I didn't get that far.

Well I hope I got NALA working in DX now....

It simply DOESN'T want to work, eh?

Doesn't seem to work the way it should... :-/

Created a new template and let's see if I can copy all the linked C# code into it

I'll first rar what I have to make sure this operation cannot cause me to lose everything!

Added tag RAR

And this, folks, is I mostly use my own engines, and don't want to be reliant on others, but unfortunately, I cannot do EVERYTHING myself :(

Aziëlla's Babbling Bubbles also uses OpenGL and refuses to work... The Kthura Map Editor is on DirectX, and was supposed to be swapped to OpenGL (which I never did due to fear of the same trouble I'll be about to face now), but at least that program works now....

The project file is actually what worries me most!

The most obvious solution... At least for the short term would be to adapt NALA to work with OpenGL, but that may be easier said than done... But it's the only thing I can do to save this project... Luckily this won't require me to change any C# or NIL code, but it will be one hell of an operation to make sure that everything will be done accordingly in the solution and project files....

Well I've created a quick OpenGL blank project where the same issue arises, and a quick DirectX project, and that one works.... It's clear the communication with OpenGL has become the eyesore here....

researching this it appears they are having trouble with OpenGL only... Should switching to DirectX really fix all this? (I hope that is not what's wrong here).

It keeps insisting my graphics drivers are no good... That's bogus... It has always worked and the Kthura editor still works.... Did some behind my back updates take place I'm not aware of?

Again no good?

All systems rebooted

I guess all that's left to do is reboot, and see what will happen then....

Added tag SYSTEM

It's my guess the last crashes did (despite .NET being protected against it) lead to a serious memory leak

Now it even claims it can't create a graphics device record

Still nothing, eh?

I guess I need to be more prune on what to allow in the init.nil and what not, as I guess it's über-fragile.... :-/

Should never be the reason something like... well THIS is caused, but okay.... :-/

Code Typo

WTF is going on here?

Well At least I fixed that... :-/

Can a forgotten ) really cause an infinite loop crashing many programs?

Added tag FUCKYOU

WTF is going on here?

And again!

On da case!

I must (of course) not forget to recompile NALA first

Temporarily deactivated the SASKIA script

I've also made an in-field command for that.

My prime target is now #14... The previous entries were to allow me to debug this more easily and check the data before I actually get into doing #14 itself

Wrote the NIL link code

Kthura Meta Data manipulation routines written

Give my brain some rest before I begin on the BoxText routine

#12

All debug lines from SASKIA as they can spook up when being used in other people's projects

According to the data I now see in the debug log, all SASKIA bugs should be accounted for...

And let's see what we get next!

And the debug line is now formed accordingly... I hope!

In order to get well into this debugging, I did a bit of study!

Well, let's try this in stead then.... :-/

WTF is happening...

Something makes NALA take too much memory, but whatever it is that causes it.... Who knows....

Well let's test this again, to see if stuff works now....

Now I did get a crash message from GIMP, but I wonder if that was the source of all "evil"

Something's wrong here... Everything froze

let's gather some info here... :-/

The counter value the debugger returns confirms this!

My hunch appears confirmed... Two sessions get into the memory in stead of one!

Let's do this to find out or rule out

Ah yeah, the start at position 2 is explained due to the OnLoad chunk containing one "end" instruction so that was at least NOT a bug!

Indeed, I had to form the call in the boxtext routine differently, so that issue has been resolved....
Doesn't answer why it takes two instructions at once though.....

Or maybe.....

The clue is, everything works the way it should except for the fact that no results are produced... Can you still follow?

More debugging lines as things do get stranger and stranger....

A little break, and boy I needed that!

Clearly... NOT!

I've added a debug line to the boxtext linker... This line will indicateif the boxtext initiator was called at all!

MOAR debug stuff to get to the bottom of this.... Are all commands skipped, or simply never executed?

Arrays in Lua are based on 1 ... not 0

Fixed the SASKIA script... I think....

Let's test!

I think I fixed this now....