RSS
Website| Monday, August 24, 2009 |
  Cogwheel 1.0.3.0 beta 3 | ||
Posted - 8/24/2009 7:10:59 PM | ||
I managed to break save states in the last build of Cogwheel (attempting to load a save state would fail, not being able to set a property). I've marked the offending read-only property with [StateNotSaved] and made the loader slightly more robust in Cogwheel 1.0.3.0 beta 3. It's beta 3, not 2, because I uploaded 2 and then noticed another issue - you couldn't change the controller mappings! This is something that must have been broken for ages, but either nobody noticed or they just didn't care to report it. Oh well, that's been fixed now. For some reason Google don't let you re-upload files, so beta 3 it has to be. Another addition is this build is preliminary support for persistent cartridge RAM. Some games, such as Phantasy Star (pictured above) let you save your progress in the game onto battery-backed RAM built into the cartridge. If you come back to the game later you should now be able to continue your progress without needing to manually save the entire emulator state. I've had reports of rather bizarre crashes bringing one poor user's machine to its knees. I'm at a loss to establish why; I've tried the emulator on four machines (two Vista, two XP) and although one of the machines displays a white screen instead of the emulator output (no pixel shader 2.0 support on its Radeon 9000) the software trundles along just fine otherwise (I can at least hear the game music!) The one notable difference between my machines and his machine is that he's using a 64-bit version of Windows, and all of the ones I have access to run 32-bit Windows. To see if this is the issue, I've changed the configuration to x86 (I've encountered strange bugs with .NET code using unmanaged 32-bit code on 64-bit Windows) to see if this will remedy issues, but if anyone has any bright ideas I'd be interested to hear them. | ||
|
Comments
|
Journal of benryves | |
 | shadowcomplex
Member since: 4/12/2005 From: Playa del Carmen, Quintana Roo | |||
Posted - 8/25/2009 9:18:20 PM | ||||
| Unfortunately I don't have any other bright ideas, but I can confirm what you suspect has been a problem for me. I had written several tools in C# and never had a problem with them on XP or Vista. However, the last game I was contracted on, one of the artists was using 64 bit Vista and the tools all exploded with bizarre (read: cryptic) errors. After trying numerous things, I changed the build settings explicitly to x86 and the problems went away. | ||||
| ||||
 | benryves GDNet+
Member since: 9/4/2003 From: Purley, Greater London | |||
|
Posted - 8/26/2009 8:00:11 AM | ||||
Quote:Thanks for the confirmation, the chap who was having the problems reported that the latest version (explicitly set to x86) now works on his machine, even though there are no changes to the main emulator code. His symptoms appeared to be excessive memory usage (which led to hard disk thrashing when he ran out of physical memory), rendering the machine unusable. Most peculiar! | ||||
| ||||
| |
All times are ET (US) | |
| S | M | T | W | T | F | S |
1 | 2 | 3 | 4 | |||
6 | 7 | 8 | 9 | 10 | 11 | |
12 | 13 | 14 | 15 | 16 | 17 | 18 |
19 | 20 | 21 | 22 | 23 | 24 | 25 |
26 | 27 | 28 | 29 | 30 |
OPTIONS
Track this Journal
ARCHIVES
September, 2010
August, 2010
July, 2010
June, 2010
April, 2010
March, 2010
February, 2010
January, 2010
December, 2009
November, 2009
October, 2009
August, 2009
June, 2009
May, 2009
March, 2009
February, 2009
January, 2009
December, 2008
November, 2008
October, 2008
September, 2008
August, 2008
July, 2008
June, 2008
May, 2008
April, 2008
March, 2008
February, 2008
November, 2007
October, 2007
September, 2007
August, 2007
July, 2007
May, 2007
April, 2007
February, 2007
January, 2007
December, 2006
November, 2006
October, 2006
September, 2006
August, 2006
July, 2006
June, 2006
May, 2006
April, 2006
March, 2006
February, 2006
January, 2006
December, 2005
November, 2005
October, 2005
September, 2005
August, 2005
April, 2005
February, 2005
January, 2005