Search found 8 matches
- Wed Oct 24, 2007 8:52 am
- Forum: Bug Reports/Feature Requests
- Topic: HQ / NTSC Filter Crash
- Replies: 41
- Views: 30168
- Thu Jun 14, 2007 6:32 am
- Forum: Bug Reports/Feature Requests
- Topic: HQ / NTSC Filter Crash
- Replies: 41
- Views: 30168
- Tue Jun 12, 2007 7:18 pm
- Forum: Bug Reports/Feature Requests
- Topic: HQ / NTSC Filter Crash
- Replies: 41
- Views: 30168
- Tue Jun 12, 2007 5:13 pm
- Forum: Bug Reports/Feature Requests
- Topic: HQ / NTSC Filter Crash
- Replies: 41
- Views: 30168
Both _seem_ to work fine. I'm not sure how I might test the system memory to see if it's the culprit.Agozer wrote:Are you using System or Video memory in e.g. Nestopia?
I also tried a few games on Bsnes last night and I can use its HQ2x filter without any problems, but something about it doesn't look right.
- Tue Jun 12, 2007 3:38 am
- Forum: Bug Reports/Feature Requests
- Topic: HQ / NTSC Filter Crash
- Replies: 41
- Views: 30168
Strangely enough, I can enable NTSC and HQx Filters without any problems in the latest versions of VirtuaNes, Nestopia, and Snes9x, but that really doesn't help me out, because the former two are NES emulators and I'd rather not use the latter. I thought the information might possibly prove to be us...
- Mon Jun 11, 2007 6:59 pm
- Forum: Bug Reports/Feature Requests
- Topic: HQ / NTSC Filter Crash
- Replies: 41
- Views: 30168
- Mon Jun 11, 2007 5:39 am
- Forum: Bug Reports/Feature Requests
- Topic: HQ / NTSC Filter Crash
- Replies: 41
- Views: 30168
- Mon Jun 11, 2007 4:55 am
- Forum: Bug Reports/Feature Requests
- Topic: HQ / NTSC Filter Crash
- Replies: 41
- Views: 30168
HQ / NTSC Filter Crash
When I click either the HQ filter or the NTSC filter, ZSNES crashes out.
This happens with versions 1.51, 1.50 and 1.42, using an Nvidia 8600 GTS with both the latest drivers and an earlier set (not sure what version exactly).
Anyone have any suggestions as to what I could do to fix the problem?
This happens with versions 1.51, 1.50 and 1.42, using an Nvidia 8600 GTS with both the latest drivers and an earlier set (not sure what version exactly).
Anyone have any suggestions as to what I could do to fix the problem?