Rockbox.org home
Downloads
Release release
Dev builds dev builds
Extras extras
themes themes
Documentation
Manual manual
Wiki wiki
Device Status device status
Support
Forums forums
Mailing lists mailing lists
IRC IRC
Development
Bugs bugs
Patches patches
Dev Guide dev guide
Search



Donate

Rockbox Technical Forums


Login with username, password and session length
Home Help Search Staff List Login Register
News:

Rockbox Ports are now being developed for various digital audio players!

+  Rockbox Technical Forums
|-+  Support and General Use
| |-+  Plugins/Viewers
| | |-+  Testing Doom for bugs and problems, found some...
« previous next »
  • Print
Pages: [1]

Author Topic: Testing Doom for bugs and problems, found some...  (Read 1839 times)

Offline Reece

  • Member
  • *
  • Posts: 101
  • AKA, ZallCaTor
Testing Doom for bugs and problems, found some...
« on: January 08, 2013, 10:35:05 PM »
        I have been testing Doom on my Sansa Fuze V2 for bugs.  When I start the TNT.wad. and select a "skill level" it freezes. I don't get an error message, it just freezes the screen and nothing happens. (I even let it sit for a while, but it just drained my battery and did not un-freeze)I don't know if this is a problem with the wad, the player, or the engine.
     
      In the options menu under "set keys" there is no option to bind the in-game-menu function to a key. This might be troublesome for some people because, by default, it takes up the "home" button. There is no option to bind a function to scroll right, scroll left, or the home button, they are just left out of the list of buttons to be bound. Also the select button has a duplicate, the "Record" and "Select" buttons are the same. The power button is called mode, so what are the "on" and "off" buttons in the list? This is very confusing. I think the "Set Keys" menu needs to be revised.

Device Used: Sansa Fuze ( Version 2 )
Logged
Reece, AKA; ZallCaTor
Devices: |Clip+|Fuze V2|

Offline saratoga

  • Developer
  • Member
  • *
  • Posts: 8974
Re: Testing Doom for bugs and problems, found some...
« Reply #1 on: January 08, 2013, 10:44:22 PM »
Doom doesn't run correctly on the Fuze v1/v2 for lack of RAM (see FS#10481).  You don't need to report problems with it. 
Logged

Offline Reece

  • Member
  • *
  • Posts: 101
  • AKA, ZallCaTor
Re: Testing Doom for bugs and problems, found some...
« Reply #2 on: January 09, 2013, 12:40:58 AM »
Is there a way to allocate more ram?
Logged
Reece, AKA; ZallCaTor
Devices: |Clip+|Fuze V2|

Offline saratoga

  • Developer
  • Member
  • *
  • Posts: 8974
Re: Testing Doom for bugs and problems, found some...
« Reply #3 on: January 09, 2013, 12:59:14 AM »
Read fs#10481.
Logged

Offline Reece

  • Member
  • *
  • Posts: 101
  • AKA, ZallCaTor
Re: Testing Doom for bugs and problems, found some...
« Reply #4 on: January 09, 2013, 11:43:55 AM »
    I am new to this, I finally figured out how to find it... Anyway, I read it through and it answered my question on the RAM usage. But what about the "Set Keys" menu? I still think this can be fixed, and should. Does this type of thing take a long time? It looks to me that the options menu is universal. Meaning that it is not specific to any device, because, as I said in the original post, some of the buttons on my device are not on the list of buttons to bound, and at the same time there are buttons that do not exist on my device.
Logged
Reece, AKA; ZallCaTor
Devices: |Clip+|Fuze V2|

Offline saratoga

  • Developer
  • Member
  • *
  • Posts: 8974
Re: Testing Doom for bugs and problems, found some...
« Reply #5 on: January 09, 2013, 11:47:32 AM »
Quote from: Reece on January 09, 2013, 11:43:55 AM
I still think this can be fixed, and should. Does this type of thing take a long time? It looks to me that the options menu is universal. Meaning that it is not specific to any device, because, as I said in the original post, some of the buttons on my device are not on the list of buttons to bound, and at the same time there are buttons that do not exist on my device.

Take a look at the doom plugin code then and see if you can get something better working.
Logged

Offline Reece

  • Member
  • *
  • Posts: 101
  • AKA, ZallCaTor
Re: Testing Doom for bugs and problems, found some...
« Reply #6 on: January 09, 2013, 04:35:31 PM »
  I will be checking it out, but I am still a beginner coder. I am going to be taking classes, and I have been learning allot on my own by using Rockbox and seeing what other people do. I will probably not be able to do anything to fix this. That's why I am going to take a coding class so I can be a little more self sufficient.
Logged
Reece, AKA; ZallCaTor
Devices: |Clip+|Fuze V2|

Offline Reece

  • Member
  • *
  • Posts: 101
  • AKA, ZallCaTor
Re: Testing Doom for bugs and problems, found some...
« Reply #7 on: January 10, 2013, 12:59:03 PM »
And one more note for anyone that might make a patch for this, try adding compatibility for double click sprint. Because there is no option for sprinting except for "always sprint," which is very annoying. Just add the option to double click the up key to sprint, like in many other games.
Logged
Reece, AKA; ZallCaTor
Devices: |Clip+|Fuze V2|

  • Print
Pages: [1]
« previous next »
+  Rockbox Technical Forums
|-+  Support and General Use
| |-+  Plugins/Viewers
| | |-+  Testing Doom for bugs and problems, found some...
 

  • SMF 2.0.17 | SMF © 2019, Simple Machines
  • Rockbox Privacy Policy
  • XHTML
  • RSS
  • WAP2

Page created in 0.064 seconds with 14 queries.