next »

[Tattomoosa]

[Schrompf]

You could hang that by the wall in some gallery. I like it. Got some explanation what I'm seeing there? What were you trying to achieve? What went wrong?

[Tattomoosa]

You could hang that by the wall in some gallery. I like it. Got some explanation what I'm seeing there? What were you trying to achieve? What went wrong?

The location and rotation of a instantiated 'cloud cover' model was wrong. Unity using 'y' as the up axis causes me all sorts of little problems but most of them don't look that good.

I won't pollute this thread with a picture of a success but you can see how it's supposed to look in the first GIF in the Chess 4X Devlog.

[MSThalamus]

This fail came about as I was making a metal texture in Photoshop from a photo of our old scratched up cookie sheet. I had left a terracotta texture I'd made earlier in another layer, but it was completely hidden. Somehow focus ended up on the Mode drop down list without me knowing it, and I scrolled the mouse wheel to move the image down. It landed on Color Burn, and this was the result:



I loved it! I've used it extensively, with a lot of manipulation, to form the basis of background textures, UI frames, etc.. Probably my most useful ever "failure."

[MSThalamus]

I'm not sure this is a BEAUTIFUL fail, but it's definitely an interesting one. (I love bloopers!)

[oahda]

That might be my favourite in this entire thread. <3

[verdog]

That's quite the dress.

[MSThalamus]

Thanks you two!

This is what she's supposed to look like:

[Ordnas]

The one before was very horror game like!

[PetSkull]

Just noticed, that after I changed some of my code - The upper layer (with objects) is misaligned with the bottom layer, giving the scene a somewhat floating experience (and a little nausea  )

I think it's due to some floating point calculation. Well, gotta track down that bug! 

[PetSkull]

And now, 5 hours later I found the bug! Studid error (aren't most of them that?).

My loop looked something like this:

* Find visible objects (which also calculates screen coordinates)
* Update all objects
* Render

By changing it to

* Update all objects
* Find visible objects (which also calculates screen coordinates)
* Render

And the problem is solved : On the other hand, I did manage to optimize the function that finds visible objects, so it now runs 1-2 ms faster :D

[JobLeonard]

This is why I like ping-pong techniques (that is, separate old and new data so you don't accidentally overwrite the old data)

[PetSkull]

Stupid, stupid robot!!! Fuck you! Spend 5 hours today to get your paths correct, and this is how you treat me???

[Pineapple]

Working on some code that works with doom WADs.

Right now I'm working with a test that reads a certain graphic from the Doom 1 WAD and writes it to a bitmap file. It was working fine. It outputted an image like this:



Made what I thought were minor changes and now it outputs images like this:

[ProgramGamer]

What a wonderful thing to have happen by accident.

[Ordnas]

Modern art by accident.

[nova++]

This one's from a bit ago, but I knew I couldn't leave without sharing something when I saw this thread.
So here is my own personal inadvertently intriguing failure in getting terrain generation to cooperate:




Here's a more recent one. An attempt at a heightmap-to-topographic-map shader had a habit of getting... interesting up close:

[oahda]

Thought I'd had animations properly implemented since some time, but after trying out a more complex model with weight painting in the engine last week, some nightmarish material surfaced to tell me promptly that it wasn't so…



Looked even more horrible taking into account those babies crying at the sight of it…



But in the end I got it working! The issue? I thought the weights would be normalised in the glTF file already but they weren't! Once I did it myself in-engine, that was it! ;_;



(also in case you're wondering, no, that's not the correct texture for that model, it's just the baby's texture!)

[JobLeonard]

Thought I'd had animations properly implemented since some time, but after trying out a more complex model with weight painting in the engine last week, some nightmarish material surfaced to tell me promptly that it wasn't so…



Looked even more horrible taking into account those babies crying at the sight of it…



But in the end I got it working! The issue? I thought the weights would be normalised in the glTF file already but they weren't! Once I did it myself in-engine, that was it! ;_;



(also in case you're wondering, no, that's not the correct texture for that model, it's just the baby's texture!)

The screaming pikmin dudes really make those gifs

[ProgramGamer]

Nice


I also have a beautiful fail from yesterday when I switched from software rendering text on the fly to a texture atlas to speed up text drawing. I love debugging these sorts of things.