Mini update

[gilesgoat]

There's been some "silence" here ...

But things are FAR from "silent", effectively I am working simultaneousl on "2 + 1/2" things plus maybe "a +1 coming soon".

But because I am not in the condition to say anything yet there's silence.

I am really working day & night all I can say is "there will be output from LS" we are NOT "flipping our thumbs" or such, ABSOLUTELY NOT.

But "because so far it's not up to us to decide when/what to say yet" there's no "update" here.

I could only say "I need another disk soon" because "the number of SDKs I have on my PC is increased and my knowledge of HW too.

[fog]

So when are you getting your PSVR2 dev-kit?

[gilesgoat]

So when are you getting your PSVR2 dev-kit?

Erm .. not yet .. but I hope maybe "after this"

[Whiteball]

We know you guys are always busy.
The only way I think Llamasoft stops coding is the day the world stops turning.

New hardware and a different SDK to usual posssibly? Hmm...interesting.
Nice to have an update, even if you can't really say anything.

[fog]

So when are you getting your PSVR2 dev-kit?

Erm .. not yet .. but I hope maybe "after this"

That's all I needed to hear

[gilesgoat]

With "certain sadness" BECAUSE AT THE MOMENT I CAN NOT SAY MORE I ONLY want to say "MANY THINGS ARE GOING" !

And I could say "some things are coming true" BUT I CANNOT SAY more yet.

It may seem "all silent" but "we are working like crazy here" .. and for now this is ALL I can say.

But so "worries not" we are NOT vanished, we are NOT "doing nothing" ( all the opposite of it ) but it's a case "MY LIPS NOW ARE SEALED" ...

But yeah "behind closed doors" there are .. things .. going on ...

[gilesgoat]

... have you ever had those moments "HOW ON EARTH THIS THING IS BEEN WORKING FOR SO LONG WITHOUT EVER CRASHING (*) ?" ...

.. I am in some of those .. well (*) .. "so long until now" ...

Let's just say that C is C, CPP is CPP ( even more rope to hang yourself with ) and "every compiler is different and does whatever the fuck wants in non-so-specified-cases" ...

Also "the more you work on certain SW, the more shit you'll find out" .. ergo "no SW is ever bug free, the bugs you have not found are only not manifest yet" ...

.. which leads to me "living in the constant state with the constant feeling that somewhere I've done something wrong I don't know yet but is there .. " ...

Also I am still TRYING to "write some notes about how some stuff is supposed to work" .. and is already tuning into an encyclopedia ..

The SW gets to a point where , if you work on it, it's truly 'undocumentable' because you'll need someone else spending 'even more physical time than you' writing shit and someone else too verifying it ..

Anyway I spent 2 days getting nuts for 16 bytes ... "uninitialised var decleared miles away and used even more miles away only in some occasions that in certain useage patterns was getting 'the correct value' but not always" .. and the compiler could not spot it of course ..

Now I am with another 'weirdo glitch' that I am 99% sure probably is "a very similar cause" but I have not found it yet, looking bits of code I haven't done I am trying to figure out what/why they are supposed to do ..

Anyway apart that is coming along nicely.

[Vargol]

I had to debug an error that turned out to be a SQL statement missing an 'ORDER BY' that had worked perfectly for a year.
It seems that every single user until then had added the data in the order the data was returned from the SQL until that one user....

[gilesgoat]

I stand correct, the weirdo glitch was exactly "same identical thing" a var that wasn't correctly initialised to 0.

Actually that was .. interesting .. there was a place where that var ( array ) was initialised to 0 BUT only for N elements while, correct for the logic it was doing, N+1 elements where used.

It should have initialised the WHOLE array to N_ELEMENTS_MAX to 0.0 rather than just 'N', which I what then I did.

It wasn't an error that N+1 but it was an error that element N wasn't set to 0.0 as well.

Also that was "a special case", in many cases all the 0..N elements were fully initialised before being used but in some special cases only N where initialised despite N+1 been used so took a while to figure out "what the heck is going on here".

I've been very lucky the bug was 100% repeateable and that I could run it in single step side by side in 2 different machines one where it was happening and one not.

Still took a few days to find it out.

[gilesgoat]

Things are still going ..

I KNOW IT LOOKS LIKE "nothing is happening" but it's quite the contrary !

Unfortunatelly .. it's still all into NDA ...

Therefore "nothing gets said" so far ...

.. but things ARE going ..

[WiteWulf]

You know how you’re not allowed to *say* anything under NDA, how about screenshots, poetry, or interpretive dance?

[gilesgoat]

You know how you’re not allowed to *say* anything under NDA, how about screenshots, poetry, or interpretive dance?

If you read through the lines .. you can grab "pieces of information" from Yak's Twitter ...

And/or you can try using your deductive powers

[Jamesac]

The robo-voice thing is making me think Berzerk/Frenzy, with Gorf or Wizard of Wor being long-shots.

[Whiteball]

I always liked the idea of something like William Mataga's Shamus.
Specifically going around the corridors exploring (maybe a maze of interconnected rooms) except these 'rooms' were more like Robotron in between.

I also loved Amok on the Vic-20 but that's another story.

Would love to see a Llamasoft update of some of them old 'shooters'

[gilesgoat]

... la la la la ... so many things I CANNOT TALK ABOUT YET .. la .. la .. la ...