Whoa, this sounds like quite the brain teaser! I mean, I’ve heard of Brainfuck before but never actually got around to writing anything serious with it—mostly because it looks like hieroglyphics to me, haha. Still, a challenge with prime numbers sounds kinda fascinating!

The sieve method you mentioned sounds neat, but I totally get how that can balloon into loads of commands. Honestly, I’m curious to see how others would even tackle primes using a language with literally eight commands? Like, how do you even handle math operations or loops elegantly with such limited options? I bet there’s some sort of clever solution out there that I haven’t even imagined yet.

If anyone else drops by with some actual Brainfuck wizardry, I’d absolutely love to see their approach. Maybe we can even get some pointers on making the program shorter—I bet there are tricks for reusing loops or memory cells efficiently.

Until then, sadly, my only advice is… good luck? 😂 You braver than me for even trying to generate primes with Brainfuck!

It sounds like you’re on the right track wanting to output depth information without using `SV_TARGET`. In your case, since you’re aiming to write to a depth stencil buffer, you can actually do this quite easily using `SV_DEPTH`.

In DirectX, the pixel shader can utilize the `SV_DEPTH` semantic to specify that it will write to the depth buffer directly. You can modify your pixel shader like this:

struct VS_OUTPUT
{
    float4 position: SV_POSITION;
};

float main(VS_OUTPUT input) : SV_DEPTH
{
    // Assuming you have a way to calculate the depth value here
    float depthValue = input.position.z; // Example: just using the z position as depth
    return depthValue;
}
    

In this version, you’re returning a float value for depth instead of a color value. The value returned by the shader will correspond to the depth that gets written to the depth stencil buffer.

Also, ensure that in your rasterizer state setup, you’re allowing depth writing and that your depth stencil view is correctly set to handle this output. You might want to check your pixel shader compilation settings to ensure they match your intentions for depth-only rendering.

Give this a try, and it should help you focus just on writing depth values!

NATO Phonetic Decoder

OK, so I think what you’re trying to do is something like this. You wanna write some code that’ll take stuff like “Foxtrot Oscar X-ray” and figure out it’s really “FOX”, right? I’m guessing JavaScript would be pretty cool here, since you can run it directly in your browser and play around with it.

Let’s keep it really simple—you basically need like a map or dictionary that goes from each NATO phonetic word to a letter, then you loop through your input, grab each word, and swap it back.

Here’s how you could do it in JavaScript:

  
const natoDict = {
    'ALFA':'A', 'ALPHA':'A', 'BRAVO':'B', 'CHARLIE':'C',
    'DELTA':'D', 'ECHO':'E', 'FOXTROT':'F', 'GOLF':'G',
    'HOTEL':'H', 'INDIA':'I', 'JULIETT':'J', 'JULIET':'J',
    'KILO':'K', 'LIMA':'L', 'MIKE':'M', 'NOVEMBER':'N',
    'OSCAR':'O', 'PAPA':'P', 'QUEBEC':'Q', 'ROMEO':'R',
    'SIERRA':'S', 'TANGO':'T', 'UNIFORM':'U', 'VICTOR':'V',
    'WHISKEY':'W', 'XRAY':'X', 'X-RAY':'X', 'YANKEE':'Y', 'ZULU':'Z'
};

function decodeNATO(sentence) {
    let words = sentence.toUpperCase().trim().split(/\s+/);
    let decoded = '';

    for (let word of words) {
        if (natoDict[word]) {
            decoded += natoDict[word];
        } else {
            decoded += '?'; // If something goes wrong, just put a '?' there.
        }
    }
    return decoded;
}

// Let's test it!
console.log(decodeNATO("Juliett Echo Sierra")); // Should show "JES"
console.log(decodeNATO("Foxtrot Oscar X-ray")); // "FOX"
console.log(decodeNATO("Victor India November")); // "VIN"
console.log(decodeNATO("Invalid Word Golf")); // "?WG"
  
  

See, it’s not fancy or anything. And if someone screws up and types a weird word, you just put a ‘?’ there to say “Hey, bro, that’s not cool code.”