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

Yep. Crosspostan

Pics for the click-shy:





The full-sized images are available by suffixing the filename with “:large”, something IPB doesn't allow.

Are these worthy of inclusion on the wiki? In any case, I found them interesting and thought I might not be the only one.

Just a couple of days ago, I was wondering about the origin of the prefixes HSS- and HST-, used in the model/catalogue numbers of Japanese consoles and games respectively peripherals and systems. I could have believed that HSS stood for Hwatever Sega Saturn, if it weren't for HST directly contradicting this idea. [edit] although Black Squirrel, combined with my mistake I just scored out, make me feel dumb for not thinking of SaTurn [/edit]

Lo and behold, today, one of the many fruits (I exaggerate tremendously) of my wanderings on the internet:

segaretro.org/Sega_Saturn said:

Does this explain their origin?

If this is a silly or old question, for example having been discussed to death in one of you guys’ big threads, then oops. But I'm interested to know either way.

Turns out FreeLoader was killed waaaay back in System Menu 3.3, and downgrading from 4.3 to 3.2 (using DOP-Mii) didn't re-enable it at all. First off, I'd appreciate if anyone knows why that is, but anyway . . .

My legitimate American copy (no, really!) of Ikaruga looks fine via Gecko OS until it crashes upon game-start (due to some issue with streaming audio).

NeoGamma loads it and lets me play (with audio, too) but constantly displays a bar of flickering lines near the top of the screen, which looks exactly like what you'd get if that particular region wasn't interlaced properly - I.e. only every other line within the area is scanned (every other frame). The bar spans the entire horizontal distance of the screen; vertically, it covers maybe 1/8th of the total screen size.

This is on PAL 480i mode (I.e. PAL60), but forcing other modes only leads to the same problem (PAL50) and/or RED EVERYWHERE (NTSC*). NeoGamma's video hacks (helpfully named No/Normal/More/All) don't appear to do anything.

What do? FreeLoader worked fine on my previous Wii, if I remember correctly (which is "if" enough, I'll admit), but that option appears to have gone down the pan. What could cause this specific problem with the video, and is there any way around it? It's not quite the end of the world, but it still sucks. (If nothing can be done, I guess I'll just burn a CD for my forthcoming Dreamcast; hooray for hilariously easy piracy!)


Edit: pesky wordfilter capitalising my I.e.s

Sup wizards,

You may remember me from such threads as Gimme miracle TV, in which LocalH posted a link that incidentally provided some background information about, but no solution to, this issue. Whereas that was slightly more general, I think this sufficiently technical to warrant posting here; move it if I've judged wrongly, of course.

In short, my Saturn looks terrible on my CRT TV, to which it is connected via an RGB SCART cable. Or rather: it looks pretty great until things start moving. Then there's interlacing everywhere.

This shouldn't happen, should it? The Saturn almost always outputs 240p, an LDTV format that should be supported by almost everything. I'm presuming my TV isn't familiar with this—possibly because of some difference introduced by the NTSC encoding?—and therefore is trying to deinterlace a signal that isn't interlaced, thus creating novel interlacing.

The TFT doesn't look great with the Saturn either, but the problem appears to be upscaling and not interlacing. That figures, since the TFT can handle NTSC signals better in my limited experience.

Wat do? I noticed this a few years ago (when I last played my Saturn ;_; ) but had less knowledge of video-related phenomena such as interlacing, so I was just as likely to attribute it to a bad output and/or cable as to the encoding. Is it as simple as needing a better TV? Tell me this isn't some unique problem of my lovely skeleton Saturn! TELL MEEE. I'm fine with buying a new cable, but I have no idea how that could be the cause.

TIA.