mer-curious

Hello Tux! I'm sorry for the late reply. Thank you for this fix! I'm glad it was easy for you to do it. Thank you for the tip. I didn't know about that option. I was wondering if this wouldn't be another case of making an alternative option as default in Raine since it is the most common behavior, that is, you select/highlight a game and then you confirm its loading by using Enter and don't have it loaded by chance when using the keyboard letters... I understand now the behavior. So it does have a logic... But my idea is that the game selector menu worked as the same as every other file selector we have interacted with in the computers, so if you press a letter it will select every item with that letter in the beginning, and if you press another letter it will try to find items with that letter in the beginning too, always wrapping around the items list to find an item starting with that letter. It would be simpler and more intuitive I guess... In this case it had to highlight Darkstalkers and then Double Dragon, no? Because it was the next game in the list starting with the letter D. But the cursor remains in Darkstalkers... I'm not sure if this is expected though... Anyway, it would be great if you could reconsider the way the game selector works with the keyboard. I think it wouldn't make a huge difference, but it would certainly make it more intuitive for new users I guess... Now I would like to add something new to my post... I tried to load Super Street Fighter 2 X: Grand Master Challenge and Raine downloaded a new romset from archive.org. I found it strange because I already have this romset in my arcade games folder. So I went and checked it to see what happened: The one I have in my arcade games folder is this: The one Raine downloaded is this: Curiously the one in my arcade games folder works fine in FBNeo, so I guess it's because it has already been updated to support the new rom versions recommended by the MAME project, right? I was wondering if it wouldn't be time to update the romsets in Raine too, and then you could redirect the downloads to the FBNeo archive.org romset until someone updates the Raine full archive. This would prevent this issue of having two different versions for the same game in the computer. It's not really a huge issue because most of these games are very small in size, but if you had something like a tool to easily sync the new romsets with Raine, maybe it could be worth it updating it, no? Anyway, I'll wait your comments on this too... Thank you so much for your time and for always replying fast in the forum.

Hello Tux! Thanks for this fix in the console. I'm posting again because I think I've found two bugs in the graphical interface: 1- If you load a game and then visit the Game options menu and hit back there, you are taken back to the Raine main menu, which is what is expected. But if you save a state or load a state or do a hardware reset and then later you try to visit the Game options menu, you will never be taken back to the main menu if you hit back there, you'll always be taken straight to the game screen. See here: https://drive.google.com/file/d/1tQAG6V0a4B_Ii-VyoDCSYs7DaArSgPyo/view?usp=sharing I think that when you use the save/load state functions or the reset function it is expected that you be taken straight to the game screen, but later if you visit the Game options again and decide to just go back to the main menu, it should be possible too, no? I stumbled upon this bug by doing many save and load states in KOF2001 using the graphical interface and for a moment I went to the Game options menu and decided I would not save a state in that time and then I hit back in the controller. I noticed I wasn't taken back to the Raine main menu but straight to the game screen instead. Hopefully you'll be able to easily reproduce it and see if it could be fixed... 2- The Change/load game selector menu is working oddly here when using the keyboard. A- If I press B in the keyboard this is what happens: https://drive.google.com/file/d/1KDBvlRVEtgMzyZiEgAa7r55NPd3A5eQV/view?usp=sharing You see that Blazing Star is immediately loaded, when the expected behavior would be to just take the cursor to the game and highlight it, no? B- Still in the game selector menu, if I press T the first game with letter T is highlighted in my game list, which is expected, but then if I press T again KOF99 is loaded, see here: https://drive.google.com/file/d/11ChUY87rj94t94igfr8_t2BLS1qmMY8L/view?usp=sharing And if I press T and then M in the keyboard, Nightmare in the Dark is loaded? See: https://drive.google.com/file/d/19tTzMQG0cmY-iWtKSI1dm65LiOXNXK82/view?usp=sharing And this random loading will happen with some other letters in the keyboard too... C- Now if I press M and then M again, Captain Commando will load? Look here: https://drive.google.com/file/d/13EAr2jsnWdHX5h7-VXAccMvbtdImrRKz/view?usp=sharing D- Finally, if I press D and then D again, nothing will happen and the cursor will remain in the first game with letter D in the list, which in my case is Darkstalkers, see: https://drive.google.com/file/d/1D00nLcJnY0dY9v-p4f4gmbhaLPZaL3CW/view?usp=sharing So, there seems to be something wrong in the game selector when using the keyboard, maybe it is working in a pattern I can't understand...? But I think the appropriate behavior would be to move the screen to the first game of the pressed letter and then move to the next game with the same letter if you pressed it again. For example, if I have Samurai Showdown, Street Fighter 2 and Super Street Fighter 2 in my game list, hitting S would take me first to Samurai, then hitting S again would take me to Street Fighter and finally to Super Street Fighter. If I hit S again Raine would then take me back to the first game with this letter in the list, which is Samurai Showdown. The game would load only if I hit left or Enter in the keyboard. Anyway, hopefully you'll be able to reproduce this issue in your game list and possibly find a way to improve it. If you need me to test some changes related to these bugs I'll be glad to try it in a test version. Thank you so much again for your work.

