Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - progets

Pages: 1 2 [3] 4 5 ... 49
General / Re: Manually Add Games to Filters?
« on: October 29, 2018, 09:56:27 PM »
Is it at all possible to manually add certain games to specific filters? I'm trying to create things like shmup, fighters, classics, 4-player, and other things. Can I create a custom .ini file or something? I'd want to do this with all my consoles (mame, nes, etc) so manual would be easiest for me (albeit slightly time consuming).

Yes, you can manually add games to filters but it's probably not the best option for what you want.

You can create basic dynamic filters without needing to manually add anything in most cases.

If you want to manually create simple text files for your filtering, you'll want to use the "tagging" feature in AttractMode. With this you could create a single text file that contains all the games for a given name/type.

You should look at these links for more information and I think you'll have a better idea of all the options:

tried that and that didn't work either

      rule                 FileIsAvailable equals 1
      rule                 CloneOf not_equals .*
      rule                 Status not_equals preliminary
      rule                 Category not_contains Electromechanical|Tabletop|Casino|Quiz|Mahjong|Computer|Microcomputer|Test|Portable|Console|Handheld|Device|Training Board|Synthesiser|Clock|Document Processors|Mature
      rule                 Category not_equals Misc.|Quiz / Korean|Electromechanical / Reels|Casino / Cards|Casino / Reels
      rule                 Title not_contains bootleg|prototype
      rule                 Manufacturer not_contains bootleg
      rule                 Year not_contains ?

Went back and to the "*"'s out for Mature in the rom list and that didn't help either

I have tested this and it works for me. Like I mentioned above, get rid of all your other rules so you can test with just one rule until you get it right. Troubleshooting with all those rules makes zero sense. Once you have it working you can then implement your other rules and see where the problem comes in.

Post your attract.cfg and your mame.cfg if you want further feed back.

Like I told you in the post above.

Your global_filter has two different "Category not_contains" rules which is likely your problem.

Append the first "Category not_contains" rule with |Mature and get rid of the second "Category not_contains" rule.

General / Re: Roms into subfolders
« on: October 29, 2018, 03:49:41 PM »
I personally don't use subfolders or multi-part games, I think it's a thing of the past since there are better ways to do this today and people just haven't caught up with it yet.

Some might create two emulators and then use the AttractMode's builtin function to combine two emulators into one romlist.

Some might use RocketLauncher with AttractMode to handle these type of things.

Some might create .cue files that point to the .cdi and gdi files. You could also create .bat files for these roms too.

I'm sure there are other options too. Let's see what others have to say.

I've added the HUD 1.0.0 layout in my ~/.attract/layouts directory, and a intro.mp4 video in my ~/.attract/intro directory. I've also got to Displays->Displays Menu Options and set Menu Style/Layout to HUD 1.0.0. When I start AttractMode I don't see the video and I still have the pacman layout displayed.

I'm a total n00b when it comes to AttractMode, so I don't know what I am doing wrong.

Do these files need special permissions? Do I have to modify any settings or configuration files? Are there limitations on what the Linux version can do?

This is on Mint Linux 19.

Any help is appreciated.

