Yeah I have no problem with SMK on my xbox 1.51 build and I tested the ROM on a winblows machine running 1.53 to make sure there was no issue and it was working fine.

If I get a chance I'll post a video.

_________________
Xtras! We do the systems others dare not!

ok. Here is the video.. It's a little harder to see it over youtube but just pay real close attention to the lap timer.

I did two rounds. One with 1.53 xbox and the weird issue. The 2nd one is 1.51 xbox without the weird issue.

Sorry for the crappy driving. I've gotten used to playing in debug mode and I was/am half asleep when I recorded it..

_________________
Xtras! We do the systems others dare not!

...Where's the video?

_________________
Snes9x FAQs | Forum Rules
What operating system are you using? 32 or 64bit? Version of Snes9x? Is the text at the bottom of the window white when you load the game?
These suggestions are usually the solution to your issue!

Whoops!

http://www.youtube.com/watch?v=hKNu0afx2N0

_________________
Xtras! We do the systems others dare not!

Ok, I see what you're talking about, it seems the Xbox is sturggling to keep up with the immense amount of sprite/DSP activity. While this does happen on the SNES, it isn't as pronounced as I see here.

Seems it's auto-frame-skipping to prevent 100% load on the CPU.

_________________
Snes9x FAQs | Forum Rules
What operating system are you using? 32 or 64bit? Version of Snes9x? Is the text at the bottom of the window white when you load the game?
These suggestions are usually the solution to your issue!

I was hoping you wouldnt say that..

Although that is my initial suspicion.. the thing that is confusing me is the reported framerate of 60fps.

Shouldn't that be dropping? Also if I use the x-port framerate calculator (which calculates how often the screen_display function is called) it shows a consistent 60fps as well.

Best I can tell S9xDeinitUpdate is only called if IPPU.RenderThisFrame is true. So if this is the case I would think the fps display would drop below 60 during the slowdown.

On the other hand if I activate the NTSC filter than the onscreen fps displays match the framerate drop.

This is where I'm totally baffled. I've even tried setting debug points where IPPU.RenderThisFrame would be set to false and they never get hit.

On a side note I originally had the same issues with 1.51 (older sound core) but once I commented out all the frametimer stuff the problem went away.

Thanks

_________________
Xtras! We do the systems others dare not!

Well if the frame counters are saying it's running with no drop in FPS, either it's emulating the IRL lag, or auto-frameskip is turned on. (Probably the latter...)

_________________
Snes9x FAQs | Forum Rules
What operating system are you using? 32 or 64bit? Version of Snes9x? Is the text at the bottom of the window white when you load the game?
These suggestions are usually the solution to your issue!

I was gonna update my last message but you replied to it alreadyl.. I had as a test set the frameskip to 0 for kicks (maybe 1 too, cant remember) and it was still doing it. I was still getting the issue.

What is IRL lag?

_________________
Xtras! We do the systems others dare not!

Basically, you're emulating the SNES's CPU, which mean that any games that naturally caused lag on the system will be present on the emulator.

_________________
Snes9x FAQs | Forum Rules
What operating system are you using? 32 or 64bit? Version of Snes9x? Is the text at the bottom of the window white when you load the game?
These suggestions are usually the solution to your issue!

IRL = in real life

Does that mean I'm screwed when it comes to super mario kart?

Well it seems to run fine in 1.51 on the xbox. So I suppose that serves as an alternative. Hence why I'm trying different versions. So at this point I'd have to chalk it up to possibly the new sound core cause I think I've exhausted about every other possibility I can think of.

_________________
Xtras! We do the systems others dare not!

IPPU.RenderThisFrame is never set automatically. If you do not have your own frameskip code that sets this then snes9x will never do frame skipping.

The internal frame display should display two values: an fps value and a x/60 value. The first is simply the number of frames emulated per second (including skipped), the second is how many of the last 60 frames were displayed.


It's a rather strange issue you're having...
Did you try it without the coreupdate changes that were included in 1.53?

You lost me on that last question. Coreupdate changes included in 1.53?

Thanks

_________________
Xtras! We do the systems others dare not!

1.53 includes rewritten IRQ handling which was in the coreupdate branch during testing. The merge is in this commit: https://github.com/snes9xgit/snes9x/com ... ddc25cc173

The changes seem to incur a speed penalty on some architectures, which is why the wii and ps3 port did not include them.

Yes I have zones IRQ/SA-1 changes removed from the get go. So no affect by them...

_________________
Xtras! We do the systems others dare not!

Cant see any issue

Alright I figured it out. One of the many changes I made reverting various sections of code to try and fix some speed issues was the source of the problem. So I'm good now..

Thanks for the help!

_________________
Xtras! We do the systems others dare not!

Glad to hear it works!

_________________
Snes9x FAQs | Forum Rules
What operating system are you using? 32 or 64bit? Version of Snes9x? Is the text at the bottom of the window white when you load the game?
These suggestions are usually the solution to your issue!

Hey guys.. Just thought I would mention. I was implementing movie playback for the xbox and I noticed the movie I tried would not playback in 1.53 but it played back just fine in 1.51.

I confirmed this issue also exists on the PC builds.

I was using the Act Raiser movie from [url=http://tasvideos.org/Movies-SNES.htmlhere[/url] as a test.

_________________
Xtras! We do the systems others dare not!

What do you mean with "would not playback"?

I have no problem playing the movie, besides from the obvious desync due to the emulation changes.