Graphics Analysis of an NES Game's Select Menu

#1

Post by dustmop » Sat, Jul 04, 2015, 3:48 PM UTC

Graphics Analysis of an NES Game's Select Menu
dustmop.io

Re: Graphics Analysis of an NES Game's Select Menu

#2

Post by gdubs » Sat, Jul 04, 2015, 6:10 PM UTC

Love these types of articles.

Also, if you develop for, say, the Apple Watch, there's a goldmine in looking at classic console games and how they made use of constrained resolution, memory, colors.

Re: Graphics Analysis of an NES Game's Select Menu

#3

Post by djent » Sat, Jul 04, 2015, 6:40 PM UTC

gdubs wrote: post #2

Love these types of articles. Also, if you develop for, say, the Apple Watch, there's a goldmine in looking at classic console games and how they made use of constrained resolution, memory, colors.

I feel like mobile developers and the creators of the hardware have given up on heavy optimization to work on minimal hardware and instead just gone with more expensive, top of the line hardware so they can continue current programming practices.

Re: Graphics Analysis of an NES Game's Select Menu

#4

Post by maccard » Sat, Jul 04, 2015, 7:08 PM UTC

djent wrote: post #3

gdubs wrote: post #2

Love these types of articles. Also, if you develop for, say, the Apple Watch, there's a goldmine in looking at classic console games and how they made use of constrained resolution, memory, colors.

I feel like mobile developers and the creators of the hardware have given up on heavy optimization to work on minimal hardware and instead just gone with more expensive, top of the line hardware so they can continue current programming practices.

I work on console targeted projects, we still have to optimise for very tight hardware constraints!

Re: Graphics Analysis of an NES Game's Select Menu

#5

Post by JoshTriplett » Sat, Jul 04, 2015, 7:23 PM UTC

It's interesting how much this page relies on the browser behavior of rendering all animated GIFs on the page in sync with each other, such that the palettes rotate in sync with the images.

Re: Graphics Analysis of an NES Game's Select Menu

#6

Post by agumonkey » Sat, Jul 04, 2015, 7:55 PM UTC

Got me to search for NES overclocking and surprisingly people did swap clocks to pump the cpu faster:

https://www.google.com/?gws_rd=ssl#q=nes+cpu+overclock

I already fried my old SNES so I won't touch my NES but still worth reading.

Re: Graphics Analysis of an NES Game's Select Menu

#7

Post by everyone » Sat, Jul 04, 2015, 9:43 PM UTC

I would imagine the limitations would make the UI design itself very effective aswell. Every extra sprite you include bears a serious performance cost so you would pare things down to whats absolutely necessary

Re: Graphics Analysis of an NES Game's Select Menu

#8

Post by djent » Sat, Jul 04, 2015, 9:57 PM UTC

maccard wrote: post #4

djent wrote: post #3

Earlier quoted context omitted.

I feel like mobile developers and the creators of the hardware have given up on heavy optimization to work on minimal hardware and instead just gone with more expensive, top of the line hardware so they can continue current programming practices.

I work on console targeted projects, we still have to optimise for very tight hardware constraints!

The reality is that the phones of today are as powerful or more so than the laptops of yesterday.

Re: Graphics Analysis of an NES Game's Select Menu

#9

Post by digi_owl » Sun, Jul 05, 2015, 1:59 PM UTC

Got me thinking about the Goonies 2 pause map.

Re: Graphics Analysis of an NES Game's Select Menu

#10

Post by jeremiep » Sun, Jul 05, 2015, 2:07 PM UTC

djent wrote: post #8

maccard wrote: post #4

Earlier quoted context omitted.

I work on console targeted projects, we still have to optimise for very tight hardware constraints!

The reality is that the phones of today are as powerful or more so than the laptops of yesterday.

Yet my phone battery used to last a week and now it doesn't even last a day. Mobile CPUs may be able to handle all that bloated code fast enough, but not long enough.