Sonic and Sega Retro Message Board: Delta - Viewing Profile - Sonic and Sega Retro Message Board

Expanding on the above post.

Screen tearing is typically never intentional. It happens when the game tries to redraw itself before the monitor has had a chance to completely draw the previous frame. This results on one half of the screen showing the new frame, while the other half is still showing the old frame. In software rendering, this has a greater chance of happening because on a PC, developers don't have a reliable way to know whether the monitor has completely drawn the previous frame.

In Direct3D/DirectX and OpenGL, however, developers have a bit more control. Both of these graphics APIs have a way to enable Vertical Sync (VSync), which tells the graphics driver to wait until it has completed the previous frame before rendering the next one, resulting in a smoother appearance. This has the side effect of limiting the game's frames per second to whatever the refresh rate of your monitor is, which is typically 60fps with modern displays.

https://dl.dropboxus...AR-20141107.zip

All the files are named such that it -should- be a drop-in replacement, which should makes things easy.

Flygon, on 06 November 2014 - 03:07 AM, said:

I can definitely see that being a problem in this case. Fixed.

My guess is time constraints. Same reason that Hidden Palace was removed from Sonic 2. These concepts are great, but the more grand your concept is, the more time it takes to implement. The team probably recognized that they would be behind schedule if they used everything in their sketches, so they simplified everything.

I'd love to see these ideas in a ROM hack. :P Or perhaps Sonic Overture.

Covarr, on 05 November 2014 - 04:26 PM, said:

I tried to be a little conservative on this redesign. The only javascript it uses is for switching stylesheets (same as the current SonAR).

It would certainly be easier to maintain if this gigantic mess of HTML were split into multiple files and accessed through AJAX. It'd be even cooler if it used some content management system with databases and all that fancy stuff, but I'm not sure if it needs all that. The content doesn't change that often.

In any case, the main benefit of AJAX is to avoid page reloads, which this one-page design already does. :P And the dropdown on the top already lists all the systems. I suppose I could turn the table of contents into submenus instead, but I'm not sure if that would actually be better.