mer-curious

Hello Tux! Thanks for the fast reply! It's good you could easily reproduce the issue there. I was wondering if Raine couldn't ignore the Windows scaling setting and just use the driver or display resolution currently set on Windows when in full-screen mode? This would fix the issue once and for all, no? No problem, for the time being I can stick to the 100% scaling setting in Windows. But I think this is the limit resolution for 100% scaling. If the user happen to have anything above that, such as a 1440p, 2k, 2.5k or 4k TV or monitor Windows will probably suggest something higher than 100%, otherwise items in the interface will be very tiny to see. For this it would be good a long-term solution, especially because 1440p monitors are becoming more common and cheaper nowadays. Thank you again for your reply and for your time.

Hello Tux! That's great to know! There are some interesting glsl shaders in Retroarch. I will be willing to test them in Raine if/when you ever implement this feature. It is the Windows scaling setting, not the Nvidia Control Panel. You right click the mouse in desktop -> Display settings and then you have an option to set the scaling. Here it shows "100% (recommended)", "125%", "150%" and "175%", take a look: I am using a 1080p TV, for 1440p monitors and 4k TVs there should be higher scaling values I believe. You should be able to reproduce this issue in your Windows installation I suppose. Here I use Windows 10. I believe this is not a recent issue, but I'm not sure about it. I didn't try changing the scaling settings in Windows before as far as I remember though... Anyway, it would be good if Raine good handle this setting better, but if not I'll need to change the scaling settings in Windows for the time being. Thank you again for your attention.

Hello Tux! Thank you so much for this super fast fix! So the issue indeed started recently as I suspected... Do you intend to add support for GLSL shaders? By the way, I think I've found another issue related to the shaders: If you change the scaling options in Windows Raine will be affected by the scaling and will produce a different effect in the shaders. Here I tested the scanline-3x shader, which is the one I use. If the scaling option in Windows is set to 100%, the scalines will be barely visible and the effect is great, as you see here: I suppose you can only see how good it looks in a 1080p TV or monitor. Now if the scaling in Windows is set to 150%, this is what you get with the shader: You have to zoom in the picture above a little to see how it really looks here. The scanlines become much thicker and the effect is not good anymore. I've noticed in "Video information" that the resolution reported by Raine is 1280x720, even if my desktop is set to 1920x1080: Maybe this is why the shader is looking bad? Raine would be taking a different resolution from the desktop, even if the one I have set in Windows is 1920x1080. Anyway, I came across this issue by using the computer from a distance to the TV, so I set the scaling to 150% to be able to see better farther. Perhaps you could make Raine always use the resolution set in the desktop and ignore the scaling adjustment? Or would this be something only fixed in SDL 3? I'll wait your comments on that. Thank you so much again for your continuing work in Raine.

Hello Tux! I have updated Samurai Shodown 2 Perfect Edition to version 2.4. Hopefully everything was done right. Also, I've found a glitch in the latest version. If you try to apply a shader on the fly it will not work. The screen will be totally black, see: https://drive.google.com/file/d/1GYKCs_Ipvi4-hkVIBrV1kcjw4DdIl2kZ/view?usp=sharing You have to close the program and then reopen it to see the shader effect in the picture. I think this started in the latest version, I don't remember experiencing this issue in the previous version... 🤔 Hopefully you'll be able to reproduce this issue in your setup and fix it easily. Thank you so much in advance for your time.

Great work, ffman1985! I didn't know Capcom did soundtrack arrangements for Street Fighter Alpha 1 and 2 in the PS1/SS ports. I'll test the associations eventually in Raine and report here if everything goes right. Thank you for sharing your work! PS: I opened a feature request in FBNeo GitHub page to support sound associations almost a year ago, but no developer has had interest in implementing this feature yet. Gladly we still have Raine and Tux to fix some possible associations issues!

Hello again Tux! Thank you so much for this fast fix and for the details on the issue. Now the language selection is working again in Raine and I could select English and save it normally. But curiously some strings are still not translated in the Portuguese translation: Japanese font Autostart drivers Background animation Profiler mode Are you sure these strings are translated in the translation file? If they are not, I could provide a translation to them... Also, in NeoGeo options you could allow us to translate the new Neo-Geo saveram function which was introduced a few versions ago. It is currently untranslated in the Portuguese translation. The memory card menu is also untranslated too... Finally, the Portuguese translation is automatically detected here the first time I run the program, so I'm still confused with what you said before in this thread, here: Anyway, I think it would be better to have English as default instead of trying to detect the OS language... I'm not sure if it's common for emulators to detect the OS language at start, but it's just a minor detail in the end of the day... I suppose you should keep the 0.97.3 version in the Old versions page. It would be weird to not have it listed there I guess, for historical purposes. It worked well, no? At least I couldn't find any problem with it except the language setting... Thank you so much again for your time and work.

