Main > Main Forum

Mame analog joystick mapping vs. u360 firmware mapping?

<< < (6/12) > >>

u_rebelscum:

--- Quote from: Neverending Project on November 18, 2009, 12:20:46 pm ---Robin is certainly the expert here, but I think he may have meant to say to use the generic map "7778...4445" The way I understand the symmetry to work, you would need to specify at least to the fourth row to allow mame to determine up/down symmetry of the rows. The periods denote the end of a row.

--- End quote ---

Yup, beat me to my own correction.

Bender:
yeah, that did it works great

Thanks everyone!

Got my personal best hi score on Qbert after the adjustment!

Bobulus:
Random thought: the u360 is programmed via a flash-rom, right? And flash roms typically have a limited life of x number of flashes before they start glitching out.

Take the example of the flash-rom memory stick that is so popular for file storage these days. It's good for something like 10,000 flashes, which is more than most people will use in a lifetime. However, some people were running Firefox off the stick, and the constant updates to the profile were creating worries that it would wear the stick out too fast, such that a flash stick version of Firefox was created that updated less often.

Now, presumably the u360 also has such a flash lifetime.

Would it be better to use the mame map exclusively, rather than flashing the u360 for every mame game, to save on the flash life, and save the u360 mapping for non-mame games?

Might be a non-issue, I'm just throwing this out there.

Bender:
The main reason I use the 360 maps are so I can use arzoo's program to load the right map for the front end and other emu's
plus it's very easy to customize the map in mame too.

good point about the flash memory though.

curious to hear what others have to say about it

I have flash memory for my camera that has well over 10,000 writes to it an it still works fine

u_rebelscum:
That write limit is per "cell" or block of cells (depending on if the blocks can be written & earased by cell or not), not per drive.  You can have single level cell (SLC) or multi level cell (MLC), like with SSDs.  These cells are grouped by blocks.  Usually individual cells can be written one by one.  For a cell to be overwritten, they must be erased on the block level.  Note that "cell" is different than "file", and if the flash drive firmware or driver is good, it can write the updated file to a different cell(s) without touching the old cell, thus saving an erase/write cycle (until the space is needed).

Many of the flash drives have a 1,000 write/erase cycle limit (per cell or block).  Some are higher, at the before mentioned 10,000 limit.  Higher end are at 100,000 or even 1,000,000 cycles.


But even with a 1,000 cycle limit drive, with level smoothing firmware a small file can be updated hundreds of thousands of times.  This assumes the drive has free space one hundred times the size of the file being updated.  If the free space is limited, then the number of rewrites drops.

There are other issues (speed) that might crop up before the cells and thus drive starts failing.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version