SolidSnake
Member
btw, r-type 3 acts strange after the boss from the third stage. After killing the boss, you have to back all the stage with the ship backwards, but i keep crashing in something that its not visible in the screen o.0
Squidgesnes 0.35
- Thread starter Squidge
- Start date
Sevish
Still Fresh
Quality work as usual Squidge!
Clonekeen trick worked for me, under FW 1.4.0.
Clonekeen trick worked for me, under FW 1.4.0.
NeoStuey
Active Member
Clonekeen suggestion didn't work for me. 
Still it's a fun little game so it wasn't a total loss adding it to my SD.
I'm using GPH firmware 1.4.0.
Still it's a fun little game so it wasn't a total loss adding it to my SD.
I'm using GPH firmware 1.4.0.
daclassicgamingmaster
It Is Your Birthday.
ok, I still cannot get this running. This time, I select a rom and it hangs on a black screen and I have to hit the power switch to get it unfrozen.
help!
help!
I'm happy to say that I haven't had any major problems with this release. The no sound thing happened once and every now and again the bg selection text will come up for no reason which is easily removed. So apart from some minor bugs, I'm loving this release because before this I never played with sound because it was always far too loud. I didn't realise how well some games actually play with sound enabled.
Nickmon
Member
I am getting the same.
Firmware 1.2.0
Copied in the new gpe into the old .34 directory and mine will oad the rom and then stop on the 'snes' screen.
.34 I left in the dir and it works fine...
Firmware 1.2.0
Copied in the new gpe into the old .34 directory and mine will oad the rom and then stop on the 'snes' screen.
.34 I left in the dir and it works fine...
sanctuary13
Still Fresh
- Joined
- Feb 10, 2006
- Messages
- 26
sorry squidge, loved .34, but .35 loaded one rom ONCE and hasnt worked since. same snes skin pop up. i tried doing the clonekeen crap, but the DOS install isnt recognized by my win xp.
sorry, playing a game to play another game aint gonna cut it, ill just keep enjoying .34 on mute for a while longer till you nail this. Good Luck!
sorry, playing a game to play another game aint gonna cut it, ill just keep enjoying .34 on mute for a while longer till you nail this. Good Luck!
Knoxximus
Member
The Spider Mastermind posted on Feb 23 2006 at 05:53 AM said:
Did you overclock? If so, what value?
Last edited by a moderator:
It works nice for me.
I have firmware 1.4.0, no other updates (well, the SDL libraries).
I created a totally new directory ("SuperNES BETA"; mi 0.34 directory is "SuperNES") and put all the new files there. Not overwriting the old ones.
Volume control works fine. The layer disable feature is also working.
I didn't play for more than 1 minute, so I don't know if it crashes after a while.
I have firmware 1.4.0, no other updates (well, the SDL libraries).
I created a totally new directory ("SuperNES BETA"; mi 0.34 directory is "SuperNES") and put all the new files there. Not overwriting the old ones.
Volume control works fine. The layer disable feature is also working.
I didn't play for more than 1 minute, so I don't know if it crashes after a while.
The Spider Mastermind
Member
Knoxximus posted on Feb 24 2006 at 06:02 AM said:
When i did it originally, no, and it still ran ok(i didnt have the oc scripts in for 1.4 fw). At 260 it runs really nice. Nice enough for me to play all the way to tubular B).
Last edited by a moderator:
Morwynd
Member
sanctuary13 posted on Feb 24 2006 at 01:31 AM said:
You can install Commander Keen under Win XP by running it in compatibility mode for Windows 95. (Right click the installer, click Properties, go to Compatibility tab)
Doing it thru DOS command line (ie, Start/Run/'cmd') also works.
Last edited by a moderator:
I have a few little things that aren't quite as they should.
When playing Mario World, there is a flickering field at the bottom of the screen, and the game seems to be a little too fast. (the rom is flawless on my comp)
The vol max/vol min gets stuck sometimes, but that's fixable by turning the vol all the way up/down, and then turning it back again.
Also it seems that the SquidgeSnes is consuming a lot of battery power. Might just be my imagination, tho. I like to play with sound sometimes, and that certainly is a factor. ^_^;
I have tried disabling all sound through settings, but there isn't really any difference.
/a
When playing Mario World, there is a flickering field at the bottom of the screen, and the game seems to be a little too fast. (the rom is flawless on my comp)
The vol max/vol min gets stuck sometimes, but that's fixable by turning the vol all the way up/down, and then turning it back again.
Also it seems that the SquidgeSnes is consuming a lot of battery power. Might just be my imagination, tho. I like to play with sound sometimes, and that certainly is a factor. ^_^;
I have tried disabling all sound through settings, but there isn't really any difference.
/a
There should be a 'force VSync' or somthing like that in the settings menu that needs to be checked. Then it will paint all the way to the bottom, it will also slow the game up a bit too...a3-h posted on Feb 27 2006 at 01:56 PM said:
Last edited by a moderator:
mooseknuckle2000
Member
Squidge, thanks for implementing the layer disable feature while transparencies are sorted out. I can now figure out what level I'm going to in my new addiction "Evo- Search for Eden". This game rocks thanks to you Squidge. Keep up the good work, everyone appreciates it immensly.
I have a question for squidge if he is still reading this thread. It seems to me that the FPS limiter works fine when sound is off, but when you enable sounds the FPS limiter holds the frame rate too low. For instance, with sound on and FPS limiter off, mario world will run between 40-55 fps in gameplay. If you run the game with FPS on though (at fs1), the frame rate generally runs at 26, but never getting higher than 28, which is slightly too slow. If you have sound off however, the FPS limiter works perfectly holding the frame rate between 29 and 30.
What would be causing this? Is this something that can be easily fixed or is it a sign of a deeper problem in the port?
What would be causing this? Is this something that can be easily fixed or is it a sign of a deeper problem in the port?
Squidge
Certified Guru
The frame rate limiter tries to ensure that every frame take the same amount of time. The way it does this is check the snes rom for the country and see if it needs 50 fps or 60 fps. It'll then divide this value into the number of milliseconds in a second (1000), so you get either 20ms or 16.6ms. If a frame takes less than these times to redner, it will be held up until these times are met.
Sound is produced by a different thread, so I can only assume that the second thread is interfering with the timing used by the first.
Sound is produced by a different thread, so I can only assume that the second thread is interfering with the timing used by the first.
I realise that no-one's posted here for a while, but i thought i'd throw this out there:
I've noticed how in all the Donkey Kong Country's (1-3) it no-longer shows the 'DK' logo on the barrels, even with all four layers turned on. Then furthermore in DK2 in one of the lava levels there are some enemies in the water that aren't visible either. Anyone else notice this?
Does it mean that these games don't use mode 1 (pixel-to-pixel)? Are there even any other display methods than mode 1 and 7, ones that allow for more than 4 layers? Or is it just a game specific bug in this new release, cos it worked on 0.34. My guess it's probably the latter, but i thought i'd see what other people made of this. Maybe other games are affected by this too? :huh:
I've noticed how in all the Donkey Kong Country's (1-3) it no-longer shows the 'DK' logo on the barrels, even with all four layers turned on. Then furthermore in DK2 in one of the lava levels there are some enemies in the water that aren't visible either. Anyone else notice this?
Does it mean that these games don't use mode 1 (pixel-to-pixel)? Are there even any other display methods than mode 1 and 7, ones that allow for more than 4 layers? Or is it just a game specific bug in this new release, cos it worked on 0.34. My guess it's probably the latter, but i thought i'd see what other people made of this. Maybe other games are affected by this too? :huh:
