Sonic: The Lost Worlds

wow, a very interesting hack you have there, I did enjoy playing it (even with the pits and occasional glitches) I found the level designs to be very nice and well fitting for it's name, but the deformation, hahaha man, I felt as dizzy as a pissed up hypnotist on a round-a-bout, that's not to say it wasn't well done, it just seemed odd in that way, and I'd like to mension that although the 2 player selection on the main menu is removed, there's still access to it on the options menu, but all-in-all I have enjoyed it and will definately keep this on my hard drive for occasional play =)

 

They are fine. Just be glad the sand pits were animated. Take the high road ALWAYS and you will be fine. And yes, whenever Sonic's feet touch the general sand, I dread too.


But yeah. Played through the rest of the game. Pits, glitches etc. Infact all my deaths were by pits. Pits and that one time I got stuck in the wall underwater and slowly drowned. That 10 Ring box was too enticing. And pits. Pits pits pits. Getting hit back by an enemy and falling into a pit with no control is the worst. Like Sonic Rush, the pits make people afraid to explore.


Still, I enjoyed playing them. Loved credits zone. The best wood zone I have played, with the badnik choices and the gimicks and the Aquatic Ruin leaves generator on the trees, that really suprised me. Made the zone feel more complete. The Sky Chase badniks were actually a threat.

 

Pits, pits and more pits. Also too few star posts. Further, tone down the needless cheap hits.

Also, In Cyber City 1, there's a spot with:

- a 10-ring box
- a platform
- fans
- a one-way door.

If you miss the jump from the platform to the fan, you WILL be stuck until you run the timer out, as the platform falls and you can't go back to respawn it. If this situation is frowned upon in Mario games, it's 10 times worse in Sonic games.

 

Agreed. This business isn't really my cup of tea, but can't you just borrow some Oil Ocean code or something?

And to be fair, Metropolis crabs shouldn't line the ground of the game's first zone, and there shouldn't be a Buzzer waiting just off screen for me bump into everytime I use a spring. There's difficulty, and then there's artificial difficulty, and then there's painfully blatant artificial difficulty.

I respect the homage, and the artwork is excellent, but maybe level design isn't your calling.

 

Glad to see this out finally!

Visually, the levels look fantastic - that, folks, is what Genocide City was meant to be. I'm also very impressed with how Rock Zone turned out! But I agree with everyone else - the level design definitely needs some touching up. The pits are irritating as hell, and yes, the Dust Hill Zone sand pits REALLY do need to be handled differently.

 

Lol this "difficulty" seems analogous to Super Mario Bros. 2 JP (aka SMB The LOST Levels).

 

You really need to something about those sand pits in Dust Hill, I've literally ran and jumped into them a few times already and I've just started playing the hack! In fact, the first time I feel down one of those sand pits, I thought it was a glitch!

Those arrow dispensers look out of place as well, itsn't it possible to modifity them to fit in more?

Other than that, the graphics are nice enough. Well done, there. Title Screen is nice too.

 

Eh, I wouldn't say the difficulty is on par with Super Mario: Lost Levels... that one was just fucked for the sake of being fucked, and intentionally cruel beyond reason.

This one just has snags that need worked out. I've kind of given up playing it for now, 'cause every time I do I find something else irritating. I just avoid Dust Hill at all costs.

 

Heh, odd, I was just playing the previous build a few hours ago. I'll take a look at this later.

 

Burned this to my flash cart - the game freezes right where the colored bars are scrolling away on the Dust Hill Zone intro screen. The music is still playing, though.

 

odd, I seem to be getting an epic slowdown shortly after starting Dust Hill, the sort of like where you overload the screen like debug mode and things just appear in front of you.

Lost a life, seems to be working OK now, the fact that pits are a darker color now is a HUGE improvement, though.

 

Ok, tried this on Picrodrive for PSP...wow, it starts off fine, but the graphics suddenly glitch up until you've got a tangled mess of glitched graphics. Pause the game, and Sonic is swept up in the glitch wave.

I guess Fusion's the only one that this will play on.

 

I have the same problem on the jenesisds, it would have been great to of had this more compatible with other emulators other than that its a pretty good hack.

maybe if you do a next update you could think about ways of making it more compatible with other genesis/mega drive emulators? idk.

 

The slowdown is to great in Genesis Plus and Generator. Not really playable for me right now.

 

It's probably a data alignment issue. Many hacks wind up pushing the code or data off word boundaries. Some emulators work fine with code or data on odd boundaries, but that causes real hardware to freeze. I could imagine some emulators running slower with the data on odd boundaries.

 

:C

That's an "Address Error" exception; the game will freeze because all of Sonic 2's exception vectors point to an infinite loop. The thing about some emulators is that they just don't seem to simulate an "Address Error" on word or long access to odd addresses, even though the processor they're emulating doesn't support that access

This is happening because something is causing Object $43 (the OOZ spiked bars that move back and forth) to be spawned into every open SST entry. The only way I can reproduce the error is by moving beyond the half-way point between the last two cactuses in the opening area of Dust Hill Act 1 and then going back to the left, so, my first guess would be that you removed the leading terminator from the object layout data.

All object layout data needs a leading terminator, and an trailing terminator, so that the game knows when to stop reading data at the beginning and end of the level. The data is saved to individual files with a trailing terminator, but not with a leading, because the one at the end of one data set also acts as the beginning for the next, the pointers must point to the start of the data and not the leading terminator, and it's assumed that you won't be removing the one that comes before the first object layout data in the assembly file or built ROM that you're working with

Try adding this immediately before your first incbin/binclude for object layout data:

Code (Text):

1. dc.w    $FFFF,$0000,$0000