Hello Tux! Thank you for your reply, and also for still trying to support these old operational systems, even if they can't do much except be used for these old games and a few arcade emulators. Yes, I hope pmc2 can still use Windows 7 or Linux in his old hardware to play with some emulators... Except for these comments, I'm mostly replying to report what I think could be a rare bug: if you load a game with IPS patches presenting ROM conflicts and then try to open the console, Raine will crash. See here: https://drive.google.com/file/d/1yC7WX9AjTgb32URZ2TSc_qL9hHnLsqtR/view?usp=sharing I stumbled upon this bug by trying to visit every option in the main menu to see that everything was right with the recent changes. Luckily I was playing KOF97, which has some ROM conflicts in the IPS patches. I couldn't reproduce this crash in other contexts, I mean, using games without patches or games with patches but without conflicts. It seems specific to this very case... You could try to reproduce it by using my kof97.ini file with some conflicts, here: https://drive.google.com/file/d/1MRMjay45G9bapkMGFeeCVZSKycF8SQ2G/view?usp=sharing You can get the corresponding IPS files in this thread: The patches are either in the YouTube video and/or in the emufrance link. They can also be in the GitHub link. It's a little confusing because I got different patches from different packs I guess. If you can't find them please let me know and I'll upload my kof97 IPS folder for you. I'm not sure if this crash was expected, but I'm reporting it anyway... Thank you so much in advance for your time and attention.

Hello Tux! Thank you for your reply. Just out of curiosity, I went and tried here an old version of Raine and it indeed worked flawlessly when switching from the laptop speakers to the TV ones. I tried version 0.91.21, the last SDL1 version I guess. I noticed it didn't have a sound device selection setting, so maybe it was the implementation of this setting which introduced this issue? Or maybe it was when Raine started saving the sound device firstly detected in the configuration file...? Anyway, I think I was surprisingly right on my memories on doing this switch without issues before, because it is something that started recently apparently... Yes, I saw pmc2's comment talking about that. I'm really sorry for that. I hate hardware obsolescence. Maybe this change could be reverted without breaking the auto-detection feature...? Or maybe with the improvements made in the test versions so far the compatibility may have been restored? I think the reasoning behind this decision in other emulators is exactly this, the "default/auto-detect" setting for the sound output device works for all contexts because it may always make the sound work. The user who is not satisfied with it may manually edit this setting if he/she wants... That's why I also think it makes more sense to have this option set as default in Raine too, applied to new configurations, I mean, so if you have already set your desired sound output device, then it wouldn't affect your setup anyhow. Thank you for this explanation. It's good that I stumble upon these weird bugs in Windows sometimes, so you can have the opportunity to check and fix them eventually. Thank you so much again for your attention in relation to the recent bug reports.

