Trouble with Warp3D, can't get it to work properly

  • Thread starter Thread starter samaron
  • Start date Start date
  • Replies Replies 44
  • Views Views 5669
samaron

samaron

Active member
AmiBayer
Joined
Nov 1, 2014
Posts
200
Country
Norway
Region
Rogaland
Hi!

I'm having some issues with my A1200 and getting Warp3D to work properly. Were suggested that I should try here for some advice on the matter.

The A1200 specs:
AmigaOS 3.9 with BB2 and CWB
rev 2B motherboard
Blizzard 1260 @ 50MHz with SCSI kit (192MB RAM total)
FastATA MK-IV
Mediator 1200TX
Voodoo3 3000
Sound Blaster 128
100mbps ethernet card
8GB CF (500MB system partition)
160GB HDD

Got some advice from fitzsteve regarding the drivers. I deleted and copied the correct ones as instructed in this thread: http://eab.abime.net/showpost.php?p=708439&postcount=119 Still, I can't properly run 3D games/programs. If I run the demo programs installed with the Warp3D, the image is really sluggish. The image updates once per second when the gear rotates on the screen. If I try to run Warp3D version of Quake (BlitzQuake) I get an error message, see pictures below. The error message in the shell window appear if I run the glquake file. If I run the other one, Malice, the game starts, but the graphics is just a big mess.




I've run the mediator config tool after copying the new drivers over. Also tried running the game without backdrop, which didn't help either. Does anyone have a suggestion to what I could try next here?


Thanks,
Frank
 
the gears demo will be slow on your system anyway,if it runs it works...

have you tried editing glquake with a text editor?
its set up with a strange screenmode and has to edited to something like 640x480 to output on the voodoo making sure you actually have that mode present,then set uop how much memory for it to use etc.
 
Thanks for the reply. I figured it were working as it were showing the gears, but were unsure if the drivers was correctly installed. If it is supposed to be sluggish on my system, then I guess nothing is wrong regarding Warp3D it self. I'll try editing glquake and have a look in the thread at English Amiga Board.
 
Some older Warp3D ports and demos may work badly or not work at all on Voodoo because developers used the only 3D chip Permedia2 available in that times (many Warp3D demos works only on Permedia2).

On the other hand there are not so many 68k games where Warp3D is supported (I know just Quake, Quake2, Descent, Hexen, Payback and yes Sokoban ;o)
 
Opened glquake with a text editor and couldn't find anything that were off. After some trial and error, I found out the parameter "-ahi" caused the shell error to pop up. Now the game starts and run fine, except it is suffering from the graphic corruption mentioned earlier. Not sure what causes this... From my experience with PC, this does suggest driver error. I double checked the files, but everything is in place. Suggestions? The games are not really playable with the heavy flickering from the graphics going crazy. I know this should work with voodoo3, as I have seen a video on youtube with similar setup and blitzquake.

 
Last edited:
Nice to see you're making progress. The -ahi declaration will use your Sound Card once you've set it up.

As for the glitches, I've seen this when testing on my A4000 with Prometheus PCI:

https://www.youtube.com/watch?v=nHkt2LepFo4

Sorry I did not find a fix, it was just experimental testing.

Try the BlitzQuake from EAB and see if that helps.

Did you try QuakeII yet? I know it will be very slow but it will be interesting to see if you get glitches.
 
Last edited:
The game does glitch like in your video, just a lot worse... :lol: I haven't tried the EAB BlitzQuake, yet. Going to look into that tomorrow. I'll extract and give Quake II a try now. I'm also thinking it might be smart to do a reinstall of the system, start from scratch. Have been installing and experimenting with different drivers and software. Now that I actually have the proper Mediator CD, things should be easier to install and actually work. I'll probably come with an update tomorrow on how things are going. :)
 
Ran the game a little while ago. Wasn't smooth in any way, as expected. But alas, it suffers the same fate as glquake. It does have glitching as well. Before continuing troubleshooting I'll do a reinstall of the system tomorrow. Good thing I backed up a clean CWB install in WinUAE. Now I know how to install and set up a few things, so I hope things will be a bit cleaner than the current install. Hopefully this will solve a few issues, as I've done a few (failed) attempts at getting the mediator stuff working.
 
Reinstalled the system today. The previous installation had a lot of junk as I've done a lot of trial and error with several programs. Now I used a clean CWB OS 3.9 install and installed everything correctly the first time. Still have the same issue with the glitching, though. Sometimes the game will display just fine, and when I move around a little bit it will start glitching again.

As you can see, "Quake II slideshow" is still glitching. Quake does the same thing as well.

 
Tried your solution, fitzsteve. For some reason the mediator will not be detected. Ran the install and config, but still no go. Without that, I really can't test the Warp3D/voodoo3.

I did check elbox.com and saw that they released a new update for the Mediator CD the 10th of January this year. Hoped that would do the trick, but was yet again let down. Still glitching...

I think I have to throw in the towel for today. Need to rest and continue the fight tomorrow. ;)
 
Have done a little bit more testing now. Thought that maybe for some odd reason the card it self is defective. I plugged it into a Windows 98SE computer I have for testing purposes and installed the latest drivers. Played Quake 2 for a while at 800x600, and no issues what so ever. Ran smooth with no glitching. That rules out that theory, that the card it self is the issue.

I then thought, might it be some problem with how it is positioned in the Mediator? The current setup is the Voodoo3 at the bottom PCI, then the fast ethernet NIC and the Sound Blaster 128. I moved the card to the top PCI slot, but then the Amiga refuse to boot into workbench. Does the Mediator have priorities on the PCI slots, that a certain order is preferred? Or is it so that, if it works, it works?
 
Last edited:
its not he card,multiple people have the seen the glitching effect.
 
From my experience with PC, such behavior (glitching) would suggest bad drivers. But again, this is a completely different computer platform. I'm still learning, so please correct me if I'm wrong.
 
Last edited:
i did see this on mine once,cant remember how i got it to go away in the end though.

have you tried reducing the screen size in game? i think you use the - and + keys
 
It's probably an envarc variable causing it, maybe a lack of available vram?
 
You must log in or register to reply here.

Similar threads

J
Help needed with Mediator 4000Di, can't get RTG to work!
Replies
2
Views
4K
keropi
keropi
dougal
I cannot get Rick Dangerous to work properly on my A4000
2
Replies
30
Views
5K
dougal
dougal
H
  • Locked
Found A1200 4MB required for WHDLoad to work properly
Replies
4
Views
2K
AndyLandy
AndyLandy
Back
Top Bottom