What's new

Rice Video 6.1.0c - HiRez Texture Loader

Status
Not open for further replies.

John Doe

New member
Does anyone know, how to get rid of those graphic glitches? I tried different settings and graphic drivers - always the same :( .

I always had those probs with Rice's Video Plugin - but only under DirectX. But since version 5.9.9 it's always there: under DirectX & OpenGL. Other video plugins (DirectX & OpenGL) don't show such glitches - but no other has the ability to load hires textures... and that's a pro i don't want to miss :) .
So... does anyone know how to solve it?
 

xSpRiGGaNx

Omini Yuu
Rice Is da-Bomb!

Um, i don't know if this has been answered before.....but has the issues with Gauntlet legends been solved yet?

cos when i played it using 5.99 it was a hell of a lot better than on 5.6 but still had serious problems.

Oh and Rice, i though you left the plugin scene. (im not complaining)
 

knowitman

New member
Hey rice. I don't know if this would cause problems, but would it be possible to tell teh plugin to only dump like the *_all version or the *_rgb and *_a versions of the textures. I don't really like having 3 versions of the same texture. It seems to clutter up my folder.
 
OP
Rice

Rice

Emulator Developer
I cannot figure out why such a thing bothers, but I guess it won't be much a trouble for you to run the DOS prompt, change to the folder and enter

delete *_rgb.*
delete *_a.*

or if you don't want *_all files, then hit.

delete *_all.*
 

knowitman

New member
Rice said:
I cannot figure out why such a thing bothers, but I guess it won't be much a trouble for you to run the DOS prompt, change to the folder and enter

delete *_rgb.*
delete *_a.*

or if you don't want *_all files, then hit.

delete *_all.*

Thanks for the info. I haven't used dos in a long time and either didn't know or forgot about that command.
 

ggab

Emutalk Member
when Rice OGL was running in ogl1.1 or 1.2/1.3 or 1.4 (mario64, zeldaOOT, etc) with lastest mesaFX ICD (opengl32.dll) in a voodoo4, i get this list of loaded extensions LOG:

>>> asked for (wglGetExtensionsStringARB)
>>> asked for (wglSwapIntervalEXT)
>>> asked for (glMultiTexCoord1dARB)
>>> asked for (glMultiTexCoord1dvARB)
>>> asked for (glMultiTexCoord1fARB)
>>> asked for (glMultiTexCoord1fvARB)
>>> asked for (glMultiTexCoord1iARB)
>>> asked for (glMultiTexCoord1ivARB)
>>> asked for (glMultiTexCoord1sARB)
>>> asked for (glMultiTexCoord1svARB)
>>> asked for (glMultiTexCoord2dARB)
>>> asked for (glMultiTexCoord2dvARB)
>>> asked for (glMultiTexCoord2fARB)
>>> asked for (glMultiTexCoord2fvARB)
>>> asked for (glMultiTexCoord2iARB)
>>> asked for (glMultiTexCoord2ivARB)
>>> asked for (glMultiTexCoord2sARB)
>>> asked for (glMultiTexCoord2svARB)
>>> asked for (glMultiTexCoord3dARB)
>>> asked for (glMultiTexCoord3dvARB)
>>> asked for (glMultiTexCoord3fARB)
>>> asked for (glMultiTexCoord3fvARB)
>>> asked for (glMultiTexCoord3iARB)
>>> asked for (glMultiTexCoord3ivARB)
>>> asked for (glMultiTexCoord3sARB)
>>> asked for (glMultiTexCoord3svARB)
>>> asked for (glMultiTexCoord4dARB)
>>> asked for (glMultiTexCoord4dvARB)
>>> asked for (glMultiTexCoord4fARB)
>>> asked for (glMultiTexCoord4fvARB)
>>> asked for (glMultiTexCoord4iARB)
>>> asked for (glMultiTexCoord4ivARB)
>>> asked for (glMultiTexCoord4sARB)
>>> asked for (glMultiTexCoord4svARB)
>>> asked for (glActiveTextureARB)
>>> asked for (glClientActiveTextureARB)
>>> asked for (glSecondaryColor3bEXT)
>>> asked for (glSecondaryColor3bvEXT)
>>> asked for (glSecondaryColor3dEXT)
>>> asked for (glSecondaryColor3dvEXT)
>>> asked for (glSecondaryColor3fEXT)
>>> asked for (glSecondaryColor3fvEXT)
>>> asked for (glSecondaryColor3iEXT)
>>> asked for (glSecondaryColor3ivEXT)
>>> asked for (glSecondaryColor3sEXT)
>>> asked for (glSecondaryColor3svEXT)
>>> asked for (glSecondaryColor3ubEXT)
>>> asked for (glSecondaryColor3ubvEXT)
>>> asked for (glSecondaryColor3uiEXT)
>>> asked for (glSecondaryColor3uivEXT)
>>> asked for (glSecondaryColor3usEXT)
>>> asked for (glSecondaryColor3usvEXT)
>>> asked for (glSecondaryColorPointerEXT)
>>> asked for (glFogCoorddEXT)
>>> asked for (glFogCoorddvEXT)
>>> asked for (glFogCoordfEXT)
>>> asked for (glFogCoordfvEXT)
>>> asked for (glFogCoordPointerEXT)
>>> asked for (glAreTexturesResidentEXT)
>>> asked for (glBindTextureEXT)
>>> asked for (glDeleteTexturesEXT)
>>> asked for (glGenTexturesEXT)
>>> asked for (glIsTextureEXT)
>>> asked for (glPrioritizeTexturesEXT)
>>> asked for (glCombinerParameterfvNV)
>>> asked for (glCombinerParameterfNV)
>>> asked for (glCombinerParameterivNV)
>>> asked for (glCombinerParameteriNV)
>>> asked for (glCombinerInputNV)
>>> asked for (glCombinerOutputNV)
>>> asked for (glFinalCombinerInputNV)
>>> asked for (glGetCombinerInputParameterfvNV)
>>> asked for (glGetCombinerInputParameterivNV)
>>> asked for (glGetCombinerOutputParameterfvNV)
>>> asked for (glGetCombinerOutputParameterivNV)
>>> asked for (glGetFinalCombinerInputParameterfvNV)
>>> asked for (glGetFinalCombinerInputParameterivNV)
>>> asked for (glBlendColorEXT)
>>> asked for (glCopyTexImage1DEXT)
>>> asked for (glCopyTexImage2DEXT)
>>> asked for (glCopyTexSubImage1DEXT)
>>> asked for (glCopyTexSubImage2DEXT)
>>> asked for (glCopyTexSubImage3DEXT)

(the gfx is not ok with 1.2/1.3 and 1.4 (only with 1.1), but it's an ogl driver issue..)
but my questions are:
Is that list correct/right, does the plugin's ogl mode (for example the 1.1) ask for these extensions??
How many extensions are missed for ogl 1.1 compatible? or, Is there a known extensions list (that the video card's drivers has to support)?

thanks a lot.
 
OP
Rice

Rice

Emulator Developer
I always check all possible ogl extensions supported by the driver and try to use supported extensions. In fact, I call some standard libraries which will try to load all possible extension functions. Of course if an extension is not supported, it won't be used. It should be fine to check them any way even not all extensions will be used.
 

xSpRiGGaNx

Omini Yuu
Combiner Quiry

Yo Rice, Nice Work!

With regard to the combiner options available with DirectX and OpenGL,
Is it better to manually set the combiner type or leave it at its default?

I have a GeForce FX 5700 which incorporates DirectX 9.0b and OpenGL 1.5.
So would it be preferable (under OGL) to leave it as is or set it to something like 1.4?

And with DX, should i use the pixelshader combiner (my card supports 2.0)?

I only want to know what would be the most stable( as some of the combiner settings have given me errors with some games).
 

archanox

New member
Hi there,
Long time reader, First time poster.
Anywho I love what you have done with the texture dumping feature (alot better than using nemu64 to dump by print screening every texture) and also loading your newly created masterpieces.
But question is how do I dump textures from
WCWvs.NWO:World Tour
it cannot create the folder to begin with because of the invalid characters in the foldername.

Thanks a bunch guys (especially Rice for making this awesome plugin!)
 

archanox

New member
Yeah I tried altering the ':' into a '-' but it still wouldnt dump. I think to get it to work rice might have to tinker with his plugin to get invalid characters ommited or something like that.
 

John Doe

New member
Am i wrong or wasn't there any possibility to change the roms internal name? Maybe it could be a solution till rice fix it with a workaround or something...
 
Status
Not open for further replies.

Top