Jump to content
LaunchBox Community Forums

Headrush69

Members
  • Posts

    1,344
  • Joined

  • Last visited

Everything posted by Headrush69

  1. That's the route I went. Some games you just need proper analog. I use my cabinet for console emulation as well, so a couple of wireless XBOX 360s that hang on 3D printed mounts on the front. Simple, clean, unobtrusive and there when needed.
  2. You are correct that the iPac is an issue, but also the joystick itself. The Sanwa JLF is a digital joystick that uses micro switches so, they report either on or off. For true analog support you need that type of joystick (Xbox/PS2 controllers, flight stick, Ultimarc 360, etc) You can play with the increment/decrement speed settings in the MAME in game menu (they are for digital inputs), and you MIGHT be able to improve things, but sometimes you just need an analog joystick for best experience in some games.
  3. You can use the Additional Apps or a running hotkey to send commands to your Gun4IR to switch reload methods needed as per game. Her is an example of a running script to turn reload off: (COM port 5 & 6 are my Gun4IRs) The first commands turns reload off, while the command in the exit key sets them back to reload button mode.
  4. Shot in the dark: do you use Game start up screens and do you have aggressive hiding of windows on?
  5. In playing around with the Retroarch MAME core I was having focus issues but completely differently. In testing I found that other cores had the issue as well but I never noticed it. It was clearly related to Startup screens and clicking the mouse when in game would switch to the startup screen. Sometimes if would time out and return to the game, other times I had to force it. It had nothing to do with Retroarch's focus controls either. I noticed the issues was on cores were I had the aggressive window hiding turned on. If you have that on maybe try turning it off. Most times this isn't needed.
  6. Sure. Are you running MAME stand alone or the MAME core in Retroarch? In MAME you can hit TAB to bring up menu, go to video options and enable/disable per game bezels. In Retroarch, in the Quick menu you can go to Overlays and enable or disable per game bezels and than save a game specific override.
  7. Your wait will be over soon. BigPEmu is getting CD support. I'm currently running a recent Patreon release and CD support is working well.
  8. Almost always these issues are MAME can't find the roms it needs. In your mame.ini is the the rom path set to where your MAME roms are? Although you can pass MAME an absolute path to a rom and it may work for some games, if the game requires auxiliary roms (BIOS, device, etc) , without the rom path set it won't know how to find them.
  9. I think we are saying the same thing but in different ways. Those emulators are expecting the gun co-ordinates in the ratio matching your display ratio. even when the actual game is only outputting 4:3. By forcing Content aspect ratio on, you are introducing those offset problems. There is no way around the fact you have to switch. I find it's easier to stay in Full and switch to Content when needed, but to each his own. I'm assuming you are using Demulshooter with SM2? I ask because I run at 4:3 and after in game calibration it works in Full screen aspect. (no need to switch)
  10. Ah. So you just don't want the crosshairs to go into the black borders or bezel area, even if it doesn't affect the game? I leave mine in Fullscreen mode and only change when needed. Not sure if it possible to restrict to Content aspect ratio when specific emulators are expecting full screen co-ordinates and adjusting themselves. I'll leave that to you to figure out. ☺️ You can set the COM ports to specific values in Device Manager. Even when the USB order may change, the COM port likely won't if set this way. My Gun4IRs COM ports are set to COM5 and COM6 and have not changed ever. (>1 year) I use a running script like this for MAME to switch to Content Aspect ratio and back to Fullscreen aspect ratio after the game is done:
  11. Those will cause issues for sure. This will need to be set on a per emulator basis. Some will require a switch to Content Aspect Ratio, others don't. You can do it with the Gun4IR app (remember to upload to gun), or using a designated button on your gun, or using a tool like SendSerial.exe to send the command to the gun to switch modes or a running script in LB. (This is easy using LB's Additional Applications to run before game and after to reset mode.) I'm confused by what you mean here. Which emulators? It works with Full Screen Aspect ratio, but you actually stretching the image to 4:3? The display size isn't necessarily what determines whether you need Content Aspect or not, it's based on specific emulators. For example MAME restrictions the mouse to the 4:3 aspect ratio so Content Aspect ratio is needed, where as Flycast standalone doesn't. Even though it's displaying in 4:3 aspect ratio (widescreen cheats off), it works perfectly fine left in Fullscreen Aspect ratio. Of course any in game calibration needs to be done once the correct aspect ratio is set. Hope that helps.
  12. Went back to my notes and double checked and I had some parts backwards. In the process of checking for you I screwed up my settings, but the good news is starting fresh I was able to configure both guns again in both gun and analog_gun mode. It's too late for me to go into details, but a few tips: Doesn't matter whether you use analog_gun or gun in Games.xml, but there are differences. (not in configuration. I would go with analog_gun as that removes the onscreen flash needed for original CRT guns) You don't need a separate Supermodel Lightgun emulator. You can have per game settings in Supermodel.ini. Just add a section and rawinput will just be used for that game. Start with a fresh configuration and delete lostwsga.nv in the Supermodel NVRAM folder and lostwsga.st* files in Saves folder. Start the game from a command prompt and follow the instructions for configuring. Once the game starts, enter the in game service menu and calibrate the guns. Do not worry about the crosshair alignment in here., it can be wrong until all 5 points for each gun are done. Generally WIndows has been stable with my mouse device ordering (They are always attached), but on the rare occasion that they stop working in game it usually means Windows changed the index and I need to adjust the index in Supermodel.ini. Here is what my lostwsga section looks like in Supermodel.ini
  13. When doing the in game calibration you do NOT use the crosshairs to aim. You have to use the sights on the gun to aim at the squares and once complete aim should be better and the crosshairs should follow the sights now. (Assuming no other issues like screen ratio setting) Which probably means your Games.xml file has the wrong settings. You need an entry like the following to use light gun mode and not analog gun mode: Edit: Some additional info: difference between gun and analog_gun
  14. Lost World uses both analog_gun and gun and there is a difference between how they work. I would stick to analog_gun, Have you switched to 4:3 mode in Gun4IR software or using your set hot key? You haven't said whether you did in game calibration. It matters, whether the crosshairs move initially or not.
  15. What do you mean when you say it's not registering? (You said using -config-input it was recognized) My Gun4IR guns didn't work until in game calibration was done. (Can't remember if I had to do it with every gun game though) Symptoms were the scaling/sensitivity was way off and only one controller worked. Also specifically in Lost World, in your supermodel.ini are you using analog_gun or just gun?
  16. Did you calibrate them within the game using the service menu?
  17. This is what I currently have and no window pop up and LEDBlinky controls stay lite: The true argument tells the script to wait until the command run ends, so LEDBlinky remains lite.
  18. I'm just in the process of redoing all my Hypseus and Singe2 games, so haven't tested everything with LEDBlinky and focus issues yet, but a few questions/suggestions: You seem to create 2 Wscript.Shell objects in the first 2 lines, is that needed? Instead of calling your command BAT file can you not call hypseus directly eliminating the extra process? Something like this: FYI, I haven't fully test this yet as long as LB calls LedBlinky before starting Hypseus this should work. (If not might have to modify)
  19. Not to speak for Jason and the team, but it's likely just a tradeoff between designing and maintaining features for such a minority of users, not hate. Has the feature ever been submitted for the features poll? For a set up with a CRT, i would think that most of the time it's going to be using Big Box, and LB only used for configuration. As a work around would a running VNC server on the machine and using LB through VNC be a workable and more pleasant option?
  20. Headrush69

    Sega Naomi

    Sorry, can't be any help here. Missed you were on Android initially. Only suggestion would be load the core and then in the Retroarch check the Information section in Quick menu and verify BIOSes are correct. Maybe also set the option to bot into the system and see if it crashes loading without a game.
  21. Headrush69

    Sega Naomi

    What you need is explained in the Retroarch documentation for the Flycast core.
  22. Headrush69

    Sega Naomi

    You are probably right. What emulator are you using, and what BIOS files did you use and where did you place them? (Retrroarch->Flycast, Flycast standalone, Demul, ...)
  23. If you temporarily rename LEDBlinkyControls.xml, restart LEDBlinky and than try again does the entry reappear in Controls Editor? If you need to manually add it to your LEDBlinkyControls.xml, here is a copy of mine:
  24. Yup. Click the FE button in LEDBlinkyControlsEditor and add 8-way joystick and set it as primary.
  25. Well maybe the file was updated, but I definitely got it earlier. It's there now for you that's all that matters. The name really isn't important. (for arcade titles) It's only named that to distinguish that it is only supports the arcade games and that their separate MESS build has the other systems. Naming it the same as the MAME binary that has support for both would lead to a lot of confusion. You can just rename mamearcade64.exe to mame.exe so you don't have to change anything in LB.
×
×
  • Create New...