I used to be able to have a nice PC monitor overlay in Doxbox until today, when i updated. Now it is gone and will not display, despite being toggled on. This is what it used to look like:
Now all I get is the dosbox output with no overlay. :(
edit:
FYI I am using the 32-bit version of Retroarch for Dosbox, as there were issues with MUNT that prevented the 64-bit version as being an option. I use the full CM-32L romset, plus I like to modify reverb, etc., and in order to do this I must run the 32-bit version of Retroarch to maintain compatibility with the Windows MUNT device driver.
This is strange, because I am on the 64-bit version of Windows 10, but that is how I have to do things so they work.
Edit 2:
With further testing I have found that overlays do indeed still work with Dosbox-SVN, however, the newest build is incompatible with custom config .cfg files located in the /config subfolder tree. The newest Dosbox-SVN is doing something odd... It starts up, obeys all my viewport parameters, but won't load the overlay. Only after manually re-selecting the overlay, will it display. It gets worse, it drops stuff from my config...
Why is the latest SVN build dropping these? As a result, even though I save a new config, when I launch with my batch file, it doesn't load properly because the pertinent lines regarding viewport position and the overlay itself were omitted.
I used to be able to have a nice PC monitor overlay in Doxbox until today, when i updated. Now it is gone and will not display, despite being toggled on. This is what it used to look like:
https://www.youtube.com/watch?v=4HxPbLwpSao&t=601s
Now all I get is the dosbox output with no overlay. :(
edit:
FYI I am using the 32-bit version of Retroarch for Dosbox, as there were issues with MUNT that prevented the 64-bit version as being an option. I use the full CM-32L romset, plus I like to modify reverb, etc., and in order to do this I must run the 32-bit version of Retroarch to maintain compatibility with the Windows MUNT device driver.
This is strange, because I am on the 64-bit version of Windows 10, but that is how I have to do things so they work.
Edit 2:
With further testing I have found that overlays do indeed still work with Dosbox-SVN, however, the newest build is incompatible with custom config .cfg files located in the /config subfolder tree. The newest Dosbox-SVN is doing something odd... It starts up, obeys all my viewport parameters, but won't load the overlay. Only after manually re-selecting the overlay, will it display. It gets worse, it drops stuff from my config...
One of my original .cfg files:
aspect_ratio_index = "23" custom_viewport_height = "777" custom_viewport_width = "1111" custom_viewport_x = "408" custom_viewport_y = "156" input_overlay = "./overlays/PC Amiga/1084x_night_wall_wood.cfg" input_overlay_hide_in_menu = "false" input_overlay_opacity = "0.400001" input_overlay_scale = "1.100000" video_message_pos_x = "0.190000" video_message_pos_y = "0.210000"
This is what the latest Dosbox-SVN saves my config as if I start with a pre-configured CFG, then re-enable the overlay:
aspect_ratio_index = "23" custom_viewport_height = "777" custom_viewport_width = "1111" input_overlay_opacity = "0.400001" input_overlay_scale = "1.100000" video_message_pos_x = "0.190000" video_message_pos_y = "0.210000"
Notice the lines that are being dropped...
custom_viewport_x = "408" custom_viewport_y = "156" input_overlay = "./overlays/PC Amiga/1084x_night_wall_wood.cfg" input_overlay_hide_in_menu = "false"
Why is the latest SVN build dropping these? As a result, even though I save a new config, when I launch with my batch file, it doesn't load properly because the pertinent lines regarding viewport position and the overlay itself were omitted.