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 - osckhar

#1
I reply myselft- no, is not possible.

Oscar.
#2
Hello 3Dfx family,

I have a question- is not possible to install SFFT Tools under Windows 2k? I cant, once installed SFFT Tools the icon will not appear as I should appear using WinXP.

Thanks,
Oscar.
#3
@Glide, I sent you a PM.

Thanks,
Oscar.
#4
Hello Glide,

Thanks for words.

About 64Mb frame buffer support- I need to check it better but I would tell in games as number 2 - draghotic - high detail that need more memory ram available FPS are not double but near.  Using 32Mb 6FPS instead 9FPS using 64Mb.

Similar happens V4 4500 modded 32 @ 64Mb where difference is really few using 64Mb instead 32Mb 3DMark2001 test 1024x768. Only when games need more memory for textures or FSAA is enabled.

Regards,
Oscar.
#5
Hello Glide,

Sorry for long silence. Busy her.

QuoteHi osckhar,

any news?


Yes, very great news here. :)

Check it

Works not stop here antoher amazing progress:

Fixed driver BUG 16Mb instead 32Mb.


Question is if really extra 16Mb is used for Rampage?  8-)

3DMark2001 - Rampage @16Mb


3DMark2001SE - Rampage @32Mb


Even simple view I noticied an amazing extra performance since not jerks for lacking of memory texture.

Note: Scores are little low since I am using my Rampage card with my agp2pci adapter since I found it works better.

Our target IS 64Mb per Rampage Chip and again NOT WORDS. Really Rampage can hadle 64Mb per chip? Yessss!!! [8D]

RAMPAGE DXDIAG TOOL 64Mb


Really extra 32Mb is handled correctly per Rampage?


SUMMARY:
    • RAMPAGE @16Mb - 478Points 3DMark2001SE
    • RAMPAGE @32Mb - 841Points 3DMark2001SE
    • RAMPAGE @64Mb - 911Points 3DMark2001SE


    Regards,
    Oscar.
#6
Hi Glide,

Yupe, I know it just not native Glide driver for Rampage. I must try to find a Glide wrapper and test it though. :)

I keep you informed.

Regards,
Oscar.
#7
Hi,

UT DEMO image quality comparative between D3D and SW render.

UT DEMO
800X600
RAMPAGE #B003




Native D3D looks better but not amazing.

- Oscar
#8
QUAKE 3 - DEMO001
BEST QUALITY NOT POSSIBLY
RAMPAGE #B003
800X600
LIGHTMAP - ON
HW RENDER ON
OpenGL WRAPPER



















Not looks bad. [8D]

Regards,
Oscar.[/orange]
#9
@ALLEN2- no, it is a new architecture nothing to see with VSA-100 family. A card never reached the market. It is a pure prototype stoped when Nvidia 'killed' 3Dfx Inc.
----------

Not a fair comparative for the Rampy but we can check how it perform using an experimental unfinished driver. It needs a lot of work though.

Test done:

    • Abit SA7 PIV@3GHz / DX8.1
    • 3DMark2001SE
    • 800x600 16Bits.
    • Core /Mem @166MHz[/b] (3Dfx tools shows by defect 183MHz on Rampage and lowered to @166MHz as V4 AGP).







    Interesting to see Rampage potential. Only debugging the driver for getting a normal value in single Fill rate texturing. It could get more than 1000MTexel fill rate multi texturing (4 pipe x TMU) but here the king is V5-6000!

    Regards,
    Oscar.
#10

THE LONGEST JOURNEY - D3D


I love how looks the game, especially sea and sky.







Regards,
Oscar.
#11
@Glide, I will try but not sure it can helps since Rampage Chip is based new design/code. Nothing to see with VSA-100 family.

3DMark2001SE - DX8.1

VERY surprised when I saw DOT3 Bump Mapping and Environment Bump Mapping supported via HW. First 3Dfx card handling such tests.  :D























Regards,
Oscar.
#12
Thanks @jix-reggio

Some SShots UT in OpenGL mode with an experimental library. Quality is bad but games works enough fast.  Anyway, it looks as in Software mode though.

NOTE- PICS BELOW ARE NOT IN OPENGL if not in SW MODE

UNREAL TOURNAMENT  - OpenGL











UNREAL TOURNAMENT - DX
- Game locks up  very often. I need to test it much better.





Regards,
Oscar.
#13
Hi Glide!

Yupe, this card is amazing. A dream for a 3Dfx Collector.

Now testing DX SW. Anyway, I will try with the beta openGL.dll and check what happens.

Here news SShots 3DMark2000 - DX7.

Enjoy them!























Regards,
Oscar.
#14
Here the beast!

My Rampage (yupe, I own it :) ) with test socket labeled #B009 with a fully Rampage chip decapped.





I am using an experimental driver sent me a SW engineer worked on Rampage project. It is dated from October 2000.

At the moment driver is only compatible with Win95/98SE/ME and only D3D support. There is an experimental OpenGL.dll but I still did not test it.

Actually using an ABIT SA7 with a PIV3GHZ, Win98SE and DX8.1

3DMark'99 - DX6.1





























More pics very soon!

Regards,
Oscar.
#15
Hi Glide,

All the test are done using WinXP with latest SFFT driver. I mean I never tried SFFT driver under Win 7 or Vista.

Quote
The point is that I'm not sure a PCI-E slot of a 1155 or 1366 mobo at hardware level manages the adapter just like a previous platform. So the crashes could be caused by a power issue.
Sorry I did unterstand you in the previous post.

Not sure if problems comes power issue. I would tell the problem comes in a bug inside SFFT core driver. Since that using same platform with Beta Kool driver all works ok.

Mobo 775 - WinXP - I only have been to able to handle correctly my 6k using SFFT drivers when I use a single PIV. In same system if I plug  a C2D then 6k lock up. I have tested different C2D , e4300, Q6600 or E8400 or other is impossible to get the system runing ok. Anyway, using Beta Kool driver the 6k is ok with C2D systems.

Mobo 1366 or 1155 - WinXP - 6k works perfect using SFFT drivers.

In all the platforms I use: 6k + agp2pci + supermicro pcix2pcie.

Regards,
Oscar.