Jump to content
LaunchBox Community Forums

Hamburglin

Members
  • Posts

    181
  • Joined

  • Last visited

Posts posted by Hamburglin

  1. 21 minutes ago, Headrush69 said:

    Lost World uses both analog_gun and gun and there is a difference between how they work. I would stick to 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.

    First of all, thank you for trying to help me.

    The calibration just made it worse. I pointed the red crosshair at the squares perfectly, and now the game's crosshair is way off to the side somewhere when my red crosshair is in the middle of the screen. And of course the initial problem remains: when I look down the sights of the gun, it doesn't align with the red crosshair OR the newly tuned in-game crosshair. Every step is offset.

    My gun4ir aspect ratio is set to content/133. This works perfectly in mame and sm2 with demulshooter. I also turned fullscreen off in supermodel3 ini to ensure that it's 4:3 aspect ratio and at 1024x768 resolution.

    As for the gun vs analog_gun, I don't understand. Gun does not work at all when in rawinput mode. Only analog_gun settings do anything.

    This does nothing at all: InputGunX = MOUSE4_XAXIS

    This works: InputAnalogGunX = MOUSE4_XAXIS

    Here is my gun configs. Again, InputGuns do NOTHING. The moment I remove InputAnalogGun stuff in rawinput mode, the guns cease to function. They don't control the crosshairs and don't react in gun tuning:

    ; Light guns (Lost World)
    InputGunLeft = "KEY_LEFT"               ; digital, move gun left
    InputGunRight = "KEY_RIGHT"             ; digital, move gun right
    InputGunUp = "KEY_UP"                   ; digital, move gun up
    InputGunDown = "KEY_DOWN"               ; digital, move gun down
    InputGunX = "MOUSE4_XAXIS,JOY2_XAXIS"    ; analog, full X axis
    InputGunY = "MOUSE4_YAXIS,JOY2_YAXIS"    ; analog, full Y axis
    InputTrigger = "KEY_A,JOY2_BUTTON1,MOUSE4_LEFT_BUTTON"
    InputOffscreen = "KEY_S,JOY2_BUTTON2,MOUSE4_RIGHT_BUTTON"    ; point off-screen
    InputAutoTrigger = 1                    ; automatic reload when off-screen
    InputGunLeft2 = "NONE"
    InputGunRight2 = "NONE"
    InputGunUp2 = "NONE"
    InputGunDown2 = "NONE"
    InputGunX2 = "KEY_T,MOUSE3_XAXIS,JOY3_XAXIS"    ; analog, full X axis
    InputGunY2 = "MOUSE3_YAXIS,JOY3_YAXIS"    ; analog, full Y axis
    InputTrigger2 = "JOY3_BUTTON1,MOUSE3_LEFT_BUTTON"
    InputOffscreen2 = "JOY3_BUTTON2,MOUSE3_RIGHT_BUTTON"    ; point off-screen
    InputAutoTrigger2 = 1
    
    ; Analog guns (Ocean Hunter, LA Machineguns)
    InputAnalogGunLeft = "KEY_LEFT"               ; digital, move gun left
    InputAnalogGunRight = "KEY_RIGHT"             ; digital, move gun right
    InputAnalogGunUp = "KEY_UP"                   ; digital, move gun up
    InputAnalogGunDown = "KEY_DOWN"               ; digital, move gun down
    InputAnalogGunX = "MOUSE4_XAXIS,JOY1_XAXIS"    ; analog, full X axis
    InputAnalogGunY = "MOUSE4_YAXIS,JOY1_YAXIS"    ; analog, full Y axis
    InputAnalogTriggerLeft = "KEY_A,JOY1_BUTTON1,MOUSE4_LEFT_BUTTON"
    InputAnalogTriggerRight = "KEY_S,JOY1_BUTTON2,MOUSE4_RIGHT_BUTTON"
    InputAnalogGunLeft2 = "NONE"
    InputAnalogGunRight2 = "NONE"
    InputAnalogGunUp2 = "NONE"
    InputAnalogGunDown2 = "NONE"
    InputAnalogGunX2 = "MOUSE3_XAXIS,JOY1_XAXIS"    ; analog, full X axis
    InputAnalogGunY2 = "MOUSE3_YAXIS,JOY1_YAXIS"    ; analog, full Y axis
    InputAnalogTriggerLeft2 = "KEY_A,JOY1_BUTTON1,MOUSE3_LEFT_BUTTON"
    InputAnalogTriggerRight2 = "KEY_S,JOY1_BUTTON2,MOUSE3_RIGHT_BUTTON"

    Gun3 and 4 are my gunri4 guns.

  2. Now the problems are:

    • When I aim at the center of the screen, the red cursor is far down to the bottom right. The red cursor + in game cursor are perfectly aligned. The X and Y control is just WAY off
    • My damn gamepads won't register ANYTHING when trying to configure their controls with raw input mode. I have no way to add coins or hit start now

    Damn, this is really frustrating.

  3. This is my supermodel 3 controls config for lost world controls:

    ; Light guns (Lost World)
    InputGunLeft = "KEY_LEFT"               ; digital, move gun left
    InputGunRight = "KEY_RIGHT"             ; digital, move gun right
    InputGunUp = "KEY_UP"                   ; digital, move gun up
    InputGunDown = "KEY_DOWN"               ; digital, move gun down
    InputGunX = "MOUSE3_XAXIS,JOY2_XAXIS"    ; analog, full X axis
    InputGunY = "MOUSE3_YAXIS,JOY2_YAXIS"    ; analog, full Y axis
    InputTrigger = "KEY_A,JOY2_BUTTON1,MOUSE3_LEFT_BUTTON"
    InputOffscreen = "KEY_S,JOY2_BUTTON2,MOUSE3_RIGHT_BUTTON"    ; point off-screen
    InputAutoTrigger = 1                    ; automatic reload when off-screen
    InputGunLeft2 = "NONE"
    InputGunRight2 = "NONE"
    InputGunUp2 = "NONE"
    InputGunDown2 = "NONE"
    InputGunX2 = "MOUSE4_XAXIS,JOY3_XAXIS"    ; analog, full X axis
    InputGunY2 = "MOUSE4_YAXIS,JOY3_YAXIS"    ; analog, full Y axis
    InputTrigger2 = "JOY3_BUTTON1,MOUSE4_LEFT_BUTTON"
    InputOffscreen2 = "JOY3_BUTTON2,MOUSE4_RIGHT_BUTTON"    ; point off-screen
    InputAutoTrigger2 = 1
    
    ...
    
    InputSystem =rawinput

    I'm also launching the game like this:

    Supermodel.exe -input-system=rawinput "...\lostwsga.zip"

    ...................

    My god. The issue was that lost world uses controls for for "; Analog guns (Ocean Hunter, LA Machineguns)" too. You need to set the analog guns there. WTF!!

  4. I honestly can't even remember how I got the bezels but I thought it was through the media download in launchbox. What doesn't make sense to me is why deleting and reinstalling retroarch would make those bezels disappear.

    Anyone know how I get the bezels back? For some reason LB has been stuck on clearing image cache for like 15 minutes after I tried downloading the bezels per the video out there. Is it stuck?

  5. Ok, I found one way to trigger the fps tug of war.

    1. Alt tab to any window besides LB to get the frame rate back up to the intended 119hz

    2. Go back into LB. It should still be at 119hz

    3. Click tools -> manage -> emulators to bring up a menu window. 

    4. OR, just launch big box and it happens immediately.

    Boom, fps is all over the place. It sometimes triggers JUST by clicking on the tools drop down menu and letting it sit there for a second.

  6. Ok, sounds like I'll need to flip through a few settings.

    I did just figure out what's causing the flickering (when it does occur).

    Something is fighting for the refresh rate in BB to be 61hz whereas the tv is trying to use 119hz:https://gfycat.com/badterrificant

    I flipped freesync off and on it got rid of the flickering. Im going to check if its a BB thing only or all around: https://ibb.co/KKk9Y2t

    Edit: only keeping premium free sync on and turning vrr + gsync off, I don't see the framerste fought over (and therefore flickering) anymore. For now...

    Strange how that only showed up in BB but maybe it's another WPF app thing.

    Edit 2: Nope, the 61 vs 119 fps fight continues on and ONLY when LB or BB are the focus window.

  7. 11 minutes ago, C-Beats said:

    Yeah, np. I get where you're coming from. Out of curiosity what card are you using, and does your system have an integrated card, a dedicated one, or both? I do know that intel integrated cards have known issues with WPF applications, so curious if something similar may be occurring on your machine.

    It's a weird one. It's an amd Vega laptop style gpu that comes physically attached onto a NUC Hades Canyon board from around 2018.

    Intel is in charge of the drivers now (even though it's red amd styled) and I think they used this relationship to start their own gpu business.

    My tv is a 77" LG C2 ran in 2560×1440 @ 120hz in its new fancy game mode with amd free sync premium (vrr) enabled.

  8. Just now, C-Beats said:

    LaunchBox doesn't have any custom code to handle rendering, it's all done by the WPF framework which is just using Direct X to do everything. A lot of what you're talking about is far too low level for the application to have any idea about it, let alone change behavior because of it.

    That's all fine and dandy. Not placing blame, just letting you guys know that ONLY big box had an issue after a driver update. Nothing else did, including retroarch, srand alone emulators, windows gui and pc games.

    I also getting flickering in big box's UI sometimes as well. The entire screen where it's black flickers really obviously a couple times a second and its a random rhythm. Not sure if it's a vudeo driver setting, resolution or framerate thing and I haven't tried to figure it out. Again, everything else works fine.

  9. 2 minutes ago, C-Beats said:

    I'd vet if you TV has a "game mode" in it that helps with response times. If the same program works on one TV but not the other it has to be because of the device of the OS settings for that device. The way LB works it really doesn't pay any attention to the monitor it's on other then to determine scaling values.

    Well, it works now on game mode with amd variable refresh rare at 120hz. It just took plugging it into another tv first.

    I imagine something changed between driver version and LB did not catch it or was defaulting to some weird mode since everything else worked fine.

  10. 2 minutes ago, moudrost said:

    Sorry I missed the fact you said this was in Big Box. So can I assume everything is fine when you play your games? This really sounds like a refresh rate issue. What does your graphics driver report when you check? When I had this issue, it was slow in Big Box and every emulator I tried. Everything showed 30 Hz

    image.thumb.png.f3d0f7559e84135af60005bfec042060.png

    Ok yeah I checked my refresh rate and resolutions and stuff already and they are correct (60hz or 120hz)

×
×
  • Create New...