Jump to content
LaunchBox Community Forums

dragon57

Members
  • Posts

    1,108
  • Joined

  • Last visited

  • Days Won

    14

Posts posted by dragon57

  1. 2 hours ago, fyrenthenimar said:

    Hello,

    Could you share or make some rings for:

    Game wheels template:
        *  Neo Geo Pocket
        *  Neo Geo Pocket Color
        * Bally Astrocade

    Thanks.

    Regards.

    @fyrenthenimar, you can find those in the downloads from this link:

    Bally Astrocade is in Console archive and the two Neo Geo files are in the Handheld archive.

  2. 47 minutes ago, Jason Carr said:

    Yeah, it's a more advanced feature anyways, so hopefully people can figure it out by experimentation if they don't understand the verbiage. Setting the aspect ratio at least on a per-platform basis is planned for a future release.

    Just the result of spacing settings that make the boxes run out of room for the selection bar.

    This is normal behavior for both OG and .Next. If there's no platform selected, it will just resume using whatever the last image group was. It's been this way for a long time, though I agree that there are probably better ways to do it. For the future, I'm thinking of reverting to the default image group instead.

    @Jason Carr That was sort of my point, and I should have been more specific. OG DOES seem to save the image group for 'ALL'. I just tried changing 5 different platforms to something different and clicking on ALL after clicking on each of those in turn do not change the setting for 'ALL'.

  3. OK, this is a weird one I almost didn't catch. It appears the 'All' platform category does not save the Image Group selection. When I click on 'All', it uses the Image Group from the previous Platform.

    I hope I am explaining this well enough. This is in .Next, btw.

  4. I am getting strange behavior in .Next when I change platforms via clicking in the left side of the .Next window. When .Next brings in the images for the currently set view it will often not draw anything for certain graphics. I must hit F5 to force a refresh before everything is drawn (sometimes it takes two or three refreshes). I am waiting on the cache bar at the top to finish its operations before doing anything. I just updated to Beta 11 and nothing has changed. I also just shutdown all LaunchBox apps, cleared the .Next cache folder, then started .Next again. I continue to see the same behavior. Is any of this normal and expected behavior? The regular LaunchBox doesn't seem to have any issue in regards to this.

  5. Should be possible. This assumes you have previously created a save state for the game you are going to execute. Put the code below in the 'Autohotkey Script' section of the Edit Emulator process for PCSX2.

    #NoEnv
     Sleep, 3000
     SetKeyDelay, -1, 110
     Send {F3}
     Return

    ; This section closes PCSX2 when pressing Escape
    $Esc::
    {
        Process, Close, {{{StartupEXE}}}
    }

  6. There is no built in way to do this. If you don't mind digging in and doing some non-standard hacks, you can create a ram disk that only houses the cache directory. This isn't for the feint of heart though. It is doable, and does work. This route would be unsupported.

    Are you using the original LaunchBox, or the new LaunchBox Next? Next has a new cache mechanism that works differently than the old, but if disk speed is your main issue, I don't think Next would change your results much.

    If you would like to pursue this avenue and need any help, let me know and I can write up something for you.

  7. First, let me say I don't know when this started, and I'm not sure this is an actual problem with recent builds, or not. Having said that,  I noticed today when I audit any platform, I got an error pointing to an xml parsing problem. I finally tracked it down to one of the plugins I have installed. When I finally backed up and deleted all plugins, the error went away. I have a number of plugins installed and wondered if there was any quicker way to figure out which plugin is causing issues versus putting one at a time back in place and starting/stopping Launchbox a number of times.

    Is there a list of plugins that are known incompatible with the new build?

  8. 6 hours ago, Jason Carr said:

    This was definitely caused by images with different DPIs, as predicted. I have it fixed for the next beta.

    Edit: For clarity, if you open up the images in Photoshop, and select "Print Size" from the View menu, you'll notice that some images show as much smaller than others, due to the differing DPIs. I think this is just caused by different people's image editors or whatever. WPF takes the DPI into account when it displays the images, so I had to override it by setting the size of the image to match the pixel width of the image.

    So glad you found the fix. That is what I get for trusting baaaaad applications. :) Thank you!

  9. 51 minutes ago, Jason Carr said:

    Hmm, I'm guessing it's the format/DPI of the images, ugh. Not sure if that's gonna be an easy thing to fix or not.

    All the images are the same format (png), the same size (452x226) and created by the same app. If you want any of them for testing, let me know. There are no issues with the normal/old Launchbox.

  10. Thanks for the new beta. Clear logo backgrounds do seem to work now, however the logos here seem to show very small, vs at normal size. See the attached pic.

    Edit: I just discovered some platforms show tiny clear logos, and some do not. I have yet to identify any rhyme or reason to it.

    Clipboard02.jpg

  11. I just realized clear logos are not being displayed in Next when I click on a game image. I have double checked the background priorities choices in Options and Clear Logo is first in the list, then Fanart - Background. I have even unchecked Clear Logo, then gone back and reselected it with no change in behavior. Am I the only one who sees this?

    I have not noticed this in regular Launchbox.

    • Like 1
  12. OK, all. I have diagnosed/solved my strange scrolling issue.

    First, sorry for a false alarm. I should have known where to look after what I had been doing to this machine. I usually make a rule to not change more than one thing at a time, but I blame my medications for making my brain foggy. ?

    I ordered a Dreamcade Replay device from Kickstarter and was just informed they ship out soon. I wanted to make sure all my controllers work with Windows 10 since the Replay will come with Windows 10 as the OS. I have been testing all my controllers, calibrating them, etc. Even though the controllers were found to all work, what I have not experienced in the past was a calibration being forgotten when a controller was unplugged, then plugged back in. All the issues were caused by one controllers calibration settings being reset. What I don't understand is why it took some time in Launchbox for the issue to show up, and how a restart of Launchbox seemed to solve the problem for a bit before reappearing.

    • Like 2
  13. 22 minutes ago, Jason Carr said:

    So weird. How fast is it moving? I'm trying to rule out what could be causing it.

    Sorry, I just saw this question. It moves pretty fast. It appears to move at the same speed as if you hold the up arrow key down and let the auto-repeat kick in. One thing I noticed, if I use the up arrow key to try and replicate the behavior, the arrow key makes the active bar scroll up, then when it hits the top of the list, it jumps up to the drop-down menu above the list. The 'ghostly' behavior doesn't continue past the platform list. It stops at the 'All' entry at the top of the Platform list.

  14. 3 minutes ago, Jason Carr said:

    Also, have you tried the latest beta @dragon57? Beta 16? Just in case there was some kind of fluke in a previous beta.

    I just updated to the latest beta, 16. All controllers are currently unplugged. I'll make sure nothing amiss is evidenced before I plug any back in.

    Also, after installing beta 16, this error just popped up after changing from one platform to another via clicking in the left panel. I can't replicate so far. It has only happened once.

    Object is currently in use elsewhere.

    App:     LaunchBox
    Version: 8.3-beta-16
    Type:    System.InvalidOperationException
    Site:    IntPtr GetHdc()
    Source:  System.Drawing

       at System.Drawing.Graphics.GetHdc()
       at System.Drawing.BufferedGraphics.RenderInternal(HandleRef refTargetDC, BufferedGraphics buffer)
       at System.Drawing.BufferedGraphics.Render()
       at System.Windows.Forms.Control.WmPaint(Message& m)
       at System.Windows.Forms.Control.WndProc(Message& m)
       at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

    Recent Log:

       2:57:37 PM Music.Pause Start
       2:57:37 PM Music.Prepare Start
       2:57:37 PM Music.Kill Start
       2:57:37 PM Music.Kill Finished
       2:57:37 PM Music.NotifyTrackList Start
       2:57:37 PM Music.NotifyTrackList Invoke
       2:59:34 PM Music.Pause Start
       2:59:34 PM Music.Prepare Start
       2:59:34 PM Music.Kill Start
       2:59:34 PM Music.Kill Finished
       2:59:34 PM Music.NotifyTrackList Start
       2:59:34 PM Music.NotifyTrackList Invoke
       2:59:37 PM Music.Pause Start
       2:59:37 PM Music.Prepare Start
       2:59:37 PM Music.Kill Start
       2:59:37 PM Music.Kill Finished
       2:59:37 PM Music.NotifyTrackList Start
       2:59:37 PM Music.NotifyTrackList Invoke
       3:25:11 PM Music.Pause Start
       3:25:11 PM Music.Prepare Start
       3:25:11 PM Music.Kill Start
       3:25:11 PM Music.Kill Finished
       3:25:11 PM Music.NotifyTrackList Start
       3:25:11 PM Music.NotifyTrackList Invoke
       3:29:40 PM Music.Pause Start
       3:29:40 PM Music.Prepare Start
       3:29:40 PM Music.Kill Start
       3:29:40 PM Music.Kill Finished
       3:29:40 PM Music.NotifyTrackList Start
       3:29:40 PM Music.NotifyTrackList Invoke
       3:33:27 PM Music.Pause Start
       3:33:27 PM Music.Prepare Start
       3:33:27 PM Music.Kill Start
       3:33:27 PM Music.Kill Finished
       3:33:27 PM Music.NotifyTrackList Start
       3:33:27 PM Music.NotifyTrackList Invoke
       3:39:23 PM Music.Pause Start
       3:39:23 PM Music.Prepare Start
       3:39:23 PM Music.Kill Start
       3:39:23 PM Music.Kill Finished
       3:39:23 PM Music.NotifyTrackList Start
       3:39:23 PM Music.NotifyTrackList Invoke
       3:43:55 PM Music.Pause Start
       3:43:55 PM Music.Prepare Start
       3:43:55 PM Music.Kill Start
       3:43:55 PM Music.Kill Finished
       3:43:55 PM Music.NotifyTrackList Start
       3:43:55 PM Music.NotifyTrackList Invoke
       4:01:32 PM Exception

  15. 54 minutes ago, Jason Carr said:

    Gotcha, so somehow this is simulating the up arrow key being pressed, either inside of LaunchBox or by another application. Another thing to check would be if you have any applications running that would cause keyboard presses (like controller software).

    I have no controller apps on this machine. What is strange is when it does happen, if I alt-tab into a different app with a 'page' that could be scrolled the same way, nothing happens. If I alt-tab back into Launchbox, the scrolling starts immediately. I have to say I'm stumped at this point, however I am trying to isolate things.

×
×
  • Create New...