Jump to content
LaunchBox Community Forums

silvusvalentine

Members
  • Content Count

    15
  • Joined

  • Last visited

Community Reputation

13 Good

About silvusvalentine

  • Rank
    8-Bit Processor

Recent Profile Visitors

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

  1. You may have to request a code for the Cabinet Support feature, which allows the game to accept command line parameters. There's a button on the main menu that will launch a web page where you enter your information, and I've also linked to it in the original tutorial. Someone from Zen Studios should then contact you, and they may ask you to send them a picture of your setup. They just want to verify that your setup isn't for public use. Once you enter the code, you should be able to launch straight into the game you choose from within LaunchBox.
  2. Previous versions: This version:
  3. @Helveticus I had the same message about the Steam Client not running. I made a guide on how to get it working here:
  4. Description: Tables for Pinball FX2 on Steam are treated similarly to DLC for other games. Therefore, the tables do not have their own launchers in Steam, and are chosen after starting up the main game. However, the following will describe how you can enter each Pinball FX2 table as an individual game in LaunchBox. Note: You may need to get a code from Zen Studios to enable command line support with Pinball FX2. There is a link within the game that will send you to the appropriate form, or you can go to it directly, here: https://blog.zenstudios.com/?page_id=5981 I don't know if this step is necessary, as I had already received a code before I imported the tables to LaunchBox. So check there first if the command line arguments aren't working. Steps: Optional: Navigate to Tools -> Manage Platforms from the LaunchBox menu bar and click the + Add... button to add a new platform. Optional: Enter the following metadata: Title: Pinball FX2 Release Date: 05/10/2013 Developer: Zen Studios Category: Pinball or Arcade Images: (See Image 1 for Clear Logo) Optional: Click the ✔ Ok button and you now have a platform for your Pinball FX2 tables. Note: The previous steps may not be necessary, depending on how you organize your platforms. The Pinball FX2 tables can be added to the platform of your choice — this is just the setup that worked well for me. Navigate to Game -> Add from the LaunchBox menu bar, or press Ctrl+N. Enter any necessary metadata in the Details section (Image 2). Since these titles do not exist as separate games, they are not currently in the LaunchBox Games DB, so I'm unaware of an easy way to scrape metadata at the moment. Beneath the Details section, within the Launcher tab, click the Browse... button next to the Application Path textbox. Note: If you see ROM File (Emulation is enabled) instead of Application Path, you will need to navigate to the Emulation tab, and uncheck Use an emulator to play this game. Navigate to your Steam install folder, select the file named Steam.exe, and click the Open button. The Application Path setting should now be set to something like: ..\Steam\Steam.exe Next, in the Application Command-Line Parameters textbox, enter the following text: -applaunch 226980 "TableName.pxp" Replace TableName in the sample text above with the name of the table you are adding (See below for the list of table names and command line parameters). This parameter will tell Steam to launch the app with the id of 226980, which happens to be Pinball FX2, and it will pass the name of the table we want to run to Pinball FX2. Click the ✔ Ok button and you should now see the game added to your selected platform. Note: Since we are passing the name of the table file to Pinball FX2 through the command line, and not the table file itself, we cannot use the usual Tools -> Import -> ROM Files... method. Images: Pinball FX2 Platform Clear Logo: Adding a Pinball FX2 Table: Table Names and Command-Line Parameters: Note: The names of the tables can be found by navigating to your Pinball FX2 directory within your Steam directory. It will be at the following location: Steam -> SteamApps -> common -> Pinball FX2 -> data_steam Ignore any of the files that are in lower case (game_cfg.pxp, gui.pxp, etc.), as well as the PTSData.dat file, as these are not table files.
  5. You can accomplish this by creating a style for background element. Let's say your background is a Grid component. In the view's XAML file, paste the following Resource Dictionary just below the UserControl tag: <UserControl.Resources> <Style x:Key="DynamicBackground" TargetType="{x:Type Grid}"> <Style.Triggers> <DataTrigger Binding="{Binding Path=SelectedPlatform.Name}" Value="Arcade"> <Setter Property="Background" Value="Blue" /> </DataTrigger> <DataTrigger Binding="{Binding Path=SelectedPlatform.Name}" Value="Nintendo 64"> <Setter Property="Background" Value="Red" /> </DataTrigger> <DataTrigger Binding="{Binding Path=SelectedPlatform.Name}" Value="Nintendo Entertainment System"> <Setter Property="Background" Value="Green" /> </DataTrigger> </Style.Triggers> </Style> </UserControl.Resources> So here's the breakdown. The Style is defined with a Key, which is basically the name that identifies the style. In this case, I've named the style DynamicBackground. Since the background will be a Grid component, I've set the TargetType to Grid. In order to vary the background color based on the platform, the color is set by using Triggers. This works by defining a condition, and if the condition is true, the value is set based on that condition. In this case, we want the color of the Grid's background to change depending on the platform, so the Trigger is the value of the selected platform. Therefore, in the DataTrigger tag, we set the Binding property to SelectedPlatform.Name, and the Value that will trigger this color is the name of the platform, for example, Arcade. When the trigger is activated, we want it to set the background color; so, inside the DataTrigger, a Setter is defined, along with the Property that we want to set and the appropriate Value. In the case of the Arcade platform, we want the Background Property of the Grid component to be set to the color Blue. This process can be repeated for as many platforms as you would like, just define a DataTrigger for each of them. To implement it, you just have to apply the Style to the Grid component, like so: <Grid Style="{StaticResource DynamicBackground}"> Since the style is defined in a Resource Dictionary, it is accessible as a StaticResource with the name DynamicBackground, in this case. Here's an example of it in action: I hope that helps!
  6. It is just for showing stars. When I said Star Rating control, I meant control as in element or component.
  7. Okay, I think I've come up with something for the Star Rating control. It's probably the worst way to handle this, but the only way I could think to accomplish it without code behind. In the view that you want to feature the Star Rating control, paste the following UserControl.Resources code at the top, so it's the first element inside the UserControl tag. Here's an example of the UserControl tag, it should be the top-most element of every view: Paste the following UserControl.Resources code: Now, wherever you want to add a Star Rating control, just use the following code: Customizing If you want to change the size of the stars, just adjust the Height property of the ContentControl. Since the stars are Path elements, you can make them as large or small as you want and you don't have to worry about pixelation. If you want to adjust the spacing between the stars, adjust the Margin property. If you want to change the star's fill color, empty color, or stroke color, that can be found at the top of the UserControl.Resources code: It's not the best solution, but it should work for now. Maybe I can try to implement it as a custom control. Hope that helps for now!
  8. If you wanted to implement the blur effect programmatically, you can add an effect to the image in the XAML. <Image Source="{Binding ImagePath}" HorizontalAlignment="Stretch" VerticalAlignment="Stretch" Stretch="UniformToFill" RenderOptions.BitmapScalingMode="HighQuality"> <Image.Effect> <BlurEffect Radius="30"></BlurEffect> </Image.Effect> </Image> Just adjust the Radius property to adjust the amount of blur. It will most likely slow down performance, but it will work for every image without having to blur them manually.
  9. I'm only just figuring out how to get shaders to work in Retroarch. I wouldn't know where to start in standalone Mame. Are there any tutorials on here that show how to set them up?
  10. I had been doing the same. I just happened to find them while I was exploring the options lol.
  11. Retroarch Version: 1.3.6 Mame Core: MAME 0.174 (The core labeled Arcade (MAME) in the Core Updater) Steps: Open Retroarch and pull up the Main Menu (Press F1 if you are in-game). Load the Mame Core if it is not already loaded (check the bottom left of the screen for the currently loaded core). Navigate to Main Menu -> Quick Menu -> Options. In the Options menu, turn ON the following options (Image 1): Hide nag screen Hide gameinfo screen Hide warnings screen Navigate back to the Main Menu and select Save Current Config. Now, when you play an Arcade game with Retroarch, it will begin loading the rom immediately. Note: The nag screens, warning screens, and info screens are the screens that display before the rom is actually loaded (Image 2). These screens usually require a button press before the process is allowed to continue. These settings will not remove the arcade startup screens, display test screens, RAM check screens, hard disk load screens, etc. Images: Settings to change: Nag screen and gameinfo screen example:
  12. For what it's worth, I think the two should be separate. The games can be played on either system, but you would have to either modify the SNES cartridges to fit inside the Super Famicom, or you would have to modify the SNES to allow the Super Famicom cartridges to fit inside the SNES. If you want to draw a parallel, many games can be played across GameBoy, GameBoy Color, GameBoy Advance, and the GameCube GameBoy Player. Here's the compatibility chart. In addition, there were some Super Famicom games that were never released for the SNES. In some cases, the games were released under different titles. For example, Final Fantasy III for SNES was actually Final Fantasy VI for the Super Famicom. In terms of artwork, the boxes were a completely different shape, so the artwork doesn't match from one system to the other, without creating custom artwork. So it makes more sense to me for the two to remain separate, but that's just my opinion.
×
×
  • Create New...