Nintendo 64 on LCD


Recommended Posts

Google isn't being much help at all with this one. I'm finding threads on forums that are full of users saying it's the cables, get an old TV etc.

I have a N64, and I want it to work on my LCD HDTV. If I have to buy something to convert the signal, I really don't care.

I know this console works, I know the cables are fine, I know the games are fine. This is a signal issue with the TV.

Can canyone tell me what I should go and buy to get this to work.

I have AV cables (red, white, yellow). I've tried them in the AV ports, and in Composite ports (plugged in correctly).

Any help would be appreciated.

Link to comment
https://www.neowin.net/forum/topic/1134382-nintendo-64-on-lcd/
Share on other sites

You will probably need a down converter, if they exist. Don't forget, the large majority of games run at 320x240 which a lot of newer TVs don't support for some reason. Do you have an expansion pak and a game which supports 640x480, such as Perfect Dark or Star Wars Episode 1 Racer? This might be a good way to try it out.

Either way.... have fun with your N64... I tried mine on my 42" HDTV for the first time a few weeks ago and I almost cried at how bad it looked. I had all upscaling features turned on on my TV and it just didn't work one bit - it was horrendous to look at. I hate to say it, but you're better off getting a cheap tablet of some kind which runs N64 emulators well and connecting that by HDMI... :(

You will probably need a down converter, if they exist. Don't forget, the large majority of games run at 320x240 which a lot of newer TVs don't support for some reason. Do you have an expansion pak and a game which supports 640x480, such as Perfect Dark or Star Wars Episode 1 Racer? This might be a good way to try it out.

Either way.... have fun with your N64... I tried mine on my 42" HDTV for the first time a few weeks ago and I almost cried at how bad it looked. I had all upscaling features turned on on my TV and it just didn't work one bit - it was horrendous to look at. I hate to say it, but you're better off getting a cheap tablet of some kind which runs N64 emulators well and connecting that by HDMI... :(

the games resolution was 320x240, but the output resolution was standard NTSC or PAL resolution when it went out via Composite video

Got a new cable and it's working. But it's on and off, really annoying.

Welcome to old N64s. i strongly recommend not blowing into the cartridges or the cartridge slot as we used to do as kids - as it turns out, all it does is just leave tiny bits of spit on the connectors and ends up rusting them :p

Do you have a PAL N64? I live in the UK and have a PAL N64, and bought a cheap AV (Red/White/Yellow) cable from ebay, and the colours were all messed up and had a massive white glare problem, turns out the PAL N64 is slightly different and these generic cables dont work well. You need one thats been especially made or altered for PAL. Not sure if this is your problem but definitly worth considering.

well... i have a 47" LED tv and the N64 simple sucks at it... the image is so streched that the fonts are barely readable... the best result I find (w/o conversos, just the colored cables) was to plug it into a 32" tv.. the image is still bad, but is a LOT better and at least readable.. i also own a 29" CRT tv which i use with the N64, but please let me know if you get some better results!

well... i have a 47" LED tv and the N64 simple sucks at it... the image is so streched that the fonts are barely readable... the best result I find (w/o conversos, just the colored cables) was to plug it into a 32" tv.. the image is still bad, but is a LOT better and at least readable.. i also own a 29" CRT tv which i use with the N64, but please let me know if you get some better results!

Can't you set your TV Input for that to be 4:3?

I'm running my SNES on a 59" Samsung Plasma, and it looks great with he standard RCA cables.

Welcome to old N64s. i strongly recommend not blowing into the cartridges or the cartridge slot as we used to do as kids - as it turns out, all it does is just leave tiny bits of spit on the connectors and ends up rusting them :p

A trick I found was just to plug and unplug the cartridge several times before switching the unit on. By doing this, you're basically scraping off the oxidized layer from the cartridge's PCB tracks, and perhaps even the connector inside the 64 - shiny surfaces will usually always become oxidized (except for gold I think). I sometimes had to do it 20-30 times (while the unit was off of course) - but it always seemed to work.

Forget blowing - it won't help a cartridge that hasn't been used for 10 years. You're probably going to make the oxidization worse.

A blank screen ("No Signal") could most likely be the sign of the cartridge not being read correctly - try my steps above. The AV part of it should be fine. The 64 will not output a signal unless the cartridge can be accessed properly.

Have a look at the cartridge contacts - if they're as dull as a well-used $1 or $2 coin, then they're most likely heavily oxidized. When the cartridge was new, they would have been shiny.

A trick I found was just to plug and unplug the cartridge several times before switching the unit on. By doing this, you're basically scraping off the oxidized layer from the cartridge's PCB tracks, and perhaps even the connector inside the 64 - shiny surfaces will usually always become oxidized (except for gold I think). I sometimes had to do it 20-30 times (while the unit was off of course) - but it always seemed to work.

Forget blowing - it won't help a cartridge that hasn't been used for 10 years. You're probably going to make the oxidization worse.

Yep, you're bang on. It's also a part luck thing too, hoping to get a good enough connection for the game to work :p

A trick I found was just to plug and unplug the cartridge several times before switching the unit on. By doing this, you're basically scraping off the oxidized layer from the cartridge's PCB tracks, and perhaps even the connector inside the 64 - shiny surfaces will usually always become oxidized (except for gold I think). I sometimes had to do it 20-30 times (while the unit was off of course) - but it always seemed to work.

Forget blowing - it won't help a cartridge that hasn't been used for 10 years. You're probably going to make the oxidization worse.

Q-Tips n' clear rubbing alcohol always worked for me. If that doesn't work, Dremel and a light buffing pad will shine the gold contacts right up. Don't over do it though! You'll need the special bit to open up the cartridges and as with all electronics, beware of static!

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
    • VidCoder 12.20 by Razvan Serea  VidCoder is a DVD/Blu-ray ripping and video transcoding application for Windows. It uses HandBrake as its encoding engine. Calling directly into the HandBrake library gives it a more rich UI than the official HandBrake Windows GUI. VidCoder can rip DVDs but does not defeat the CSS encryption found in most commercial DVDs. You’ll need the NET 8 Desktop Runtime. If you don’t have it, VidCoder will prompt you to download and install it. The Portable version is self-contained and does not require any .NET Runtime to be installed. You do not need to install HandBrake for VidCoder to work. Feature list: Multi-threaded MP4, MKV containers Completely integrated encoding pipeline: everything is in one process and no huge intermediate temporary files H.264, H.265, MPEG-4, MPEG-2, VP8, Theora video Hardware-accelerated encoding with AMD VCE, Nvidia NVENC and Intel QuickSync AAC, MP3, Vorbis, AC3, FLAC audio encoding and AAC/AC3/MP3/DTS/DTS-HD passthrough Target bitrate, size or quality for video 2-pass encoding Decomb, detelecine, deinterlace, rotate, reflect, chroma smooth, colorspace filters Powerful batch encoding with simultaneous encodes Customizable Pickers to automatically pick audio and subtitle tracks, destination, titles and more Instant source previews Creates small encoded preview clips Pause, resume encoding VidCoder 12.20 changes: Updated HandBrake core to 1.11.2. Download: VidCoder 12.20 | 47.0 MB (Open Source) Download: Portable VidCoder 12.19 | 89.3 MB Link: VidCoder Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Too soon, I'm still not over this death!
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      590
    2. 2
      +Edouard
      185
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!