Reply 2140 of 2152, by rcblanke
- Rank
- Oldbie
I'm already logged in on the website, doesn't make a difference.
I'm already logged in on the website, doesn't make a difference.
rcblanke wrote on 2025-05-28, 10:03:I've uploaded beta12 with a small improvement; all dialogs will now save their screen position in order to prevent them from falling partly off the screen (Steve).
Regards,
Ronald
I'm the Steve that Ronald referred to. This worked and everything opens entirely on my screen. Thanks!!!
Hello @rcblanke.
First of all, thanks for the continuous support to DBGL.
I'm on the process to update my game profiles from ECE to DOSBox Staging, the 0.83 alpha version currently.
I want to report some change regarding the mixer in Staging.
Now you can't set the volume for a device that is not active, e.g. if you try to set the GUS volume without having the GUS activated, the mixer didn't set it (DOSBox give the "GUS channel is not active" message).
These leads to the problem that if you put more than one channel volume level in the command, e.g. "mixer master 70 mt32 200 gus 150" and one of this device is not activated, then the volume will not be set for other channels too.
This make the GUI with the sliders for volume adjustment in DBGL a bit misleading, since users can set various devices volume even if such device is not activated in the config file, and so the mixer command will fail.
Another change is the renaming of the mixer channels (from version 0.79):
SPKR to PCSPEAKER
FM to OPL
Thanks for the heads-up Crysli, I'll see what I can do to improve support for the Mixer command in DOSBox Staging!
EDIT: For what's it worth, I wouldn't recommend using Staging 0.83 alpha in DBGL at the moment. This upcoming Staging release currently has SO many changes to the configuration file (I estimate ~40%) , that I wonder if I can ever fully support this. In any case, it is certainly very much broken at the moment (not just the mixer).
I've just uploaded beta13 with improved support for the mixer command using DOSBox Staging.
And some good news; I've been able to contact TheGamesDB for an API key, and have re-implemented support. As always, please let me know if you experience issues using TheGamesDB in DBGL. Check it out in beta14.
Nice! Between Doom TDA and the new Switch, haven't even had time to try b13 yet haha. Looks like its b14 and some Bard's Tale to start today off! 😁
Is there any chance that the final release will receive support so I can register DOSBOX Staging 82.1 with the correct version number? Or is there a way to manually add that in the configuration I am unaware of?
Awesome, used TheGamesDB to finally fill in the info for Akalabeth, and it works great! Not sure why Moby couldn't find that one anymore. It used to be there years ago, but was probably lumped into the 'Ultima Collection' it was actually released on..
Still getting the 403 error popping up when I try to use MobyGames though..
Thank you so much and sorry for the late reply, it was some busy years.
Indeed, the culprit was dbgl.data.userhome=true for MacOS, a behaviour I wasn't ware/didn't expect -> problem solved 🙇🏽
rcblanke wrote on 2023-10-26, 17:56:Hi rfc, […]
Hi rfc,
Thanks for the question. This comes up every once in a while, I'll update the documentation on the website.
By default, DBGL will use ~/Library/dbgl to save its data on a Mac. On Linux it is ~/.local/share/dbgl (as defined in the XDG specification). For Windows machines, on the other hand, all data is stored in the DBGL folder itself (unless it is read-only, then %localappdata%/dbgl is used). Let's call this location the 'DBGL data location'.
Linux and OSX can also use the DBGL folder. On Mac, open DBGL.app/Contents/MacOS/dbgl with a text editor and change -Ddbgl.data.userhome=true to -Ddbgl.data.userhome=false. A similar change is required for Linux in the dbgl startup script. In your case, changing this setting will prevent your DBGL dosroot from being copied from the NAS to your local machine.
So, if you just want to have all DBGL content in a single directory structure, use dbgl.data.userhome=false . This should also work fine if you running it from off the NAS share.
But what if you want to use DBGL with different Operating Systems? This question has come up quite a while ago. Most of the information in that thread is still correct, but to summarize:
- Create a directory on your NAS (or USB stick) for DBGL and mount it (with RW permissions); let's say /Volumes/dbgl for Mac, \\mynas\dbgl for Windows or /Media/USBSTICK/dbgl for Linux. Let's call this the 'shared content location'.
- Install DBGL on your different OS' and start it once. Please note that for Mac and Linux, you should use dbgl.data.userhome=false !!
- After closing DBGL, there will be a settings.conf file in your DBGL folder. Open that file with your favorite text editor and change the 'data' setting. By default, it's set to '.', which means DBGL expects all user-generated content to be in the 'DBGL data location'. Change the value to your 'shared content location', for example data=/Volumes/dbgl
- Move the folders captures, db, dosroot, export, profiles, templates and xsl to the 'shared content location'
If you use this solution, you have all your DBGL user-generated content in one place, while maintaining the flexibility to customize your DBGL installation on the various OS systems. For example, you can still use different system environment options (inside DBGL) on each OS. This allows you to set a specific SDL output renderer for each Operation System, for instance.
Please note that this technique has its limitations, especially with regards to DOSBox versions. Because of the fact that you're sharing DOSBox Version settings with multiple operating systems, it is required that you'll have the various DOSBox versions in the correct subdirectories on the local machines. For example, by default a 'DOSBox-0.74-3' folder is expected to exist (on your local machine, inside the DBGL folder) and have (at least) the dosbox executable and dosbox.conf files. When using Windows, DBGL will look for 'DOSBox.exe'. On Mac, 'DOSBox' is expected, and on Linux, 'dosbox'.
Also note that you can start only one instance of DBGL at the same time.
In the end, you can configure and play your DOS games on all systems using one familiar interface, without the need to export and/or import anything.
Please let me know if anything's unclear, or requires a better explanation.
Regards,
Ronald
Monotremata wrote on 2025-06-09, 16:29:Still getting the 403 error popping up when I try to use MobyGames though..
Yes, it seems that the MobyGames website is now using Cloudflare, which makes it *very* hard to scrape any website content. I've tried a few things, but it seems that no (reliable) workaround is available (for the moment). If it doesn't work, all you can do is just copy-pasting from a web browser. If anybody has any ideas on this matter, I'm all ears.
rfc wrote on 2025-06-09, 18:08:Thank you so much and sorry for the late reply, it was some busy years.
Ha ha, I know the feeling. Thanks for the confirmation! 😀
GabeCube wrote on 2025-06-08, 13:18:Is there any chance that the final release will receive support so I can register DOSBOX Staging 82.1 with the correct version number?
Ah, totally forgot about that. Support is added in beta15 (just 1 new option: 'gus_filter').
Support for eXoDemoScene v2.0 is also implemented in the importer and convertor.
rcblanke wrote on 2025-06-10, 16:00:Monotremata wrote on 2025-06-09, 16:29:Still getting the 403 error popping up when I try to use MobyGames though..
Yes, it seems that the MobyGames website is now using Cloudflare, which makes it *very* hard to scrape any website content. I've tried a few things, but it seems that no (reliable) workaround is available (for the moment). If it doesn't work, all you can do is just copy-pasting from a web browser. If anybody has any ideas on this matter, I'm all ears.
Ahh that makes sense. GamesDB is pretty nice, but I liked Moby as it seemed a little more 'correct' (GamesDB claims Ultima II was developed by Origin Systems who didnt exist yet haha). Easy enough to work around.
On to beta15 now when I get off work tonight! 😁
Maybe GamesDB should be set as the default source for game info until (if ever) the Mobygames thing is solved.