Jump to content
LaunchBox Community Forums

Mock

Members
  • Posts

    32
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Mock's Achievements

8-Bit Processor

8-Bit Processor (3/7)

6

Reputation

  1. What i mean by not using the mouse, is installing software on android to virtually use the mouse, so its as different as i can be from the normal mouse input. For the WPF part i was looking into the case if it has anything to do with .net core 6 or 3. or the interface was using webgl that could be used when making a gui. i have no idea if this is the case, but wanted to try different thing if this issue only relates to very few cases. i have now direct knowledge of how the 3D rotation is made and what components are in play. i am just a user and have wanted to call up some devs to look into this issue that has been ongoing for so long.
  2. I have done tests with out a mouse. As well as different mice on Bluetooth, usb-c and wireless transmitter. Still had the same issue. But on this same setup I have experienced. It can get working, but is very rare as It typical requires having launchbox open longer then normal and maybe is in a platform not used. This is not certain that it is related to that part, as I am unable to reproduce a metode to get it working
  3. Here is an overview of what has been tried without luck Disabling controllers in Launchbox Using different mice (wired/wireless, different DPI) Fresh install of Launchbox Restarting PC Trying different monitors (including a TV) Verifying if the problem is specific to a certain hardware setup (Nvidia GPUs were used in all cases) Checking if the problem is related to the database or rendering of Launchbox Testing with a virtual mouse, used from an Android APP Investigating Launchbox's use of Chromium Embedded Framework (CEF) Adding and removing game platforms/roms Looking into potential cache issues
  4. Does any have a way of best importing af full set of Mame into launchbox Android. It seems when importing it also imports bios files and not only the Game roms. Also i see games like Virtua tennis as i remember and other games show up multiply times, even though i have selected only to import roms without clones and not add additional roms. i also made sure to click that similar titles show up as one game. I also tried to both have finalburn games and Mame, by first importing my folder with only FBneo romset. and then after i tried to import a full merged mame set. and click that it should not import already existing. my idea was to manually change emulator for games that didn't work to mame4droid. but it seems it ignores the settings and i ended up with duplicate games of everything. it seems something is wrong in the dat files or how it detects the games. Now i will try and go with having bios and roms in different folders. and exported all system files out of the rom folder. and then for FBneo i have no plan. hope some day there will be a way to have two arcade categories in LB android. as i use the retorach FBneo for retroachievements and bezels. also it has some better shader filters.
  5. i really don't understand if this is a bug or by design. but i tried to import a full merged fb neo set. and when i look at my file names there is multiply issues i am not having a game called shinobi1.zip inside launchbox the file is shown as the same even that i don't have the game it starts with a Japan version of the game. don't know how its even possible to start something that don't exist my real game is Shinobi.7z so the extension also shows up wrong if i rename the game inside the data folder to be shinobi.zip it actually starts the US version of the game as i would have expected from the beginning. but how again? when this is a 7z file. i imported the prefered "north american" roms so why it select a japan version of the game i also don't know. when selecting alternativ versions to play, i tried all 6 versions and non was US for the shinobi1.zip so it was not an issue with combined roms as i first expected I had trouble finding out why my bezels didn't work. and the issue was that it was loading wrong rom. My storage files /Main Storage/LaunchBox/Data/Platforms/arcade.xml <ApplicationPath>/storage/emulated/0/LaunchBox/Games/Arcade/shinobi1.zip</ApplicationPath>
  6. just connect you android device to a computer and access this path /Main Storage/LaunchBox/Data/Platforms here you can view the xml file at see what is going on it should be said the way lauchbox fetches file names something is really wrong. as the file names from this list not always match the file system.
  7. I think it has been fixed in 13-7 Beta 5. it is the first time i see it work now.
  8. This still giving me problems. but could see everything works fine in Bigbox
  9. I just tried but didn't fix anything for me.
  10. Maybe you first need an account. when i just tested the link it worked fine
  11. It did a bug report here https://bitbucket.org/jasondavidcarr/launchbox/issues/7747/rotating-freeze-in-new-3d-cover-display-in Computer specs Nvidia RTX 4090 Intel 13900KF Ultrawide Alienware Oled 1440P*175hz G-sync ultimate 32GB / 5600mhz memory Software Windows 11 Enterprise Launchbox 13.3 Nvidia Driver 531.79 Winver 10.0.22000.1817
  12. Tried a lot, just upgraded to a RTX 4090 and 13900K still cannot get a smooth rotation of the 3D covers. i did see a difference when using the controller instead for rotating.
  13. Yes that was one of the first things i did. As i expected my large library or updates could have broken the installation. when using a 3090+13900 it should be possible to at least do a rotation from the small detail window but can see there is a difference when using mouse or controller the FPS is a lot higher when using mouse, so maybe it cause my unlocked fps or it reloads the pictures when rotating instead of loading to memory
  14. its inside the options where you choose the detail page what should be shown. there is a static 3D cover and the rotating that get generated, at this moment this feature is a part of the beta testing
  15. Tried to do a fresh installation, and only load a few covers. but still see the same issue
×
×
  • Create New...