Reply 400 of 1111, by d1stortion
Yes obviously I did start it with Kernelex. It's off per default and default compatibility mode is activated for UT.
Yes obviously I did start it with Kernelex. It's off per default and default compatibility mode is activated for UT.
What drivers did you use for this to work?
I got this to work. 😀 For whatever reason the windowed resolution was set to 640x471, setting it to 640x480 fixed it (even though I run fullscreen).
Wonder if it is possible switching out SGLDrv.dll with an older version...
No because SGLDrv.dll (like the rest of the DLLs) are built on headers tied to the specific Core.dll and Engine.dll libraries. You can not mix and match drivers between versions or other UnrealEngine games.
Here's how the game looks. Some varying degrees of screwup on the HUD, compared to the video. 4.1.2 Revolution drivers used.
If you can, try the original release build (400) or even the demo (348) and don't apply the hex editing step. It looks much better in the older builds.
I haven't tried it progressively patched to see what exact version the SGLdrv screws up though...
Well there is actually some truth to the "pro gamer" comment on the video description, it is a lot easier to see enemies 🤣 it would be hilarious to play online with this card, but with it being Win9x only and UT anticheat requiring 2k something tells me that these people have no love for the PCX2...
Is it known which Unreal version introduced the broken SGLDrv? It is a shame they removed this completely in Gold, but I've heard any vanilla version will work with Kernelex.
Btw Forsaken demo looks surprisingly bad on this, wasn't expecting black squares given that the game offers a PowerVR path.
Here's some Unreal, vanilla unpatched version. Second shot with VertexLighting=True. Hmm, it could be argued that the default settings aren't that great for the PowerVR card...
The lightmap is alpha blended 😀
Hi,
In this thread i saw a link to the discsimg for the matrox m3d, but the files are gone. Does someone know where to find them. I would really appreciate it!
I never got 24-bit/32-bit rendering working in Unreal even with the depth set to 24. Anyone else ever got it to work?
It would be better since it'll run faster 😀
Why do the textures look like that? I'm really curious now... Man screenshots make a load of difference compared to youtube videos...
“I am the dragon without a name…”
― Κυνικός Δράκων
I'm on the lookout for a PCX2, so if anyone wants to get rid of theirs or knows a source I'm all ears 😎
wrote:Why do the textures look like that?
The lightmap is intensified and then alpha blended (brighter light = less alpha). It's also why it's so blocky since it does not have precise bilinear filtering on alpha channels.
I get this sinking feeling Tim Sweeny must of been disappointed with the PowerVR renderer.
“I am the dragon without a name…”
― Κυνικός Δράκων
wrote:I get this sinking feeling Tim Sweeny must of been disappointed with the PowerVR renderer.
It is even more mystifying that a RRedline renderer wasn't written by Rendition or Epic. Though I suppose the lack of per pixel mip mapping may have been the nail in that coffin for Unreal.
Sweeney's favorite renderer is SoftDrv 😀
wrote:Sweeney's favorite renderer is SoftDrv 😀
He still wants CPU based rendering today AFAIK. He liked Larrabee. GPUs seem to be slowly heading in his desired direction.
For those Midas owners who stumble upon this thread, you can now also find the drivers from DriverGuide here. They've yet to be tested AFAIK:
http://www.vogonsdrivers.com/getfile.php?fileid=530
http://www.vogonsdrivers.com/getfile.php?fileid=531
A bit more info here:
http://forum.beyond3d.com/showthread.php?t=60603&page=4
"I see a little silhouette-o of a man, Scaramouche, Scaramouche, will you
do the Fandango!" - Queen
Stiletto
I assume that's a Midas 3 driver? Seeing as PCX1 and 2 are also Midas cards it might be confusing if you don't use the 3.