Hello Tux! Thank you so much for this fast fix, as always. I tried here the latest test build and everything seems right now with the game picture. I enjoyed a good playing session with different arcade games and also Samurai Shodown RPG and didn't see any issues to report. It looks like the bugs with the window manager in Windows are ended hopefully! There is only one issue left, which is that of the window positioning after leaving full-screen in a desktop with different resolution. But since I am having a seamless experience between different devices now, I don't need to leave full-screen mode often, so it doesn't bother me much... Yes, it would be great if someone else joined you in improving the project, especially fixing the Windows bugs. I do my best testing the new features and reporting bugs, but I don't know programming, so I can't help on that part unfortunately. Yes, I never complained about that before, but I think I didn't experience that issue before either...? Maybe Raine was still using SDL1 back then, or maybe the sound output device detection worked differently...? It may have been a recent change in Raine that surfaced this issue with switching between different sound output devices in Windows, because I didn't use to see that issue when hooking my laptop to the TV... Anyway, my thinking of letting "Auto-detect" as default in Raine is to prevent this issue from happening with other users in the long term, or even with me again if I happen to forget to set it up manually. I some times delete my config file to test new features and fixes and see that everything works fine from a "new-user perspective", so it is easier and quicker if I don't have to manually set another important option in my testing. But that change would only apply to new configurations. If you mostly use Linux and try to keep your configuration file for a long time, I suppose it wouldn't affect you, no? You'll keep seeing your specified sound output device showing in the Sound Options menu, I suppose... All in all, the most important is that the auto-detection feature is finally implemented and working as intended, which is great. For now we need to select it manually, but maybe you'll reconsider this decision eventually... Thank you again for your great improvements during the last week. Maybe it is time for a new release finally...?

Thank you so much for providing this new test build, Tux! I tried it here and everything seems rightly fixed. The sound device auto-detection works perfectly between different sound output devices set in the Windows desktop. So my problem is finally solved! My last request related to this new feature is that the "Auto-detect" option became the default option in Raine for new configuration files. This way users wouldn't have to worry about setting this up and possibly coming across the "no sound" issue which happened to me when switching between different devices. The "Auto-detect" option may also work in your mini PC as well as in every other context by default, so I suppose it's safe to have it as the default option at least in new configuration files, no? This way Raine would also follow what other emulators do in relation to this option. Please let me know what you think about this suggestion. Except that, I think I may have found the last bug related to the "black frame/black border around the game picture" issue. Yes, I found a new way to trigger it. Here is how to reproduce it: - run Raine and toggle full-screen mode either by using Alt+Enter or the Full-screen option in Video options menu; - save your configuration by using the Quit function; - reopen Raine and load a game; - when you leave the GUI, you may notice the game picture has now the black frame/black border around the game picture; Comparison screens: Normal picture: Black frame/black border around the picture: Here's a quick video of me reproducing it in case you need: https://drive.google.com/file/d/1vh9lk3wqSkwDFQGNJQgehMButhUbzzRd/ I came across this bug by trying to create a "perfect configuration file" without even loading a game first. So I went to full-screen and quit to save the configuration, then when I came back to finally load a game, I noticed the black frame around the picture was surprisingly back! Anyway, you should be able to reproduce it easily in your setup hopefully. The black frame may be less noticeable if you use a 16:10 aspect ratio monitor, but it will be there too. Thank you so much again for your various recent improvements in Raine emulator.

Duplicated again due to the forum bug...

Thank you so much for your explanation on this issue. I suppose this would be hopefully the last nuisance related to the new window manager, no? But it can surely wait for another time when you finally think about how resolving this... Thank you for this fix too. I'll be sure to check if everything is OK as soon as you are able to share a test build here. Thank you so much for your reconsideration of this request. I'm glad you could find a solution for that without much work I hope. I'm looking forward to testing this new feature in a test version soon. If the forum doesn't return to operation soon, you could try dragging and dropping the zip file in a GitHub comment, such as in here: https://github.com/zelurker/raine/pull/75 Thank you again for your willingness in fixing all these recent reported issues in Raine.

