emmanuel56

Hi Steven It's okay. I deleted the steem.ini I had and let the 64-bit version recreate it. Now it works: the game's B drive is recognized correctly without needing to reboot Steem. Actually, when you switch from 32-bit Steem to 64-bit Steem, as I did, it's best to delete the old steem.ini and recreate it, because otherwise, like me, you risk experiencing strange behavior. Thanks, and sorry for taking up your time.

Hello Steven I'm having a problem with Steem.SSE.4.2.0.Win64.D3D.R4 When loading the game Barbarian, when I insert disk B into the drive when the program asks me to, it isn't recognized. I have to quit SteemSSe and restart it for disk B to be recognized and for the game to finish loading.

Dosbox.exe from DOSBox_0.74-3+xBRZ_1.9+Save_States_Win32.zip is not a valid win32 application. People like me are fooled with such erroneous titles. DOSBox_0.74-3+xBRZ_1.9+Save_States_Win32.zip must be titled DOSBox_0.74-3+xBRZ_1.9+Save_States_Win64.zip Yes, there are troglodytes people like me who are still using Windows XP 32 bits in 2022.

Dosbox.exe from DOSBox_0.74-3+xBRZ_1.9+Save_States_Win32.zip is not a valid win32 application. People like me are fooled with such erroneous titles. DOSBox_0.74-3+xBRZ_1.9+Save_States_Win32.zip must be titled DOSBox_0.74-3+xBRZ_1.9+Save_States_Win64.zip Yes, there are troglodytes people like me who are still using Windows XP 32 bits in 2022.

Dosbox.exe from DOSBox_0.74-3+xBRZ_1.9+Save_States_Win32.zip is not a valid win32 application. People like me are fooled with such erroneous titles. DOSBox_0.74-3+xBRZ_1.9+Save_States_Win32.zip must be titled DOSBox_0.74-3+xBRZ_1.9+Save_States_Win64.zip Yes, there are troglodytes people like me who are still using Windows XP 32 bits in 2022.

DOSBox_0.74-3+xBRZ_1.9+Save_States_Win32.zip is not a valid win32 application. People like me are fooled with such erroneous titles. DOSBox_0.74-3+xBRZ_1.9+Save_States_Win32.zip must be titled DOSBox_0.74-3+xBRZ_1.9+Save_States_Win64.zip Yes, there are troglodytes people like me who are still using Windows XP 32 bits in 2022.

Yes it was D3D. I download the debuggers and beta but can't reproduce the issue today. Crisp rendering is fine with beta. I don't know what happened yesterday, it was blur whatever rendering option I chose

(Test on release 32 bits) crisp rendering is blurry in fullscreen in beta whereas crips rendering is perfect in fullscreen in release R5