The UBETE4N error is related to vertex shaders, the only time I saw that error was when I had my vertex shader set lower then 2.0 (as a side note, on ubuntu with experiemental drivers and wine, CoD4 gives this same message and only detects 1.1)
Zombie driver, I never tried it with this program but before, it would start but it would be all white Back to CoD4, I managed to get past the UBYTE4N error and the create2Dtexture error by ticking the first plugin in the window (AF something) but I never get to see the movie or anything, and it crashes back to desktop without error. @Mentally Are you saying that basically you lowered all the settings in CoD4 with SS and then was able to start CoD4 up with DXTweaker, with the same settings and everything, but just get the UBYTE4N error? As for L4D, I can't seem to quite figure out why it does the brightness glitch. With TnL enabled, L4D displays shader errors, pointing directly at vertex decl, which there is a setting for somewhere in DXTweaker. UT3 Demo, I can't make it start, it still crashes without a actual error message (just the generic windows one). World of Warcraft crashes on exit, so I can't get it to display a logfile of what graphic options are enabled. I know WoW works without having anything special, I was curious about it's vertex shader usage. On Tue, Dec 22, 2009 at 1:29 PM, Many6 <[email protected]> wrote: > Okay guys for COD 4 I guess u should try ticking all the items in > "Caps Changer" and see what happens then... > As for the UBETE4N Vertex shader error that should'nt actually be a > problem as we can emulate that by going into "Caps Changer" and then > "Vertex Input".. > But this seems somewhat complicated and will take some time to work > out... Anyways Guys Try It!! > > INTEL 9xx SOLDIERS SANS FRONTIERS > -- Espionage724 Has A Signature... INTEL 9xx SOLDIERS SANS FRONTIERS
