Submit it and see what happens! Usually as long as sound is present it's OK

It would probably be rejected. Which site?

I recommend getting an emulator - nestopia or mesenrta are current favorites!

GLHF and welcome :D

Not at this time

Due to emulation inaccuracy, the moderating team has amended rule #8 to disallow polystation and similar clone consoles. It now reads:

Banned consoles: RetroN 1 (at least but not limited to HD+AV), Polystation. (Note: All inaccurate clone console submissions will be rejected.)

I recommend using nestopia or mesenrta emulators instead. glhf!

You might consider, as an easier/beginner strat, bonking the first koopaling, then bonking it on its left side so that he goes to the right to kill the bro. This is much easier, removes the danger of bro, builds pspeed easily, and only costs a second or two. glhf

the smb3 mods have been reviewing clone consoles since some emulator quality/accuracy/fidelity discrepancies have been observed. as a result, we have decided to ban the clone console "RetroN 1", and consider this a warning if you are playing on or considering a low price clone console option.

the retron 1 does not accurately observe lag frames, even in lag frame heavy levels like 2-pyramid, 7-4, 8-tank1, and others. as a result, for longer runs, the retron could have a timing drift of several seconds. this makes it challenging and unfair to compare on a board in which competing runners could otherwise have different positions on the board.

we'd like to look for other clones and related issues (e.g. polystation), and also solicit feedback from other runners and technical folks about this. we don't own all clones, so other insight is welcome. please leave comments in smb3 discord so everyone can participate and learn. thanks all, glhf!

note: audio quality and palettes were not considered as criteria for ban, though anecdotally, they can be associated with lower accuracy underlying hardware.

• mesen is fine

• emulators, usb, more importantly your display/monitor, all contribute to a small amount of input latency. the emulator and usb itself probably doesn't contribute much. usually it'd be your display. in many cases this is not noticable, but sometimes it can be quite bad and cause 1-2 frames of input latency.

• you can play in any resolution, but i suggest you play in 4:3 aspect ratio and use integer scaling only.

• down+right dpad directions can be simultaneously pressed, yes. the original controller allows this kind of motion. do you mean left+right? left+right is not allowed, since it is not possible on the original controller.

The new styling on src probably includes underlying script updates, so you'll want to hard refresh your browser cache with shift-f5 so download the new assets. Otherwise, I'm not surprised stuff broke.

Also earlier today everything was going very slow. Exacerbating factors :narfmaLolsob:

Legacy reasons, but I suppose it was like that because there is more error introduced by using 60fps over ~60.09fps. Significant digits. Not accurate enough to value caring.

For posterity, for those interested, we discussed this in the official discord :)

I'm trying not to be pedantic but I think that's the crux of this post, pardon!

We never defined "begins" and I think that's what you are concerned about. It's not the a press, its defined as x frames before some visual cue. This is expected to me; as long as the runs are consistent against the doc I don't care if it doesnt match the TAS.

I've added a more explicit note in the document, thanks! doc link: https://docs.google.com/document/d/1gVoljNjR3lagg9EgqONeQZ9FQVhtBEz5mkyPdmpXZy4/edit#heading=h.8lala6xubnmv

Usually it is fine. Sometimes emulator accuracy is sacrificed in favor of performance, especially on old consoles, so we need to know the specific emulator used.

What is the nes emulator? Name and version?

preferable to leave milliseconds off of submissions

Yep! Mods will delete milliseconds anyways in most cases. It should save you some time to get more practice+attempts in too :)

Scroll to the bottom here: https://docs.google.com/document/d/1gVoljNjR3lagg9EgqONeQZ9FQVhtBEz5mkyPdmpXZy4/edit#heading=h.m9yf2rct9jp4 there's a distinctive image with about 15% of the curtain up top with tan lower 85% or so. That frame is 54 frames after start at 60fps. More detail is in the doc.

We default to permissive and enumerate the small ban list rather than a large allow list. EH manipulation is not mentioned and thus allowed, but we/i can add an explicit note saying eh manip is allowed on console and emulator.

We accept nes classic runs in general (beware: you'll have a harder time syncing with the different framerate!)

We allow flashcart soft resets in general

Pardon the confusion!

edit: I updated the src warpless rules to explicitly state it is allowed

Here is TEEX's spreadsheet: https://docs.google.com/spreadsheets/d/1j5MTbh14h6Rx1zXJpIop5negFPi6OvLts0KFJGJlh9k/edit#gid=677991048 EH+hands sounds useful. Several runners redundantly keep track of it themselves anyways. :D

The right side of the screen is the safest place to be, and spamming fireballs pushes the possibility of taking dmg (from rocky wrenches) to near 0. There is a small element of being near the end of a good pace run and wanting to do something that is simple and unlikely to screw up (vs bouncing on bullets to get 99 lives, 2 minutes before you could PB, which is an unnecessary risk and scary :) ).

Given you are on the right side of the screen and shooting fire already, why not shoot them as fast as possible as a form of practice and flaunting your leet button-mashing ability ;).

"Start Enable" is not a default setting, you may have to go to the layout/scriptable auto splitter tab and check the box.

Do your settings look like this: https://imgur.com/a/Ktn2FmA ? In "Script Path", does the smb3.asl file exist at that path? Are you running a (generally) unmodified rom, like PRG 0, and not a practice rom? FWIW FCEUX 2.2.3 on windows 10 just worked for me (without running as admin).

Note: thread bumping is generally frowned upon in most online communities :)

Do you have a video example? I'd suggest using tools like a wrong warp practice rom to verify your setup is correct. Then we can rule out the most common way of crashing, which is incorrect memoery values. That said, even pixel perfect, we've seen some crashes. Checking a video we can point out where, and playing the practice rom can empower you to figure it out.

Ping me if you get a board up, I'd probably submit a run. I did a couple with a patch and it was so much faster :)

Naively, I'd initially route like hundo but pwing from 7-9 on 5-9 🤷