Hello!

Ok, right to the topic:

I guess, SFFT driver development is being documented, just as any major software project.

Would it be possible to post release notes for every new alpha release? It would make the driver testing process a lot easier, 'cause then you really know what to look for. Otherwise, a tester gotta test his whole array of games every time and check for old and new bugs, which is rather not optimal.

So, Release Notes documenting any bugfixes or new features publically would make things a lot easier, and may even speed up development due to faster and more precise feedback.

Thank you very much.

Greetings!

I recently switched my v5 6000 Box to Win2000 to try the newer AmigaMerlin 3.1 drivers. They really got a lot of stuff working, that the older AmigaMerlin 2.9 on Win98 wouldn't do.

I got stuck however with a rather annoying bug: The well-known 60Hz Bug, that affects D3D, OGL and Glide. I already tried ReForce, V5 Frequency Selector, and i tried to modify the refresh registry entries all by myself, to no avail.

I went to...
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{<My Monitor Device Group ID>}\<Active Monitor Number>\Modes\1024,768\
...and tried to set the minimum vertical refresh rate to 85Hz for 1024x768, the resolution i'd like to use currently. I even modfied the minimum horizontal refresh rate to 96kHz, but it just doesn't help a bit. The modified entry looks like this: 96-254.0,85.0-85.0,+,+, where 96 is the minimum horizontal refresh rate in kHz (default 2.0) and the first 85.0 should be the minimal vertical refresh rate in Hz (default 60.0).

To be absolutely sure, i even applied my changes to all inactive monitors, didn't do anything either. I just can't get past 60Hz in Win2000, i also tried to reinstall the drivers several times.

v5 Freq Selector and ReForce have been tried several times after fresh driver installations too: No effect. As always, help is greatly appreciated... Staying at 60Hz vertical refresh rate just isn't an option.

Thanks very much in advance!

Update:
Tried V.Control now, since V.Control is supposed to overwrite the registry settings and apply changes by direct HW access. With the MS Windows Plug & Play monitor driver, i cannot select a single resolution in V.Control.

I can select a few very high res though when using the original driver for my monitor (Sony GDM-F520). I however cannot access lower resolutions like 1024x768 for instance.

See:

Greetings!

I have a major Problem using Games with K.R.A.S.S. Engine on my 6000. I tried AmigaMerlin 2.9 in Win9x and 3.0 XP in 2000, same problem. The K.R.A.S.S. games say, they cannot find the target resolution. Doesn't seem to have anything to do with desktop resolution and/or color depth however.

Spellforce works, initializing 1152x864, but as soon as i try to change the res, it does the same as AquaNox, giving me this ominous error message and telling me to install the latest 3dfx drivers. Spellforce however only works within the menu, when starting a campaign, the game crashes.

Now i DO know, that K.R.A.S.S. works on v5 5500 cards - so it should go well with the 6000, which it unfortunately does not.

Any suggestions? I'd love to see K.R.A.S.S. powered games come to life on my Rev.3400-A3. Thanks!

Recently i compared the performance of "Sacred" between a v5 5500 and v5 6000, and the 6000 is able to display the minimap, and to support smooth gameplay at full zoom level while not within a city. The 5500 was extremely sluggish here, looked like it didn't have enough texture memory left to support the game at maximum zoom.

My idea: Couldn't FXT1 be forced in Direct3D? That would GREATLY help with a few newer games that make use of rather large textures. Maybe games like sacred could be played smoothly with FXT1 forced, and even 2xFSAA might get possible.

On top of that, it'll not only do a lot for v5 6000 owners, but also for those 5500 cards.

Is this possible?

Greetings!

I'll start right away:
"Memmap returned an error trying to map memory!"

I guess, some Voodoo²(SLI) users know that line all too well, and so do i. I encountered the bug when plugging my Quantum3D Obsidian2 X-24 into my P4 Box (Abit TH7-II RAID, 256MB RDRAM, 1.6A), and it's not limited to that card! I also tried a single 12MB Monster3D II. The symptoms may vary depending on what driver you use, but there is one symptom, that always shows up: Glide and OGL will not initialize regularily or at all!

I searched the web and found evidence, that Voodoo² cards generally just have some MAJOR problems with more modern systems. The card just won't initialize, but it will, however, be listed in the device manager without problems. There are two threads in here, that describe the same problem.

I found out, that the card would initialize every 50-80 tries, and if it DOES, everything runs fine (Diablo II, UT,...). The instability could also be linked to system speed, but i can't confirm that yet.

I would suggest to take a look into this matter and try to fix the problem in an upcoming FastVoodoo2 driver release, if this can be resolved by a software-side approach. Because the current drivers seem not to address this bug, and it's clearly a major one. The issue seems to be limited to NT5x operating systems by the way, so it does not show up in Win95/B/C or Win98/SE.

If you decide to do something about this issue, your effort would be greatly appreciated!

Thanks.

Just thought you might be interested in those...

SET SSTV2_SLIM_VIN_CLKDEL="0"
SET SSTV2_SLIM_VOUT_CLKDEL="0"
SET SSTV2_SLIS_VIN_CLKDEL="0"
SET SSTV2_SLIS_VOUT_CLKDEL="0"

Voodoo²SLI Master/Slave Latencies. I could set them to "0" on my Quantum3D Obsidian2 X-24 without problems and to "2" or "3" on normal SLI Systems. Default is "6" or even higher as far as i know. This resulted in a few extra fps for me...

Currently my v5 6000 card is on it's way to Hank and he'll take a look at it (HiNT Bridge blown - maybe more...).

Meanwhile i would like to ask which mainboards are optimal for a v5 6000. I would like to use an Intel Chipset, Slot-1 or Socket370. Hank told me, that the PCI Bus behind the HiNT HB1-SE66 won't tolerate too much Overclocking, so i cannot use my i440BX Boards (2/3 AGP multiplier) in combination with Tualatin P-III S Processors...  (AK4 - AG1 mod to run on older GTL+ Chipsets with 1.5VTT).

I don't really want to use i815EP, so i'd like to try i820 Camino (pure Rambus - no MTH, 1/2 AGP multiplier). Does anybody here have any experiences with Intel based Mainboards + v5 6000 or v5 6000 AGP OC?

Thanks in advance.