Posted January 29, 2022
READ EDIT BELOW FIRST!!!
So, I just decided to try and install the original Unreal from a CD I had laying around. Wanted to replay the game and also to test whether the CD still works. The game installed without issues and detected nGlide flawlessly. It has to be said, it is incredible how well made Unreal Engine was for its time. To be able to just plop in a CD from 1998 and the game from it flawlessly working on a Windows 10 PC.
nGlide works perfectly, but, I've had this one slightly irritating problem with, not just with Unreal but with pretty much any game I try to use it it in. The top and left of the game window always have a line of pixels on the edge, which "retain" certain effects forever and it never refreshes. Example: you shoot a blue projectile and you quickly turn the camera. Now there is a persistent blue line on the top and left edges of the game window, depending on how you moved the camera at the moment and where the projectile touched the screen edge. It happens to me in pretty much every game and never had any idea how to solve it. In the screenshot is an example from me trying it in Unreal. Caused by repeatedly shooting the dispersion pistol (blue projectile) and jerking the camera around. Had to take a photo on a phone, because screenshot does not capture this weird graphical glitch. Also attached are my nGlide settings.
Anybody know what this dead line of non-refreshing pixels on the 2 screen edges is? Any fixes? It never happens at the right and bottom edges.
EDIT:
False alarm. Turns out I got lost in the multitude of copies of nGlide confiugators present on my PC. While 2.1 was bundled with many GOG games I have installed, the main nGlide install I had on my PC (and which Unreal was loading) turned out to be an outdated 2.0 version. The main result from my Windows search was directing me to an nGlide config for a specific game and not the global config. This issue was fixed in the 2.1 version so sorry for creating this thread If you ever run into the same issue, make sure you have the latest version actually installed.
So, I just decided to try and install the original Unreal from a CD I had laying around. Wanted to replay the game and also to test whether the CD still works. The game installed without issues and detected nGlide flawlessly. It has to be said, it is incredible how well made Unreal Engine was for its time. To be able to just plop in a CD from 1998 and the game from it flawlessly working on a Windows 10 PC.
nGlide works perfectly, but, I've had this one slightly irritating problem with, not just with Unreal but with pretty much any game I try to use it it in. The top and left of the game window always have a line of pixels on the edge, which "retain" certain effects forever and it never refreshes. Example: you shoot a blue projectile and you quickly turn the camera. Now there is a persistent blue line on the top and left edges of the game window, depending on how you moved the camera at the moment and where the projectile touched the screen edge. It happens to me in pretty much every game and never had any idea how to solve it. In the screenshot is an example from me trying it in Unreal. Caused by repeatedly shooting the dispersion pistol (blue projectile) and jerking the camera around. Had to take a photo on a phone, because screenshot does not capture this weird graphical glitch. Also attached are my nGlide settings.
Anybody know what this dead line of non-refreshing pixels on the 2 screen edges is? Any fixes? It never happens at the right and bottom edges.
EDIT:
False alarm. Turns out I got lost in the multitude of copies of nGlide confiugators present on my PC. While 2.1 was bundled with many GOG games I have installed, the main nGlide install I had on my PC (and which Unreal was loading) turned out to be an outdated 2.0 version. The main result from my Windows search was directing me to an nGlide config for a specific game and not the global config. This issue was fixed in the 2.1 version so sorry for creating this thread If you ever run into the same issue, make sure you have the latest version actually installed.
Post edited January 29, 2022 by idbeholdME
No posts in this topic were marked as the solution yet. If you can help, add your reply
