ikishade

Good to know! That's one of our core selling points.

Thank you for the explanation. That makes sense, and I've experienced first-hand getting ghosted with a provable 6x, so I think you're right there too. I guess it's back to the drawing board for what I can build with it in the next 1-2 months.

That's a very good point. Thank you!

Ah it's okay! I'd edited the post to reduce details since I didn't want to force people to read so much. There's a number of ways it can make money.

1. In 2024, I built a demo of my internal tool for level design and tested building a level in Unreal 4, Source (2013) and Unreal with my tool. Source took 164 minutes, Unreal (alone) took about 122 minutes, but with my tool Unreal took about 23 minutes. A level developer's average salary at that time was $112,000. I projected 40% of their time on a block-out, and a 6x reduction (based on those numbers), which is a savings of $37,333.33 per-developer.

2. The heuristic maps have let me create a level the size of an old school game (Gameboy Color) in around the span of an afternoon. But because the implementations I'm using are simple (I only had time to build them over a few days), they don't have the full fidelity depth of such a map.

3. There's one demo I was building, but needed a full custom MIDI library for, that would let you style-transfer from a single song of sheet music onto an existing song's sheet music. I'd planned to try style-transferring Moonlight Sonata. I could see this being huge for musical creation, but the investors I talked to all mentioned that the music field is extremely niche and none of them understood it.

4. The newest technique I discovered was implanting it into a finite state machine lets it record how someone reacts to certain types of events in digital environments. But to demo this, I'd need a game, game engine, virtual developer environment, or a custom shell. Walking through the math on-paper though, it should be able to replicate basic developer responses in consoles similar to mitigating simple on-call issues.

I think all of these solve problems, but I've still struggled to get any eyes or interest.

Thank you for the advice! Mine's mainly for limited palette upscaling, so that might be Apples to Oranges, but I'll give it some thought.

In this context, an image where there's some data represented by each unique RGBA value, and less of the "smooth" complexities of normal images like from a camera. So ones with small color palettes. Depending on the output size, it can run very fast and I've used it to up-scale a simple 2-color map for an island in water off one 512x512 training image.

I tried to demo this to HN back in July, but my post back then was buried.

It's applicable in a large variety of cases, but I originally invented it for procedural generation of 2D video game levels. But after I created it, I began to see other (better) use cases. I tried to launch the tool I originally built, but during my beta with developers I knew, everyone was unwilling to try it because the UI was a CLI based domain specific language.

I have a tool that can up-scale heuristic images based on a training sample, and a smaller input image. But I've found the reception to that to be very lukewarm, maybe because technical proc-gen is quite niche?

I actually tried to show my work previously through my company website. I'm not an academic, so I can't even publish to arxiv right now. I have plenty of mathematics materials to prove what I've been working on though. Do you have any suggestions given that?

I'm proud today to be revealing what I've been working on for a long time now, a brand new core AI algorithm. I know the article is pretty lengthy, but I had a lot to say. I'm interested to see everyone's response to what I've written and have! Thanks for reading.