Notices by Kawaoneechan (kawa@mas.to), page 3

@foone This annoys me to no end because I know Too Much about these games and engines.

But this example specifically makes me reach for the "delete this" gun because those aren't even the same *engine*.

"I just used this new decompiler to reconstruct the C source code for Sonic the Hedgehog."

"You mean Sonic Spinball, right?"

"... no, why?"

@foone Whereas the CGA flag is simply a tricolor of cyan, white, and magenta (not to be confused with the trans flag), the composite pride flag adds nine black discs on the middle band, in rows of five and four.

#vexillology

@foone COMPRIDE.EXE

@foone Originally I had a thin wrapper with the [Debug] attribute that called Console.WriteLine(...). For whatever damn reason, that's slow when running from VS2015's IDE.

It was suggested to use System.Diagnostics.Trace.WriteLine(...) instead. I *still* have an Output panel full of shit, but for whatever damn reason it runs much smoother. Not as smooth as from outside of the IDE or VS2019, but... yeah.

Weird, but I'll take it.

I have been given a very interesting suggestion and now it runs at a nice 30 something with barely a hitch when running from VS2015.

I don't understand why, but it does.

An interesting observation: when I run a debug build of #Noxico in #VisualStudio2015, all the debug outputs in a populated town board make the game run very slow, like 20 to 30 FPS. The _exact same build_ running from #VisualStudio2019 updates the exact same town board at a full 60 FPS.

Running it from outside either IDE also gives 60 FPS for the same board.

I find that quite interesting. Does anyone have any insights about this?

@foone True, there aren't any mermaids in the Atlantic.

Not since The Incident.

@foone ... they say after sixty-something notes already appeared.

@foone I was about to pack up and go home so I didn't have time to post it on both. Yet.

No thots, bed empty.

This should print "3.14" twice. Does it?

For some reason, optimization levels affect the result.

-O0: Neither works.
-O1, -O2, -Os, -Og: "This is fine" works, "this breaks" does not.
-O3, -Ofast: Both work.

I've been using -Os all this time now, but that really doesn't matter as much as how
this does not make sense to begin with.

Just found out floating point on the #Asspull3X is fucking broken. I haven't the tools, knowledge, or means to even *begin* finding out why, let alone fix it...

Emulation counts, right?

Right?

Reminder that the #Asspull3X is an actual, real thing.

To celebrate Blender 4.0, here's a render done with Blender 4.0 but without actually using any of its new features.

#blender3d #blender4 #Asspull3X

Just beat #HalfLife and you know what? It was impressive enough years ago but now that I know all the things I know about game engines and all that sorta stuff, it's only more impressive.

@aral Ah, yes. The exact version I ripped the level data from for mine.

I should finish it.

@foone Why though?

... oh wow those sudden feelings of imposter syndrome and such hit HARD

ouch