Emulator Coder, Published Author, Site Developer, Site Owner, Expert player
(3636)
Joined: 11/3/2004
Posts: 4758
Location: Tennessee
For many games, there aren't any options. This is because the FBA savestates are often missing important data necessary for sync. I recall trying to fix some sound data that was missing in TMNT, but I eventually gave up. Unfortunately this is not a very good emulator.
Emulator Coder, Published Author, Site Developer, Site Owner, Expert player
(3636)
Joined: 11/3/2004
Posts: 4758
Location: Tennessee
Trying not to guide this convo too much right now. But I will point out that the poll question using any mention of a specific tier is a non-starter. Tiers will change over time. What if we add a "regular" tier? Or a demos tier. Or a Pony tier? What if later we remove these? The whole point of the system is that it is flexible enough to change when site politics change. Should we change the poll each time this happens?
Emulator Coder, Published Author, Site Developer, Site Owner, Expert player
(3636)
Joined: 11/3/2004
Posts: 4758
Location: Tennessee
BizHawk 1.5.3 Released!
This release features a significant rearchitecture of the dll files, and a renaming of the rather mundane bizhawk.multiclient.exe to EmuHawk.exe. As a result you must extract this into a fresh folder. If you extract over an existing release it will not work! Also, sorry to say, again an old config.ini is not recommended.
Main features of this release are some very big fixes (especially for N64Hawk), and more core specific lua functionality (including "lua breakpoints" for many cores).
As usual, I recommend reading the
full release notes.
Windows binary
Emulator Coder, Published Author, Site Developer, Site Owner, Expert player
(3636)
Joined: 11/3/2004
Posts: 4758
Location: Tennessee
I do not want two poll questions, nor do I want a poll about publishing, as it would have little value. You silent vote of "no this shouldn't be published" has really no weight. Do you understand the criteria for rejection? Is it suboptimal? Is that why you are voting no? I can't guage any of this from a silent vote. Also, rejection is rather non-subjective these days since entertainment value isn't a factor.
The simplest way I can put it is this:
Vote on entertainment, DISCUSS technical details. Also discuss entertainment, discussion beats a poll any day.
Emulator Coder, Published Author, Site Developer, Site Owner, Expert player
(3636)
Joined: 11/3/2004
Posts: 4758
Location: Tennessee
thatguy wrote:
Good to see that this got published before the ET improvement. Congratulations adelikat, you hold the record for the two worst games ever made at the same time.
Emulator Coder, Published Author, Site Developer, Site Owner, Expert player
(3636)
Joined: 11/3/2004
Posts: 4758
Location: Tennessee
Spikestuff wrote:
TASeditor wrote:
Nice improvement. This is vault stuff, voted no for not being entertaining.
Yet again. MEH EXISTS! I cannot stress this enough
Why are you stressing incorrect voting behavior at all?
Meh doesn't mean vault. Meh means you were had a neutral opinion about the entertainment value of the movie. If you weren't entertained by the movie, no is the correct vote.
I think you are mistakenly interpreting voting as this:
No = don't publish
Meh = Vault
Yes = Moon
As opposed to:
No = not entertained
Meh = neutral
Yes = entertained
where judge determines vault eligibility, and vault vs moon based on the overall voting results and posts.
Vault is intended to be non-subjective, we (usually) don't need voters to decide that. We need voters for the subjective part, deciding if the movie is entertaining, thus the poll question.
Tech quality can result in a rejection. However, you should be having a DISCUSSION about this. (You can vote no too, but I would recommend discussing the situation before voting).
In summary:
Vote on entertainment value
Discuss tech issues
Judge will determine tier
Emulator Coder, Published Author, Site Developer, Site Owner, Expert player
(3636)
Joined: 11/3/2004
Posts: 4758
Location: Tennessee
ALAKTORN wrote:
“Ending choice
The fixed version fix the fact that you can't kill the final boss. The original has a bug where you can get him down to 1 health, but the final blow will not do damage. In the fixed versions, they kill the boss. In my version, since I can't, I at least get him down to 1 health and promptly commit suicide. I think this is the best way to handle this situation, though there are other reasonable ideas.”
don’t forget to update that
Emulator Coder, Published Author, Site Developer, Site Owner, Expert player
(3636)
Joined: 11/3/2004
Posts: 4758
Location: Tennessee
Right now the site and BizHawk calculate at exactly 60, I haven't ever been told a precise number to use instead. Plus, it is kind of silly to go that precise when the N64 emulators are WAY off in timing accuracy anyway. As the console verified movies show.
Emulator Coder, Published Author, Site Developer, Site Owner, Expert player
(3636)
Joined: 11/3/2004
Posts: 4758
Location: Tennessee
Ok, replaced the submission file with a movie that does kill the boss.
What I didn't realize was that there is indeed a bug that was fixed in the fixed version. But the logic is that if you have 1 health you can't kill the boss. If you have at least 2, he will in fact die. Unfortunately when I was figuring all that out, I was down to 1 health >.<
Emulator Coder, Published Author, Site Developer, Site Owner, Expert player
(3636)
Joined: 11/3/2004
Posts: 4758
Location: Tennessee
Honestly, that stuff is outside my expertise. I just know I get blazing fps after buying a card.
EDIT:
Yes, tool dialogs that need to draw slow things down and are GFX card irrelevant. The only thing that the GFX helps with is the N64 core specifically, nothing else. Everything else is CPU dependent.
For Ram Watch you can select Options -> draw on screen and then close it. Also, I recommend File -> Recent -> autoload in combination with that.
Emulator Coder, Published Author, Site Developer, Site Owner, Expert player
(3636)
Joined: 11/3/2004
Posts: 4758
Location: Tennessee
Anybody trying to do serious non-SNES work should use this for now. Your freezing bugs are fixed, for instance.
Also, you can get more fps using more cores, CPU is by nature a non-threaded task, the client can run on a separate thread but is minimal in cpu usage. In the case of N64, it is your GFX card that matters most since it uses opengl for 3D rendering.
I bought be decent card recently rather than relying on my onboard one. I went from 60sih fps for N64 to about 400 at high resolutions
Emulator Coder, Published Author, Site Developer, Site Owner, Expert player
(3636)
Joined: 11/3/2004
Posts: 4758
Location: Tennessee
creaothceann wrote:
Khaz wrote:
Edit: Oh yeah. And my CPU is an AMD Phenom II "Deneb", 3.4 GHz
Well on my AMD Phenom II X6 1050T ("Thuban") I get ca. 71-76 fps on SMW's intro (when the screen isn't blank).
But are you recording a movie? In BizHawk, we enforce deterministic emulation when recording. Unfortunately, in the case o bsnes, this necessitates savestating every frame which has a healthy speed cost.
Emulator Coder, Published Author, Site Developer, Site Owner, Expert player
(3636)
Joined: 11/3/2004
Posts: 4758
Location: Tennessee
Khaz wrote:
I have "Automatically Backup Movies" checked.
The specific behavior of this feature is that before you do something destructive to a movie for the first time, it goes ahead and makes a backup. Therefore, your first recording won't be affected by this feature. However, when you resume recording in your next recording session it will backup the movie first, before doing the record. As such, it is still dependent on you to at least save something first.
Also, at any point in recording you can right-click and select "Backup movie", or "Save movie". Just like any program where you edit a file, saving often is critical!
As for your "Crash", most "crashes" in BizHawk are actually exception that it can recover from just fine (Just click ok). So if you had your emulator completely die, I'd like to know specifically what you were doing, and what the error message, if possible.
Emulator Coder, Published Author, Site Developer, Site Owner, Expert player
(3636)
Joined: 11/3/2004
Posts: 4758
Location: Tennessee
No, I'm not going to bother writing this in a language that serves no purpose to any other project. The whole point of this was to write an engine that would be relatively easy to port to other emulators.
The main point in writing it in Lua is precisely portability to other emulators. If you had made a lua script, it would immediately be usable in about 15 other emulators that implement the same Lua standard. For example, nearly every emulator in this list
Emulator Coder, Published Author, Site Developer, Site Owner, Expert player
(3636)
Joined: 11/3/2004
Posts: 4758
Location: Tennessee
Patashu wrote:
Can Bizhawk be made smart enough to know whether to use it or not? e.g. check number of cores on user's CPU, if it's greater than 3 turn ring buffer I/O on else turn it off, and if the user has changed it personally respect their choice.
These reason it doesn't currently do this is because we don't know for sure this is what will happen. The assumption is that the optimal choice is 2 cores = don't use it, 3+ = use it. But it will take more people trying it and posting the results to know this. Until then, it is just an assumption that is probably inconsistent at best.
Emulator Coder, Published Author, Site Developer, Site Owner, Expert player
(3636)
Joined: 11/3/2004
Posts: 4758
Location: Tennessee
In SNES, you can go to SNES -> Options, and click "Always Double-Size Framebuffer" to get this behavior.
Should this be the default setting?
Genesis has no option yet, but you really shouldn't be using Genesis anyway, it isn't finished :D
Emulator Coder, Published Author, Site Developer, Site Owner, Expert player
(3636)
Joined: 11/3/2004
Posts: 4758
Location: Tennessee
Slowking wrote:
So there shouldn't be "any%" and "any% glitched", where "any% glitched" is actually the faster movie. There should be "any%" and "any% doesn't use a particular glitch", where any% is the faster movie.
Exactly. glitched any% as a name should go away. Fastest = any%, and then we need to do a better job categorizing any% movies that forgo time saving glitches/techniques.
