OldUnreal (Engine)

Yep, i can confirm i have the same problem, since i bought ati radeon 4870HD, so i guess it is something in patch that is not compatibile with ATI cards
As stated above, it happens on skins and on weapons, in opengl mode, i will try using D3d.

One more thing, is D3D mode compatibile with s3TC textures?

2. And i have one more bug to report: When i tried to connect to 227e servers i (think it was JOLT.UK) unreal crashes...

2. : no bug although a known problem. Since the patch can be made only compatible to either 224/225/UGold OR any previous 227 patch its no question that its made compatible against the old versions to keep backwards compatibility. Any server with 227e should update to 227f anyway since it was a testversion only and 227f contains a lot of bugfixes.

believe it or not, ligthing affects the openGL, or so I've read. maybe that is having an impact on rendering?

NoDynamicLights=True

does this have any effect?

It had no effect on me whatsoever  :(

Tested with D3D9, there are no problems

It is opengl only.

Same problem here. Radeon 4850 / Catalyst 9.1

Tried installing Catalyst 9.5 - the problem is still there.

Tried patch 227e, the problem disappeared (but other problems appeared

Update: Finally tried direct3d, no problems there, and looks like S3TC textures are working as well! I thought its only possible with opengl.

Radeon 9550 (basically an underclocked 9600), Catalyst 9.5.... Direct3D8 and 9 is no longer available, no clue why, SOOOO i will try using the OMEGA drivers instead, Ill let you know if it does anything different!

very weird. The renderer wasn't really changed between 227e and 227f for the gameplay. Some changes for UED but this isn't affecting the game. Only change which is in question here is the continuous updating for lighting (like when being the boat in this nali passage, somewhere is a bugreport for this here). My guess is that here this triggers the problem. Still it very much like a driver failure in the end for me, since only ATI cards are affected.
Really need a system with radeon card...*sigh*

Hey smirf, I have a Saphire Radeon 9200 sittin around here. and the omega drivers were a no go. still have the dynamic light issue, and the update for continuous light update, that very well could be the problem, as you stated. although the omega drivers turned my radeon 9550 into a radeon x1050 via overclock =D (used ATI tool as well)

Do this happen by this?

- Fixed feature with Meshes vs. LightEffects LE_Spotlight and LE_StaticSpot for more realistic lighting.

http://www.oldunreal.com/cgi-bin/yabb2/ ... 2188/40#40

I think its maybe triggered by:
http://www.oldunreal.com/cgi-bin/yabb2/ ... 2188/40#41

But as said, I don't think this is the cause, just the trigger, I suspect the real problem to be in the driver. But this is only an assumption and needs to be tested yet, so don't nail me on this.

BTW, whcih version has better visuals - OpenGL or Direct3D? Because I fixed other problems I had with 227e (turned out I just needed to turn vsync on) and now I have a choice

thats a question of personal preference. I always disliked D3D because in previous versions it was always choppy and never satisfied me in performance. Nowadays, thanks to Chris, D3D9 and OpenGL perform almost equal so it doesn't really matter, just check which "feels" better for you

Hmm, vsync usually lowers fps depending on your system.. idk, ill have to try it, idk if its on or what. I've tried drivers from ATI, and Omega, so idk if it is driver related or not. It could be, but... after trying 2 different driver sets, it is unlikley. Nontheless, nobody is nailing you on this smirf

Vsync didn't help me with disappearing skins - I'll try new Catalyst 9.6 when I'll find some free time. The problem is OGL only so I assume it's fault of drivers.

Could try "dgl buffertris" from the console to see if it changes anything when see this.  This will toggle general buffering of everything going through DrawGouraudPolygon().  Also good to have the log open when doing this to see what it set it to.
Log: BUFFERTRIS [0]     //Disabled
Log: BUFFERTRIS [1]     //Enabled

Could also try toggling the UseVertexProgram setting while running.  This will change how texture coordinates are handled in various places.  The base texture looking all one color but lighting over it still looking reasonable is a potential fit for might be an issue with (partial) bad texture coordinates.

Don't need to restart for either of these to take effect.  Could narrow down the areas to look at if either of these change anything.

It was vertex program fault. I've turn it off and it seems it solved the problem.

No no no, I've never said vsync has anything to do with disappearing skins!

I fixed other problems I had with 227e (turned out I just needed to turn vsync on)

The key word is "other"

I fixed disappearing skins bug by using Direct3d instead of OpenGL. I don't see any visual difference.

No no no, I've never said vsync has anything to do with disappearing skins!

I fixed other problems I had with 227e (turned out I just needed to turn vsync on)

The key word is "other"

I fixed disappearing skins bug by using Direct3d instead of OpenGL. I don't see any visual difference.

Direct 3D is different varying from machine to machine Open GL is usaly faser.
And my solution for this probem is the vertexprogram. It solved all my problems. So I think it may be safe to say use OpenGL, but set the UseVertexProgram to FALSE in the rendering options!

All thanks to SMP Dev for spotting that, thumbs up to ya

I just got a report that this happens only if "SinglePassFog=True"
Can anyone confirm this?

I just got a report that this happens only if "SinglePassFog=True"
Can anyone confirm this?

Did *not* resolve my issue.

However while in editor, when selecting specific surface it makes the mesh get textured again. It seams like after DrawComplexSurface without any color it draws first Gouraud polygon list from a mesh it renders it without texture. However if the mesh is multi-skinned it draws only first skin as untextured while rest are textured.

Here's a comparison (gasbags shoulders are different texture apart from rest of the body):

Could have wrong first texture in low level GL renderer code if it ever lost track of active texture state.  With how it's designed now, the active texture needs to always be left set to GL_TEXTURE0_ARB outside of DrawComplexSurface or a few things could break.  Looked through the code a bit, but didn't see any paths where DrawComplexSurface would change the active texture but not do a glActiveTextureARB(GL_TEXTURE0_ARB) call before returning in cases where it may have modified it.

For inside the editor, could see if Textured view versus Dynamic Light view makes any difference (to get rid of the lightmap texture).  Also should try detail textures disabled.  Many detail texture modes put the alpha gradient texture in texture unit 0.  Wrong previously set world texture likely easier to notice as matching some other texture, but this one is alpha only so has RGB zero / black if ever drawn incorrectly as base texture.