Tweetovi

Blokirali ste korisnika/cu @byuu_emu

Jeste li sigurni da želite vidjeti te tweetove? Time nećete deblokirati korisnika/cu @byuu_emu

  1. Prikvačeni tweet
    30. sij

    Greetings! byuu is an upcoming multi-system emulator that seeks to provide the accuracy of higan with the ease-of-use of bsnes. Development has only just begun, but I will be posting news and screenshots here while the emulator is being created. I aim to launch some time in 2020!

    byuu emulator (preview)
    Poništi
  2. prije 57 minuta

    Menu save states, hotkey save states, and status bar status messages are in. I'll try to tackle system reset and video scale settings next. That should get us to a point where the emulator is fully usable, provided your images are uncompressed.

    Prikaži ovu nit
    Poništi
  3. prije 2 sata

    Well that one was easy at least.

    Prikaži ovu nit
    Poništi
  4. prije 2 sata

    Coming along fast ... hotkey support is in, though there's not many there yet. Critical functionality needed: video scaling, save RAM, save states, ZIP support. Hundreds of features will be needed to complete this project, of course.

    Prikaži ovu nit
    Poništi
  5. prije 3 sata

    Driver settings are in. They mirror bsnes' design, since it works well enough. Bit of a trade-off here in that I'm exposing a lot of options to allow fine control compared to only a few to make it simpler to use. But getting this right is important, so ...

    Prikaži ovu nit
    Poništi
  6. proslijedio/la je Tweet
    prije 4 sata

    Question: would folks rather I post WIP development news to (this account) or to (separate account)? I'll go with whatever result wins. Thanks!

    Poništi
  7. prije 24 sata

    v0.2 is up on GitHub. You can now basically play NES games, but without saves or features, heh. It's not much, but it proves the concept at least: I can wrap higan cores into a bsnes-like API and UI. The amount of work to do is a bit overwhelming, but a little more each day ...

    Poništi
  8. 2. velj

    (if it's any consollation to the latter, I was rooting for v108 myself, but v1 is good too.)

    Prikaži ovu nit
    Poništi
  9. 2. velj

    v1 won by a large margin, so v1 it is. I appreciate the input, thanks everyone! Apologies to those who wanted v108 ^-^;;

    Prikaži ovu nit
    Poništi
  10. 1. velj

    Real input mapping is in for the virtual controller.

    Poništi
  11. 1. velj

    Question: should byuu start with version 1 since it's a new project, or with version 108 and stay in sync with higan (since they share the same underlying emulation cores)? bsnes went with the latter, but eventually forked and desynced anyway.

    Poništi
  12. 1. velj

    That feeling when you get really tired of writing boilerplate input mapping code and just hardcode the emulated controller to your keyboard directly.

    Poništi
  13. 31. sij

    "It seems like you do the same thing than retroarch. Why you dont release core for each system instad of developing another retroarch?"

    Poništi
  14. 31. sij

    By default when you go into the per-system input mapping, it'll show the global mappings and how they relate to a given system in a lighter font color (eg SNES X = Upper Middle), so you see what corresponds where. But you'll also be able to assign your per-system overrides here.

    Prikaži ovu nit
    Poništi
  15. 31. sij

    Once you've loaded an individual system, there will be some sort of per-system configuration window that will let you map things the way you do in bsnes today. Possibly at a later date, but not too far off.

    Prikaži ovu nit
    Poništi
  16. 31. sij

    So here's how it'll look: the usual settings panel will map an abstract controller. In the future, maybe I'll also allow mapping an abstract second player, mouse, etc. It's modeled to provide all the keys of the SNES controller + Genesis fighting pad.

    Prikaži ovu nit
    Poništi
  17. 31. sij

    I know that virtual/universal controller mappings are controversial, so you can basically pretend it's not there at all, and map the controller for each system directly if you'd prefer. I would then only use the virtual mappings for the gamepad OSD navigation (once it's ready.)

    Prikaži ovu nit
    Poništi
  18. 31. sij

    On input: it's just not practical to expect users to map every controller type for all 25 systems byuu will support to their gamepads. I intend to start with a virtual gamepad to map all systems, but allow per-system overrides. So both use cases will be supported.

    Prikaži ovu nit
    Poništi
  19. 31. sij

    Audio mixing is in. The really huge pain is always the input bindings. That requires about 30x the amount of code as video and audio combined =/ Also, holy heck, 300 follows! I'm always overwhelmed by the support, thank you all so much, the kind encouragement helps a lot~! ^-^

    Prikaži ovu nit
    Poništi
  20. 30. sij

    Think of this as making every system into a nail, so that we can use a simple hammer to construct the user interface for all of higan's supported systems. It's crude and misses nuance, but it makes the program *substantially* easier to use in the end.

    Prikaži ovu nit
    Poništi
  21. 30. sij

    higan's new tree node system is *incredibly* complex by necessity, and the linear structure from previous releases is no longer present to create an easy UI. But since all problems can be solved with abstraction, I'm using an intermediate layer to provide this missing metadata.

    Prikaži ovu nit
    Poništi

Čini se da učitavanje traje već neko vrijeme.

Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.

    Možda bi vam se svidjelo i ovo:

    ·