Notice ~ 

Are you searching for our italian Community  Forumzone.it?
Main Menu
Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - avengerx

#1
Is there a way to accelerate that ugly windows screensavers using the 3d acceleration provided by voodoo3 (maybe replacing the opengl32 driver on windows/system directory by any other?)

ty! :)
#2
I Think I can give an answer for that, as I am from brazil tho. Well, Brazil uses the PAL-M standard for TV-everything. It is a country standard. There are lots of kinds of PAL-Xes. Theres PAL-E, the pure PAL, and Brazil uses PAL-M standard for instance. This way, graphics emitted on PAL-M are b&w for NTSC or just-PAL capable apparatus. What he needs is a PAL-M->NTSC transceiver, and everything would be just nice. In brazil it can be found for R$30,00 (R$ our currency) in 'mercado livre' (www.mercadolivre.com.br).
Mabybe the 'Standard Select' app from ps47 does the conversion from PALM->PAL or PALM-NTSC? One thing again to consider: pal-m is not pal.
#3
I've heard about something like the v3's does a texture compression. That is: it may receive a texture compressed for 16bit and spit out on the screen it decrunched as 32bit texture. That limitation was due to memory and bus timings maybe to enable production of both agp and pci, or maybe agp2x were too slow like pci (uh 400mb/s slug)
#4
Well, I got a v3 3k, and am Enjoying the 1280x1024 views from here. V2 SLI did only 1024x768. Single voodoo: 800x600. I just left a mm sli v2 mix that worked damn cool despite the -25 and -28 memory timing on them (which made sometimes the odd lines look like unsynched with the even ones). But just in some remote situations.
Ah yes, I'm under win98se, using just am2.9 and 3dhqb10 drivers as yet. I'm still making some tests to tweak it to the most like I've done with the v2s (oh they're just sitting there waiting to their day come to be used again). I particularly found lots of improvements from v2 to v3 like the max res, some framerate imp, desktop running better, movies somewhat faster (although vodoomovie did scrap to the movies -- way too blocky. better see them via soft anyway). Ah 2d movies now faster and can be played on any res (w/ sis530 I'd better take screen res to 640x480 or 800x600 16kcolor in order to watch to movies).

But I think my next evil plan is not with software: but hardware. I've already read a 'guide' for overclocking it (sorry I don't remember the link right now, just looked for 'voodoo3 overclock' on google). Now I got a Duron/athlon heatsink w/cooler and a k6/2 'better' heatsing w/out cooler. I mean to put the duron sink to the main processor, and the k6/2 maybe with cooler to the transistor in the upper left corner of the card, which heats way too much (the card is even browny in the surroundings of the transistor!).

About the transistor, I've heard sometimes that the hotter the transistor is, the better, but... Not that hot, right? I hope just a bit cooling wouldn't hit too bad (maybe I use the original voodoo heatsink in the transistor if the k6 does not fit there).

About the main processor.. Please, any hint on how I'd safely take off that glued heatsink from there? May I just pull it over? I've read on the oc' guide that it's better to do when the chip and heatsing are still hot, to imply less fierce to pull the heatsink off the chip. I am afraid I may break the card apart! But i'll cautionously check up what can I do.

Ah, My v3 is just a PCI version. Forgot to mention. This makes it slower don't-know-in-which-part. One particular difference is that the heatsink does not have the nails pressing it against the card.

Other question... Any nice ideas on how to fix the duron heatsink to the main v3 processor? I don't think the presils that come w/ the heatsink will help a thing I'd supposedly have to take them off to prevent them from bugging me :). Thanks everyone! :)
#5
When u use voodoo2 oc, and set the gauge to 97MHz, are you changing BOTH sli cards to 97, or there's some trick to assure both cards are in the same clock rate?
#6
Voodoo2 Setup and tweaking / voodoo2 and dx9
02 February 2005, 19:05:09
I think that using 3dfx ref drivers would help you less than fv2 drivers. d3d games will still work on dx9 although you can't use dxdiag to see if d3d is working. I am -not- sure, but I think that if a game requires dx8.1 or older, it will work fine even if you have dx9 installed. the problem could raise if you play a game that uses dx9 functions. In other words, downgrading to dx8.1 will not change things other than being able to see that spinning cube on dxdiag's test.

also, seems that 3dfx ref drivers support only ~dx6... fv2 goes up to dx8.1.
#7
I got my v2 working with doomsday. Sorry for the delay to posting the notice here, I shall share the news for whose try to run too!..

