Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
When 227J is released, it will contain a new renderer called XOpengl, that runs the game from the GPU rather than the CPU. 227J and Xopengl are still in a developmental phase, so smirftsch is still working on fixing bugs and making the performance of 227J and Xopengl better. Though so far with XOpengl, subjecting the game to a stress test scene of 4000 animated animated blades of grass (this was something we tried), Smirftsch was able to improve XOpengl's original framerate by about 4 times, and that was when XOpengl had around as good performance as normal OpenGL.
XOpengl will also support some modern features like normalmapping for modders/level designers/content creators to make use of, aswel as other 'nice things'.
One question I should also ask, is what your colour depth is set to? 16 bit will run slower than 32 bit, and as far as I remember, a fresh steam install of Unreal Gold has the colour depth set to 16bit by default.
Edit: Also, it might be good to make a thread about this on the www.oldunreal.com forums, as there are very knowledgeable guys there compared to the steam discussions here on average. It is also the home of the 227 patch.
I actually don't know much about the directX9 renderer, as I rarely use D3d, but Melvin8D could always try to switch to that renderer to see if it changes anything.
The main reason quite a few people don't use d3d though is that the colour richness is not as good as OpenGL. That was the problem myself and some other people had with it anyway, though.
he's bulls**ting you about this new community patch. Any renderer other than 'software' is using your GPU exclusively.
It has nothing to do with patch or rendering API.
Sure, new patch is supposed to have new rendering features for opengl renderer, but it has nothing to do with current performance.
Have you tried to do a clean install of GPU drivers? It often helps.
But perhaps @that's what she said should take your argument up with www.oldunreal.com, the Unreal 1 community nexus and the home of the 227 patch (the site is run by the guy who Epic gave the sourcecode to and who works on the 227 patch) rather than spreading unhelpful information here about the 227 patch not being essential for performance and modern day systems (not really entirely sure what you mean to be honest).
Thus go to Preferences - Video, Change video devices. I bet you didnt do this. 227 includes the latest opengl renderer.
Also the 227 patch actually is made so that people with modern machines can play the game fluiently.
With that PC, I would actually install an older windows too.
This could also be a frame limit problem in the ini file.
Btw, if you're not hitting 60fps on a 210 at 1080p that's because the card's useless. I had one and I couldn't.