jiXo escribió:desarchivado
.
So the Xbox 360 port is back again from the dead. I was unable to do anymore work on the 360 when myK 360 broke down. I got a Slim 360 from JPizzle and Matthie sometime ago which made it possible for me to resume work on this port.
Unified menu system
We have finally reached the stage where all the different versions of RetroArch use the same centralized menu system. This means that while they may look differently in terms of appearance, they are exactly the same functionality-wise and feature more or less the same options.
This is a big milestone, especially for the Xbox 360 port since it was always lagging massively behind the other versions when it came to features implemented. Having to duplicate work per port is really unsustainable and it’s fortunate that we finally have a more robust menu abstraction that allows us to not even think so much about the platform this is going to run on.
In similar fashion, the XUI presentation layer for the menu has been updated. It is basically a single XUI scene consisting of a listview that gets updated manually by the underlying RetroArch menu code. There may be some label updating issues still left in, but these issues will be sorted out in subsequent releases.
There are some other big advantages this time:
- The menu presentation uses a fullscreen viewport whereas the other image uses the user-defined viewport. In previous versions of RetroArch 360, the UI would only be visible on the user-defined viewport. This meant that at times the UI would be cut off and wouldn’t render fully. Thankfully this is behind us now.
- Previously, you could not ‘return’ one directory level up in the filebrowser. Since the code that the XUI layer is now using is the same as all other versions, this is now possible.
- It is now also possible (thanks to the unified menu system) to set path settings.
Please be aware that certain options in the menu may either not be available right now on Xbox 360 or serve no purpose anyway. If so desired, we may put in some ifdefs to hide some of these options for 360, but for now it tries to expose as many menu options as possible.
More features implemented
The video driver has been given a big makeover, and it now implements integer scaling options. Blitting has also been made faster, which should reduce video input latency some.
On the input side, it is now possible to map the left or right analog sticks to the D-pad. Full analog stick support has also been implemented – so cores that make use of RETRO_ANALOG functionality (such as TyrQuake) can be played now with analog controls. It is now also possible to map any button to any action. You can even bind the analog stick axes to certain frontend actions if you so desire.
Auto S-RAM Save has been carried over from the other ports. Core Detect functionality is in now.
MAME 2003 0.78
The MAME 0.78 libretro core has been out for a while now on PlayStation3, Android, iOS, Blackberry, and PC. Now it hits Xbox 360 as well. On 360 thankfully we have more than enough RAM for any game that MAME circa 2003 supported, which leaves performance as the only issue. 360 performs a little bit better than the PS3 for this core, although it’s by no means a huge difference. In any case, the Mortal Kombat/Midway DCS games should be fully playable at fullspeed with the DCS Speedhack enabled. Taito F2/F3 is borderline fullspeed, and Street Fighter The Movie and Konami GX (Sexy Parodius/Salamander 2) as well.
It should also be possible to bring up the MAME OSD menu by pressing the Right Shoulder button – and it is possible to remap the buttons from MAME’s OSD menu as well.
A work in progress
Let it be known – this release is a Work-In-Progress. There are many features that don’t work just yet, but also many new features which already work just fine.
Among the things known not to work right now is:
Threaded video. Don’t try to toggle it in the menu.
Shaders. More on this later, but for now just pretend like the shader submenu doesn’t exist (yet).
Onscreen keyboard. This will be added in future releases and it will allow you to input text for certain settings in the menu that require it.
Custom ratio. Well, this does work but it’s slightly finicky right now in terms of how to set it up. Fortunately, integer scaling will save the day for overscan correction purposes in case setting up the custom ratio proves too irksome.
Overlays. Not implemented yet. Just ignore the stub functions for now.
Netplay. Not even tested yet. It won’t be of much use anyway until the Onscreen Keyboard has been implemented.
Why no shaders yet?
This is a fair question. If you have used RetroArch PS3, then you know that one of its strong points is the shader system that allows you to configure up to eight passes at the same time, and also allows you to set Framebuffer Object sizes 2 to 5 times as big as that of the original game image. It’s fair to say that the PS3 out of all game consoles so far is in a league of its own here.
So why don’t we have this goodness on Xbox 360 yet? Well, it turns out that Microsoft just went about things in a very stupid way that basically prevents us from ever reaching this kind of visual fidelity on 360.
And it’s all due to the fault of this thing called EDRAM. The Xbox 360 came with 10MB of embedded RAM (called EDRAM) – this has long been touted as a chief selling point for 360 that made all sorts of framebuffer and anti-aliasing effects essentially “free”. However, here comes the big caveat – Microsoft expects you to put ALL your render targets (Direct3D’s equivalent term for ‘FBOs’) into 10MB of EDRAM.
And if you’re thinking that – hey – maybe I can just use a memory pool from that big unified 512MB main RAM block and put my render targets on there, bad news again – you can’t. So there is a pretty severe problem where you’re expected to put your entire framebuffer, your depth buffers and your color buffers all inside a paltry amount of RAM that is even 6MB less than the Dreamcast’s VRAM. No wonder so many Xbox 360 games had sub-720p resolutions and this spilled over into the PS3 ports as well.
Another big handicap of this EDRAM approach BTW? The shader units can’t fetch from it – so instead, the EDRAM image needs to be copied (otherwise called ‘resolved’) back to main RAM whereupon the shader unit can fetch colors from it.
Microsoft suggests using the built-in predicated tiling to ‘work around’ the EDRAM limitations but there is really nothing to work around really and it doesn’t magically ‘fix’ the structural problem either – overall it is simply inferior to what we are able to do on PS3. On PS3 I have a full 256MB segment of VRAM that I can put my render targets on, my LUT textures – whatever. This is perfect for RetroArch’s purposes since 256MB of main RAM seems to be more than enough for most cores out there (especially emulators), and that still leaves you with a big block of RAM which you can totally dedicate to graphics, shaders and LUT textures.
So – long story short? Pretty big compromises will have to be made when shaders make their return for the 360 port. Previously – before we took shaders out – we had several hacks in that already catered to this limited amount of EDRAM – for instance, game frame images could be 512×512 max in size. Obviously this will not be sustainable with upcoming cores like ScummVM running comfortably at 640×480 so a less hacky and generic solution will have to be thought of.
Maybe we will have to go with just one shader you can apply instead of allowing for several shader passes. I’ll be researching my options for 1.0.0.3. In any case, this is definitely one area where PS3 has the lead and it turns out that the same situation is repeating itself now between Xbox One and PS4 – with the Xbone’s limited amount of ESRAM not capable of holding a full 1080p framebuffer, depth/color buffers etc.
Final notes
NOTE: DON’T USE OLDER CONFIG FILES WITH THIS NEW VERSION OF RETROARCH 360. Start out with the one that comes withe the release and go from there.
RetroArch Xbox 360
- Threaded Auto SRAM save should be available now.
- Reimplemented the menu – now uses the common menu code.
- XUI GUI no longer is bound to the game’s viewport – so it should no longer cut off when using certain aspect ratios.
- It’s now possible to go back a directory level in the file browser.
- It’s now possible to change path options.
- Analog input works now – cores that support RETRO_ANALOG (such as TyrQuake) should now have working DualShock controls.
- Analog mapping to D-pad works now for all cores.
- Ported MAME 2003 [0.78] to Xbox 360.
- Integer scaling works.
- All the changes made to RGUI since the last release (Core Information, reorganized Settings, possible to map frontend actions to gamepad buttons/analog axes, etc)
- Faster blitting – now uses XGCopySurface
PD: La verdad que es una lastima ver como se saca algo tan interesante como una actualización y info muy jugosa de una de las suites de emuladores más interesantes, pero parece que cada vez interesa menos, es algo que entiendo y no puedo criticar a nadie, yo mismo ahora estoy más dedicado a steam y a otros asuntos, aunque siempre saco algo de tiempo para sacar la consola de su descanso, a ver si un año de estos me pongo con algo que no me gusta dejar a medias.
Pararegistros escribió:Bueno compañeros, después de echarle un ojo a las 14 páginas del hilo, no he visto aún cómo configurar los paths para las roms. Es caótico.
Quiero añadirle el path de las carpetas de Roms de los otros emuladores que tengo instalados para no tener que mover ni duplicar las mismas al meterlos dentro de la carpeta Roms del Retroarch y nada.
El primer engorro es que voy a Settings y al pulsar "A" funciona como "B" ordinariamente (volver atrás); pulso "B" y funciona como "A" (validar), estoy en Path Options y veo los siguientes:
- Content directory <default>
- Core directory: game
- Core Info directory: game\roms
Me meto en este último y veo game: : (Dir) entro y me encuentro las siguientes opciones:
<Use this directory>:
- media: (Dir)
- roms: (Dir) ... etc.
Entro en Roms y ahí están:
- doom : (Dir)
- nxengine-datafiles: (Dir)
Y hasta ahí puedo llegar sin añadir un puñetero path. ¿Qué es lo que estoy haciendo mal?
Gracias.
alfageorge escribió:no me aclaro, donde se meten las roms de cada uno de los sistemas?
dentro de la carpeta roms que esta dentro de RetroArch-360?
y si es asi, dentro de esa carpeta puedo separar las roms en otros subdirectorios para cada sistema?
si el programa una vez lo ejecutas desde la 360 te da la opcion de navegar entre directorios, entonces da igual donde pongas las roms. no se como funciona pues aun no lo probe.
snake218 escribió:alfageorge escribió:no me aclaro, donde se meten las roms de cada uno de los sistemas?
dentro de la carpeta roms que esta dentro de RetroArch-360?
y si es asi, dentro de esa carpeta puedo separar las roms en otros subdirectorios para cada sistema?
si el programa una vez lo ejecutas desde la 360 te da la opcion de navegar entre directorios, entonces da igual donde pongas las roms. no se como funciona pues aun no lo probe.
No es que todas las roms van revueltas, dentro de la carpeta roms se pueden crear subdirectores, varias carpetas para separar por sistemas. Y puedes buscar directorios siempre y cuando estén dentro de la carpeta principal del retroarch.
Lo que yo hice fue crear en la carpeta roms carpetas para nes, snes, etc, y para q funcione con los otros emus configure sus rutas para que apunten a retroarch/roms/snes (por ejemplo)
Para poder usar los archivos de mame del fbanext y del mame 360, con el retroarch, como éstos emus solo aceptan buscar archivos dentro del directorio principal, la única solución que encontré para que compartan archivos, es poner estos emus dentro de la carpeta retroarch, quedando algo asi
retroarch/roms/mame/archivos del mame360/archivos del fbanext/roms
Es un relajo pero es la única forma de que estos tres emus compartan las mismas roms, ya que no permiten buscar roms que no estén en un subdirectorio. Aunque claro, se puden poner normalmente cada emulador de mame en su respectiva carpeta y con sus roms, pero me gusta ahorrar espacio
alfageorge escribió:snake218 escribió:alfageorge escribió:no me aclaro, donde se meten las roms de cada uno de los sistemas?
dentro de la carpeta roms que esta dentro de RetroArch-360?
y si es asi, dentro de esa carpeta puedo separar las roms en otros subdirectorios para cada sistema?
si el programa una vez lo ejecutas desde la 360 te da la opcion de navegar entre directorios, entonces da igual donde pongas las roms. no se como funciona pues aun no lo probe.
No es que todas las roms van revueltas, dentro de la carpeta roms se pueden crear subdirectores, varias carpetas para separar por sistemas. Y puedes buscar directorios siempre y cuando estén dentro de la carpeta principal del retroarch.
Lo que yo hice fue crear en la carpeta roms carpetas para nes, snes, etc, y para q funcione con los otros emus configure sus rutas para que apunten a retroarch/roms/snes (por ejemplo)
Para poder usar los archivos de mame del fbanext y del mame 360, con el retroarch, como éstos emus solo aceptan buscar archivos dentro del directorio principal, la única solución que encontré para que compartan archivos, es poner estos emus dentro de la carpeta retroarch, quedando algo asi
retroarch/roms/mame/archivos del mame360/archivos del fbanext/roms
Es un relajo pero es la única forma de que estos tres emus compartan las mismas roms, ya que no permiten buscar roms que no estén en un subdirectorio. Aunque claro, se puden poner normalmente cada emulador de mame en su respectiva carpeta y con sus roms, pero me gusta ahorrar espacio
ok gracias, ahora me pongo con el.
un saludo.
edit, pos no chuta, pase la carpeta "retroarch-360" tal cual a la raiz de una unidad usb de disco duro, me salen las opciones seting, cores y demas, pero al darles con el A no pasa nada, si le doy con el B me aparecen los cores, le vuelvo a dar y me manda de nuevo a las opciones de inicio del programa despues de hacer como un amago de carga pero de nuevo sin nada cargado.
le de a lo que le de con el boton B, siempre me manda a "core selection" cuando le doy a uno de los cores de nuevo con B, hace que carga, se pone la pantalla en negro y me vuelve a las opciones de inicio sin cargar nada.