1. The "Displays Menu" is a main menu of systems and not for the specific systems/emulators/displays
2. Artwork and videos for the "Displays Menu" needs to be stored in ~/.attract/menu-art/
3. No special permissions are needed as long as you installed AttractMode as the same user that is try to run it (i.e. not installed as "root" and trying to run it as "joe".
4. different layout/themes might call the artwork by different names, make sure you adjust the layout.nut file for your artwork naming convention or use the artwork naming convention provided in the default layout.nut (i.e. some people call videos "snaps" while other might call them "videos".
5. make sure you enabled the intro video to be run (Configure-->Intro-->Play Intro = Yes) and make sure your have the right settings for the other options in this menu.

There really shouldn't be any limitations when running AttractMode on Linux. They are more likely configuration issues or possibly bugs.

If these suggestions don't help you fix your issue, post your ~/.attract/attract.cfg file so we can take a look.

General / Re: Opening Display to first game in a romlist
« on: October 28, 2018, 11:03:55 PM »
Edit this file... change all numbers to 0
Save the file
Edit the permissions to read only...gonna work
For sure....

U have to make it Read only because if not it won’t go back to 0 the next time u start

Interesting idea. How did you come up with it? What do all of these numbers mean? Can you please explain the format of the file? Will setting every number to "0" or making it read only effect other parts of AttractMode?

General / Re: RetroArch works but shows a black screen
« on: October 28, 2018, 10:37:05 PM »
The Window one fixes it, but it's very undesirable because it runs windowed instead of fullscreen, I see the taskbar, and so on. Any other solution?

Yes, a lot. This all depends on YOUR setup
- Try "Window (no border)" mode in AttractMode
- Set RetroArch to use the same resolution as your OS
- Set RetroArch to use "full screen" mode
- use a different video driver in RetroArch (i.e. gl, d3d9. d3d11, d3d12, sdl2)
- make sure you have the latest directX drivers installed and working properly if you're using any of the RetroArch d3d* video drivers
- make sure you have the latest video card drivers installed for the OS (and check their setting if they use an application to change them instead of the OS tools)
- make sure that AttractMode is using the same video resolution as RetroArch
- make sure that you have the correct/latest MS Visual C++ redistributable installed for RetroArch

There are many variables in play. Only you have your exact setup to test them.

Rules are case sensitive. Your example of "not_contains mature" should be "not_contains Mature" based on the romlist entries you provided.

General / Re: RetroArch works but shows a black screen
« on: October 28, 2018, 07:41:52 PM »
Try the different AttractMode "Window Mode" options. One should fix it.

Configure-->General-->Window Mode = Full screen/Fill screen/Window/etc.

General / Re: Compiling Attract on Rasbian Stretch Lite
« on: October 28, 2018, 07:39:28 PM »
Compiling steps for Stretch should be similar to Jesse.

Hardware decoding is always prefer since it will use the GPU instead of the CPU. This will allow the Pi to run much cooler and provide more CPU power for non-graphics tasks. Hardware decoding supports less codecs than software decoding. If you enable hardware decoding and a video is selected with an unsupported codec it will try to use the hardware decoding, fail and instead use software decoding which may cause a slight delay. This is no big deal unless most of your videos are using unsupported codecs in which case most videos will have a delay.

You will find that the Pi's resources are very limited compared to what you're used to having on your Mac and PC. Keeping as many tasks offloaded from the CPU helps preserve it's power for tasks only it can preform.

Hardware decoding + properly encoded videos = the best solution for a low resource device like the Pi.

General / Re: Roms into subfolders
« on: October 28, 2018, 01:26:56 AM »
@firewater - Because you want to use subfolders and multiple file extension you have a complex issue with multiple solutions.

IMO, your best solution is to
1. determine whether you have more .cdi or more .gdi games
2. create your emulator file to cater to the larger selection of games
Code: [Select]
# Generated by Attract-Mode v2.4.1
executable           \Emulators\nullDC\nullDC_Win32_Release.exe
args                 -config ImageReader:defaultImage="[rompath]\[name]\[name].gdi"
rompath              \Roms\Sega Dreamcast
romext               <DIR>;.cgi;.gdi
system               Sega Dreamcast
3. create exceptions for the games that don't use the file extension mentioned in your emulator file. This can be done within AttractMode by selecting the game in the FE and then pressing the button configured for edit game (Configure-->Controls-->Edit Game=?) and setting this
Code: [Select]
Custom Arguments -config ImageReader:defaultImage="[rompath]\[name]\[name].cdi"

Exceptions can also be manually created with simple text files too. Here's an example.
\AttractMode\romlists\Sega Dreamcast\Crazy Taxi.cfg
Code: [Select]
args -config ImageReader:defaultImage="[rompath]\[name]\[name].cdi"

General / Re: Roms into subfolders
« on: October 28, 2018, 12:50:25 AM »
I think "[name]\[romfilename]" in arguments will take care of directories so <dir>may not be needed in romext. Please try:

executable           C:\attract\EMU\zsnes\zsnesw.exe
args                 -m "[name]\[romfilename]"
rompath              C:\attract\EMU\zsnes\roms\
romext               cdi;gdi

No offence but this won't work for several reasons. First, "[name]\[romfilename]" = "gamename_without_extension\full_path_to_and_including rom" which isn't correct. Second, by not having "<DIR>" as a romext he won't be able to build romlists. Third, I don't think you can use "[romfilename]" with multiple romext.

1. Your global_filter has two different "Category not_contains" rules which is likely your problem. To test you should only use one rule to be certain what works and doesn't work on its own.

2. If your romlists don't contain the correct data then your rules won't work.

General / Re: Roms into subfolders
« on: October 27, 2018, 02:19:37 AM »
e.g. zsnes:
if folder-name and romfilename are identical (C:\attract\EMU\zsnes\roms\mygame1234\mygame1234.smc)
Code: [Select]
executable           C:\attract\EMU\zsnes\zsnesw.exe
args                 -m "[romfilename]\[name].smc"
rompath              C:\attract\EMU\zsnes\roms\
romext               <DIR>

set as rom-extension <DIR>
and set as argument for zsnes -m "[romfilename]\[name].smc"

just adjust config to dreamcast arguments.

How does this work if I have multiple extensions on the folder?

I don't understand this. What does "multiple extensions on the folder" mean? Do you mean "multiple extensions in the folder"?

This is an old thread. What OS? What emulator? What folder structure?

General / Re: Meaning of "emulator" in regards to displays
« on: October 27, 2018, 01:44:35 AM »
As progets said, its far better to match emulators with displays. But you can direct both GB and GBC emulators to a single location like D:\Gambatte. If you are just starting on AM I would recommend that you develop standard naming conventions to keep things organized. e.g. I use "System (Primary Emulator)".

As I mention in the first post, if you want to use a more complex setup in the future (RocketLaucher as and example), the "[emulator]" is passed as a varible and would require the system name and display name to match (or be very complex otherwise).

As a best practice, I would use the RocketLauncher naming convention in case you ever wanted to use it (even if you never plan on it). This would make things universal across FEs. The only other logical naming convention would be the if you planning on scrapping from there but I personally would still go with the RL naming convention for maximum flexibility in the future.

P.S. From years of experience, as much as you might want to call your emulators and/or displays NES, SNES, SMS, GEN, it's not the best long term idea - IMO.

Pages: 1 2 [3] 4 5 ... 49