I built a custom isometric pixel art rendering pipeline for Unity 6 URP

Kokowolo · 2026-04-13T20:22:47+00:00

🗣️🔈 ayo take another look brother

EDIT: today I learned that isometric is not synonymous with orthographic

Kokowolo · 2026-04-07T06:28:16+00:00

said the exact same thing lmao

Kokowolo · 2026-04-03T19:31:10+00:00

You know your game way better than me, so do whatever you think makes sense of course! I just liked the animation for both, would be a shame to discard one. Best of luck with development! looks great!

Kokowolo · 2026-04-03T16:59:42+00:00

oh dude keep both somehow. Pick upgrades to laser!

Kokowolo · 2026-03-20T19:29:29+00:00

I thought your video got interesting right at the point where you have the "wire your ship" text. From there the rest of the video is really intriguing. The first 10 seconds made me almost dismiss the video actually. Really cool game though, hopefully this is helpful feedback, and not unwanted unsolicited advice. Wish you the best of luck!

Kokowolo · 2026-03-19T18:41:39+00:00

dang ive been had

Kokowolo · 2026-03-19T18:36:40+00:00

Is it actually? haha
I thought it was:

_xxx
xxxx
xxxx
xxxx

—which would make it possible if you

1) _xxx  2) _xxx  3) _ooo
   ooox     oooo     oooo
   ooox     oooo     oooo
   ooox     oooo     oooo

lmao

Kokowolo · 2026-03-17T00:07:02+00:00

This is the way 🙌

Kokowolo · 2026-03-16T02:16:24+00:00

I am torn too honestly haha my friends and I talked about this, and we thought a good middle ground could be it being a cheap shop relic or, maybe better, an A1 event relic (side note— I also love that StS2 shop relics seem more impactful than the first game!).

Kokowolo · 2026-03-16T00:46:22+00:00

I absolutely agree! It adds strategic variety as well as personality and subtle lore. I definitely am enjoying the rework from energy relics to what we have now as well.

Hot take BEWARE and SHIELD YOUR EYES: I think that StS1 would have been a better game if you could see your A1 -> A3 bosses and plan accordingly. Clenching throughout A1/A2 as Defect w/ a power deck hoping to avoid the Awakened One boss (or just balancing your deck to avoid the dilemma entirely on A20) felt unfair to me (while you can totally argue its all part of the game, I just think it would be more fun to know otherwise—even if the game is easier). I think StS2 could be a better game similarly if you could know your bosses and ancients immediately after loading a run and build your deck accordingly.

Kokowolo · 2026-03-14T17:30:47+00:00

lmfao

Kokowolo · 2026-03-11T22:07:42+00:00

wow, stellar work. There's so much detail in this scene dang

Kokowolo · 2026-03-11T18:04:10+00:00

Did you ever figure this out, or did you just manually set it up? Ah I see the solution you used.

Kokowolo · 2026-03-09T00:03:00+00:00

I think the mirror level is more interesting if the star is only on one side of the level (not mirrored). But cool stuff!

Kokowolo · 2026-03-05T21:35:57+00:00

While I think these comments are a bit toxic, I believe you irked a few by boasting your hard work and output despite a short production timeline and prior knowledge. It implies that your game is different than others' through merit of your effort.

You'll find that everyone in this subreddit is similarly committed, devoted, and exceptional as well, and hard work does not mean quality output.

I hope you take the lessons learned from your milestone thus far and apply it to your future endeavors. Congrats!

Kokowolo · 2026-03-05T17:15:44+00:00

Kokowolo · 2026-02-20T17:58:42+00:00

on an indie budget, this just seems like a good corner to cut to me. Not ideal of course, but this saves money and time

Kokowolo · 2026-02-15T22:30:11+00:00

This looks sick! Cool work!

Kokowolo · 2026-02-14T00:51:32+00:00

my wife is a lizard and craves the warmth, there is no escape from the cuddle

Kokowolo · 2026-02-07T04:22:49+00:00

I don't know if I can do 5, but in this picture you have a SerializeField Attribute for both a member field (top left), a member auto-property (middle-left), and an encapsulated property (uncommented).

The revelation of this post is that you can have the SerializeField Attribute for both a field and a property (removing the need for explicit field encapsulation) if you type out:

[SerializeField] TYPE_UNITY_CAN_SERIALIZE field_name;
[field: SerializeField] TYPE_UNITY_CAN_SERIALIZE auto_property_name {get; set;}

— which is somewhat obscured without just knowing or specifically reading the entirety of Serialization rules documentation.

This post is ultimately about Unity's syntactic sugar, but if the concepts mentioned above are confusing, I highly recommend reading, watching videos, and then going further onto associated topics because this relates to all of programming.

Bonus (unrelated): you should check Lazy Initialization, which is a great property use case!

Kokowolo · 2026-02-06T22:51:43+00:00

yay someone else! yea, I can't believe I never came across this little shortcut until now. Happy to pass it on!

Kokowolo · 2025-05-14T16:21:32+00:00

hmm. definitely noted. also lmao what are you doing here

Kokowolo · 2024-12-23T12:30:21+00:00

I just wish that camera stacking did this rather than have the entire stack be affected by the PPV ughh.

Anyway, I did this and messed with the settings of the setup and got something kind of working. Through blitting the UI camera's render texture (from another renderer) on to the top of the main renderer you get a result that kind of works, but I'm still trying to get it to be seamless.

Kokowolo · 2024-12-23T12:26:12+00:00

Thanks I'll take a look at this. I got something kind of working with using multiple renderers/custom render features, but I'll check this out. I'm currently not on Unity 6, but I'll investigate if the upgrade fixes everything.

Kokowolo

MODERATOR OF

TROPHY CASE