Hello Tux! Thank you so much for your fast reply, as always. Quote from Tux: For the 1080p -> 1366x768 not sure what happens, I might do some tests later. edit : after testing, it's minor, it's just about the placement of the window, not sure there is something to do about it, it's after resizing the screen so that it fits in the new resolution, so no wonder it can change the position while doing so. And it can be fixed manually without too much trouble, or just stay in fullscreen, so really minor. Thank you for your investigation. I agree with you. I only see this as a real issue in case someone switches from a big display resolution to a smaller one, for instance, switching from a 4k display to a 1366x768 or a 1280x720 monitor would possibly be difficult to manage the floating window depending on where it would show in the new smaller resolution, because the window could be even barely seen. It's interesting that when you first create a config file in full screen and then return to window mode, the window is perfectly centered. But if you take this same configuration to a different display with different resolution, then something happens and it can no longer position the window in the center when leaving full screen mode. It seems Raine saves some kind of memory of the first full-screen resolution in the config file, and then it does not adapt/update it to other display sizes... Except this, I've finally a new bug to report. It was maybe created after you fixed the game picture in different display sizes. So, here's how to reproduce it, using the latest test build: - run Raine without a configuration file; - load a game in windowed mode; - there should be no game picture when you leave the GUI; - if you try to go full-screen the game picture will be distorted. - if you return to windowed mode, the distortion will be retained until you show the GUI again; See all this happening here: https://drive.google.com/file/d/1wu1Kstf732xAX-3OdInWXy0hnSi9Zz_Q/ Hopefully you'll be able to reproduce and fix this too. You are correct, I understand this can be done. My feature request was with the thinking of letting this process automatic by default. If we have a "default/auto-detect/auto-select" parameter available, we can enjoy the game play without worrying about this kind of particular configuration. But without this option we need to set the sound output device every time we save the configuration file with the computer speakers, and then switch to a second or external sound device such as the one in HDMI TVs. Currently the auto detection only works in these conditions: - you don't have a configuration file created yet; - you have your computer/laptop hooked to an external display with built in speakers; - in Windows desktop you have set the display speakers as your sound output device; - you run Raine and visit the Sound Options menu or load a game and then save the configuration. In this situation the auto-detection works perfectly. Raine detects the sound device I'm currently using in Windows (in my case, the Samsung TV speakers). The auto-detection also works if: - you have a configuration file created while Windows sound output was set to the TV speakers. - you disconnect your computer/laptop from the TV and and Windows now reset the sound output to the computer speakers; - you run Raine and visit the Sound Options menu or load a game and then save a configuration file. In this case the sound output auto-detection also works and is updated to the current sound device set in Windows, which in my case is Realtek HD Audio (the only one available). The sound device auto-detection won't work in the following situation: - you have saved your Raine configuration file while having only one sound output device available in Windows (in my case, Realtek HD Audio). - you hook your computer/laptop to a TV display and have the TV speakers set as default sound output in Windows. - you run Raine and load a game or visit the Sound Options menu. In this case the auto-detection doesn't work, Raine keeps set to the Realtek HD Audio device and does not detect Windows is now using the TV speakers. As you said, you can fix this by going to the Sound Options menu and manually selecting the TV sound output device listed in Raine. If a "Default/Auto-detect/Auto-select" setting is implemented, there will be no need for that. Raine will behave as exactly as every other emulator, it will feature a seamless switch between different setups and sound output devices in Windows desktop. If such an option couldn't be added at all, then Raine on the other hand could try to always auto-detect/auto-select the sound device currently set in Windows desktop and use it instead of picking the one previously found in the config file, that is, it would always refresh it when necessary. I think one of these approaches would finally provide a seamless experience with using Raine in different contexts, making it more user-friendly in terms of important settings to be manually configured by the user. Anyway, I hope I may have clarified a little more my idea in relation to this feature, if you happen to reconsider it eventually someday. Thank in so much again for your continuing improvements in Raine.

Testing... The forum is broken somehow. I cannot post a specific reply. It seems that if I insert a quote or link it blocks me from posting, I get a 500 internal error or 504 time out error... Very weird...

