1
Announcements / Re: RetroFE development
« on: October 25, 2020, 09:24:53 PM »
This release fixes an issue with volume animation, where animating the volume to 1 would make the video disappear.
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.
2
General Discussion & Help / Re: RetroN
« on: October 18, 2020, 02:36:13 PM »
That would fall under single item, so no, not at the moment.
3
Announcements / Re: RetroFE development
« on: October 17, 2020, 10:38:51 AM »
This release fixes some control issues, especially with zero delay encoders. If your keys get stuck, use this version, and use:
collectionInputClear = yes
playlistInputClear = yes
jumpInputClear = yes
in your settings.conf file.
collectionInputClear = yes
playlistInputClear = yes
jumpInputClear = yes
in your settings.conf file.
4
General Discussion & Help / Re: RetroN
« on: October 17, 2020, 07:19:37 AM »Okay, different question. Can you set multiple list paths in the settings config for a system?
For separate items (video, logo, etc.): yes.
For a single item, as in multiple paths for video: no, not at the moment.
5
General Discussion & Help / Re: RetroN
« on: October 17, 2020, 07:18:28 AM »Okay, different question. Can you set multiple list paths in the settings config for a system?
Sure, the code needs to be adapted in order to support that. I'm also not sure everyone would want that to happen to be honest, so perhaps it should be a separate sound?
6
General Discussion & Help / Re: Launcher per game
« on: October 15, 2020, 09:09:05 PM »
Yes, you can set a game specific launcher in the launchers directory of a collection, e.g. you want to use the mame64 launcher (in stead of the mame launcher) for daytona in the arcade collection, you'd create a collections\arcade\launchers\daytona.conf file, in which you simply put the single word
mame64
This will use the launchers\mame64.conf launcher in stead of the launchers\mame.conf launcher.
I really should explain this better in the documentation; I still haven't been able to find this feature, even though I programmed it ages ago.
mame64
This will use the launchers\mame64.conf launcher in stead of the launchers\mame.conf launcher.
I really should explain this better in the documentation; I still haven't been able to find this feature, even though I programmed it ages ago.
7
General Discussion & Help / Re: Can anyone create a modern live persistent Linux USB for RetroFE usage?
« on: October 07, 2020, 07:40:24 AM »
There’s a CoinsOPS Diamonds version getting ready for launch soon. That might be a good base to work from or use as is.
8
General Discussion & Help / Re: ubuntu 20.04 Problems compiling retrofe
« on: October 07, 2020, 07:37:38 AM »
The only issue I encountered is that the Mercurial package doesn’t exist. If you don’t remove it from the install list, Ubuntu won’t install the rest either, and so the compile will fail. I used Kubuntu 20.04 myself.
9
Announcements / Re: RetroFE development
« on: October 01, 2020, 10:47:26 PM »
This should fix issues with container boundaries and reflections. I've also replaced the full word check on the direction with a find search, so you can now use e.g. "leftright" to display reflection on both the left and the right of an object.
10
Announcements / Re: RetroFE development
« on: September 27, 2020, 06:52:49 AM »
This should fix the video issues with older themes.
11
General Discussion & Help / Re: Prior Menu artifacts in current list / no videos in current collection
« on: September 24, 2020, 08:47:44 PM »
RetroFE doesn't log every image and video it cannot find though; that would quickly fill up the log after all. 
Perhaps I should build debug logging for that sometime though.
If it's v0.10.0 I'm not sure what the issue might be. Perhaps if you can send me a copy of a small setup with what it should do, I can have a look to see where things go wrong. If there are issues in the code I will certainly try to fix them.
Perhaps I should build debug logging for that sometime though.If it's v0.10.0 I'm not sure what the issue might be. Perhaps if you can send me a copy of a small setup with what it should do, I can have a look to see where things go wrong. If there are issues in the code I will certainly try to fix them.
12
Announcements / Re: RetroFE development
« on: September 24, 2020, 06:07:22 PM »
Ok, I think I've updated the documentation accordingly. I'll first look into some issues with older themes with the v0.10.2 release, and then move on to fix some issues with regards to reflection.
13
General Discussion & Help / Re: Prior Menu artifacts in current list / no videos in current collection
« on: September 24, 2020, 05:54:31 PM »
Is this with the v0.10.0 release or the v0.10.2 release? I'm currently looking into some issues with the v0.10.2 release regarding video display, including some issues with some of the Core themes.
14
Feature Requests / Suggestions / Re: Possible for never played playlist
« on: September 13, 2020, 11:27:12 AM »
I'll have a look at it. I've been thinking about keeping stats for how many times a game is played anyway (which should be updated when new games are added as well), and could probably generate some playlists from there.
15
Announcements / Re: RetroFE development
« on: September 12, 2020, 07:05:14 PM »
My apologies for the delay. It took me a while to get my compile environment up and running again after my HDD crash, and downloading a lot of the material I had lost. Since yesterday i can finally compile under Linux again as well, and it seems the new code compiles there as well. In any case, here is a new executable to play with, though for people using the default theme: it needs a fix in order to prevent getting echoed sound due to the new features.
Let's start with the source code: Due to the drop for Mercurial support in bitbucket I have moved the source code to github: https://github.com/phulshof/RetroFE
The current v0.10.2 release has the following new features:
- I've added support for multiple videos. The reloadableVideo tag now supports a type parameter as well as a volume parameter. The type parameter defines the directory the video is searched in, and defaults to "video". Note that with the default theme this will actually cause two instances of the video to be played rather than the dual display of a single video it used to, which will cause an echo in the sound. The default theme needs to be changed so one of those videos has the volume set to 0.
- I've used this support for multiple videos to allow the menu tag to support a videoType parameter. Just like the imageType parameter was (and is) used to select the image type to be displayed (e.g. logo), the videoType parameter allows for a video type to be displayed. This will allow you to create a scrolling menu consisting of videos in stead of images. You may want to play with the volume settings for the non-selected items though, or it quickly becomes messy.
- I've added support for multiple monitors. A numScreens parameter has been added to settings.conf to define how many monitors you have. screenNum0, screenNum1, etc. parameters can then be used to link them to a specific monitor. The fullscreen, horizontal, and vertical parameters have been given postfix support for monitor numbers to define the monitor you're configuring, and the layout.xml tags have been given support for a monitor parameter to define on which monitor an element is supposed to be displayed. This can be used to e.g. display marquees on a second monitor.
An example for settings.conf:
numScreens = 2
fullscreen0 = no # Full screen SDL applications often clash with the focus of other SDL applications
horizontal0 = stretch # or enter in the screen pixel width (i.e 1920)
vertical0 = stretch # or enter in the screen pixel width (i.e 1080)
screenNum0 = 0 # Screen numbers start at 0!
fullscreen1 = no # Full screen SDL applications often clash with the focus of other SDL applications
horizontal1 = stretch # or enter in the screen pixel width (i.e 1920)
vertical1 = stretch # or enter in the screen pixel width (i.e 1080)
screenNum1 = 1 # Screen numbers start at 0!
- I've added an attractModeCyclePlaylist parameter to settings.conf to allow attract mode to use the cycle playlist in stead of the full set of playlists.
I hope to update the documentation soon, and then have a look at fixing the code for container based cropping of the reflections like someone requested. Again: my apologies for taking so long, but it's taking me quite some time to get completely up and running again, and work has kept me extremely busy lately.
In any case, here is a new executable to play with, though for people using the default theme: it needs a fix in order to prevent getting echoed sound due to the new features.Let's start with the source code: Due to the drop for Mercurial support in bitbucket I have moved the source code to github: https://github.com/phulshof/RetroFE
The current v0.10.2 release has the following new features:
- I've added support for multiple videos. The reloadableVideo tag now supports a type parameter as well as a volume parameter. The type parameter defines the directory the video is searched in, and defaults to "video". Note that with the default theme this will actually cause two instances of the video to be played rather than the dual display of a single video it used to, which will cause an echo in the sound. The default theme needs to be changed so one of those videos has the volume set to 0.
- I've used this support for multiple videos to allow the menu tag to support a videoType parameter. Just like the imageType parameter was (and is) used to select the image type to be displayed (e.g. logo), the videoType parameter allows for a video type to be displayed. This will allow you to create a scrolling menu consisting of videos in stead of images. You may want to play with the volume settings for the non-selected items though, or it quickly becomes messy.
- I've added support for multiple monitors. A numScreens parameter has been added to settings.conf to define how many monitors you have. screenNum0, screenNum1, etc. parameters can then be used to link them to a specific monitor. The fullscreen, horizontal, and vertical parameters have been given postfix support for monitor numbers to define the monitor you're configuring, and the layout.xml tags have been given support for a monitor parameter to define on which monitor an element is supposed to be displayed. This can be used to e.g. display marquees on a second monitor.
An example for settings.conf:
numScreens = 2
fullscreen0 = no # Full screen SDL applications often clash with the focus of other SDL applications
horizontal0 = stretch # or enter in the screen pixel width (i.e 1920)
vertical0 = stretch # or enter in the screen pixel width (i.e 1080)
screenNum0 = 0 # Screen numbers start at 0!
fullscreen1 = no # Full screen SDL applications often clash with the focus of other SDL applications
horizontal1 = stretch # or enter in the screen pixel width (i.e 1920)
vertical1 = stretch # or enter in the screen pixel width (i.e 1080)
screenNum1 = 1 # Screen numbers start at 0!
- I've added an attractModeCyclePlaylist parameter to settings.conf to allow attract mode to use the cycle playlist in stead of the full set of playlists.
I hope to update the documentation soon, and then have a look at fixing the code for container based cropping of the reflections like someone requested. Again: my apologies for taking so long, but it's taking me quite some time to get completely up and running again, and work has kept me extremely busy lately.