Support and General Use > Plugins/Viewers

Testing Doom for bugs and problems, found some...

(1/2) > >>

Reece:
        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 )

saratoga:
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. 

Reece:
Is there a way to allocate more ram?

saratoga:
Read fs#10481.

Reece:
    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.

Navigation

[0] Message Index

[#] Next page