My only complaint left is having to select the ROM file type whenever I load a ROM. Why it doesn't remember the type you used last is beyond me.
As of r3529 this has been fixed, so you may now feel free to bugger off if you so choose.
For the sake of completeness, I will answer your question. Here's why: it's called a bug. Sometimes things don't work right. Luckily we can rely on you to discover it and write about it as if its some weird kooky mystery or bolded egregious crime against humanity.
For the sake of completeness, I will answer your question. Here's why: it's called a bug. Sometimes things don't work right. Luckily we can rely on you to discover it and write about it as if its some weird kooky mystery or bolded egregious crime against humanity.
Sounds a lot like trolling, but whatever. Who the hell ever said the reports were a crime against humanity?
Ever since I joined these forums, I've been getting nothing but bad vibes, so yeah, time for me to sod off.
Zeromus is not a troll. He helps code the emulator you're complaining about and fix the bugs that people report. And he can't help you if you don't give him real problems with the program instead of contradicting complaints.
Leave if you want, but this is the only place you can get help with BizHawk, if you really want help.
Zeromus is not a troll
Leave if you want, but this is the only place you can get help with BizHawk, if you really want help.
Well, it sure as hell seemed like trolling. I do want help, but I guess I suck balls at explaining properly.
CoolKirby wrote:
He can't help you if you don't give him real problems with the program instead of contradicting complaints.
Such as? When did I contradict myself? If someone gives me an example, I'll reiterate. I might leave, I might not, but based of the vibes I'm getting here, my presence is just as welcome as a skunk at a picnic.
The reports arent crimes against humanity. The bugs are. According to the reports. Any statement describing an unfortunate situation that's bolded is interpreted as a crime against humanity. That's how the internet works. I was just spelling it out for you, since you seemed not to understand. In general, you do not seem to understand how you come across, although now that you have devised the skunk analogy, it seems you may have some idea after all. You may find that leaving is a simple solution. Or you could just quit stinking. If you would like instructions for the latter method, perhaps that could be arranged. I'm sure you can handle the former method quite well yourself.
The reports arent crimes against humanity. The bugs are. According to the reports. Any statement describing an unfortunate situation that's bolded is interpreted as a crime against humanity. That's how the internet works. I was just spelling it out for you, since you seemed not to understand. In general, you do not seem to understand how you come across, although now that you have devised the skunk analogy, it seems you may have some idea after all. You may find that leaving is a simple solution. Or you could just quit stinking. If you would like instructions for the latter method, perhaps that could be arranged. I'm sure you can handle the former method quite well yourself.
Alright, I obviously can't take back my formerly posted douchebag comments and no, I wasn't aware how using bold text was emphasized in such a manner. I can try to retract what I said and the tone I stated such things in, but doing so would be in vain and wouldn't do a damned thing when it comes to mending ways with people in the forums.
I honestly didn't know what the f**k I was doing, much less when I was reporting bugs with the Snes core in BizHawk. The GUI confused me as certain options where in places I didn't expect them to be in, such as with the filtering. I expected bilinear to be in "filters" and not "GUI". As for what I can do right now, I don't know how to continue, or what to do next time I freak out.
Just take my advice, quit talking about synchronization, and try to explain your problems using the methodology I outlined in that same post. I cant promise we can solve your problems but at least we can get them written down in a way that makes sense.
Emulator Coder, Site Developer, Site Owner, Expert player
(3600)
Joined: 11/3/2004
Posts: 4739
Location: Tennessee
I don't know that the_randomizer is genuinely trying learn how to modify his behavior, but I'll post here anyway as it could help everyone!
"Why it doesn't [bug] is beyond me.", I would delete this from your vocabulary. It comes off rude. Also it shouldn't be beyond you at all because the reason is simple. It was an oversight, or a bug, or not built yet. This is open source software, we try to make things good, it gets there eventually. I think any programmer would find this sentence insulting.
Don't put a bug in bold. Again, seems insulting.
Use the issue tracker and wait for the problem to be resolved. I recommend this one for everyone, it is difficult to track bug statuses in a thread format.
Also, if you post in a thread such as this and no the Bug Reporting thread, I make no promises that I will read it.
Don't get mad if your bug isn't in the next release. There's limited coder resources here, and I try to prioritize. Your priorities may not be the same as mine.
Just take my advice, quit talking about synchronization, and try to explain your problems using the methodology I outlined in that same post. I cant promise we can solve your problems but at least we can get them written down in a way that makes sense.
Alright, we can drop synchronization, but I will explain the current issue at hand.
The Bsnes core on BizHawk 1.x.x experiences very noticeable vertical screen tearing, but the framerate itself never drops below 60 frames per-second, which is good seeing as I thought I still had an issue with speed. That alone proves my CPU is more than powerful enough to run it. Force-enabling V-sync does not resolve said tearing when using the nVidia control panel to switch it on.
So, we can knock off a few of the complaints I had earlier
- Bilinear filtering has been added
- Resizable window options have been added (although custom sizes can't be saved due to the Snes native resolution of 256x244)
- Audio issues I though existed seemed to have been resolved
- Speed issues also have been resolved, no framerate dips exist
The only thing left is vertical sync, hopefully that can be added in the near future.
Edit: Turning off GDI fixed the tearing. Is there a way to change the aspect ratio?
Yeah, I just saw that, and enabled it. I'll stop my fu**ing bitching and never step foot on these forums again.
Promise this time? Not only did you derail this topic, you made a complete fool of yourself.
the_randomizer wrote:
I'm not a damned noob you know.
WAHAHAHAHAHAHA.......HAHAHAHAHAHAHAHAHA!!!
You didn't see my last post on the bottom of the third page, did you? I retract what I said. Read my last post next time before you make baseless assumptions. Good day.
All you do is retract what you say, which one can only assume that means you don't think before you say anything. If you want help, post in the appropriate thread.
All you do is retract what you say, which one can only assume that means you don't think before you say anything. If you want help, post in the appropriate thread.
Yes, Master. Now I'm really getting the hell outta here.
Never dropping below 60 fps does not prove that your cpu is "more than powerful enough" for anything. Only the unthrottled performance of your CPU being in the 120fps range proves that it is unambiguously more than powerful enough.
Using drivers to force vsync can't always be expected to work; and we won't support it. You should never ask an application developer for support with that.
I'm not sure what the relation between the snes core and saving custom sizes. I don't see what snes has to do with it; the concept of 'saving custom sizes' in bizhawk is foreign to me.
Vsync option: Config > Speed/Skip. I'll imagine that you looked hard in all the menus instead of mis-reasoning where it ought to be and just missed it every time.
Vsync doesnt apply to gdi+ display method. GDI+ display method is an emergency backdrop. It is impossible to vsync with that method; and so vsync does not work.
Theres no way to change the aspect ratio. You should not be surprised, as this is a member of a constellation of display presentation features which includes filtering, a department bizhawk is clearly lacking in right now.
And finally, consider that, when you get the hell out of a place, because one twerp is being amateurishly abrasive towards you, you disrespect anyone who might already be in the middle of helping you by throwing away their time investment.
Never dropping below 60 fps does not prove that your cpu is "more than powerful enough" for anything. Only the unthrottled performance of your CPU being in the 120fps range proves that it is unambiguously more than powerful enough.
Using drivers to force vsync can't always be expected to work; and we won't support it. You should never ask an application developer for support with that.
I'm not sure what the relation between the snes core and saving custom sizes. I don't see what snes has to do with it; the concept of 'saving custom sizes' in bizhawk is foreign to me.
Vsync option: Config > Speed/Skip. I'll imagine that you looked hard in all the menus instead of mis-reasoning where it ought to be and just missed it every time.
Vsync doesnt apply to gdi+ display method. GDI+ display method is an emergency backdrop. It is impossible to vsync with that method; and so vsync does not work.
Theres no way to change the aspect ratio. You should not be surprised, as this is a member of a constellation of display presentation features which includes filtering, a department bizhawk is clearly lacking in right now.
And finally, consider that, when you get the hell out of a place, because one twerp is being amateurishly abrasive towards you, you disrespect anyone who might already be in the middle of helping you by throwing away their time investment.
Whoa, whoa, whoa. Dude, when did I ever say I was being abrasive or disrespectful to you? I was directing that towards Pasky13, not you. The reason I mentioned getting out of here is because I guess I can't take the s**t people throw in my direction, I guess it's time for me to grow some balls.
What the f**k am I supposed to do now that I'm in deeper crap than when I started? The more I post here, the deeper I get.
Edit: Didn't test the audio thoroughly enough, it still pops/skips every ten seconds.
I should just stick to Snes9x despite its inaccuracies compared to Bsnes. All I really care about is the high compatibility and Blaarg's super-accurate SPC700 core, without the audio skipping.
Whoa, whoa, whoa. Dude, when did I ever say I was being abrasive or disrespectful to you? What the f**k am I supposed to do now that I'm in deeper crap than when I started? The more I post here, the deeper I get.
Read harder. When did _I_ ever say you were being abrasive?
the_randomizer wrote:
Didn't test the audio thoroughly enough, it still pops/skips every ten seconds.
Right now to avoid periodic sound hiccups you need to use "config > sound > sound throttle" which probably necessitates disabling of vsync at this time. Theres some thorny issues in the codebase right now, this is the best you can do.
Whoa, whoa, whoa. Dude, when did I ever say I was being abrasive or disrespectful to you? What the f**k am I supposed to do now that I'm in deeper crap than when I started? The more I post here, the deeper I get.
Read harder. When did _I_ ever say you were being abrasive?
the_randomizer wrote:
Didn't test the audio thoroughly enough, it still pops/skips every ten seconds.
Right now to avoid periodic sound hiccups you need to use "config > sound > sound throttle" which probably necessitates disabling of vsync at this time. Theres some thorny issues in the codebase right now, this is the best you can do.
There I go again, misconstruing something someone said, go fig. I'll give those settings a try and if they don't work the way they should, I'll go back to Snes9x until these issues can be neutralized or improved.
It's not, that's something out of my control due to my capture card. This is not a precise timing comparison, a couple of frames off is to be expected because the card only captures at 30.00fps while bizhawk is recording at 60.098fps. So you're going to eventually lose timing towards the end of the video. Also keep in mind I'm not perfect and it's difficult to get the correct starting frame for the console vs the emulators due to the different capture rate. If you notice at the beginning it's also slightly off by 1 frame at some points, that is why.
What I'm doing is not exact, although I wish I could be, but is more to spot blatantly obvious mistiming. So if bsnes is off by ~4 frames by the end of the video (10minutes), I'd say that's pretty accurate.
One frame may be within the margin of error for this kind of study. the difference seems to happen at about 6:56. Theres no reason to believe theres a glitch in the game timing there, since it has passed that point earlier without missing anything. Therefore I expect that is the point in which some judder in the capture process occurred.
If it was off by ~4 frames at the end of the video and the demo had looped 4 times, that would be suspicious.
Fixed the Link to the Past video, it's now properly cropped, scaled, and the audio is now the console's output. It's also using snes9x 1.52 to compare rather than 1.51
Chrono trigger. This time I tried using AssumeFPS(60.000) for bizhawk (not necessary in the snes9x's because they both capture at 60.000) since it records at 60.098. It doesn't seem to change anything, I compared it without the AssumeFPS() and it still seems to be in the same spot as this video, starting frame was the 1st frame the text appeared:
Link to video