Hello again Tux! Thanks a lot for this new test version. I tried here the config file last saved using the built-in monitor in my laptop in my TV and finally the game picture is properly resized to the bigger screen. Also, if you save the configuration in the TV and return to the built-in laptop monitor, the screen is perfectly resized again to the smaller screen. So the switch is finally seamless now! The only minor issue still related to the window manager at this point is this: - if you leave full-screen mode in my 1920x1080 TV, Raine window will be perfectly centered in the desktop area, as you see here: - now if you use this same config file in my 1366x768 laptop built-in monitor, this is what happens when you leave full-screen mode: You see that the Raine window is no longer centered in the new 1366x768 desktop area. It looks like it is still trying to center the window in the original 1080p display resolution, which was the one I first created the config file in. It's a minor issue compared to the others I've reported so far, but I'm reporting it again in case it could be easily fixed by you...? As for the sound output device changes, here are my results: - if you just open Raine and close it by the Quit function the config file won't be updated. You need to either run a game or visit the Sound Options menu and then Quit to save the config file with the new string naming value. - if you switch from using the built-in computer speakers to the external TV speakers (which Windows does automatically when you hook the computer to an external display with built-in speakers such as a TV), Raine still can't auto-detect and select the new sound device set in the desktop by Windows. It will retain the previous configuration found in the config file, which in my case is the Realtek HD Audio output, and for that there will be no sound. I suppose the next step in this matter would be to implement a "Default/Auto-detect/Auto-select" setting in Sound output device in Raine as we have with most emulators out there. This way the switch between internal and external sound output devices and even between additional sound devices installed in Windows would be seamless in Raine. If I had selected that option in Raine the program would simply automatically use the sound output device set in my desktop when using the TV, which in my case is the NVidia High Definition, set by Windows as default. I don't know how difficult would this be for you to implement this though. Hopefully SDL2 will have such a feature and let you do that eventually. This new setting would end the problems with switching between sound devices in Windows. Anyway, I'm already glad that Raine usability has become more seamless between different devices, which is a context more common nowadays with HTPCs, mini PCs, laptops and other portable Windows devices with external display connectivity being available in the market. Thank you so much again for the time working on these little improvements in the emulator.

Hello Tux! Thanks a lot for this fast fix. Hopefully it will be the last correction related to the window manager. If you would like to provide a test build, I would be glad to test it again. Thank you so much for that too. I thought of still preserving the numbers in the config file and only changing the look in the graphical interface. So, in the config file, 1 would be the default/auto-detect sound card (it will always use the one selected as default in Windows desktop), value 2 would be the first sound output device reported by driver and manually selected by the user, 3 would be the second sound output device found and manually set by the user, and so on... I think if you keep the numbers in the config file you may preserve compatibility with the current config files. For example, in my case I saved my Raine configuration in my laptop disconnected from the TV, so it had only one sound device available and the value set in the config file was 1. That's why I don't have sound when I reconnect the laptop to the TV, because the Samsung TV speakers are identified by Raine as the second output device, which was supposed to be value 2 in the config file. But if value 1 becomes default/auto-select, I suppose the compatibility will be preserved in my current config file when switching between sound devices in the desktop (which Windows automatically does when you hook the computer to a TV, for example). I'm not sure how difficult would it be to implement this though, but it seemed a good solution to have the default Raine configuration to be set as "Default/Auto select/detect" for the sound device, which is what happens with most emulators I've tried. There are some emulators such as Dolphin which don't even let you select the sound output device, they simply use the one set in the desktop. Anyway, I will also be glad to try any approach you make in this regard in Raine. The idea above was just a suggestion.. Thank you so much again for your time and continuing work.

Thank you so much for this new test build, Tux! I have tried it here and the issues are finally gone! The game picture is perfectly resized now to match the smaller monitor resolution, and the sound is no longer stopped if you visit the Sound options menu. Everything fixed correctly. Yes, I understand, I'm sorry for the extensive reports. It's just that sometimes I think that a video may illustrate better what I write with words. Anyway, I still have some things to report about these issues. I saved my configuration file on the desktop/laptop monitor and then thought of switching back to my Samsung 1080p TV to see if everything would be working fine when going back to the big screen. Here is what I've found: 1) The game picture will retain the smaller resolution from the monitor and show it in a frame in the bigger resolution screen, take a look: https://drive.google.com/file/d/1Tv4p5PJjDWXKVTBUrd0uPvjPA-C669b_/ This is my laptop monitor configuration (1366x768) running in my desktop monitor (1600x900). You notice that the frame is not so big because the resolution difference is not big either. And this is my laptop monitor configuration (1366x768) running in my 1080p TV screen (1920x1080): https://drive.google.com/file/d/1wMUdgELxPv_LX-pZxZqwWZtmFOFWrY5d/ Notice that the black frame is now bigger because the resolution difference is bigger. I suppose that if I used this same configuration in a 4k TV there would be an even greater frame difference. Maybe this escaped from your testings in this test version. Hopefully it will be easy for you to fix it... 2) The program no longer auto-detects the Samsung TV speakers set as default in the Windows desktop, so I have no sound in Raine, as you see here: https://drive.google.com/file/d/1OBhQiy9V20TV6uDv7_JrGoM5hH39RyZA/ You see that even if you visit the Sound options menu, it will stick to the Realtek HD Audio sound output, even if in Windows desktop I have set the Samsung TV speakers as default. I was wondering how you could fix this and thought of maybe doing what most emulators do: add a "Default" sound output device value to the sound device setting. See this option in Duckstation: Now see it in PCSX2: So this could maybe be the solution for this problem, no? It would allow the program to always detect the default sound device which is being used by the Windows desktop, be it the internal PC speakers (in my case, Realtek HD Audio), the external display speakers (Samsung TV) or others. If the user wanted to set a different or specific sound device, then he/she could select it by the list reported in Raine. The Default sound device value could be 0 or 1 in the config file, and then the other sound devices could start at 1 or 2, 3, 4 and so on. Let me know if this could be a good idea to fix this issue. Anyway, hopefully this can be the beginning of the end of these sound device and window manager issues in Windows... Thank you so much again for your continuing work in the emulator.

