I dabble in coding, linux, gaming, HEMA, LARP, e-mobility, carhacking, simpits and… parenting?

  • 17 Posts
  • 70 Comments
Joined 3 years ago
cake
Cake day: June 16th, 2023

help-circle



  • So often connected devices have to be “overriden” again within Wine too.

    There are now still 2 entries for the same Model and Vendor id in the Wine reg. One for xinput. And this is e.g. prioritized by some games like Elite so they will only start to listen on xinput here, where nothing ever arrives. In that case references to xinput have to be removed again from the registry. Only to be auto repopulated by the next Proton upgrade in some cases or when the device enumeration changes for some reason. Pain.


  • I do this but that’s not all. There are some options that remap especially additional joysticks to SDL XInput Mapping devices automatically. Probably(!) back from the days where games could not deal with more than one joystick anyway. Layers in layers and sometimes it’s detective work to figure out why and where the device stopped working. Again. And this is before the terribly broken input system of some games is even reached.

    Random trivia: Touch panels count too.













  • That is interesting. Do I understand this correct that it has to be SBS left/right for this to work? I read conflicting reports on this.

    Thing is my glasses need right/left and most of what’s on YT does simply not work when I just go fullscreen with SBS enabled so I have to drag it out of YT first and run it through Bino (or use ffplay with stereo3d filter) to “fix” this again.

    This looks like if I want to make it convenient for VR I make it inconvenient for XR glasses users like XREAL and Viture users. I’m highly confused.

    Oh and what about h265 or V1? The example only suggests h264:

    ffmpeg -i input_file.mkv -vcodec libx264 -x264opts “frame-packing=3” output_file.mp4

    Tried if h265 would happily eat frame-packing too but it’s an unknown option for it :/