Hello Tux! I'm sorry, but I guess I didn't understand what you said. You mean "it makes more sense to try to detect the language for the 1st launch", right? Because this is what Raine is doing currently, it detects the language in my OS in the first time I run the program and selects it. My request was in the opposite direction, it was to have English always set as default language in the GUI for new configurations regardless of the OS language setting. If someone wants another language in the interface to match the OS, then he/she may change it in the GUI options. So there would no longer be a language auto-detection feature... Anyway, I tried here version 0.97.4 and some things are still broken, take a look: 1) Strings in the Portuguese translation remain untranslated: You see that the language in my OS is now properly detected and displayed in the GUI, but some strings are still not translated, they are: Japanese font Autostart drivers Background animation Profiler mode Are you sure these strings are translated in the Portuguese translation? 2) The language setting is broken, it will always be the one in your OS, regardless of the option you choose: If you decide you want another language than the one automatically detected by Raine, the setting will change but the interface will remain in the OS language Raine first detected in a new configuration. In the example above, I selected "default (English)", quit the program using the Quit function and when I opened it again, it was still in Portuguese, although the language setting had changed to English. Hopefully you'll find a way to reproduce this issue an possibly fix it. Please let me know if you need me to try a test version to check that this issue is fixed. Thank you so much again for your time and work.

Hello Tux! You are correct! I hadn't realized that before you noticed it. Very weird indeed... Everything seems right in this folder apparently. I didn't change anything, just extracted the zip and filled the folder with the new DLL files, and then started the program without a previous configuration file. I suppose so, because it didn't happen in the previous version... I was wondering if it wouldn't be better to have the default language always set to English for new configuration files. Then the user could go the GUI options and set his/her preferred language to match the one he/she prefers. This would prevent this glitch from happening, no? Also, other languages may be added to Raine in the future, so this change would avoid an issue with them too, no? Anyway, I'll wait your comments on that... Thank you so much again for your attention.

Hello Tux! Thank you for the fast response. You mean you have your Windows set to French and Raine starts in English in a new configuration file? Or does it start in French and show French in the GUI options? Here I have my Windows language set to Portuguese (Brazil) and Raine used to start in English until last version. Now it started in Portuguese (Brazil) but the option shown in the GUI is not correct, it shows "default (English)" instead of Portuguese. I'm not sure which is the intended behavior, if it is to detect the OS language and start Raine with that language in a new configuration file, or if it is to start Raine in English first in a new configuration file, regardless of the OS language setting. Ok, here is what I have: ALLUSERSPROFILE=C:\ProgramData APPDATA=C:\Users\Elvis\AppData\Roaming CommonProgramFiles=C:\Program Files\Common Files CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files CommonProgramW6432=C:\Program Files\Common Files COMPUTERNAME=DESKTOP-S09R0U5 ComSpec=C:\Windows\system32\cmd.exe DriverData=C:\Windows\System32\Drivers\DriverData FPS_BROWSER_APP_PROFILE_STRING=Internet Explorer FPS_BROWSER_USER_PROFILE_STRING=Default HOMEDRIVE=C: HOMEPATH=\Users\Elvis JD2_HOME=C:\Users\Elvis\AppData\Local\JDownloader 2.0 LOCALAPPDATA=C:\Users\Elvis\AppData\Local LOGONSERVER=\\DESKTOP-S09R0U5 NUMBER_OF_PROCESSORS=12 OneDrive=C:\Users\Elvis\OneDrive OS=Windows_NT Path=C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program Files\dotnet\;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Users\Elvis\AppData\Local\Microsoft\WindowsApps; PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC PROCESSOR_ARCHITECTURE=AMD64 PROCESSOR_IDENTIFIER=Intel64 Family 6 Model 165 Stepping 3, GenuineIntel PROCESSOR_LEVEL=6 PROCESSOR_REVISION=a503 ProgramData=C:\ProgramData ProgramFiles=C:\Program Files ProgramFiles(x86)=C:\Program Files (x86) ProgramW6432=C:\Program Files PROMPT=$P$G PSModulePath=C:\Program Files\WindowsPowerShell\Modules;C:\Windows\system32\WindowsPowerShell\v1.0\Modules;C:\Program Files\Intel\Wired Networking\ PUBLIC=C:\Users\Public SESSIONNAME=Console SystemDrive=C: SystemRoot=C:\Windows TEMP=C:\Users\Elvis\AppData\Local\Temp TMP=C:\Users\Elvis\AppData\Local\Temp USERDOMAIN=DESKTOP-S09R0U5 USERDOMAIN_ROAMINGPROFILE=DESKTOP-S09R0U5 USERNAME=Elvis USERPROFILE=C:\Users\Elvis windir=C:\Windows ZES_ENABLE_SYSMAN=1 As you see, there is no LANG or LANGUAGE string in the results... Please let me know if you need me to test or report something else. Thank you so much again for your time.

Thank you for the fast reply! Now I could finally start the program. I noticed in a new installation (without previous configuration file) that Raine is now showing the GUI in my current operational system language. I suppose it had to start the program in the default (English) language, no? At least this was always the case here... Also, if you visit the GUI options, you still have "default (English)" selected, even if the interface is in my OS's language, take a look: Maybe this happened when you fixed the region changes...? Anyway, this is a minor glitch and for now the only one I've found in the new version. Thank you so much again for your continuing support.

Hello Tux! Happy New Year and thank you for this new release! I tried a quick run of the new Raine version and I am getting the following error message: After that message the program does not start. It seems to be something to do with a DLL file maybe? I have the DLL pack from November 3rd, 2024. I'm not sure if there has been an update to it recently. Anyway, hopefully you'll figure this out quickly... Thank you in advance for your time and work. 👍

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.