Well, What I've done, is dig up the internet to the latest possible v2 drivers for both glide and d3d, supporting MM SLI. The D3D part which comes with FV2 4.5 (at least for win9x) are ok. But the glide, are for non MM-SLI setups. So I got the drivers from the site of a man I think that work[ed] for metabyte, which made drivers for v2 MM sli with glide support. Also, I used wicked GL driver with doomsday. I got the 'normal' driver from the folder of wicked, and put into doomsday's bin/ folder named opengl32.dll. All worked fine. Here attached are the glide drivers (there's D3D also in the .zip, but they seem older than FV2 4.5 files), so copy only the glide files and not the 3dfx32-blah-blah file. If things are getting harder, ask me for packaging my dll's (I have them sepparate in a dir here), so you can install FV2 4.5 and overwrite the files on your windows/system directory.
Also, I took care in keeping the DirectX version at 8.1. DX9 have a lot of issues even with not-3dfx cards, and must be installed only when you find a game that requires it. Anyway, I don't think that a game which requires dx9 will be compatible with fv2 4.5 d3d drivers.

Perhaps the files I am offerring here are interesting to be inside the pack of a newer release of fv2 4.x -- remember i'm under win9x, no guarantee if this works under winXP.

Ah! Doomsday worked also with MESAFX glide driver, but there's some things missing... Interesting how different glide drivers change things...

Download Attachment: best-mismatched-sli-win9x-v30202-files.zip
358.13 KB
#8
Games / Soul Reaver 2 × voodoo2
02 February 2005, 18:20:54
NightBird, I can u/l it somewhere and send u. if u interest, send me a mail and i'll answer with the link for the iso img.[:p]

But, you played it using the voodoo2 adapter?.. i was really unable to even get video with voodoo2. I was able to 'see' the game only when used with my sis530 poor 3D emulated thing -- and slowly. With voodoo2 all I get is audio. Under settings, when I choose the 3dfxzone.it driver, it gives me no resolutions on the drop-down box... I'm sure that if it works with voodoo2 it would be a weird lot faster than with sis530. [^]
#9
Voodoo2 Discussions / Voodoo2 & DivX
20 January 2005, 23:36:11
In my setup (v2 sli MM), the movie goes better in my onboard card than in the v2... Theres way too much lag between the frames, and the movie plays almost like a slideshow.
I'm using VoodooMovie (full, I guess) v2.1, w/ glide3x 3.03.00.670 (proper to v2 SLI MM)
Lowering resolution gives a bit of framerate, but still unplayable.
I'm using DivX 5.11, and under SiS530 the movie goes very fair (not perfect, but what can I expect from a K6/2 550 w/64Mo?).
Next step would be to give a try on the FFDSHOW package. What does that SSE/SSE2 optimization mean? I mean, would I use that optimizations if I use this in such a system like mine?..
#10
Games / Soul Reaver 2 × voodoo2
20 January 2005, 16:56:53
Wonder that... I can enter (and play) the game using my onboard SiS 530 video card, although I have 64Mb of phys ram and a 550 K6/2. Despite it runs, thigs goes really slow with such a "3D" card. [B)]
The problem is that when I choose Fastvoodoo2's, no video modes become available on the setup dialog of the game (sr2.exe -setup). I can't even try to just change the registry to fit any res. It would cleanse up right when I open the game (it should do some tests).[}:)]

Any Idea on what could prevent d3d games from showing resolutions for a v2? (it's a mm sli v2, and runs other games well on d3d).

Nightbirt: How would I be able to check which texture size does a game use?.. The site's infos doesn't seem to explain that detail.
#11
It put things to work under Open GL. But, unfortunately, there seems to have too much texture corruptions... But I'm not sure that it could be the game I was trying to play or the glide driver... I'll try some most classical GL game like GL Quake....
Have you ever tried doomsday in opengl mode with a more 'normal' voodoo2 schema?.. I'm getting great texture problems with it... Other GL dooms also gave me troubles... But I'm still trying things, and will see if the problem is with the game or the engine.
#12
After some hours of googling, I finally found the fate towards my sought. Thanks also to Manuelson, without his idea i'll never look for this fix!

http://home.earthlink.net/~aosnovich

Thanks to Andrei Osnovich for making opengl drivers for v2 sli MM, and even with 3dnow! instructions (dunno it would work on intel archs due to this).
Here's a short howto to make everything work (w9x series):

. Install FastVoodoo 4.6 (which comes w/ d3d sliMM support), as normal, to both cards (remember sweeping out last installation before this, if tis the case).
. Get http://home.earthlink.net/~aosnovich/mismatch.zip from this site above.
. Decompress it to a folder and copy only glide2x.dll, glide3x.dll to windows/system directory.
. It will allow you to use your windows/system/3dfxvgl.dll as your opengl32.dll file on the games (copy it into game's dir and rename to opengl32.dll).

 You'd better not copy all files from the zip file into windows/system directory, there's a 3dfx32v2.dll that's the D3D portion of the SLI MM for the v2, and this is already fine and well worked (and up to date) by the fv2 4.6 team!..
 These glide drivers are based on 2.54 version, and fv2 4.6 comes with 2.56. Although newer, they are not patched for support v2 SLI MM, then we should only expect for updated glide drivers adhept of SLI MM support.

I hope this helps everyone who may enter in the same dillema like me, and I also hope this kind of glide drivers could be shipped with a future fasvoodoo2 package! :)

This attach is just for security purposes, it's the http://home.earthlink.net/~aosnovich/mismatch.zip file. Who knows if that page could be off tomorrow or so?

Download Attachment: mismatched-glide2x3x.zip
474.5 KB
#13
Is there any intent of applying drivers for glide support on SLI MM schema with fastvoodoo2 package? :)
#14
I'm using 93MHz on both cards cause i've seen somewhere that anything greater than this will need additional cooling, and I don't have even space for cooling (even with bare heat dissipators). But I've didn't notice that both are at the same clock, once the properties tab have only gauges for one card... I assumed it clocked both the cards... so, do I have to do something to assure that both are at same clock?
#15
uh... it pains to know that... Is there chances of being developed, as done for D3D, such opengl drivers?.. There's not so much sense on using a voodoo2 not for glide although there are quite a number of games which works very well w/ it... But even some games that support d3d, if they also support gl, the preference for 3dfx cards is to use glide. :[

would that be a chance of future gl drivers for mm v2? :/

Anyway, now I know what to search in order to put things to work. Thanks!