Thank you so much for providing a test build! This may be useful to avoid several hot-fix releases in a short time. I made a quick test here with this test version using my current configuration file in Raine, that is, the one created with the desktop computer/laptop computer hooked to the TV to check if the problems have been solved. Here are the results: - the issue with the game picture not resizing appropriately for a smaller resolution display is still present in this test version. I no longer have a game picture out of bounds though, it is just a black screen now, take a look: https://drive.google.com/file/d/1vQ2OyXaRyxgjJy2nRgrpZk5R4uM0AKCM/ So the change you implemented did change something in this regard, but it is not perfect yet. Hopefully you'll be able to understand what is going on with this issue... - the issue with Raine not detecting the current sound output device and showing a "None" value in the Sound options menu has been partially fixed. This is what is happening now: 1) if you load a game before visiting the Sound options menu, the sound device setting will be normally filled with the current sound output device found in Windows, take a look: https://drive.google.com/file/d/1ly7fQTWlOnHFJwD27v0Yat66gf-X_0h3/ The sound seems to work normally in this case as far as I've tested. 2) if you visit the Sound options menu before loading a game, then the "None" value will remain set as the sound output device and there will be no sound during the game play. This will also trigger the "Z80 error/MVS slot check" error in KOF2000 as mentioned before. See here: https://drive.google.com/file/d/1jJInRBM7Z0bxba7P0vc2_sgxxN743pNk/ So, the change you have implemented did fix the issue with the sound device detection, at least partially. There is only the case that if you visit the Sound options menu before loading a game, it will trigger the issue and then the sound will be broken. In case of KOF2000 and possibly other NeoGeo games, it will also produce the "Z80 error/MVS slot check error". The Z80 error does not allow you to play the game, as you see here: https://drive.google.com/file/d/1o05mq-RM6tg0leivib5vXm4e9v9q7o4Z/ Hopefully this test will be useful for you somehow when checking those issues again. Thank you so much for your time and work.

Hello Tux! This is really good news! I should be testing these workarounds as soon as a new version is released. Thank you so much for that. Hopefully those were the last issues related to the sound device detection and the window management feature... No problem, I cannot reproduce this issue in a normal installation either. It only happens when I have the configuration file created in my TV with my laptop or desktop computer and then try to use it with the monitor, that is, when you have the "None" value in the Sound options menu. If you have set the Unibios, it will show the "MVS slot check" error. If you have set the default Europe bios, it will show the "Z80 error". Just out of curiosity, I took the configuration file created in my laptop and tested it in my desktop computer and could consistently reproduce the error. Here's a capture showing the procedure I make, if you would like to try it once more: https://drive.google.com/file/d/1AhpKDgOwk9YeR_LdLURSosRSIqzbQCla/ As you see in the video, you need to visit the Sound options menu before loading the game to trigger the error. I have provided above the configuration file created in my desktop connected to the TV. Now I provide the configuration file created in my laptop when it was connected to the TV: https://drive.google.com/file/d/1AXfBp2K1VwRDILBorzrpnzZsNsdcXwxA/ I'm not sure it will make a difference in your testing, but since you couldn't reproduce it at all, maybe you could try it with this one too...? Anyway, I am already glad the other two issues have been fixed. Thank you so much again for your continuing work in Raine.