Trouble with Warp3D, can't get it to work properly
- Thread starter samaron
- Start date
- Replies 44
- Views 5669
Try to launch the game from a lower colour and resolution to free up some. Also when you run the mediator configuration program you set a memory size but I can't remember the exact settings that worked. Try to look at the settings defined within the text files of my image I sent you and duplicate them as this setup definitely worked. Failing that try the voodoo in another slot, I always used the top slot for voodoo and 4th one down for sound card. I had the 6 slot mediator sx.
Last edited:
Allright, I'll do some more testing. Going to try out the different things suggested. Tried moving the voodoo card to the top slot, but that didn't work well. The computer refuse to start the workbench then for some reason. Even if I set it to a native mode before doing so. Worst case I'll set it up from scratch again with the clean CWB install. If that fail, I'll try a clean OS 3.9 without CWB.
Have tinkered with the different settings for a few hours now. Lost count on how many times I've rebooted the system... I tried the settings from your system files, fitzsteve. Didn't help I'm afraid. I tried setting low vram, high vram, nothing made a difference. Tried different options for glquake, low resolution, high resolution, colors, etc. Also tried smaller screen size in-game. Nothing made a difference. I came a cross a note in the documentation for the game saying that if the user experience high amounts of graphical corruption, try setting the Mediator jumper "Wait" as closed. Did that, but then the system would just freeze after booting into workbench.
I did however notice something. When running the Mediator configuration, if I selected "No" for MMU, then the workbench were smoother in a way. The text under the icons didn't appear rough and the shadow on the menu when right-clicking didn't have color speckles anymore. Quake didn't run when this was selected, of course. Just got a white screen that had slight flashing/flickering.
Still haven't tried a clean OS 3.9 install. Have some minor issues getting that working on my Amiga. Hopefully I'll sort that out tomorrow.
I did however notice something. When running the Mediator configuration, if I selected "No" for MMU, then the workbench were smoother in a way. The text under the icons didn't appear rough and the shadow on the menu when right-clicking didn't have color speckles anymore. Quake didn't run when this was selected, of course. Just got a white screen that had slight flashing/flickering.
Still haven't tried a clean OS 3.9 install. Have some minor issues getting that working on my Amiga. Hopefully I'll sort that out tomorrow.
I just took a picture of the screen, hope that was okay. I installed picasso96 2.1b as per instructions found on the mediator CD. Renamed the driver file CVision3D to voodoo, as you can see. Also included a picture showing what I meant with the text below the icons being rough when selected "Yes" for MMU during the configuration.
Last edited:
Copied over a fresh CWB OS 3.9 install to my CF card and tried your files. Picasso96 were missing the install script, but saw in one of the files that it were version 2.0, so I downloaded that from Aminet. Another issue were the Mediator setup. It doesn't detect my board, since it is newer. The install CD is only for SX and not TX. I just went ahead with my CD for the TX board and P96 2.0 instead of 2.1b that I used earlier. Still the same result in the end, glitching. 
Yes, I expected the setup to be challenging, but now this much trouble. I'll try contacting Elbox. I'm on the lookout for a PPC card, maybe I should put this on hold until I get that card. Not sure if it should make any difference, but worth a try before putting more effort into the matter I guess.
Hehe, going to get a PPC anyway. This is obviously some sort of software issue, so it shouldn't be impossible to figure out. No pain, no gain. 
I'll have to sit down and think a little about the situation and try out some more things. Have to look through everything and see if I can find anything else to configure. Could any of the software included in CWB cause issues like this?
I'll have to sit down and think a little about the situation and try out some more things. Have to look through everything and see if I can find anything else to configure. Could any of the software included in CWB cause issues like this?
its probably worth noting i had seen the glitching effect on older software...
i dont use cwb installs,and i use the older drivers and it was there still.
like i said,i cant remember what i did to fix it...
i dont use cwb installs,and i use the older drivers and it was there still.
like i said,i cant remember what i did to fix it...
I installed a clean OS 3.9 installation now with BB1 & BB2 applied. Sad to say it didn't help, were greeted with a nice glitching screen when I started quake. Going to try something else tomorrow. Thought I could try to replace the driver files with the ones from an older MMCD.
Last edited:
Did some more testing today. Read somewhere about something called Wazp3D, which is a replacement library file for Warp3D. Thought that could be worth a try, but didn't help at all. 3D software ran really slow, even slower than Quake II. The picture updated once a minute or something like that.
I also tried to copy the driver files from your system files, fitzsteve. Can report that wasn't a sucess either. I also looked further into the parameters for glquake, and added "-litfiles -lm_RGBA", didn't work... or sort of. If I quit the game and started it again, the glitching would to some degree disappear. The flickering would go away, but the textures in the game would have colored lines in them, making it look sort of weird.
I am also going to write elbox an e-mail regarding the issue. Not sure how much they can help, though. Worth a try anyway. I'll report back if I get an answer or try out something else.
I also tried to copy the driver files from your system files, fitzsteve. Can report that wasn't a sucess either. I also looked further into the parameters for glquake, and added "-litfiles -lm_RGBA", didn't work... or sort of. If I quit the game and started it again, the glitching would to some degree disappear. The flickering would go away, but the textures in the game would have colored lines in them, making it look sort of weird.
I am also going to write elbox an e-mail regarding the issue. Not sure how much they can help, though. Worth a try anyway. I'll report back if I get an answer or try out something else.
Tried some more today. I installed an updated version of picasso96 that I found, version 2.1e is it called. It contains updated drivers. I installed it and now the file names under the icons on the workbench doesn't have graphics corruption any more. But it didn't fix the glitching issue with Quake. I also tinkered with the picasso96 settings for my screen resolution options. I changed it from True Color to True Color & Alpha. I also installed Mediator CD update 2.5 and HSMathLibs. It really gave a boost to the gears demo, whuch runs a lot smoother now. If I start Quake after I reboot the computer, it doesn't glitch like crazy anymore, but the textures in the game have really funky colors. The menu and console screen have colored lines. If I close the game and start it up again, the colors will be correct, but it glitches. Quite strange...
Uploaded a short video showing what's happening with the graphics: www.youtube.com/watch?v=UBhYvtWoGbk
I also sent elbox an e-mail today. Hopefully they can provide an answer.
I also sent elbox an e-mail today. Hopefully they can provide an answer.
Last edited:
