Posts for zeromus

1 2
35 36 37
45 46
Posted: 7/7/2014 4:08 AM
Quote
zeromus
Editor, Emulator Coder, Experienced Forum User
Joined: 8/7/2008
Posts: 1156
None of those details affect the difficulty of emulating it. The size is irrelevant. There could be something else odd about that game, though. Virtual memory probably has nothing to do with this. You shouldn't disable your pagefile, it just breaks things (other than this). If it fixes more things than it breaks for you then I suggest you figure out why it's breaking things. A malfunctioning disk or motherboard/sata device perhaps. It's gonna be bad news eventually one way or another. If virtual memory is in fact involved here, then I would think the only way it could happen in this case is by actual exhaustion of memory which would require the participation of a bunch of other programs sucking down memory. You'd know if that was happening. There's really no reason to suspect this, but I guess it is noteworthily odd that you've got it disabled.
Posted: 7/5/2014 6:15 AM
Quote
zeromus
Editor, Emulator Coder, Experienced Forum User
Joined: 8/7/2008
Posts: 1156
Beed28 wrote:
In the new version (1.7.1), rewinding on SNES games (both cores) is really choppy whereas it was fine on the previous version (aside from the rare crash, but that could have been the compatibility core). The rewind feature still works fine on NES games.
Just so you know this is still on our minds... I believe the snes rewinding is slower because the loadstate process may have slowed down substantially in r6687 and r6679 due to the rom getting reloaded every time a loadstate happens. This was done to fix a bug with firmwares getting cleared when loadstate happened, as part of a comprehensive effort to make sure everything gets cleared. The only way to make the firmware reload was to make the whole rom reload, and that's serious business. I'll have to think of an entirely different way to clear only the needed parts without losing the rom(s)
Posted: 6/26/2014 6:01 AM
Quote
zeromus
Editor, Emulator Coder, Experienced Forum User
Joined: 8/7/2008
Posts: 1156
check it in yabause. sounds like a yabause core bug, nothing we could do about that
Posted: 6/24/2014 5:38 AM
Quote
zeromus
Editor, Emulator Coder, Experienced Forum User
Joined: 8/7/2008
Posts: 1156
Kurabupengin, your problem hasn't been solved yet. TAG, it means you didn't copy enough information from the event viewer for us to do anything with.
Posted: 6/20/2014 5:35 PM
Quote
zeromus
Editor, Emulator Coder, Experienced Forum User
Joined: 8/7/2008
Posts: 1156
"jit debugging problem" sounds like "program is crashing". Look for information in event viewer.
Posted: 6/18/2014 12:43 AM
Quote
zeromus
Editor, Emulator Coder, Experienced Forum User
Joined: 8/7/2008
Posts: 1156
for the record: it's another intel 3150, this time on XP. This video card is going to be intel's biggest turd since the pentium's FPU
Posted: 6/17/2014 8:04 PM
Quote
zeromus
Editor, Emulator Coder, Experienced Forum User
Joined: 8/7/2008
Posts: 1156
please state which GPU you use, and check for information related to .net or bizhawk in the windows application log.
Posted: 6/17/2014 3:21 AM
Quote
zeromus
Editor, Emulator Coder, Experienced Forum User
Joined: 8/7/2008
Posts: 1156
thanks for finding that sappharad, i wouldntve gone looking for it. i still find it a little hard to believe.. not all sources on google are in complete agreement. anyway... 1. ill try and trap those errors better, if possible, which it may not be 2. why didnt Kurabupengin's system pop open an application-crashed dialog? is this a common thing? 3. i guess thats an increment to the priority of making an alternative to the opengl display method...
Posted: 6/16/2014 7:02 AM
Quote
zeromus
Editor, Emulator Coder, Experienced Forum User
Joined: 8/7/2008
Posts: 1156
run eventvwr.msc open windows logs > application look for .net or bizhawk related things with recent timestamps.
Posted: 6/15/2014 4:31 AM
Quote
zeromus
Editor, Emulator Coder, Experienced Forum User
Joined: 8/7/2008
Posts: 1156
zeromus wrote:
, the next step is to find the actual 'application' log, i.e. the one in the windows event viewer.
Posted: 6/12/2014 5:09 PM
Quote
zeromus
Editor, Emulator Coder, Experienced Forum User
Joined: 8/7/2008
Posts: 1156
i added that line to the cgp file and it _did_ filter, since im using r6848. make sure you restart emuhawk.
Posted: 6/12/2014 8:00 AM
Quote
zeromus
Editor, Emulator Coder, Experienced Forum User
Joined: 8/7/2008
Posts: 1156
there was a bug, and i fixed it in r6847/r6848. under some conditions, an extra bilinear filtering pass was getting applied to the input to the scanline filter. however, the way you like it was the buggy way, an accident. The scanline filter is available for you to edit in BizScanlines.cgp and BizScanlines.glsl, the .cgp using retroarch standard. You can add this line to get what you want filter_linear0 = 1
Posted: 6/11/2014 3:59 AM
Quote
zeromus
Editor, Emulator Coder, Experienced Forum User
Joined: 8/7/2008
Posts: 1156
Ohhh yeahhhh thanks for reporting back the victory. I blame security software all the time, it's nice to find out that sometimes it's actually at fault. It's possible that it's finding some kind of subtle virus-like bug in the exe which we could fix or work around, but not anytime soon.
Posted: 6/11/2014 1:15 AM
Quote
zeromus
Editor, Emulator Coder, Experienced Forum User
Joined: 8/7/2008
Posts: 1156
OK, you said it 'tries to open the window' but you have no evidence of that, since the window never appears, and you don't have a message that says 'now trying to open window'. What do you see in the app log that 'it actually opens the emulator'? I doubt the app log says 'it disappears'. Perhaps when you say 'app log' you mean 'task manager'. If the answer is yes, to save time, the next step is to find the actual 'application' log, i.e. the one in the windows event viewer.
Posted: 6/11/2014 12:19 AM
Quote
zeromus
Editor, Emulator Coder, Experienced Forum User
Joined: 8/7/2008
Posts: 1156
So, you mean, the bizhawk window actually appears, and then stays visible for 0.5 seconds, showing static or just a frozen screen, and then disappears? Is there anything related in your windows application log? And which OS are you using, and which video card?
Posted: 6/11/2014 12:07 AM
Quote
zeromus
Editor, Emulator Coder, Experienced Forum User
Joined: 8/7/2008
Posts: 1156
Same what thing? Are you reading my posts?
Posted: 6/11/2014 12:06 AM
Quote
zeromus
Editor, Emulator Coder, Experienced Forum User
Joined: 8/7/2008
Posts: 1156
I suspect your security software is interfering with the IPC between the programs or causing the snes core to malfunction and freeze for some reason, or the snes core exe gets corrupted on your system. Try disabling something like that. The MD5 of my libsneshawk-32-compatibility.exe from the bizhawk 1.7.0 archive is 4F4B88FCBF7BE521028B004C3184BADA The problem would seem to be happening while the c# is waiting for the c++ libsneshawk.exe side to boot up.. before the c# side has had a chance to even issue any specific instructions, like loading a rom, or pretty much anything at all. But I'm not completely confident of that.
Posted: 6/10/2014 7:54 PM
Quote
zeromus
Editor, Emulator Coder, Experienced Forum User
Joined: 8/7/2008
Posts: 1156
ignore what i said, and ill ignore what you said. lets try again. Dont worry about the process being left open. It isn't interesting.. it isn't a separate bug. It's only getting left open because it's malfunctioning, according to the screenshot provided. Just kill them as necessary for now.
Posted: 6/10/2014 5:03 PM
Quote
zeromus
Editor, Emulator Coder, Experienced Forum User
Joined: 8/7/2008
Posts: 1156
which SNES rom? WOrking fine for me over here. Don't worry about the process being left open. It's left open because its freezing. If it didnt freeze, it wouldnt be left open.
Posted: 6/10/2014 4:55 PM
Post subject: Re: Bilinear filter getting reset...
Quote
zeromus
Editor, Emulator Coder, Experienced Forum User
Joined: 8/7/2008
Posts: 1156
I couldnt repro this, but...
geoslake wrote:
I checked the display menu, it was still checked (when i unchecked it it was even less filtered).
this sounds dangerous, like you havent described or understood what's happening properly. Bilinear filtering is either on, or it isn't. Theres no 'low-power' bilinear filtering which can be reduced further to 'no-power' bilinear filtering by unchecking the option. You'll have to post some screenshots, all this stuff works perfectly to my knowledge.
Posted: 6/10/2014 4:03 AM
Quote
zeromus
Editor, Emulator Coder, Experienced Forum User
Joined: 8/7/2008
Posts: 1156
should be fixed in r6832
Posted: 6/10/2014 2:13 AM
Quote
zeromus
Editor, Emulator Coder, Experienced Forum User
Joined: 8/7/2008
Posts: 1156
Kurabupengin, what happens when you open it? Is anything displayed? Does nothing happen at all? Is there anything related in your windows application log?
Posted: 5/27/2014 10:07 PM
Quote
zeromus
Editor, Emulator Coder, Experienced Forum User
Joined: 8/7/2008
Posts: 1156
use an actual PAL rom in the gameDB which is marked as PAL. If your rom isn't in the gameDB (gamedb_sega_8bit.txt), then you could add it. If you're not using a PAL rom, then don't change the region to PAL. Or use a newer svn version than 1.6.1
Posted: 5/25/2014 7:26 AM
Quote
zeromus
Editor, Emulator Coder, Experienced Forum User
Joined: 8/7/2008
Posts: 1156
zeromus wrote:
There is no reason. It is not top priority.
synnchan wrote:
Then how is it not a priority to make it possible to do runs for yet another game system?
I said it was not a top priority. You read this as as 'not a priority'. Please don't argue with us when you cant understand what we've written, as typing it repeatedly for people like you who demand to know why everything can't be done immediately is one of the main reasons things arent already done. Also, we have lives outside of TASing.
Posted: 5/24/2014 1:46 AM
Quote
zeromus
Editor, Emulator Coder, Experienced Forum User
Joined: 8/7/2008
Posts: 1156
There is no reason. It is not top priority.
1 2
35 36 37
45 46