Jump to content
LaunchBox Community Forums

EvoluZion3

Members
  • Posts

    26
  • Joined

  • Last visited

EvoluZion3's Achievements

8-Bit Processor

8-Bit Processor (3/7)

3

Reputation

  1. Hopefully one for 13.13 then thanks for your suggestions, I'm sure a solution will present itself soon.
  2. This ought to be obvious but I can't find how to only move the files. Apologies, which menu option should I be using, "Change ROMs Folder Path" or "Export/Copy ROM Files"? Neither of them ask whether I want to move only. I'm on LB 13.12.
  3. Thanks for your suggestion. Only one of the ROMs had an additional app so I'm happy to proceed, however when I select all the games and click File Management, I'm a little confused because I can only either: i) "Change ROMs Folder Path" which won't move the files, only repoint them to a new folder where they won't exist, or ii) "Export/Copy ROM Files to New Folder" which will create a copy of all the "genuine" ROMs in the new folder, leaving me to manually identify the extra ones in the existing directory amongst the originals. I suppose I could use a folder comparison tool to do this. Or option iii) would be to Export/Copy to a new folder, then Change ROMs Folder Path, then delete all files in the original folder, then Export/Copy back to the original folder, then Change ROMs Folder Path back to the original folder. This should fix it but seems a long way around (plus I won't be able to identify the rogue ROMs and have a look into why they won't import in the first place).
  4. This sounds quite obvious but is there a way to achieve the above? e.g. if I have 100 files in a Game folder for a platform, but when I import them all I only get 95, how can I identify and/or remove the rogue 5? Performing a "Scan for Removed..." doesn't work because the 95 identified games are still there. The rogue 5 aren't "disk 2" or non-game files. All 100 should import so I'm interested to see which/why the rogue 5 exist.
  5. @deuxcolors I don't have a walkthrough but I can put a bit more detail here. This is what I do personally for my LB system: i) Take a backup copy of your retroarch.cfg file, then open the original one and make sure: config_save_on_exit = "false". I don't think I made any other changes to this. This means that when you exit RA after playing around, no changes you made via the UI will be saved (unless you manually Save it). I did this because my work-around for getting per-platform overlays and shaders involves temporarily appending specific extra lines to the RA config. ii) In LB, go to Tools > Manage > Emulators... > RetroArch > Associated Platforms. For the platform you want to get set up, make sure the Extra Command-Line Parameters looks like this (here's my Atari 2600 line): -f --appendconfig "overlays\Atari 2600.cfg" --set-shader "Atari 2600.slangp" iii) In the RetroArch\overlays folder, I have created one config file per platform (regardless of core). For example, my Atari 2600.cfg looks like this: aspect_ratio_index = "23" video_scale_integer = "false" custom_viewport_height = "1150" custom_viewport_width = "1360" custom_viewport_x = "420" custom_viewport_y = "100" input_overlay = ":\overlays\_MR.RETROLUST\Bezel_Atari_2600_Night_Mr_RetroLust.cfg" input_overlay_enable = "true" video_windowed_fullscreen = "true" For each of the config files I have, one per platform, most of the above is identical. The only difference is the input_overlay, which points to the appropriately-named config file in the _MR.RETROLUST subfolder (I didn't change anything in this folder), and the custom viewport X, Y, Width and Height. (for info, this _MR.RETROLUST folder I think is just what was downloaded from here and has just the overlay PNG images, and some other config files - one per platform). Unfortunately getting the X/Y/W/H correct was trial and error (running a game, then adjusting the co-ords, then rerunning again, until the emulated game screen appeared correctly within the Overlay's TV screen image) "right a bit, up a bit, left a bit, a bit wider, a bit shorter, right a bit more, etc.". I'm sure these would have been set up correctly by the big man himself but for some reason they were incorrect (I maybe did something wrong) so for each system I had to go through this. Actually it would only take about 2-3 minutes to get each one correct and was kind of fun. iv) In the RetroArch\shaders folder, I have also created one config file per platform (regardless of core). They are all .slangp files, and each one simply points to an existing RA preset which I liked for the platform. For example, my Atari 2600.slangp looks like this: #reference "shaders_slang\crt\newpixie-crt.slangp" ...whereas my Nintendo GameCube.slangp looks like this: #reference "shaders_slang\crt\crt-frutbunn.slangp" The top few lines of my Associated Platforms therefore looks like this: That's all I did, from what I can remember, and it works perfectly. If there's anything I've forgotten then it'll be in the retroarch.cfg file. In case it helps, here are the video lines in my retroarch.cfg: video_adaptive_vsync = "false" video_allow_rotate = "true" video_aspect_ratio = "1.333300" video_aspect_ratio_auto = "false" video_autoswitch_pal_threshold = "54.500000" video_autoswitch_refresh_rate = "0" video_black_frame_insertion = "0" video_context_driver = "" video_crop_overscan = "true" video_ctx_scaling = "false" video_disable_composition = "false" video_driver = "vulkan" video_filter = "" video_filter_dir = ":\filters\video" video_font_enable = "false" video_font_path = "" video_font_size = "32.000000" video_force_aspect = "true" video_force_srgb_disable = "false" video_frame_delay = "0" video_frame_delay_auto = "false" video_fullscreen = "false" video_fullscreen_x = "0" video_fullscreen_y = "0" video_gpu_record = "false" video_gpu_screenshot = "true" video_hard_sync = "false" video_hard_sync_frames = "0" video_hdr_display_contrast = "5.000000" video_hdr_enable = "false" video_hdr_expand_gamut = "true" video_hdr_max_nits = "1000.000000" video_hdr_paper_white_nits = "200.000000" video_layout_directory = ":\layouts" video_layout_enable = "true" video_layout_path = "" video_layout_selected_view = "0" video_max_frame_latency = "1" video_max_swapchain_images = "3" video_message_color = "ffff00" video_message_pos_x = "0.050000" video_message_pos_y = "0.050000" video_monitor_index = "0" video_msg_bgcolor_blue = "0" video_msg_bgcolor_enable = "false" video_msg_bgcolor_green = "0" video_msg_bgcolor_opacity = "1.000000" video_msg_bgcolor_red = "0" video_notch_write_over_enable = "false" video_post_filter_record = "false" video_record_config = "" video_record_quality = "2" video_record_scale_factor = "1" video_record_threads = "2" video_refresh_rate = "0.000000" video_rotation = "0" video_scale = "3" video_scale_integer = "false" video_scale_integer_overscale = "false" video_shader_delay = "0" video_shader_dir = ":\shaders" video_shader_enable = "true" video_shader_preset_save_reference_enable = "true" video_shader_remember_last_dir = "true" video_shader_watch_files = "false" video_shared_context = "false" video_smooth = "false" video_stream_config = "" video_stream_quality = "11" video_stream_scale_factor = "1" video_stream_url = "" video_swap_interval = "1" video_threaded = "false" video_vsync = "true" video_waitable_swapchains = "true" video_window_auto_height_max = "1080" video_window_auto_width_max = "1920" video_window_custom_size_enable = "false" video_window_opacity = "100" video_window_save_positions = "false" video_window_show_decorations = "true" video_windowed_fullscreen = "true" video_windowed_position_height = "720" video_windowed_position_width = "1280" video_windowed_position_x = "0" video_windowed_position_y = "0"
  6. Brilliant, thanks Retro_Rage that sounds like a plan. I'll wait for 0.262 to come out and experiment with it then
  7. My "Arcade" platform is a MAME full set but I chose only to have arcade games. I'd like to have a separate Platform called "Arcade - Other" or whatever which has just the slot games, card games, etc. and no arcade games. I suspect the best/easiest way to do this is via a Playlist or two, but I wondered if I could do this via Platforms instead. I guess I could possibly run another Import > MAME Full Set, call it "Arcade - Other", point it to the same ROM folder as the arcade games, run a full import (including all game types), then find a way to selectively remove the arcade games from the "Platforms/Arcade - Other.xml", possibly by searching for the <Genre> tags?
  8. hmm ok thanks it looks like it may be best to keep things simple and leave RA to read the .opt file. Thanks Headrush
  9. ah thanks Headrush, that's created an .opt file just for the game which now has the different setting I needed! I wonder just for completeness is it possible to pass the filename of this .opt file from LB to RA, just to "formalise" it (I much prefer LB to run the show and spoon-feed RA what it needs to do, rather than letting RA recognise the incoming game filename and look for the .opt file itself). Even better would be if LB could override the specific parameter atari800_system = "400/800 (OS B)" just for this game but I doubt you can pass this low level of override to RA.
  10. Thanks JoeViking, that's very useful to read. I think what might make this more difficult is it's the same core "Atari - 5200 (Atari800)" but two different options I want (the core lets you choose between different "Atari Systems" such as 400/800, 800XL, 130XE, etc.) so I want some games to use one option and some to use another, unless you were suggesting having two copies of the same core, but one core set to one option (400/800) and the other core set to the the other option (800XL)?
  11. Some of the games in my Atari 800 collection need the 400/800 system, some require the 800XL system. I can swap from one to the other manually using the RetroArch Core Options but I wondered if there was a way of passing/overriding this setting from LB to RA.
  12. Ach yes that makes sense. Quickly scrolling through all the default 3D Box images it doesn't look like much if anything has been affected, although for example EmuMovies has confused the two "Mystery" games and downloaded the same video clip for them both (one's a Mario-like game and one's a gem puzzle game) although the two LaunchBox IDs are different and correct, but I guess EM would have done this anyway as I believe it doesn't recognise LB IDs.
  13. I'm sure you'll not be too annoyed if I post up and join the dozens of people who have said WOW, THANK YOU for such an unimaginable effort to curate and develop the C64 Dreams project. I've browsed through all 43 pages of this thread and the attention to detail and care you put into so many aspects of this project is astounding. And the unwavering support you give in problem solving, advice, and taking suggestions on board really is quite remarkable. I've downloaded the project and with a little shoe-horning have managed to incorporate it into my existing LB without too much trouble. Admittedly I'm not interested in the non-game aspects of the project, so the magazines etc didn't make it across and so I flattened out the Parent structure so "Commodore 64" appears normally as a platform in my list. Once it was up and running, a simple refresh media and the EmuMovies video clips and other media came straight down, where they were available. C64 also looks good in BigBox! So thanks once again and keep up the fantastic work and enthusiasm!!
  14. I've added a few MS-DOS games and love the box images, however some of the games have a rotatable 3D box, but not an individual 3D Box image (for the "3D Boxes" image group). Long shot but is it at all possible to create a single 3D Box image from the rotatable 3D box? And in bulk?! Most of the rotatable 3D Box images look perfect for the "3D Boxes" image group!
  15. I'm sure there'll be differing opinions on this and definitely no right/wrong answer but my personal preference is for RetroArch to be vanilla and kind of a slave to LaunchBox. So for me, RetroArch has no preferences set at all other than the style of the menu (PS2) and almost all options set to the defaults, and the CLI from LB to RA dictates the shader to use, and the overlay (the RetroLust overlay) to use. This way I can set the overlay to use on a platform-by-platform basis (not a core-by-core basis). But each to their own for sure. Definitely take a copy of your retroarch.cfg file (if it's not already too late), as when I was messing about trying to get the overlays to work I mucked up my cfg file and had to recover it from a backup.
×
×
  • Create New...